2 3JK10864AAAAWBZZA Radio Resource Management

Section 1 Module 2 Page 1
All Rights Reserved Alcatel-Lucent 2008

3JK10864AAAAWBZZA Issue 02
Do not delete this graphic elements in here:
12
Module 2
Radio Resource management
Section 1
Radio Algorithms
EVOLIUM
E-GPRS Radio Algorithms and Parameters Description B10
3FL11830ACAAWBZZA2 Issue 02
EVOLIUM E-GPRS Radio Algorithms and Parameters Description B10
Radio Algorithms Radio Resource management
1 2 2
Blank Page
This page is left blank intentionally
First edition Last name, first name YYYY-MM-DD 01
Remarks Author Date Edition
Document History
1 2 3
Module Objectives
Upon completion of this module, you should be able to:
Describe the algorithms of Resource Management and the related parameters
1 2 4
Module Objectives [cont.]
This page is left blank intentionally
1 2 5
Table of Contents
Switch to notes view!
Page
1 (E)GPRS Channels 7
2 Autonomous Packet Resource Allocation 22
3 TBF Radio Resources Allocation and Re-Allocation 57
4 TBF Release Routine 78
1 2 6
Table of Contents [cont.]
Switch to notes view!
Page
1 2 7
1 (E)GPRS Channels
1 2 8
1 (E)GPRS Channels
Overview
PDCH Slave PDCH
PTCCH
PDTCH
PACCH
PTCH
physical channel
control channel
traffic channel
signaling associated control channel
logical channel category
logical channel
1 2 9
1 (E)GPRS Channels
GPRS Physical Channel, PDCH
0 7 0 7 0 7
1 TDMA frame = 4.615 ms
0 1 2 49 50 51
The 52-multiframe= 240 ms
X X Block
Frame
0 4 8 1213 17 21 25 26 30 34 3839 43 47 51
PTCCH
B0 B1 B2 B3 B4 B5 B9 B10 B11 B6 B7 B8
Packet Data Channel (PDCH): a physical channel which carries GPRS
logical channels
PDCH frame:
Made up of 52 TSs of the same rank belonging to 52 consecutive TDMA frames.
The 52 TSs are divided into blocks of 4 consecutive TSs.
12 blocks are created and 4 single TSs:
TS12 and TS38 for the Timing Advance,
TS25 and TS51 are pseudo Idle TS for transmission purposes (synchronization with the occurrences of
SACCH on the GSM 26-multiframe).
According to the PDCH design, a maximum of 8 PDCHs can be created with one TRX.
A PDCH can be entirely allocated to a single user, which is close to the principle of circuit in GSM.
1 2 10
1 (E)GPRS Channels
GPRS Physical Channel, PDCH [cont.]
1 RLC PDU uses 1 PDCH block
Except in MCS-7 to MCS-9 where 2 RLC PDUs use 1 PDCH block
2 kinds of physical channel PDCH
master PDCH (MPDCH)
A PDCH which carries the PCCCH and PBCCH logical channels
For signaling purpose
slave PDCH (SPDCH)
A PDCH which carries PTCH logical channels
For traffic purpose
The MPDCH has been introduced with the B7 release (details are given in the annex).
The use of GSM CCCH for the GPRS traffic offer can lead to QoS problem in GSM (PCH use more specifically).
1 2 11
1 (E)GPRS Channels
(E)GPRS Logical Channels
Different GPRS logical channels mapped on PDCH, which are shared on
a block basis:
PTCH: PDTCH and PACCH
Packet Timing advance Control Channel (PTCCH)
1 2 12
1 (E)GPRS Channels
(E)GPRS Logical Channels [cont.]
Packet Traffic Channel (PTCH):
used for user data and associated signaling transmission
Packet Data Traffic Channel (PDTCH):
unidirectional channel used for user data transmission
mapped on one PDCH
up to 8 PDTCHs may be allocated to an MS on different PDCHs with the same
frequency parameters
Issue: the network shall control the multiplexing of several users on a unique UL PDCH avoiding collision
occurrence. This is achieved by the RLC/MAC functions and the use of USF, RRBP and TFI fields of the
RLC/MAC header.
The number of PDTCHs allocated to one MS belongs to:
The MS capabilities (multislot class),
The traffic in the BSS,
Operator configuration of the BSS parameters.
NB: max number of PDTCHs to one MS = 8 because the MS has to be allocated TSs on a unique TRX, and one
TRX can support 8 PDCHs max.
1 2 13
1 (E)GPRS Channels
Packet Traffic Channel (PTCH):
Packet Associated Control Channel (PACCH):
A bidirectional channel used to transmit control and acknowledgement messages
Mapped on one PDCH:
if a single PDTCH is allocated to an MS, the PACCH is allocated on the PDCH carrying the PDTCH
if multiple PDTCHs are allocated to an MS, the PACCH is allocated on one of the PDCH carrying
the PDTCHs (Alcatel BSS)
Caution: PACCH blocks are used to carry the BSS signaling but not the GSS signaling.
The scheduling of PACCH blocks in the UL and the DL is monitored by the MFS. The most frequent use of the
PACCH blocks is for Packet Ack/Nack messages.
It can be used as well for CS Paging message when Master Channels are not available.
It is necessary for the MS to update the PSI13 on a regular basis in order to achieve proper RLSs and Power
Control mechanisms. The PSI13 content can be sent to the MS in Packet Transfer Mode via a PACCH.
1 2 14
1 (E)GPRS Channels
Packet Timing advance Control Channel (PTCCH):
bidirectional channel (DL: TA messages; UL: Access Burst for TA calculation)
used by the continuous timing advance mechanism
the PTCCH of one MS is carried by the PDCH carrying the PACCH
Timing Advance Index (TAI), used for the scheduling of the AB, is part of the
radio resources allocated to an MS.
The TAI is a PDCH parameter
The TAI takes 16 values
MFS
A
c
c
e
s
s
B
u
r
s
t
T
A
M
e
s
s
a
g
e
The Access Burst in the UL and the Timing Advance Messages in the DL are scheduled in time manner on TS12
and TS38.
The TAI is part of the GPRS radio resources allocated by the MFS to the MS. Each mobile needs to have a TAI.
The TAI range value is a limitation to MS multiplexing on a same TS, as both MS in the UL transfer and MS in
the DL transfer send their AB in the UL and receive their TA value in the DL.
16 values for TAI means that each MS sends an AB every 1.96 s, when the content of the TA Messages is
updated every 480 ms (every 4 occurrences of TAM).
Idem TAM 1 12 N+2 4
idem TAM 4 38 N+7 15
TAM 0 38 N+1 3
TAM 0 12 N+1 2
TAM 0 38 N 1
4 repetitions of the 16
TA values (4 TA
values updated)
TAM 0 12 N 0
TA Message
On PTCCH TS
number
A.B. scheduled for MF-
51
TAI value
1 2 15
1 (E)GPRS Channels
Multiplexing of (E)GPRS Logical Channels
Temporary Block Flow (TBF): a unidirectional flow of data between the
MS and the MFS for the transfer of one or more LLC PDUs (refer to GSM
04.60)
Several TBFs can be transmitted on one PDCH (TFI 5)
One TBF can be served on several PDCHs (TFI 17 & 24)
A TBF is identified by a Temporary Flow Identity (TFI)
PDCH 1
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 2
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
PDCH 3
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11
TBF with TFI = 5 TBF with TFI = 17 TBF with TFI = 24
Temporary Flow Identity (TFI): Each TBF is assigned a TFI by the MFS.
Important: It is possible to establish 32 TBFs per TRX.
TBF: 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.
There is still a 3 RTS shift between Rx and Tx, on the TDMA frame.
1 2 16
Downlink PDTCH and PACCH blocks multiplexing
Uplink PDTCH and PACCH for a UL TBF multiplexing
1 (E)GPRS Channels
Multiplexing of (E)GPRS Logical Channels [cont.]
PDTCH
T
F
I
2
4
U
S
F
=
5
PDTCH
T
F
I
1
7
PACCH
T
F
I
2
4
T
F
I
U
L
PDTCH
/
PACCH
+1
DL PDCH N2
UL PDCH N2
Downlink PDTCH and PACCH blocks multiplexing:
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, an 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.
This is the principle of the Dynamic Allocation, which allows a maximum of two TSs in Uplink
NB: the values of the USF are entirely dedicated to PDTCH and PACCH transfers. See further (MPDCH and
RRBP)
The TFI is used 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 2 17
1 (E)GPRS Channels
Multiplexing of (E)GPRS Logical Channels [cont.]
Uplink PACCH for a DL TBF scheduling:
S
/
P
f
a
l
s
e
PDTCH
T
F
I
2
4
Packet DL
Ack/NAck
message
PACCH
T
F
I
2
4
U
S
F
=
0
0
0
PACCH
T
F
I
X
X
U
S
F
=
5
PDTCH
T
F
I
1
7
RRBP = +3
T
F
I
U
L
PDTCH
/
PACCH
DL PDCH N2
UL PDCH N2
Exercise
RRBP: Relative Radio Block Period
Allocation of a PACCH block for the sending of acknowledgements in the UL of blocks received in the DL:
The MS has no USF because it is involved in a DL TBF
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 an RLC/LAC block is checked each time by the MS whose TFI
is written in the RLC header.
When S/P is false, no UL PACCH is scheduled.
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 the MS has to send an acknowledgement message to the MFS.
1 2 18
1 (E)GPRS Channels
Extended Dynamic Allocation
B10
EDA allows higher throughput in uplink through the support of more
than two TSs
Principles
Same basic principles as Dynamic Allocation (i.e. based on USF)
Differences
A mobile station detecting its assigned USF value on one assigned PDCH is
allowed to transmit on that PDCH and all higher numbered assigned PDCHs
The mobile station needs not to monitor all the downlink PDCH corresponding to
its uplink PDCH allocated
B10 MR2
The EDA feature is optional
for the network.
1 2 19
1 (E)GPRS Channels
Extended Dynamic Allocation [cont.]
B10
USF scheduling for
EDA mode:
DL TS0 TS1 TS2 TS3
BP n
UL TS0 TS1 TS2 TS3
DL TS0 TS1 TS2 TS3
BP n+1
UL TS0 TS1 TS2 TS3
DL TS0 TS1 TS2 TS3
BP n+2
UL TS0 TS1 TS2 TS3
DL TS0 TS1 TS2 TS3
BP n+3
UL TS0 TS1 TS2 TS3
DL TS0 TS1 TS2 TS3
BP n+4
UL TS0 TS1 TS2 TS3
DL TS0 TS1 TS2 TS3
BP n+5
UL TS0 TS1 TS2 TS3
1 2 20
1 (E)GPRS Channels
Extended Dynamic Allocation Usage [cont.]
B10
Uplink Throughput increase:
Class 11 (2+3):
0 1 2 3 4 5 6 7
UL
0 1 2 3 4 5 6 7
Ttb Tra
DL
Tx Tx Tx
Rx Rx Mx
Class 12 (1+4):
0 1 2 3 4 5 6 7
UL
0 1 2 3 4 5 6 7
Tta Trb
DL
Tx Tx Tx
Mx Rx
Tx
1 2 21
1 (E)GPRS Channels
Extended Dynamic Allocation Usage [cont.]
B10
EN_EDA: disabled (default Alcatel value).
Changeable at OMC-R on Cell level
EDA_MS_ACTIVATION_LEVEL: activation level
Gives an artificial mean to limit the activation domain (inter-operability
issues)
Possibility is given by the parameter ALLOW_DTM_EDA_COMBINATION
to allow DTM and EDA combination
(i.e. support of 2+3 configuration for DTM multislot class 11)
EDA_MS_ACTIVATION_LEVEL and ALLOW_DTM_EDA_COMBINATION are relevant if EN_EDA = 1.
EDA_MS_ACTIVATION_LEVEL=0 (Alcatel default value) and it can be set at the OMC-R (BSS Level)
ALLOW_DTM_EDA_COMBINATION = 0 (Alcatel default value) and it can be set at the OMC-R ( BSS Level)
Note : none of the combination of the three paramters allows activating EDA only in case of DTM
operations
The Ms is supporting EDA mode depending on the following PCC flag:
EDA_Allowed_GPRS (respectively EDA_Allowed_EGRPS) which is set to true if:
The cell belongs to an Evolium BTS
The cell is not an extend cell
EN_EDA parameter is activated
EDA is supported by the MS in GPRS (respectively EGPRS)
EDA is enabled in the BSS ( EDA_MS_ACTIVATION_LEVEL parameter)
The N_UL_BIAS_FOR_EDA last observed biases since the transfer start are uplink
There is no RT PFC associated to the MS
1 2 22
2 Autonomous Packet Resource
Allocation
1 2 23
2 Autonomous Packet Resource Allocation
Definitions: SPDCH Group
SPDCH group = time slots usable for PS traffic
Only 1 SPDCH group per TRX
contains TS
belonging to the same TRX
having the same frequency configuration
without hole
MPDCHs are not part of the SPDCH group
Up to 16 PDCH groups per cell
A TRX is PS/CS capable only if TRX_PREF_MARK = 0
TRX_PREF_MARK <> 0 then the TRX is only CS capable
Any TRX should possibly support one SPDCH group except for one case: Concentric cell or multi-band cell
design, an SPDCH group can NOT belong to the inner zone.
An SPDCH group can be supported by both hopping and non-hopping TRXs.
Only one Mobile Allocation (MA) is supported in a cell.
1 2 24
Definitions: SPDCH Group [cont.]
Example: BBH is used, NB_TS_MPDCH=0
0 1 2 3 4 5 6 7
TRX1
TRX2
TRX3
BCCH SDCCH
SDCCH
TRX4
TRX_PREF_MARK
0
1
0
1
SPDCH group1
SPDCH group2
SPDCH group3
SPDCH group4
SPDCH group2 Null
SPDCH group4 Null
CAUTION: animated slide.
1 2 25
Definitions: 8-PSK High Power Capability
GMSK
constant envelope
(amplitude) modulation
one bit per modulated
symbol over the radio path
8-PSK
Envelope modulation not
constant
3 bits per modulated
symbol over the radio path dB
(147 bits)
P
N
0
-20
dB
t
(147 bits)
542.8 0s
P
N
dB
t
(147 bits)
542.8 0s
P
N
Q
I
1,1,
1
0,1,
1
0,1,
0
0,0,
0
0,0,
1
1,0,
1
1,0,
0
1,1,
0
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.25 symbol periods. A normal burst has a duration of 3/5.2 seconds (577 Ts). (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.25 bits (6 tail bits + 26 training sequence bits + 116 encrypted bits + 8.25 guard
period (bits)).
Modulation gross bit rate = (156.25 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.25 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.
Amplitude varies constant Carrier envelope
EGPRS GPRS / EGPRS Packet radio service
810 Kbit/s 270 Kbit/s Gross bit rate per carrier
200 KHz 200 KHz Channel spacing
Phase modulation Frequency modulation Modulation type
8-PSK GMSK
1 2 26
Definitions: 8-PSK High Power Capability [cont.]
G4 TRE characteristics
30 W
44,77 dBm
25 W
43,98
dBm
30 W
44,77 dBm
12 W
40,79 dBm
30 W
44,77 dBm
25 W
43,98 dBm
30 W
44,77 dBm
15 W
41,76 dBm
8-PSK
output
power
60 W
47,78 dBm
35 W
45,44 dBm
60 W
47,78 dBm
45 W
46,53 dBm
GMSK output
power
1800 900
Frequency
band
High power Medium power High power Medium power Type
TADHE
EDGE+
TADH TRADE
EDGE+
TRAD TAGHE
EDGE+
TAGH TRAGE
EDGE+
TRAG
G3 TREs are not able to handle the 8-PSK modulation. Only G4 TREs (also called TRA) are EDGE capable.
The TRA sensitivity is as follows:
GMSK: - 111 dBm.
8-PSK: - 108 dBm for MCS5, - 99 dBm for MCS9.
1 2 27
Definitions: 8-PSK High Power Capability [cont.]
The GMSK output power is:
The minimum value among the maximum TRE output power in:
One cell
One frequency band
The maximum output power in the cell
The 8-PSK output power
Is given for one TRE by the modulation_delta_power
= [Maximum output power in the cell] [8-PSK TRE output power]
And a possible attenuation, in order not to exceed the GMSK power in the
cell (case of BS_TXPWR_MAX <> 0 dB)
8-PSK High Power Capability
G4 HP TRE if the modulation_delta_power < 3dB
G4 MP TRE if the modulation_delta_power > 3dB
The 8-PSK High Power Capability is used in the TRX ranking process
CAUTION: do not confuse MP and HP given as a TRE hardware characteristic and MP and HP defined
by the 8-PSK High Power Capability.
The first ones represent the maximum power a TRE can transmit (in GMSK or 8-PSK).
The second ones represent the capability of a TRE to emit with an 8-PSK power close to the maximum GMSK
power in a given cell.
1 2 28
Input / Output
Definitions: TRX Ranking
TRX Ranking
function
8-PSK High Power Capability (G4 HP, G4 MP, or G3)
TRX Ranking Table
DR TRE capability (FR or DR)
Inputs Outputs
TRX_PREF_MARK
PS_PREF_BCCH_TRX
Radio cell configuration (nb of SPDCHs per TRX)
TRX id (0,1,,14, or 15)
TRE
Characteristics
TRX or cell
Characteristics
TRX Rank
E-GSM, P-GSM, GSM850 or DCS TRX
Once the TRXs are mapped to the TREs (after a possible TRX adjustment), the TRX Ranking function is
computed. This function consists in ranking the TRXs in order to ensure that the CS and PS allocations will be
consistent.
HP means there is less than 3 dB of difference between the maximum power of the GMSK TRXs and the
maximum power of the 8-PSK TRXs in the cell. On the contrary, MP means the difference is more than 3 dB.
1 2 29
Ranking criteria (from the highest preference for PS allocation to the
lowest)
Concerns only PS capable TRX: TRX_PREF_MARK = 0
PS_PREF_BCCH_TRX
= 0 (no specific preference) then the BCCH TRX is managed as a non-BCCH TRX
= 1 then the BCCH TRX has the highest preference
= 2 then the BCCH TRX has the lowest preference (B9 MR4)
HW TRE capability: G4 HP > G4 MP > G3
DR TRE capability: FR > DR
E-GSM TRX preference: E-GSM TRXs > P-GSM/GSM850/DCS TRXs
TRX(s) having the maximum SPDCH group size
TRX having the lowest TRX index
Definitions: TRX Ranking [cont.]
Exercise
The TRX with the lowest Rank value has the highest preference for PS allocations.
Step 01: Separation of non-PS and PS capable TRXs
The first step consists in removing the non-PS capable TRXs, i.e., the TRXs having a non-null TRX_PREF_MARK. Only the PS capable TRXs
are then kept for the TRX ranking.
Step 02: Ranking of the PS capable TRXs
First criterion: PS allocations preferred on the BCCH TRX
If the BCCH TRX is a PS capable TRX and the parameter PS_PREF_BCCH_TRX is set to 2, then the BCCH TRX has the highest rank
in the TRX Ranking Table. This means that this TRX is selected last for PS allocations.
If the BCCH TRX is a PS capable TRX and the parameter PS_PREF_BCCH_TRX is set to 1, then the BCCH TRX has the lowest rank
(i.e., Rank 1) in the TRX Ranking Table. This means that this TRX is selected first for PS allocations.
If the parameter PS_PREF_BCCH_TRX is set to 0, then the rank of the BCCH TRX is determined by the remaining criteria.
Second criterion: HW TRE capability
The TRXs mapped on a G4HP TRE are ranked first, then they are followed by the TRXs mapped on a G4MP TRE, finally by the TRXs
mapped on a G3 TRE.
Third criterion: DR TRE capability
Among the TRXs having the same HW TRE capability, select first the FR TRX, then the DR TRX.
Fourth criterion:E-GSM TRX preference
Among the TRXs having the same HW TRE capability and the same DR TRE capability, select first the E-GSM TRXs, then the P-
GSM/GSM850/DCS TRXs.
Fifth criterion: Maximum SPDCH group criterion
Among the TRX having the same HW TRE capability, the same DR TRE capability and the same E-GSM TRX preference, rank first
the TRX having the maximum number of consecutive SPDCHs per TRX. Note that this is a static information given by the O&M
configuration of the TRX.
Sixth criterion: TRX identity
Among the remaining TRXs, select first the TRX having the lowest TRX id. This criterion aims at having a deterministic criterion at
the end of the TRX Ranking function.
Note:
The TRX ranking function does not take into account the current traffic load.
1 2 30
Allocated PDCH: MIN_PDCH = 1
Established TRX: MIN_PDCH = 1 and EN_FAST_INITIAL_GPRS_ACCESS =
enabled
BSS Resources Reservation
MFS BSC
PDCH
BTS
Air
MFS BSC
M-EGCH PDCH M-EGCH
BTS
Air Abis AterMux
TRX
The 3 following states are handled, for a PDCH:
allocated TS: timeslots allocated to the MFS.
not-allocated TS: timeslots allocated to the BSC
de-allocating TS: transitory state, TS allocated to the MFS but must be given back to the BSC
1 2 31
If EN_FAST_INITIAL_GPRS_ACCESS = enabled
1 PDCH is always available for (E)GPRS traffic
This PDCH is located
on an established TRX
with at least N_GCH_FAST_PS_ACCESS (=1) GCHs allocated on this TRX
Mandatory rule:
MIN_PDCH ; NB_TS_MPDCH + 1
Since MIN_PDCH is the number of master and slave PDCHs that are
permanently allocated
Otherwise, the rule is MIN_PDCH ; NB_TS_MPDCH
Fast Initial PS Access
The first TRX of the cell having some allocated RTSs is identified thanks to the latest RR Allocation
Indication message received from the BSC. When considering the sorted TRX list in the latest RR Allocation
Indication message, it is the TRX supporting the first RTS allocated to the MFS, according to the
SPDCHs_Allocation bitmap.
1 2 32
Principle
The BSC indicates regularly to the MFS in the RR Allocation Indication
message:
The number of TSs allocated for PS traffic
MAX_SPDCH_LIMIT
The location of those SPDCHs on the PS capable TRXs
Using the SPDCHs_Allocation bitmap
The MFS sends to the BSC the RR Usage Indication message to:
Confirm the allocated / de-allocated TSs to the BSC (Acknowledgement)
Indicate the PS usage state of those TSs
This message is sent:
Periodically
After the reception of the RR allocation Indication from the BSC
All the usable PS capable radio time slots are explicitly allocated to the MFS through the RR Allocation
Indication message.
A coordination is performed between the MFS and the BSC to allocate radio time slots for the PS traffic.
1 2 33
Principle [cont.]
MFS / BSC Synchronization
BSC
MFS
RR Allocation Indication
RR Usage Indication
RR Usage Indication
TCH_INFO_PERIOD (5s)
TCH_INFO_PERIOD
RR Allocation Indication
RR Usage Indication
RR_ALLOC_PERIOD (2)
x
TCH_INFO_PERIOD
B10
The RR Allocation Indication message:
Is sent from the BSC to the MFS to provide the MFS with the location of the allocated SPDCH.
Is transmitted periodically every RR_ALLOC_PERIOD * TCH_INFO_PERIOD seconds = 2 * 5 seconds.
Contains the SPDCH_Allocation bitmap which indicates whether available time slots in the cell are allocated or not to
the MFS.
The RR Usage Indication message:
Is sent from the MFS to the BSC periodically (every TCH_INFO_PERIOD seconds) or in response to a Radio Resource
Allocation Indication message.
Contains 4 bitmaps:
The SPDCHs_Confirmation bitmap. The role of this bitmap is to indicate the status of each SPDCH from the point of
view of the MFS and also to acknowledge the allocation of SPDCH newly granted by the BSC and the deallocation of
SPDCH given back to the BSC. The value of each bit in the SPDCHs_Confirmation bitmap has the following meaning:
1: this SPDCH is allocated to the MFS (SPDCH allocation state is allocated or de-allocating).
0: this SPDCH is not allocated to the MFS (SPDCH allocation state is not allocated).
The SPDCHs_Usage bitmap:
1: this SPDCH is allocated to the MFS and used (one TBF, RT PFC or one UL block has some radio resources
allocated on it, and/or if its basic Abis nibble is being used by a GCH channel or is still switched to an Ater
nibble in the BSC).
0: this SPDCH is either allocated to the MFS and unused (*), or is not allocated to the MFS.
The SPDCHs_RadioUsage bitmap:
1: this SPDCH is allocated to the MFS and there is at least one TBF allocated on it.
0: this SPDCH is either allocated to the MFS and there is no TBF allocated on it, or is not allocated to the
MFS.
The SPDCHs_DTM_TCH_List bitmap:
1: this SPDCH is used as TCH for DTM.
0: this SPDCH is used as No TCH for DTM.
The bitmaps are present for all the available PS capable TRXs of a cell, even if no SPDCH is allocated to the MFS for a
given TRX.
1 2 34
Computation of
MAX_SPDCH_LIMIT
Functional Entities
AV_USED_CS_TS
AV_USED_PS_TS
AV_UNUSED_TS
MAX_SPDCH_LIMIT
CS/PS Margin
Load Evaluation
Thresholds
computation
NB_TS
LOAD_EV_PERIOD_GPRS
HIGH_TRAFFIC_LOAD_GPRS
THR_MARGIN_PRIORITY_PS
MARGIN_PRIORITY_CS
MARGIN_PRIORITY_PS
NB_TS_DEFINED
NB_TS_SPDCH
MAX_PDCH_HIGH_LOAD
MAX_PDCH
MIN_PDCH
NB_TS_MPDCH
NB_USED_CS_TS
NB_USED_PS_TS
MAX_SPDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
B10
The BSC peridically computes the number of Slave PDCHs that it can provide to the MFS. This number of
SPDCHs is denoted MAX_SPDCH_LIMIT. In order to evaluate the value of this parameter, the BSC requires to
compute a certain number of other parameters.
This different steps to evaluate MAX_SPDCH_LIMIT are the following ones:
Computation of MIN_SPDCH, MAX_SPDCH and MAX_SPDCH_HIGH_LOAD from O&M parameters and from NB_TS
which has a changeable value (in case of TRX failure for example, seen later)
Computation of MARGIN_PRIORITY_CS and of MARGIN_PRIORITY_PS
Computation of MAX_SPDCH_LIMIT
1 2 35
Thresholds Computation
Computation of
MAX_SPDCH_LIMIT
AV_USED_CS_TS
AV_USED_PS_TS
AV_UNUSED_TS
MAX_SPDCH_LIMIT
CS/PS Margin
Load Evaluation
Thresholds
computation
NB_TS
LOAD_EV_PERIOD_GPRS
MARGIN_PRIORITY_CS
MARGIN_PRIORITY_PS
NB_TS_DEFINED
NB_TS_SPDCH
MAX_PDCH_HIGH_LOAD
MAX_PDCH
MIN_PDCH
NB_TS_MPDCH
NB_USED_CS_TS
NB_USED_PS_TS
MAX_SPDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
1 2 36
Thresholds Computation [cont.]
MAX_SPDCH = Roundup [Min(MAX_PDCH NB_TS_MPDCH ;
NB_TS_SPDCH) x Availability_TS_Ratio]
MAX_SPDCH_HIGH_LOAD = Roundup [Min(MAX_PDCH_HIGH_LOAD
NB_TS_MPDCH ; NB_TS_SPDCH) x Availability_TS_Ratio]
MIN_SPDCH = Roundup [(MIN_PDCH NB_TS_MPDCH) x
Availability_TS_Ratio]
Where Availability_TS_Ratio(k) = NB_TS(k) / NB_TS_DEFINED
evaluated at instant tk, every RR_ALLOC_PERIOD x TCH_INFO_PERIOD (10s)
NB_TS(k) takes into account the possible TRX failures
NB_TS_SPDCH is the total number of TCH/SPDCH time slots in the cell, without taking into account the
possible TRX failure. This parameter can be retrieved by the BSC from the O&M configuration of the cell.
NB_TS_DEFINED is the total number of pure TCH, TCH/SDCCH, or TCH/SPDCH time slots, without taking into
account the possible TRX failure. This parameter can be retrieved by the BSC from the O&M configuration of
the cell.
NB_TS is the total number of pure TCH, TCH/SDCCH, or TCH/SPDCH time slots (evaluated every 10s), taking
into account possible TRX failures.
A TCH/SPDCH is a TS which can be allocated for either CS traffic or PS traffic (i.e. mapped on a PS capable
TRX and inside the SPDCH group).
A pure TCH is a TS which can be allocated only for CS traffic (i.e. outside the SPDCH group).
A TCH/SDCCH is a dynamic SDCCH (can be allocated as either a TCH or an SDCCH).
1 2 37
Load Evaluation
Computation of
MAX_SPDCH_LIMIT
AV_USED_CS_TS
AV_USED_PS_TS
AV_UNUSED_TS
MAX_SPDCH_LIMIT
CS/PS Margin
Load Evaluation
Thresholds
computation
NB_TS
LOAD_EV_PERIOD_GPRS
MARGIN_PRIORITY_CS
MARGIN_PRIORITY_PS
NB_TS_DEFINED
NB_TS_SPDCH
MAX_PDCH_HIGH_LOAD
MAX_PDCH
MIN_PDCH
NB_TS_MPDCH
NB_USED_CS_TS
NB_USED_PS_TS
MAX_SPDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
B10
1 2 38
Load Evaluation [cont.]
The BSC computes 3 averaged values
AV_USED_CS_TS(k), AV_USED_PS_TS(k) and AV_UNUSED_TS(k)
For each cell
At sampling instant tk, every RR_ALLOC_PERIOD x TCH_INFO_PERIOD (10s)
Using a sliding window, LOAD_EV_PERIOD_GPRS
Same formula for AV_USED_PS_TS(k) and AV_UNUSED_TS(k) based on
NB_USED_PS_TS(k) and NB_UNUSED_TS(k)
NB_UNUSED_TS(k) = NB_TS(k) NB_USED_CS_TS(k) MAX[MIN_SPDCH(k) ;
NB_USED_PS_TS(k)]
1 - RIOD_GPRS LOAD_EV_PE
0 = i
i) - (k _TS NB_USED_CS
RIOD_GPRS LOAD_EV_PE
1
= _TS(k) AV_USED_CS
B10
NB_USED_CS_TS(k): number of available time slots handled by the BSC and carrying CS traffic in the cell at
sampling instant tk. A time slot is taken into account in the evaluation of NB_USED_CS_TS(k) if:
SPDCH allocation state = not allocated,
Occupancy state = used.
SPDCH allocation state = allocated or de-allocating
DTM mode = DTM TCH
NB_USED_PS_TS(k): number of available time slots used for PS traffic in the cell at sampling instant tk. A time
slot is taken into account in the evaluation of NB_USED_PS_TS(k) if:
SPDCH allocation state = allocated or de-allocating,
Occupancy state = used.
DTM Mode = DTM TCH
These variables are updated every TCH_INFO_PERIOD (5s).
1 2 39
Load Evaluation [cont.]
TCH_INFO_PERIOD = 5s
AV_USED_CS_TS(k)
AV_USED_PS_TS(k)
AV_UNUSED_TS(k)
NB_USED_CS_TS(k)
NB_USED_PS_TS(k)
NB_USED_TS(k)
NB_UNUSED_TS(k)
k k-1 k-2
LOAD_EV_PERIOD_GPRS = 3
k+1 k+2
AV_USED_CS_TS(k+2)
AV_USED_PS_TS(k+2)
AV_UNUSED_TS(k+2)
RR_ALLOC_PERIOD * TCH_INFO_PERIOD
B10
1 2 40
CS/PS Margins
Computation of
MAX_SPDCH_LIMIT
AV_USED_CS_TS
AV_USED_PS_TS
AV_UNUSED_TS
MAX_SPDCH_LIMIT
CS/PS Margin
Load Evaluation
Thresholds
computation
NB_TS
LOAD_EV_PERIOD_GPRS
MARGIN_PRIORITY_CS
MARGIN_PRIORITY_PS
NB_TS_DEFINED
NB_TS_SPDCH
MAX_PDCH_HIGH_LOAD
MAX_PDCH
MIN_PDCH
NB_TS_MPDCH
NB_USED_CS_TS
NB_USED_PS_TS
MAX_SPDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
1 2 41
CS/PS Margins [cont.]
MARGIN_CS = MAX(MARGIN_PRIORITY_CS(k), AV_UNUSED_TS(k) / 2)
Where:
MARGIN_PRIORITY_CS = THR_MARGIN_PRIO_CS x (NB_TS
MAX_SPDCH_HIGH_LOAD)
THR_MARGIN_PRIO_CS = 100% - HIGH_TRAFFIC_LOAD_GPRS
MARGIN_PRIORITY_PS = THR_MARGIN_PRIO_PS x
MAX_SPDCH_HIGH_LOAD
Where:
THR_MARGIN_PRIO_PS = 10%
These 2 margins are used to ensure that a certain number of TSs is kept
available for the arrival of new calls / transfers between 2 RR Allocation
Indication messages
B10
These new margins, one for CS traffic and one for PS traffic are here introduced to guarantee that a certain
number of timeslots are kept available for the arrival of new calls between two transmissions of RR Allocation
Indication messages.
MARGIN_PRIORITY_CS : dedicated to CS traffic.
MARGIN_PRIORITY_PS : dedicated to PS traffic.
These margins are re-evaluated every RR_ALLOC_PERIOD * TCH_INFO_PERIOD, before the computation of
MAX_SPDCH_LIMIT.
1 2 42
MAX_SPDCH_LIMIT Computation
Computation of
MAX_SPDCH_LIMIT
AV_USED_CS_TS
AV_USED_PS_TS
AV_UNUSED_TS
MAX_SPDCH_LIMIT
CS/PS Margin
Load Evaluation
Thresholds
computation
NB_TS
LOAD_EV_PERIOD_GPRS
MARGIN_PRIORITY_CS
MARGIN_PRIORITY_PS
NB_TS_DEFINED
NB_TS_SPDCH
MAX_PDCH_HIGH_LOAD
MAX_PDCH
MIN_PDCH
NB_TS_MPDCH
NB_USED_CS_TS
NB_USED_PS_TS
MAX_SPDCH_HIGH_LOAD
MIN_SPDCH
MAX_SPDCH
1 2 43
MAX_SPDCH_LIMIT Computation: Functional Entities
MAX_SPDCH_LIMIT Computation of
MAX_SPDCH_LIMIT
MIN_SPDCH
MARGIN_PRIORITY_PS
Computation of
MAX_SPDCH_LIMIT_CS
Computation of
MAX_SPDCH_LIMIT_PS
AV_USED_CS_TS
AV_UNUSED_TS
AV_USED_PS_TS
MARGIN_PRIORITY_CS
MAX_SPDCH
MAX_SPDCH_HIGH_LOAD
MAX_SPDCH_LIMIT_CS
MAX_SPDCH_LIMIT_PS
The basic idea for the evaluation of MAX_SPDCH_LIMIT is to start from the number of unused time slots and to
share them between CS and PS traffic, taking into account 2 margins (one for CS, one for PS traffic) defined to
guarantee a certain number of time slots available to serve incoming calls/transfers.
1 2 44
MAX_SPDCH_LIMIT Computation: Formulas
MAX_SPDCH_LIMIT is equal to:
MAX_SPDCH_LIMIT_CS under normal load
MAX_SPDCH_LIMIT_PS under high CS load
MAX_SPDCH_LIMIT_CS
Represents the maximum number of SPDCHs that can be allocated to the
MFS ensuring the CS allocation is not degraded
= RoundDown[NB_TS AV_USED_CS_TS MARGIN_CS]
MAX_SPDCH_LIMIT_PS
Represents the minimum number of SPDCHs that can be allocated to the
MFS ensuring the PS allocation is not degraded
= RoundUp[AV_USED_PS_TS + MARGIN_PRIORITY_PS]
OR
B10
1 2 45
MAX_SPDCH_LIMIT Computation: Formulas [cont.]
Choice between MAX_SPDCH_LIMIT_CS and MAX_SPDCH_LIMIT_PS
If MAX_SPDCH_LIMIT_CS >= MAX_SPDCH_HIGH_LOAD then
MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_CS ; MAX_SPDCH]
Else
If MAX_SPDCH_LIMIT_CS > MAX_SPDCH_LIMIT_PS then
MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_CS ; MAX_SPDCH]
Else
MAX_SPDCH_LIMIT = Min[MAX_SPDCH_LIMIT_PS ; MAX_SPDCH_HIGH_LOAD]
MAX_SPDCH_LIMIT is always between MIN_SPDCH and MAX_SPDCH
B10
1 2 46
MAX_SPDCH_LIMIT Computation: Example
NB_TS=14 MAX_SPDCH=14 MIN_SPDCH=1
MAX_SPDCH_HIGH_LOAD=2 HIGH_TRAFFIC_LOAD_GPRS=80%
Exercise
2
4
6
8
10
12
14
High CS load
Without PS traffic
CS
Traffic
Normal
load
CS
Traffic
PS
Traffic
High PS
load
PS
Traffic
High CS load
with PS traffic
CS
Traffic
PS
Traffic
Case Normal Load: The capacity is shared between CS and PS taking into account the associated margins.
Case High CS load: When the CS traffic increases, MAX_SPDCH_LIMIT is reduced down to
MAX_SPDCH_HIGH_LOAD to ensure a minimum capacity for the PS traffic.
Case Very high CS load: When the CS traffic increases and in the same time there is no PS traffic,
MAX_SPDCH_LIMIT is decreased down to MIN_SPDCH to ensure the maximum capacity for the CS.
Case High PS load: MAX_SPDCH is not the only criterion taken into account to limit the PS capacity, the
CS_MARGIN is applied too.
1 2 47
PS Zones: Definition
MAX_SPDCH = 12, MIN_SPDCH = 1, MAX_SPDCH_LOAD = 8
MAX_SPDCH_LIMIT = 7
TRX3 TRX1
BCCH SDCCH PS PS PS PS CS CS CS
Non pre-emptable zone
MAX_SPDCH_HIGH_LOAD zone
MAX_SPDCH_LIMIT zone
PS traffic zone
B10
MAX_SPDCH_HIGH_LOAD zone: this zone corresponds to the MAX_SPDCH_HIGH_LOAD consecutive PS capable
time slots that are preferred for PS allocation. In this zone, allocated TBFs cannot be preempted. If the value
of MAX_SPDCH_HIGH_LOAD is not modified, this zone remains unchanged.
For a DTM request, the MFS will always allocate DTM TCH in this zone, and try to select the leftmost
timeslot as DTM TCH.
Non pre-emptable PS zone: this zone is always inside the MAX_SPDCH_HIGH_LOAD zone. In this latter zone,
we search for the rightest time slot allocated to the MFS and used, or allocated to the MFS, not use, TCH for
DTM. Then, all time slots situated at its left define this non pre-emptable PS zone.
MAX_SPDCH_LIMIT zone: this zone corresponds to the MAX_SPDCH_LIMIT consecutive PS capable time slots
that are preferred for PS allocation.
PS traffic zone: this zone corresponds to the larger zone between the non pre-emptable PS zone and the
MAX_SPDCH_LIMIT zone.
1 2 48
PS Zones: Selection of MAX_SPDCH_LIMIT TS
The MAX_SPDCH_LIMIT timeslot are selected within:
the non pre-emptable PS zone
It contains all the TS that can be or are allocated to the MFS
the MAX_SPDCH_LIMIT zone
If the number of selected TS is still lower than MAX_SPDCH_LIMIT, the process
continues outside this zone until this number reaches MAX_SPDCH_LIMIT.
Once MAX_SPDCH_LIMIT timeslot have been selected, the remaining TS
are allocated to the BSC
The TS carrying the TCH of a MS in DTM remains allocated to the MFS:
Even if they are outside the MAX_SPDCH_LIMIT zone
It only concerns the TCH of the MS, not the TBF resources
B10
Caution: animated slide.
The BSC shall not de-allocate a DTM TCH timeslot carrying CS traffic, even if the DTM TCH is outside of
MAX_SPDCH_HIGH_LOAD value and MAX_SPDCH_LIMIT zone (in case of TRX failure, the BSC will adjust
MAX_SPDCH_HIGH_LOAD value, so it is possible the DTM TCH timeslot is outside of non-emptable zone) until
the DTM CS connection is released. When the DTM CS connection is released, the BSC notifies it to the MFS,
the MFS changes the DTM TCH timeslot from TCH for DTM to no TCH for DTM and indicates this
information to the BSC through the message RR Usage Indication, only then the BSC can de-allocate it.
1 2 49
PS Zones: Impact on CS Call
If EN_RETURN_CS_ZONE_HO = enabled
AND a CS call is inside both
The Non pre-emptable zone and
The MAX_SPDCH_LIMIT_ZONE then
An intra cell HO cause 30 is triggered
TRX1
CS CS BCCH SDCCH PS PS PS PS CS
HO cause 30
PS PS
TRX3
MAX_SPDCH_HIGH_LOAD zone
PS traffic zone
B10
The BSC shall not de-allocate a DTM TCH timeslot carrying CS traffic, even if the DTM TCH is outside of
MAX_SPDCH_HIGH_LOAD value and MAX_SPDCH_LIMIT zone.
Cause 30 is not applied in case of TS carrying a DTM TCH. SPDCH allocation state is equal to TCH for DTM
1 2 50
SPDCH Allocation: Conclusion
Example of an SPDCHs_Allocation bitmap
MAX_SPDCH_LIMIT = 7
TRX3 TRX1
BCCH SDCCH PS PS PS PS CS CS
1 1 1 0 1 1 1 1 0 0 0 0 0 0 0 0
B10
CS
*
DTM MS
CS
* :
DTM TCH
The algorithm of selection of MAX_SPDCH_LIMIT TCH/SPDCH time slots to allocate to the MFS and of building
of the SPDCHs_Allocation bitmap is performed as follows:
Initialization:
Definition of the non pre-emptable PS zone and of the MAX_SPDCH_LIMIT zone,
nb_selected = 0,
Begin with the time slot having the lowest index and situated on the TRX having the lowest rank in the
TRX Ranking Table.
Process on each TCH/SPDCH time slots available in the cell:
First, begins with the non pre-emptable PS zone: analysis of all time slots within this zone. At the end of
this zone:
If nb_selected >= MAX_SPDCH_LIMIT: stop the process and the remaining time slots are allocated
to the BSC,
Otherwise: continue the process in the MAX_SPDCH_LIMIT zone. At the end of this zone:
If nb_selected = MAX_SPDCH_LIMIT: stop the process and the remaining time slots are
allocated to the BSC,
Otherwise: continue the process outside the MAX_SPDCH_LIMIT zone. When nb_selected =
MAX_SPDCH_LIMIT: stop the process and the remaining time slots are allocated to the BSC.
1 2 51
SPDCH De-allocation: Principle
A preemption is triggered in the MFS
At the reception of an RR Allocation Indication message from the BSC
In case there is one or several PDCH to give back to the BSC
It concerns only used PDCHs where:
Its mapped basic Abis nibble is used in an M-EGCH link
At least 1 TBF is allocated on it
CS preemption takes place in two main steps:
Soft preemption
Fast preemption
SPDCH de-allocation is based on GCH inactivity timers
Timers T_GCH_INACTIVITY and T_GCH_INACTIVITY_LAST are used to de-
allocate the unused GCHs
OR
B10
1 2 52
SPDCH De-allocation: Preemption Mechanism
All T1 requests
played successfully
No TBF candidate for T1 or
T_PDCH_Preemption expiry
Fast preemption
Soft preemption T1 re-allocation
Unlock PDCHs
Arrival of RR
Allocation
indication message
Lock PDCHs
On TRXs with all its basic Abis
nibbles impacted by CS
preemption
Step 1: lock the PDCHs of the TRXs which are highly impacted by the CS preemption
This step is only applicable to Evolium BTSs
The basic Abis nibbles of the time slots preempted by the BSC may be currently used by some GCHs in the cell. Thus, the TRXs (or
M-EGCHs) using these GCHs will be impacted by the preemption, even if the preempted TSs are not on these TRXs. Thats why the
TRXs of the cell for which the 2 following conditions are fulfilled have all their PDCHs locked by the preemption process, it means
that they cannot accept anymore traffic:
Nb_GCH_Impacted_By_CS_Preemption > 0
Established_Nb_GCH Nb_GCH_Impacted_By_CS_Preemption <= Min_Nb_GCH_GBR
Where:
Nb_GCH_Impacted_By_CS_Preemption is the number of established GCHs in the M-EGCH link using a basic Abis nibble
mapped onto a radio time slot that is being deallocated by the BSC.
Established_Nb_GCH is is the number of GCHs that are activated in the M-EGCH link and that will be kept activated
during a certain time.
Min_Nb_GCH_GBR is an estimation of the minimum number of GCHs necessary in a given M-EGCH link for the GBR
(Guaranteed Bit Rate) traffic supported by the TRX in both directions (UL and DL).
Step 2: soft preemption process
2 kinds of TBF are candidate for the T1 re-allocation process:
The TBFs whose PACCH is supported by a preempted time slot.
The TBFs for which it will no longer be possible to serve their on-going max allowed (M)CS because of the subsequent
reduction of the M-EGCH link size of their TRX.
In addition, in the case where the number of TBFs established on a TRX will become too high according to the remaining number
of GCHs in the M-EGCH link of the TRX, then some TBFs will be released.
Step 3: fast preemption process
At T_PDCH_Preemption timer expiry:
The TBFs which could not be T1 reallocated are released.
The locked PDCHs which do not carry PACCH are released (TBF throughput reduction).
The GCHs using the basic Abis nibbles of the preempted radio TSs are released.
Step 4: unlock the PDCHs:
If some PDCHs were locked in step 1, they are unlocked. Indeed, the CS preemption process is over, so the existing M-EGCH
links will no longer be disturbed by the release of some of their GCHs due to the fast preemption.
1 2 53
SPDCH De-allocation: Preemption Mechanism [cont.]
B10
Fast preemption
Soft preemption
Unlock PDCHs
Arrival of RR
Allocation
indication message
Lock PDCHs
On TRXs with all its basic Abis
nibbles impacted by CS
preemption
No T1 reallocation will be
triggered during
T_PDCH_Preemption
TBF resources of the MSs are
released.
TCH ressources shall not be
deallocated
Case of resources allocated in DTM mode
The preemption of a PDCH in the TCH state is controlled by the BSC Through arrival of RR Allocation
Indication message
That situation is rare as the TSs used for an MS in DTM mode are only allocated in the non preemptable PS
zone
A PDCH supporting a BE TBF for an MS in DTM mode can be preempted by the BSC. That situation can occur:
if a RR Usage Indication message indicating the TSs used by the BE TBFs crosses a RR Allocation Indication
message sent by the BSC which preempts some of those TSs.
or due to a change of the non preemptable PS zone of the cell
In such situation the following algorithm shall be applied:
tep 1: Identical to non DTM case
Step 2: The same conditions as non DTM ones apply
If the DTM TBF resources are impacted by the CS preemption , the a notification message will be
sent to RRM-PPCC. This notification message will be ignored by RRM-PCC and no T1 reallocation
will be triggered by RRM-PCC.
Step 3: fast preemption process
The same conditions as non DTM ones apply
RRM-PCC will release the TBF resources (both UL and DL) of the MSs. The TCH resources shall not
be deallocated (TCH resource deallocation will happen on BSC-Shared-DTM-Info-Indication reception in the
nominal case)
Step 4: unlock the PDCHs:
Identical to non DTM case
1 2 54
SPDCH De-allocation: Soft Preemption
The MFS locks all the PDCHs impacted by the CS preemption:
i.e. The de-allocated PDCH indicated in the RR Allocation Indication message
sent by the BSC (the PDCHs to be preempted)
The MFS locks also all the PDCHs of the TRX which have a GCH mapped on a RTS impacted by preemption and
only in case of all the GCHs of the TRX are impacted by the preemption (rare case).
1 2 55
SPDCH De-allocation: Soft Preemption [cont.]
2 kinds of TBF are candidate for the T1 re-allocation process:
The TBFs whose PACCH is supported by a preempted time slot.
The TBFs for which it will no longer be possible to serve their on-going max
allowed (M)CS because of the subsequent reduction of the M-EGCH link size of
their TRX.
TRX1
TRX2
TRX3
TRX4
RSL
OML
31
TRX1
TRX3
BCCH SD
TBF1 CS2
PDCHs to
be
preempted
Bonus Bonus
.
.
.
TBF2 is candidate for
T1 re-allocation
Abis
TBF2 MCS7
1 2 56
SPDCH De-allocation: Fast Preemption
Fast preemption:
At expiry of T_PDCH_PREEMPTION, the MFS de-allocates the TS before TBF
ending, having the following impacts:
The TBFs whose PACCH is impacted (the corresponding PDCH is marked) are
released.
The MFS sends a Packet TBF release message with polling (i.e acknowledgement is requested)
The TBFs whose PACCH is not impacted are not released but have a throughput
reduction.
The MFS sends a Packet PDCH release message indicating the preempted PDCHs
T_PDCH_PREEMPTION = TCH_INFO_PERIOD 1 = 4s
T_PDCH_PREEMPTION cannot be set at the OMC-R anymore
The PACCH blocks are the most important blocks to monitor. Many GPRS features ensure that PACCH blocks
are always monitored by the MS:
The PTCCH is carried by the same PDCH as the PACCH.
The RXLEV measurements for the power control and CS adaptation are made on the PDCH that carries the
PACCH blocks.
Some RLS mechanisms are based on whether or not the MS is able to send or listen to PACCH blocks.
1 2 57
3 TBF Radio Resources Allocation and
Re-Allocation
1 2 58
ASAP: used for BE TBF establishment, T1, T2 and T4 reallocation
Its goal is to serve the request as soon as possible.
OPTIMAL: used for T3 reallocation
Its goal is to ensure that a significant bandwidth will be offered to the MS
upon T3 reallocation, even if it takes some time to establish all the necessary
GCHs
Nb_GCH_For_TBF_Estab:
Minimum number of GCHs, which are required on the TRX to serve the
request.
3 TBF Radio Resources Allocation and Re-Allocation
Definition of the 2 TBF Allocation Policies
1 to 5 (Max_Allowed_(M)CS of concurrent TBF) Optimal T3 TBF reallocation (MS in PTM or in DTM
1 ASAP DTM allocation request
1 to 2 (Max_Allowed_CS of concurrent TBF) ASAP T4 TBF reallocation
1 ASAP T1 TBF reallocation
1 to 5 (Max_Allowed_(M)CS of concurrent TBF) ASAP TBF establishment (with concurrent)
1 ASAP TBF establishment (without concurrent)
Nb_GCH_For_Estab Policy Type of request
New
B10
1 2 59
Depends on the type of TBF (GPRS / EGPRS) and of the direction of the
TBF (UL / DL)
Is based on the number of established GCHs:
Established_Nb_GCH Nb_GCH_Impacted_CS_Preemption
Is limited by:
GPRS / EGPRS TRX capability,
MAX_GPRS_CS and MAX_EGPRS_MCS
Determination of the Max_Allowed_(M)CS of a TBF
CS-4 2
CS-2 (UL) / CS-1 (DL) 1
Max_Allowed_CS Nb_GCH
MCS-9 5
MCS-7 4
MCS-6 3
MCS-5 2
MCS-2 (UL) / MCS-1 (DL) 1
Max_Allowed_MCS Nb_GCH
Established_Nb_GCH is is the number of GCHs that are activated in the M-EGCH link and that will be kept
activated during a certain time.
1 2 60
Functional Entities

Candidate TS allocation
Best-effort TBF allocation/reallocation request
(received from RRM-PCC or dequeued from an Li list)
TRX list
computing
Cf. session 2.2
Best candidate allocation computation
No candidate TS allocation

RADIO RESOURCE ALLOCATION/REALLOCATION
ALGORITHM
TBF ESTABLISHMENT PROCESS
Cell Transmission Equity
Enough GCHs Not enough GCHs
ALLOC OK case
ALLOC FAILED case
Test if enough GCHs
Available_Nb_GCH_With_Equity
TRX list
Transmission Resource
Availability
DSP
congestion state
TRX list sorted
by the BSC
Available_Nb_GCH
Transmission resource
reservation
n_MS_requested,
n_MS_requested_concurrent
Multislot class,
Bias,
Traffic type
Number
of radio TSs
determination
Type of the TBF request
PDCH capacity/TFI/TAI/USF
allocation
- rejected request
- or L4 queuing
- or L5/L6 queuing
- or L7 queuing)
- or try to change TBF mode (EGPRS case)
L4
The list of DL TBFs which are still not served (due to a lack of resources).
This list is sorted according to the PDU lifetime of the first DL LLC PDU of each queued request.
On PDU lifetime expiry, the request is removed from the queue.
L5
The list of MSs with UL bias which are candidate for resource re-allocation due to trigger T3.
This list is sorted according to the following criteria:
The candidate MSs are processed according to a FIFO order: the first request posted in the list is the
first processed by RRM PRH.
In case it is not possible to reallocate resources to a candidate MS, the MS is put back at the end of the
list.
L6
The list of MSs with DL bias which are candidate for resource re-allocation due to trigger T3.
This list is sorted in the same way as L5.
L7
The list of MSs which are candidate for resource re-allocation due to trigger T4.
The candidate MSs are processed according to a FIFO order: the first request posted in the list is the first
processed by RRM PRH.
In case it is not possible to reallocate resources to a candidate MS, the MS is put back at the end of the list.
1 2 61
Transmission Resource Availability
Best -effort TBF allocation/reallocation request
(received from RRM -PCC or dequeued from an Li list)
TRX list
computing
Cf. session 2.2
ALGORITHM
ALLOC OK case
ALLOC FAILED case
Test if enough GCHs
TRX list
Availability
DSP
congestion state
TRX list sorted
by the BSC
Available_Nb_GCH
reservation
n_MS_requested,
Multislot class,
Bias,
Traffic type
Number
of radio TSs
determination
allocation
- rejected request
- or L4 queuing
- or L5/L6 queuing
- or L7 queuing )
B10
The transmission resource Availibility step determines the total number of new GCHs which can be established:
with free Abis and Ater resources (only the non-CS pre emptable Abis ressources are considered for RT PFC)
with inter-cell GCH preemptions
This number is:
Available_Nb_GCH in case of Best Effort TBF allocation
Available_Nb_GCH_for_GBR in case of RT PFC allocation
1 2 62
Transmission Resource Availability: Example
3 cells with 2 TRXs:
Max_PDCH_High_Load = 4 => a maximum of 4 non CS preemptable basic Abis
nibbles can be established in the cell
MAX_PDCH = 8, MAX_EGPRS_MCS = MCS-9, MAX_GPRS_CS = CS-4
Max_SPDCH_Limit = 6 =>a maximum of 6 basic Abis nibbles can be
established in the cell
CS
radio
Cell A
Cell B
Cell C
Abis
Basic
nibbles
6x4
extra
nibbles
1 2 63
Transmission Resource Availability: Example [cont.]
First EDGE MS1, class 8 in cell A -> Target_Nb_GCH = 18
GCH Allocation for MS1
4 basic Abis nibbles in the Max_PDCH_High_Load zone
14 extra Abis nibbles
Total = 18 GCHs
Cell A
Cell B
Cell C
basic
extra
CS
MS1
CS
Cell A
1 2 64
Second EDGE MS2, class 8 in cell B -> Target_Nb_GCH = 18
GCH Allocation for MS2
4 basic Abis nibbles in the Max_PDCH_High_Load zone
10 free extra Abis nibbles
2 basic Abis nibbles outside the Max_PDCH_High_Load zone
Inter GCH preemption between Cell A and Cell B:
14 extra Abis in cell A, 10 extra Abis in cell B
2 extra Abis nibbles are preempted from Cell A to Cell B
Total = 18 GCHs
basic
extra
Cell A
Cell B
Cell C
CS
MS1
MS2
CS
Cell A
Cell B
1 2 65
After GCH allocation of MS2 in cell B
In Cell A: Established_Nb_GCH = 16
Next Periodical GCH process in Cell A: Equity process
2 basic Abis nibbles outside the Max_PDCH_High_Load zone
Total = 16 + 2 = 18 GCHs
basic
extra
CS
MS1
MS2
CS
Cell A
Cell B
Cell A
Cell B
Cell C
1 2 66
Transmission Resource Availability: High Ater Usage
Each time some radio resources are allocated on a new PDCH of a TRX
No radio resources were formerly allocated on this PDCH for some TBFs
If the Ater is in high usage
Percentage of used Ater nibbles, in a GPU > Ater_Usage_Threshold
Then, the number of GCHs targeted per PDCH is reduced
Target_Nb_GCH_per_PDCH x GCH_RED_FACTOR_High_Ater_Usage
In case of DTM:
Ater_Usage_Threshold is not taken into account
B10
For other cases, each time some radio resources (for a TBF or for an RT PFC) are allocated on a new PDCH of a
TRX (new PDCH means that no radio resources were formerly allocated on this PDCH for some TBFs or for
some RT PFCs), then a value called alpha_HiAter shall be associated to this PDCH.
The value of alpha_HiAter to be associated to a newly-used PDCH is computed as follows:
If the Ater usage of the GPU is normal (nominal case):
alpha_HiAter = 1,
If the Ater usage of the GPU is high (high Ater usage situation):
alpha_HiAter = GCH_RED_FACTOR_High_Ater_Usage,
with GCH_RED_FACTOR_High_Ater_Usage the O&M parameter value.
The value of alpha_HiAter is used in the Target_Nb_GCH computing.
If the Ater usage of the GPU is high, this will have the effect of applying a GCH reduction factor
(GCH_RED_FACTOR_High_Ater_Usage) to the number of GCHs targeted per PDCH, when opening new PDCHs.
Some consequences of this mechanism are:
If the Ater usage of the GPU becomes high, then the Ater consumption will increase more slowly from this
moment,
If the Ater usage of the GPU stays high for a long time, and if the PDCH closure and (re)opening rate
is sufficient in the GPU, then the GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) will tend to be
applied on many of the TRXs managed by the GPU, which will lead to a pseudo-equity in the usage of the
Ater resources of the GPU.
1 2 67
Transmission Resource Availability: High Ater Usage [cont.]
Example:
Considering an MEGCH link of a TRX supporting one 4-TS best-effort EGPRS
TBF
MAX_EGPRS_MCS = MCS-9
GCH_RED_FACTOR_High_Ater_Usage = 0.75
Target_Nb_GCH = 1*4.49+1*4.49+1*4.49+1*4.49 = 18 GCHs if Ater usage of
the GPU is normal
Target_Nb_GCH = 0.75*4.49+0.75*4.49+0.75*4.49+0.75*4.49 = 14 GCHs if
Ater usage of the GPU is high
For other cases, each time some radio resources (for a TBF or for an RT PFC) are allocated on a new PDCH of a
TRX (new PDCH means that no radio resources were formerly allocated on this PDCH for some TBFs or for
some RT PFCs), then a value called alpha_HiAter shall be associated to this PDCH.
The value of alpha_HiAter to be associated to a newly-used PDCH is computed as follows:
If the Ater usage of the GPU is normal (nominal case):
alpha_HiAter = 1,
If the Ater usage of the GPU is high (high Ater usage situation):
alpha_HiAter = GCH_RED_FACTOR_High_Ater_Usage,
with GCH_RED_FACTOR_High_Ater_Usage the O&M parameter value.
The value of alpha_HiAter is used in the Target_Nb_GCH computing.
If the Ater usage of the GPU is high, this will have the effect of applying a GCH reduction factor
(GCH_RED_FACTOR_High_Ater_Usage) to the number of GCHs targeted per PDCH, when opening new PDCHs.
Some consequences of this mechanism are:
If the Ater usage of the GPU becomes high, then the Ater consumption will increase more slowly from this
moment,
If the Ater usage of the GPU stays high for a long time, and if the PDCH closure and (re)opening rate
is sufficient in the GPU, then the GCH reduction factor (GCH_RED_FACTOR_High_Ater_Usage) will tend to be
applied on many of the TRXs managed by the GPU, which will lead to a pseudo-equity in the usage of the
Ater resources of the GPU.
1 2 68
Number of Radio TS Determination

TRX list
computing
Cf. session 2.2

ALGORITHM
ALLOC OK case
ALLOC FAILED case
Test if enough GCHs
TRX list
Availability
DSP
congestion state
TRX list sorted
by the BSC
Available_Nb_GCH
reservation
n_MS_requested,
Multislot class,
Bias,
Traffic type
Number
of radio TSs
determination
allocation
- rejected request
- or L4 queuing
- or L5/L6 queuing
- or L7 queuing)
1 2 69
Number of Radio TS Determination [cont.]
The number of radio TSs is determined for:
The direction of the request (n_MS_requested)
The concurrent direction (n_MS_requested_concurrent)
Taken into account
The MS multislot class, (or DTM (E)GPRS multislot class)
Maximum number of PDCH allocated to a single (E)GPRS connection:
MAX_PDCH_PER_TBF
The direction mainly used (in terms of throughput) by the on-going
application: the bias
The MFS counts and averages the number of bytes transferred in both directions
By default bias = DL
Except when the first TBF establishment is a UL 2 phase access
Extended Dynamic Allocation allowed or not (EN_EDA)
The traffic type
Only 1 TS is allocated in case of GMM/SM signaling traffic
B10
When allocating resources to an MS, both n_MS_requested and n_MS_requested_concurrent are considered, even when only one TBF is
established or being established, to take into account a potential future concurrent TBF, except in case of UL TBF establishment without
concurrent DL TBF (Immediate UL TBF establishment), where only n_MS_requested is taken into account to allocate resources for the UL
TBF.
General purpose of the bias determination:
GPRS MSs are often involved in consecutive UL/DL transfers for a unique service.
The Bias determination shall identify the direction of the main flow of data (based on the quantity of data exchanged at a specific
moment) in order to prioritize:
The initial allocation on the biased direction.
The re-allocation process on the main direction (likely to carry the useful data).
Each time n_received_octets_UL = N_BIAS_DETERMINATION or n_sent_octets_DL = N_BIAS_DETERMINATION (whichever is reached first),
RRM determines the bias as follows:
if Av_n_received_octets_UL > Av_n_sent_octets_DL, the transfer is deemed uplink biased,
else the transfer is deemed downlink biased.
RRM then resets to 0 the counters n_received_octets_UL and n_sent_octets_DL.
Where:
n_received_octets_UL represents the number of octets received in the UL.
n_sent_octets_DL represents the number of octets sent in the DL.
Av_n_received_octets_UL represents an average number of octets received in the UL.
Av_n_sent_octets_DL represents an average number of octets sent in the DL.
Av_n_received_octets_UL (new) = WEIGHT_BIAS_DETERMINATION * Av_n_received_octets_UL (old) + (1 - WEIGHT_BIAS_DETERMINATION)
* n_received_octets_UL.
Av_n_sent_octets_DL (new) = WEIGHT_BIAS_DETERMINATION * Av_n_sent_octets_DL (old) + (1 - WEIGHT_BIAS_DETERMINATION) *
n_sent_octets_DL.
N_BIAS_DETERMINATION and WEIGHT_BIAS_DETERMINATION are MFS (DLS) parameters used to tune the bias determination. The
weighting factor is used in particular to avoid changing too quickly the bias of a transfer so that this determination takes into account the
number of octets exchanged in the past.
Default values:
N_BIAS_DETERMINATION = 3 KB
WEIGHT_BIAS_DETERMINATION = 0,7
1 2 70
Best Candidate Allocation Computation

TRX list
computing
Cf. session 2.2

ALGORITHM
ALLOC OK case
ALLOC FAILED case
Test if enough GCHs
TRX list
Availability
DSP
congestion state
TRX list sorted
by the BSC
Available_Nb_GCH
reservation
n_MS_requested,
Multislot class,
Bias,
Traffic type
Number
of radio TSs
determination
allocation
- rejected request
- or L4 queuing
- or L5/L6 queuing
- or L7 queuing)
B10
1 2 71
GPRS
EGPRS
The same states and parameters are used
But, only EGPRS TBFs are taken into account
Specific state for GPRS UL TBF allocation: EGPRS PDCH
PDCH used in the DL by an 8-PSK capable EGPRS TBF
TCH State: If a TCH has been allocated by the MFS on this PDCH for a DTM-
capable MS
SPDCH States
MAX_XX_TBF_SPDCH
PDCH
FULL
PDCH
ACTIVE
PDCH
ALLOCATED
PDCH
TCH State
B10
Following states are defined for a PDCH:
Allocated: the PDCH is an SPDCH which has been indicated as usable for PS traffic by the BSC.
Active: an allocated PDCH is active if it supports at least one radio resource allocated for a TBF or for an RT
PFC.
Full: an allocated PDCH is full in a given XL (XL = UL or DL) direction if and only if:
for GPRS Best Effort TBF: Nb_RT_PFC_XL + Nb_BE_TBF_XL MAX_XL_TBF_SPDCH
for EGPRS Best Effort TBF: Nb_RT_PFC_XL + Nb_BE_EGPRS_TBF_XL MAX_XL_TBF_SPDCH
for RT resource allocation: Nb_RT_PFC_XL + Nb_BE_TBF_XL MAX_XL_TBF_SPDCH
This is the same definition as in B8 release except that the concepts of RT PFC and best effort TBF are
introduced.
EGPRS: An allocated PDCH is in the EGPRS state if some radio resources are allocated in the DL direction,
for an EGPRS TBF or an EGPRS RT PFC. This state is only used when running the radio resource
allocation/reallocation algorithm in GPRS mode and when considering the UL direction of the candidate TBF
allocations.
1 2 72
Available Throughput Computation
For a GPRS TBF, in case of only BE TBFs with the same priority
available_throughput_candidate_XL = R_AVERAGE_GPRS *
NB_TBF
PDCHi
represents the number of already allocated GPRS and EGPRS
TBFs on the PDCH i
For an EGPRS TBF, in case of only BE TBFs with the same priority
available_ throughput _candidate_XL = R_AVERAGE_EGPRS *
NB_TBF
PDCHi
represents the number of already allocated EGPRS TBFs on the
PDCH i
=
+
n
1 i
PDCHi 1 NB_TBF
1
=
+
n
1 i
PDCHi 1 NB_TBF
1
Appendix
1 2 73
Candidate TS Allocation Sorting
The criteria of the TBF radio resource allocation/reallocation algorithm
are throughput-based:
ALPHA/ For ASAP policy only: the candidate time slot allocations, which are on
some TRXs for which (Established_Nb_GCH - Nb_MPDCH) is greater than
Nb_GCH_For_TBF_Estab are preferred
A/ For UL GPRS TBF establishment / reallocation only: the candidate time slot
allocations, which have the lowest number of PDCHs in the EGPRS state are
preferred
B/ the candidate time slot allocations, which have the highest available throughput in
the direction of the bias are preferred
C/ the candidate time slot allocations, which have the highest available throughput in
the direction opposite to the bias are preferred
D/ the candidate time slot allocations, which are on the TRX with the highest
priority, are preferred
E/ for EGPRS TBFs establishments only: the candidate time slot allocations, which
have the lowest number of GPRS TBFs in the direction of the bias, are preferred
F/ combinations with the PDCHs that have the lowest index are preferred
Exercise1 Exercise2
When evaluating criterion [F], the concurrence constraints imposed by the MS multislot class (if it is known) or
by the default multislot class (if the MS multislot class is not known) shall be taken into account. This will
indeed avoid unnecessary subsequent T2 TBF reallocations (after having established an incoming TBF without
concurrent TBF).
Criterion [DTM A]: The TS of a candidate timeslot allocation supporting the TCH shall not be taken into
account in the evaluation of this criterion.
This criterion is only relevant for:
GPRS DTM allocation request
T3 GPRS TBF reallocation request for an MS in DTM mode when considering the UL direction of a candidate
timesolt allocation.
Criterion [DTM TCH 1]: Nb_BE_TBF_XL indicates the total number of BE TBFs (GPRS or EGPRS) which have some radio
resources allocated on the considered PDCH in a given direction.
Criterion [DTM TCH 2]: This criterion is only applicable for an MS whose DTM [E]GPRS multislot class is 11.
This criterion shall not be applied for an MS whose DTM [E]GPRS multislot class is 5 or 9.
This criterion has for goal to allow (if possible) a future T3 reallocation of the UL TBF of the DTM MS from DA
to EDA mode
Example :
Criterion [DTM TCH 3]: For an MS whose DTM [E]GPRS multislot class is 11, criterion [DTM TCH 2] will have
precedence over this criterion, thus preventing (if possible) the usage of the leftmost TS of the TRX of a
TCH allocation.
1 2 74
Candidate TS Allocation Sorting [cont.]
The criteria of the TBF radio resource allocation/reallocation algorithm
in case of DTM mode are throughput-based:
DTM A/ The candidate time slot allocations, which have the lowest number of PDCHs
in the EGPRS state are preferred
DTM B/ the candidate time slot allocations, which have the highest available
throughput in the direction of the bias are preferred
DTM C/ the candidate time slot allocations, which have the highest available
throughput in the direction opposite to the bias are preferred
DTM TCH 1/ the candidate time slot allocations for which (Nb_BE_TBF_DL +
Nb_BE_TBF_UL)
Is the lowest on the TS supporting the TCH are preferred
DTM D/ the candidate time slot allocations, which are on the TRX with the highest
priority, are preferred
DTM TCH 2/ for an MS class 11, the candidate time slot allocations whose TCH is
located on TS(n), with n>=1 and with TS(n-1) valid to support TBFs resources in both
UL and DL are preferred
DTM TCH 3/ the candidate time slot allocations whose TCH has the lowest TS index
(on a given TRX) is prefered
B10
If only TS0 and TS1 are allocated, a DTM
request for a MS class 11 will be reserved on
TS0 (DL and UL), TCH on TS1. If a third TS is
allocated, a T3 reallocation of the UL TBF to
EDA will be possible
1 2 75
Re-allocation
4 different TBF reallocations are permanently activated:
T1: reallocation to maintain a TBF alive despite the CS preemption of some
RTSs or of some GCHs in the cell
T2: reallocation of an on-going TBF when establishing a concurrent TBF
T3: reallocation useful to
Establish a new M-EGCH link for one of the TRXs of the cell
Perform a radio de-fragmentation process
Provide a higher throughput, if it is possible, to a TBF
Reallocate the UL TBFs established in the cell
From DA to EDA mode, or from EDA to DA mode
T4: reallocation to move a UL GPRS TBF sharing one PDCH with a DL EGPRS
TBF onto PDCHs which do not support a DL EGPRS TBF. It concerns only GPRS
TBFs
In case of DTM mode, reallocations are forbidden (MR1)
B10
To be candidate to subsequent resource re-allocation (T3 and T4), the following conditions have to be met:
the TBF established in the biased direction is marked with subsequent allocation.
more than N_CANDIDATE_FOR_REALLOC bytes have been transferred for the TBF in the biased direction.
T3192 is not running (specific to UL TBF re-allocation when T3192 is running for the DL TBF).
Note: the case where an UL TBF is established using EDA, the MS bias become equal DL and the DL TBF
(concurrent of the UL TBF) is released is neglected. In this case, as there is no TBF established in the direction
of the bias (DL), the MS will not be candidate for T3 reallocation, and the reallocation from EDA to DA will not
operate for the UL TBF, even if the usage of EDA is no longer valid for this UL TBF.
The subsequent re-allocation is done whether or not the TBF corresponds to the bias transfer direction of the
MS.
N_CANDIDATE_FOR_REALLOC default value = 200 Bytes, it cannot be set at OMC-R level.
1 2 76
Re-allocation [cont.]
T3 TBF reallocation:
A T3 TBF reallocation is based on the following principles:
Computing of a THROUGHPUT_RATIO (= Allocated_Throughput /
Optimal_Throughput) to know how sub-optimal a TBF allocation is
A T3 TBF reallocation will only be allowed if a significant THROUGHPUT_RATIO gain is
reached. The minimal gain is set by the system parameter: MIN_THROUGHPUT_GAIN
(= 40%)
THROUGHPUT_RATIO:
for each MS which is candidate for a T3 TBF reallocation, a throughput ratio is calculated.
this throughput ratio is useful to:
validate the candidate TBF allocations when playing the radio resource reallocation algorithm.
sort the T3 TBF reallocation requests within the L5 and L6 lists: low value of the throughput ratio means
high priority of the request.
THROUGHPUT_RATIO = ALLOCATED_THROUGHPUT / OPTIMAL_THROUGHPUT
ALLOCATED_THROUGHPUT is the throughput currently allocated to the TBF in the direction of the bias
and is equal to potential_throughput_PDCH * available_capacity_candidate_XL.
OPTIMAL_THROUGHPUT is the optimal throughput that could be potentially allocated to the TBF in the
direction of the bias by considering its multislot class and is equal to potential_throughput_PDCH *
n_MS_requested.
Best candidate allocation computation:
a candidate TBF allocation shall fulfill the following conditions:
NEW_THROUGHPUT_RATIO min(1, (1+MIN_THROUGHPUT_GAIN ) * CURRENT_THROUGHPUT_RATIO).
NEW_THROUGHPUT_RATIO is the throughput ratio of the candidate TBF allocation.
CURRENT_THROUGHPUT_RATIO is the throughput ratio of the current TBF allocation.
MIN_THROUGHPUT_GAIN is an O&M parameter.
1 2 77
Re-allocation: Example
Initial situation:
3 MSs (MSa, MSb, and MSc), all GPRS and (4+1)
MSC is the most impacted by the multiplexing in terms of throughput
Final Situation:
MSC is candidate for T3 reallocation
A new TRX will be established (cf. Optimal policy) and MSc will then be reallocated
on this new TRX
0 1 2 3 4 5 6 7
DL
UL
MSa MSa MSa MSa MSb MSb MSb MSb
MSc MSc MSc MSc
MSc MSb MSa
0 1 2 3 4 5 6 7
DL
UL
0 1 2 3 4 5 6 7
DL
UL
MSa MSa MSa MSa MSb MSb MSb MSb
MSb MSa
0 1 2 3 4 5 6 7
DL
UL
MSc MSc MSc MSc
MSc
1 2 78
4 TBF Release Routine
1 2 79
Justification
Wap access to home page without any feature
With Delayed DL TBF Release (B7)
With Delayed DL TBF TBF Release & (I) Extended UL TBF Mode (B10)
Typical gain on Wap access to home page:
~8 seconds with Delayed DL TBF Release
+ ~2 seconds with Extended UL TBF Mode
New B10 feature to enhance MS battery saving
UL
DL
B10
1 2 80
Delayed DL TBF Release
(1): There is no more DL LLC PDU stored for the MS. The BSS sends the last segment of the last useful RLC
block. This block contains the last segment of the last useful DL LLC PDU, completed by a dummy LLC PDU
in order to maintain the DL TBF alive. The Final Block Indicator is not set (FBI=0) and a polling is requested
to the MS. T_Delayed_DL_TBF_Pol_Initial is activated (default value = 100 ms).
(2): When the MS has acknowledged the last useful DL RLC block, T_Delayed_DL_TBF_Rel is activated
(duration of the delayed DL TBF release phase).
(3): At T_Delayed_DL_TBF_Pol_Initial expiry, a new RLC block containing one or more dummy LLC PDUs is sent
to the MS. This RLC block contains a polling indication so that the MS can request a UL TBF establishment, if
required. T_Delayed_DL_TBF_Pol (default value = 200 ms) is activated.
(4): At T_Delayed_DL_TBF_Rel expiry, a last DL RLC block is sent with the Final Block Indicator set (FBI = 1),
indicating the end of the DL TBF. The normal release procedure then applies.
1 2 81
Delayed DL TBF Release [cont.]
Artificial extended DL TBF duration aiming at coping with jerky DL
traffic from the CN
Procedure:
the last DL RLC blocks are marked with FBI=0
the TBF state goes from Active to Delayed
periodical Dummy DL RLC blocks in polling (S/P=1) sent by the MFS to trigger
acknowledgement from the MS (FAI=0)
when a new DL LLC PDU arrives at the MFS, the useful RLC Block transfer is
resumed
the TBF state goes from Delayed to Active
The MS does not take into account Dummy LLC PDU during the delayed
release phase
Jerky LLC PDU delivery at MFS due to buffer capacities of servers, SGSN and MFS. A TCP segment can generate
up to 3 LLC PDUs. Also called Bursty traffic. HTTP and WAP services are likely to benefit from this feature.
FBI: Final Block Indicator (RLC header)
FAI: Final Acknowledgement Indicator
S/P: triggers polling (packet Ack/Nack message) when set to 1
Periodical sending of DL RLC Blocks = polling period calculation: the MFS takes into consideration T3190
(guarding timer between 2 valid data received from the Network) in addition to the requirement of receiving
at least one block every 360 ms (78 TDMA frames). (T3190n = 5 s (Alcatel recommended value), it cannot be
set at OMC-R level).
T3190n = Timer used in the procedure DL TBF abnormal release: when the DL TBF is cut due to the radio
link quality or loss of the MS, the TFI and TAI cannot be reallocated during T3190n. The default value is 5s and
it cannot be set at the OMC-R level.
The UL Delayed TBF release (scheduling of additional USF) is only possible for Rel-4 MS.
1 2 82
End of delayed released period when T_Delayed_DL_TBF_Rel expires
T_Delayed_DL_TBF_Rel = T_NETWORK_RESPONSE_TIME
The MFS sends a Dummy UI command marked with FBI=1, S/P=1
Acknowledged mode:
The MS sends the last Packet DL Ack/Nack message (FAI=1)
Non-Acknowledged mode:
The MS sends the last Packet Control Ack message
T3192n and T3192 are triggered (Fast DL re-establishment)
T_NETWORK_RESPONSE_TIME corresponds to the time difference between a command sent to the SGSN and
the response received at the MFS. The default value is 700ms but it can be set at OMC-R level and can be
tuned according to Gb traces.
1 2 83
RRM periods on MFS side:
T_DELAYED_DL_TBF_POL_INITIAL (=60ms): the time that the MFS shall wait
before sending the first RLC data block containing only LLC Dummy UI
2 timers are used to define the period between 2 DL Dummy UIs sent to the MS:
T_MIN_POLL (=60ms), in case of the MS is alone on the PDCH which carries the
PACCH
T_DELAYED_DL_TBF_POL (=200ms) in case of the MS is multiplexed on the PDCH
which carries the PACCH
T_DELAYED_DL_TBF_POL_UL (=2s): the period between 2 DL Dummy UIs sent to
the MS, when there is an on-going UL TBF
Upon each expiry of T_DELAYED_DL_TBF_POL (the timer reaches T_DELAYED_DL_TBF_POL_INITIAL or
T_DELAYED_DL_TBF_POL), a new Dummy UI command is inserted and T_DELAYED_DL_TBF_POL is restarted.
T_DELAYED_DL_TBF_POL_INITIAL = 60 ms
T_DELAYED_DL_TBF_POL = 200 ms
T_MIN_POLL = 60 ms
T_DELAYED_DL_TBF_POL_UL = 2000 ms
All these timer values are default ones and they cannot be set at OMC-R level.
T_DELAYED_DL_TBF_POL is used to:
give the opportunity to the MS to request a UL TBF through the Packet DL Ack/Nack acknowledging the
polling, without too much disturbing the other TBFs (data transfer for the DL and USF scheduling for the UL)
multiplexed on the same PDCH (--> not too short period for Dummy UI commands).
maintain the DL TBF at MS level (re-activation of T3190 timer (5s) in the MS) (--> period for Dummy UI
commands < 5s).
T_MIN_POLL is applied when the PDCH corresponding to the PACCH of the considered DL TBF is not shared
with another enabled DL TBF and when there is no activated UL TBF on this PDCH (ie, no UL TBF in enabled or
extended mode, for which USF may be scheduled).
1 2 84
DL TBF Extension
(1): The DL TBF is in delayed DL TBF release phase. Periodically Dummy UI Command messages are sent to the
MS with polling indication to give to the MS the opportunity to send a UL TBF request.
(2): The MS uses a Packet DL Ack/Nack to request a UL TBF. The UL TBF is established and
T_Delayed_DL_TBF_Rel is stopped (the DL TBF remains in delayed DL TBF release state, during the UL TBF).
(3): At UL TBF release, the timer T_Delayed_DL_TBF_Rel is re-activated.
(4): When a DL LLC PDU is received, the first DL RLC data block can be immediately sent and
T_Delayed_DL_TBF_Rel is stopped.
(5): T_Delayed_DL_TBF_Rel is stopped, when the first UL RLC data block is received.
1 2 85
DL TBF Extension [cont.]
When a UL TBF is established during a delayed DL TBF release:
T_Delayed_DL_TBF_Rel is stopped and reset
The delayed DL TBF release state is maintained during the UL TBF
DL Dummy UIs are sent every T_DELAYED_DL_TBF_POL_UL
The aim of this timer is just to maintain the DL TBF at MS level (must be lower than
T3190)
Therefore T_DELAYED_DL_TBF_POL_UL > T_DELAYED_DL_POL
At the end of the UL TBF, T_Delayed_DL_TBF_Rel is restarted
Exercise
The aim of this function is to avoid the case where a UL TBF is established on the PACCH of a DL TBF which is
at the end of its delayed DL TBF release phase.
Indeed in this case, the subsequent DL LLC PDU (i.e., corresponding to a server response) may be received
after the release of the DL TBF.
1 2 86
Fast DL TBF Re-establishment
After DL TBF release, the following timers are considered
MS side
T3192 started after sending of final Packet DL Ack/Nack message (FAI=1)
during T3192 the MS listens to the PDCH carrying the PACCH blocks of its
last DL TBF
T3192 = 500 ms (default value which can be set at OMC-R level).
1 2 87
Fast DL TBF Re-establishment [cont.]
MFS side
T3192n started after reception of final Packet DL Ack/Nack message
Wait for reuse of MS radio resources (PDCHs, TAI, TFI)
If a DL LLC PDU is received by the MFS, a fast DL TBF re-establishment is
triggered on the PACCH
T3192n = T3192 (T_Round_Trip_Delay + T_Fast_DL_Margin)
During T3192n, a UL TBF establishment is not possible
During the on-going of T3192n, no UL TBF establishment procedure can be proceeded. This is a limitation to
fast switching from DL TBF to UL TBF during the MS-GSS signaling procedure (location update for example). In
order to avoid a too long duration of these procedures, the MFS anticipates the UL TBF establishment by
starting the procedure before the end of the DL TBF release.
T3192n takes into account the trip time needed for Packet DL Ack/Nack message from the MS to the MFS
(T_Round_Trip_Delay + T_Fast_DL_Margin) AND trip time needed for Packet DL Immediate Assignment
message from the MFS to the MS (T_Round_Trip_Delay + T_Fast_DL_Margin).
Round_Trip_Delay (MFS-MS) = 160 ms (default value which can be set at OMC-R level).
T_Fast_DL_Margin = 50 ms (default value which cannot be set at OMC-R level).
Note: during T3192n seconds, the Timing Advance is monitored. Even so, if TAI occurs, the MS must send its
Access Burst for the Timing Advance calculation by the BTS. The MS shall listen to the TA Messages in the DL.
1 2 88
Non-DRX Mode after Packet Data Transfer
Discontinuous Reception (DRX mode):
Used in GSM to increase the battery autonomy on an MS as in GSM CS: the
MS listens only to its Paging Group
Downlink TBF establishment through PCH long as compared with the TBF
duration
The MFS establishes a DL TBF on the first available PCH message of an MS
Paging group
Non-DRX:
Continuous monitoring of AGCH messages by the MS
The MFS establishes a DL TBF on the first available AGCH block (without
MPDCH) or the first PPCH occurrence (with MPDCH)
This feature outlines one of the major differences between the GPRS service (non connected mode) and the
GSM service (connected mode). The DRX mode is highly recommended in GSM to save the cell battery when it
may be a handicap in GPRS (where the paging is likely to occur more frequently).
1 2 89
Non-DRX Mode after Packet Data Transfer [cont.]
Non-DRX mode:
Non-DRX period
Min (NON_DRX_Timer; DRX_TIMER_MAX)
Non-DRX period computed by the MFS and sent in Packet DL Immediate Assignment
message
The DRX mode of an MS is evaluated each time the MFS receives DL LLC PDU
from the SGSN
The MFS keeps the MS context until expiry of:
DRX_TIMER_MAX if NON_DRX_Timer unknown for the MS
Non-DRX period otherwise (provided within the DL LLC PDU)
DRX_TIMER_MAX limited to 4 seconds, broadcast on SI13
NON_DRX_Timer is unknown for the MFS when after the release of an uplink TBF, no DL concurrent TBF was
Established, or after the release of a downlink TBF when the DL LLC PDUs do not convey the DRX parameters.
When the MFS assesses that the MS returns to the DRX mode during the transmission of the assignment
message, the message is sent to the PCH or PPCH channel. The MFS shall then take into account the 95% AGCH
or PPCH queuing time (about 400 ms) in addition to the round trip time delay measured at RRM level (about
160 ms).
Assuming a Non-DRX period of 2 seconds, this means that the downlink LLC PDU shall be received within 1.4
second to speed up the establishment of the DL TBF.
DRX_TIMER_MAX = 2 s (Alcatel recommended value) and it can be set at OMC-R level.
1 2 90
DL TBF Release: Summary
DL TBF
T_NETWORK_RESPONSE_TIME
TBF delayed
release
Fast DL TBF
establishment via PACCH
TBF active
DL TBF
T3192
Fast DL TBF establishment
via AGCH or any PPCH
DL TBF
T3192
Non-DRX mode
DRX_TIMER_MAX
DL TBF
T3192
Non-DRX mode
DRX_TIMER_MAX
DL TBF establishment
via PCH or PPCH
of MS paging group
The tables below indicate examples of the expected DL TBF establishment duration with or without the
feature.
1 2 91
Delayed UL TBF Release: Without Extended Mode
The UL TBF release is delayed when:
T_DELAYED_FINAL_PUAN <> 0
No concurrent DL TBF:
Is established
Is being established
Is being Released
During the delayed UL TBF release:
The MFS can establish a DL TBF on the PACCH/DL of the UL TBF
The DL TBF establishment is speeded up
The UL Delayed TBF release (scheduling of additional USF) is only possible for a Rel-4 MS.
1 2 92
Delayed UL TBF Release: Without Extended Mode [cont.]
No DL LLC PDU is received during the delayed final PUAN phase
T3180n
T3180
P. UL Ack/Nack (FAI=0, SSN = n) (3)
RLC/MAC block (BSN=n, CV=0) (1)
(4)
Packet Control Ack (6)
final P. UL ACK/NACK + polling (5)
MS MFS SGSN
LLC PDU (last LLC) (2)
T_DELAYED_FINAL_PUAN
(7)
(1): The last UL LLC PDU is received by the RLC. The RLC maintains the UL TBF alive since a normal end is not
allowed.
(2): The UL LLC PDU is sent to the RRM. A flag is set by the RLC, in order to notify the RRM that it is the last
UL LLC PDU of the TBF.
(3): A Packet UL Ack/Nack is sent to the MS, without polling, with FAI=0.
This message does not acknowledge the last block (n).
(4): Upon receipt of the last UL LLC PDU, the RRM starts an instance of the timer T_DELAYED_FINAL_PUAN.
The UL LLC PDU is forwarded to the SGSN.
(5): At T_DELAYED_FINAL_PUAN expiry, the RRM requests the RLC to release the UL TBF, by sending a
PCC_RLC_Activate-req allowing the RLC to perform a normal TBF end.
The RLC sends the final packet UL Ack/Nack to the MS and waits for Packet Control Acknowledgement.
T3180n is activated (T3180n = T3180 - Round Trip Delay - T_DELAYED_FINAL_PUAN).
(6): The MS acknowledges the receipt of the final PACKET UL Ack/Nack message.
(7): The RLC notifies the RRM about the release of the UL TBF. The resources of the UL TBF are released. The
RRM informs the BSSGP layer about the release of the UL TBF, and the BSSGP de-allocates the corresponding
throughput. T3180n is stopped.
1 2 93
Delayed UL TBF Release: Without Extended Mode [cont.]
Delayed final PUAN, with DL TBF establishment
T3180n
T3180
P. UL Ack/Nack (FAI=0, SSN = n) (3)
RLC/MAC block (BSN=n, CV=0) (1)
(5)
(4)
final P. UL ACK/NACK + polling
LLC PDU (last LLC) (2)
PACKET DOWNLINK ASSIGNMENT (6)
MS MFS SGSN
DL LLC PDU
(8)
(10)
(1): The last UL LLC PDU is received by the RLC. The RLC maintains the UL TBF alive since normal end is not
allowed.
(2): The UL LLC PDU is sent to the RRM. A flag is set by the RLC, in order to notify the RRM that it is the last
UL LLC PDU of the TBF.
(3): A Packet UL Ack/Nack is sent to the MS, without polling, with FAI=0.
This message does not acknowledge the last block (n).
(4): Upon receipt of the last UL LLC PDU, the RRM starts an instance of the timer T_DELAYED_FINAL_PUAN.
The UL LLC PDU is forwarded to the SGSN.
(5): A DL LLC PDU is received by the MFS while the timer T_DELAYED_FINAL_PUAN is running.
(6): Radio resources are requested to RRM-PRH. Upon RRM-PRH response, the RRM-PCC stops the timer
T_DELAYED_FINAL_PUAN, delays the release of the UL TBF until the completion of the DL TBF establishment
procedure, establishes the DL TBF on the PACCH/DL of the UL TBF.
If T_DELAYED_FINAL_PUAN expires before the response of the RRM-PRH, then the RRM-PCC requests the
RLC to release the UL TBF, by sending a PCC_RLC_Activate-req allowing the RLC to perform a normal TBF
end. In this case, at RRM-PCC response, the DL TBF will be established on CCCH, at the end of the UL TBF
release.
(7): The MS acknowledges the receipt of the assignment message and listens to the DL resources. The BSS
sends a Packet Power Control and Timing Advance and then begins the DL data transfer.
(8): Upon receipt of the PACKET CONTROL ACKNOWLEDGEMENT, the RRM immediately requests the RLC to
release the UL TBF, by sending a pcc-rlc-activate-req primitive allowing the RLC to perform a normal TBF
end. The RLC sends the final PACKET UL Ack/Nack to the mobile station and waits for a PACKET CONTROL
ACKNOWLEDGEMENT.
(9): The MS acknowledges the receipt of the final PACKET UL Ack/Nack message.
(10): The RLC notifies the RRM about the release of the UL TBF. The RRM stops T3180n. The resources of the
UL TBF are released. The RRM informs the BSSGP layer about the release of the UL TBF, and the BSSGP de-
allocates the corresponding throughput.
1 2 94
Delayed UL TBF Release: with Extended Mode
Principle
At the end of the active phase (CV=0)
The MFS continues to schedule some USFs
To allow the MS to send some dummy RLC blocks
P. UL Ack/Nack (FAI=0, SSN = n+1)
RLC/MAC block (BSN=n, CV=0)
Packet Control Ack
final P. UL ACK/NACK + polling
LLC PDU (last LLC)
T_MAX_EXTENDED_UL
USF
Dummy RLC data block
MS MFS SGSN
USF
.
.
.
start
expiry
The aim of this feature is to extend the duration of the UL TBF in order:
To quickly restart data transmission in UL if higher layers in the MS deliver new data, without having to re-
establish a new UL TBF, after the countdown procedure has started.
To maintain the UL TBF established, some time after the last block (CV=0) has been acknowledged by the
network.
This feature allows to improve the access time to the GPRS network. It also improves the throughput in some
cases.
The feature is described in 3GPP TS 44.060 - V4.18.0. It applies for R4 MS.
1 2 95
Delayed UL TBF Release: with Extended Mode [cont.]
The UL transfer can resume at any time during the extended phase
LLC PDU (last LLC)
T_MAX_EXTENDED_UL
USF
MS MFS SGSN
USF
USF
RLC/MAC block (BSN=n+1)
start
stop
USF
RLC/MAC block (BSN=n+2)
.
.
.
Active UL
data transfer
Extended UL
data transfer
Active UL
data transfer
LLC PDU
1 2 96
Conditions to operate
EN_EXTENDED_UL_TBF = enabled
Rel-4 MS
The MS has to know if the BSS supports the feature
The BSS capability (NW_EXT_UTBF) is broadcast on BCCH (SI13)
The BSS has to know if the MS supports the feature
The MS radio access capability is
received at downlink TBF establishment in the first downlink PDU, or
retrieved through the Radio Access Capability Update which involves the SGSN
If EN_RA_CAP _UPDATE = enabled
If one of these 4 conditions is not fulfilled, the normal UL TBF release is
performed, as in B8 (T_DELAYED_FINAL_PUAN is applied)
TLLI context retrieval procedure
This procedure has been developed in B8 for the feature full intra PDU re-routing.
The TLLI is known in the SGSN and by one GPU in the MFS. The TLLI retrieval procedure allows to retrieve
information linked to the TLLI, among which the Radio Access Capability from another GPU.
This procedure can be triggered at uplink TBF establishment, as soon as the contention resolution is
completed.
Radio Access Capability Update
Enabled or disabled the Radio Access Capability update on Gb by flag, EN_RA_CAP _UPDATE. It is
recommended to enabled this flag if EN_EXTENDED_UL_TBF is enabled and Radio Access Capability update is
supported by the SGSN.
At UL TBF establishment, immediately after the contention resolution procedure, the radio access
capability update procedure is triggered in the BSS. The BSS requests an MSs current Radio Access
capability and/or its IMSI by sending to an SGSN an RA_CAPABILITY_UPDATE, which includes the TLLI of the
MS and a Tag. Then it starts timer T5_RA_CAP_UPDATE (value = 5s). In case of timer expiry, the BSS shall
repeat the request up to RA_CAPABILITY_UPDATE_RETRIES times (value = 3).
The SGSN shall respond by sending an RA_CAPABILITY_UPDATE_ACK, which includes the TLLI of the MS, the
Tag received in the corresponding RA_CAPABILITY_UPDATE.
When the SGSN answers, the MS Radio Access capability is updated and the Extended UL feature can be
used if the GERAN Feature Package 1 bit is set. Otherwise, the MS does not support the extended uplink
feature.
1 2 97
The way to schedule the USFs in extended UL TBF mode:
Scheduled only on the PDCH which carries the PACCH
IF the PDCH supports uplink TBFs which are all in extended mode AND
EN_FAST_USF_UL_EXTENDED = enabled THEN
the throughput in radio blocks is equally shared between MSs
So USFs are scheduled as follows:
One MS in extended mode on PACCH: USF scheduled every 20ms
Two MSs in extended mode on PACCH: USF scheduled every 40ms
n MSs in extended mode on PACCH: USF scheduled every n x 20ms
ELSE (if EN_FAST_USF_UL_EXTENDED = disabled OR if the PDCH supports at
least one MS which is in UL transfer)
A period T_EXTENDED_UL_TBF_POL (200 ms) is used to schedule the USFs for all the
MSs in extended mode
The remaining bandwidth is used for MSs in transfer
RRBP mechanism has priority over USF scheduling
This means the USF scheduling may be shifted if RRBP request from the RLC
1 2 98
Delayed UL TBF Release: Improved Extended Mode
Principle: make optional the MS answers to USF
BSS sends first USF at each block or every T_EXTENDED_UL_TBF_POL
In case of no MS answer, N3101 is incremented
When N3101 reaches N3101_POLLING_THR, BSS sends polling (PUAN with
polling request) every T_UL_RLS_EUTM
In case of no answer to the polling, N_POLLING_EUTM is incremented
When N_POLLING_EUTM_LIMIT is reached, Tbf is abnormally released
Regular USF sent allows MS to resume UL traffic at any time (but N3101 is no
more incremented when no MS answer)
B10
Principle is to make optional MS answers to USF in Extended UL phase
When an MS enters Tbf UL releasing phase, BSS knows only if MS supports Extended UL (but can not know if
the MS supports Improved or Normal Extended UL mode)
1 2 99
Delayed UL TBF Release: Improved Extended Mode [cont.]
UL transfer can resume at any time during the improved extended
phase
Packet Control Ack
P. UL ACK/NACK + polling
LLC PDU (last LLC)
T_MAX_EXTENDED_UL
USF
MS MFS SGSN
USF
.
.
.
start
NO ANSWER N3101 ++
NO ANSWER N3101 ++
N3101_POLLING_THR
P. UL ACK/NACK + polling
T_UL_RLS_EUTM
USF
USF
USF
Packet Control Ack
B10
When an MS enters Tbf UL releasing phase, BSS knows only if MS supports Extended UL (but can not know if
the MS supports Improved or Normal Extended UL mode)
1 2 100
UL TBF Release: Summary
Delayed final PUAN (without extended mode)
Extended UL TBF mode
UL TBF
release
TBF active
UL TBF
release
T_MAX_EXTENDED_UL
TBF active TBF extended
The UL TBF can be released before the expiry of the timer T_MAX_EXTENDED_UL: in case of a concurrent DL
TBF is present and after the completion of DL delayed phase, the expiry of T3192 triggers the release of the
UL TBF.
Consequently, the uplink TBF in extended mode is released when either T3192 expires or
T_MAX_EXTENDED_UL expires.
1 2 101
5 Exercises
1 2 102
5 Exercises
(E)GPRS Channels
UL PDTCH and PACCH multiplexing on SPDCH:
UL transfer? DL transfer?
Downlink Uplink
Block number
TFI
USF RRBP
Block n
Block n+1
Block n+2
Block n+3
Block n+4
Block n+5
Block n+6
TFI a USF j
TFI b USF k
TFI a
USF j + 3
TFI b USF k
TFI b ???
TFI b USF j
TFI a USF k
false
false
false
false
false
false
PDTCH / PACCH a
PDTCH / PACCH b
PDTCH / PACCH a
PDTCH / PACCH b
PDTCH / PACCH b
PDTCH / PACCH a
PDTCH / PACCH b
RLC header MAC header
?
?
?
?
?
?
?
Block Content?
Back
1 2 103
5 Exercises
Autonomous Packet Resource Allocation
Considering one cell with the following configuration:
4 TRXs in the DCS1800 band
PS_PREF_BCCH_TRX = 0
NB_TS_MPDCH = 0
In the next slide, find the rank of each TRX
Time
allowed:
10 minutes
1 2 104
5 Exercises
Autonomous Packet Resource Allocation [cont.]
0 1 2 3 4 5 6 7
BCCH SDCCH TRX1
TRX2 SDCCH
TRX3
TRX4
TRX_PREF_MARK
0
1
0
1
TRE G3
TRE G4 MP
TRE G3
TRE G4 MP FR
DR
FR
DR
RANK= ?
RANK= ?
RANK= ?
RANK= ?
Back
1 2 105
5 Exercises
Autonomous Packet Resource Allocation [cont.]
Inputs:
NB_TS = 14, AV_USED_CS=0, AV_USED_PS=11
MIN_SPDCH=0
MAX_SPDCH=14
MAX_SPDCH_HIGH_LOAD=2
HIGH_TRAFFIC_LOAD_GPRS=80%
THR_MARGIN_PRIO_PS=10%
Find the value of:
MARGIN_CS, MARGIN_PRIORITY_PS
MAX_SPDCH_LIMIT_CS, MAX_SPDCH_LIMIT_PS
MAX_SPDCH_LIMIT
Any Remark?
Define a rule (relationship between some parameters) to fix this non-
optimal setting
Time allowed:
30 minutes
Back
1 2 106
5 Exercises
TBF Radio Resources Allocation and Re-allocation
GPRS allocation on BCCH TRX (7 PDCHs are allocated)
UL TBFs 1 to 11 are established one after the other
It is assumed that a concurrent DL TBF is established after the UL, and before
the next UL
All transfers are deemed DL biased
Inputs:
BCCH TRX, 1 unique SPDCH group
NB_TS_MPDCH = 0
MAX_XX_TBF_PER_SPDCH = 5
En_Fast_Initial_GPRS_Access = disabled
The MS GPRS multislot class is given below:
Time
allowed:
20 minutes
Back
1 2 107
5 Exercises
TBF Radio Resources Allocation and Re-allocation [cont.]
Fill in the initial TBF allocation TS mapping UL/DL
DL
UL
1 2 108
5 Exercises
GPRS/EGPRS allocation case:
Cell with 2 PS capable TRXs:
TRXa: EGPRS capable, SPDCH group = TS0 to TS7
TRXb: non-EGPRS capable, SPDCH group = TS0 to TS7
Ordered TRX list: TRXa > TRXb
En_Fast_Initial_GPRS_Access = enabled
MIN_PDCH = 1
NB_TS_MPDCH = 0
MAX_GPRS_CS = CS-3;
MAX_EGPRS_MCS = MCS-6
Default MS multislot class = 4 + 1
All the MSs are 4 + 1 MSs
Time
allowed:
20 minutes
Back
1 2 109
5 Exercises
MS constraints:
Consecutive establishments:
MSa: GPRS UL TBF followed by DL TBF
MSb: EGPRS UL TBF followed by DL TBF
MSc: GPRS UL TBF followed by DL TBF
MSd: EGPRS UL TBF followed by DL TBF
Bias = DL
Time allowed:
20 minutes
Rx Mx
0 1 2 3 4 5 6 7
DL
Tx
UL
0 1 2 3 4 5 6 7
Ttb Tra
Rx Rx Rx
1 2 110
5 Exercises
Fill in the initial TBF allocation TS mapping UL/DL
DL
0 1 2 3 4 5 6 7
PDCH
UL
UL
DL
TRXa
EGPRS
TRXb
GPRS
Rank
1
2
1 2 111
5 Exercises
DL TBF Release Routine
DL TBF routine in acknowledged mode
Fill in the blanks in the diagram of a DL TBF displayed on the next slide:
name of the timers T_?????
states of the DL TBF? ACTIVE, DELAYED, RELEASED
Time
allowed:
10 minutes
1 2 112
5 Exercises
DL TBF Release Routine [cont.]
Back
1 2 113
Self-assessment on the Objectives
Please be reminded to fill in the form
Self-Assessment on the Objectives
for this module
The form can be found in the first part
of this course documentation
1 2 114
End of Module
Radio Resource management

2 3JK10864AAAAWBZZA Radio Resource Management

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

2 3JK10864AAAAWBZZA Radio Resource Management

Hochgeladen von

Copyright:

Verfügbare Formate

Section 1 Module 2 Page 1

All Rights Reserved Alcatel-Lucent 2008

Das könnte Ihnen auch gefallen