3-Claro B9 RRM Algorithms

Radio Resource Management Algorithms in B9
B9 Claro Workshop - February 14th 2006
All rights reserved 2005, Alcatel
Agenda
Page 2
Autonomous Packet Resource allocation

Computation of MAX_SPDCH_LIMIT Selection of allocated PDCH Impacts on CS Preemption algorithm
TBF allocation/re-allocation strategy

Transmission resources usage Best candidate allocation of radio TS Modifications of TBF reallocations algorithms Parameters & Quality of Service indicators
B9 Claro Workshop / February 14th 06
Modification of the PDCH allocation strategy
Autonomous Packet Resource Allocation

Page 3
In B8:
The BSC evaluates the number of timeslots that the MFS could use to carry PS traffic (Max_SPDCH_Dyn),
The MFS does not know which timeslots are usable for PS traffic, To serve a new TBF, the MFS needs to request new timeslots to the BSC. Event-triggered mechanism
Max_SPDCH_Dyn = 8
TS allocated to BSC
TS allocated to MFS
Autonomous Packet Resource Allocation (RAE4)

Page 4
In B9, the following new needs have appeared:

Need to know the list of basic Abis nibbles which are currently available to establish GCHs, Need to know which basic Abis nibbles are preemptable / notpreemptable for CS traffic by the BSC. This information is useful: For the QoS feature (in order to be able to ensure a given GBR for an RT PFC). To define some priorities in the Abis nibble selection (preference is given to the non-preemptable basic Abis nibbles in order to limit the interaction of CS over PS traffic). Need to accelerate TBF establishment times (the B8 round trip delay between MFS and BSC to allocate some PDCHs can be avoided).
To meet all those needs, a process called Autonomous Packet Resource Allocation has been introduced in B9.

Page 5
In B9:
The BSC evaluates a number of timeslots that the MFS can use to carry PS traffic (Max_SPDCH_Limit), Periodical exchange of messages between the BSC and the MFS:
BSC to MFS: list of RTS that the MFS can use, MFS to BSC: acknowledgement of allocated / de-allocated RTS.
The MFS knows which timeslots can be used to serve a new TBF. Periodical mechanism
Max_SPDCH_Limit = 8 TS allocated to BSC TS allocated to MFS

Page 6
CS/PS sharing is based on the evaluation of Max_SPDCH_Limit. The Max_SPDCH_Limit value:

Corresponds to a number of timeslots allocated to the MFS, Evaluated at the BSC level, Periodically, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD, Transmitted to the MFS using the RR Allocation Indication message, Comprised between Min_SPDCH and Max_SPDCH.
The evaluation of Max_SPDCH_Limit is based on:

O&M parameters (Max_PDCH, Min_PDCH, Max_PDCH_HIGH_LOAD, HIGH_TRAFFIC_LOAD_GPRS, THR_MARGIN_PRIO_PS), CS and PS load, averaged using a sliding window of size Load_EV_Period_GPRS, PS load: provided to the BSC by the RR Usage Indication message. Sharing of unused TSs between CS and PS traffic.
RAE4 : Load evaluation

Page 7
At the expiry of the TCH_INFO_PERIOD timer, the following load samples are calculated:
NB_USED_CS_TS(k) & NB_USED_PS_TS(k) NB_USED_TS(k) = NB_USED_CS_TS(k) + NB_USED_PS_TS(k) NB_UNUSED_TS(k)
k-2 k-1 k k+1 k+2
TCH_INFO_PERIOD = 5s
NB_USED_CS_TS(k) NB_USED_PS_TS(k) NB_USED_TS(k) NB_UNUSED_TS(k)
RR_ALLOC_PERIOD * TCH_INFO_PERIOD
LOAD_EV_PERIOD_GPRS = 3
AV_USED_CS_TS(k) AV_USED_PS_TS(k) AV_UNUSED_TS(k)
AV_USED_CS_TS(k+2) AV_USED_PS_TS(k+2) AV_UNUSED_TS(k+2)
for each cell, every RR_ALLOC_PERIOD * TCH_INFO_PERIOD, the BSC computes three averaged values through a sliding window of size LOAD_EV_PERIOD_GPRS (default value = 3):
RAE4 : MAX_SPDCH_LIMIT Calculation

Page 8
the BSC periodically (every RR_ALLOC_PERIOD * TCH_INFO_PERIOD) computes the number of Slave PDCHs that it can provide to the MFS: MAX_SPDCH_LIMIT
MAX_PDCH_HIGH_LOAD MAX_PDCH MIN_PDCH NB_TS_DEFINED NB_TS_MPDCH NB_TS_SPDCH
O&M parameters
AV_USED_CS_TS AV_USED_PS_TS AV_UNUSED_TS
MIN_SPDCH MAX_SPDCH NB_TS Computation of Thresholds MAX_SPDCH_HIGH_LOAD Computation of MAX_SPDCH_LIMIT MAX_SPDCH_LIMIT
Computation of CS/PS Margin
MARGIN_PRIORITY_CS MARGIN_PRIORITY_PS
THR_MARGIN_PRIORITY_CS THR_MARGIN_PRIORITY_PS
= 100 HIGH_TRAFFIC_LOAD_GPRS O&M parameter

Page 9
Two new margins are introduced, to guarantee that a certain number of timeslots are kept available for the arrival of new calls between two transmissions of the RR Allocation Indication message CS Margin
TS that should be kept at BSC for possibly incoming CS calls Computation based on HIGH_TRAFFIC_LOAD_GPRS
PS Margin
TS that should be allocated to the MFS for possibly incoming TBF Computation based on THR_MARGIN_PRIO_PS and MAX_PDCH_HIGH_LOAD

Page 10
MAX_SPDCH_LIMIT Calculation :
It can be in the range of [MIN_SPDCH, MAX_SPDCH] Unused TS are shared equally between BSC and MFS If the number of unused TS is too low (e-g high CS/PS traffic), then Margins are used
Higher priority is given to CS over PS, except when used PDCH are below Max_PDCH_High_Load
reserved for PS priority for PS priority for CS reserved for CS
MIN_SPDCH MAX_SPDCH_HIGH_LOAD MAX_SPDCH_Limit MAX_SPDCH
Agenda
Page 11


MAX_SPDCH_LIMIT TS selection
Page 12
BSC Radio Resource Allocation SPDCHs_Allocation

TCH_INFO_PERIOD x RR_ALLOC_PERIOD TCH_INFO_PERIOD
MFS
Radio Resource Allocation Indication message:

Periodically, every TCH_INFO_PERIOD * RR_ALLOC_PERIOD, SPDCHs_Allocation bitmap: contains information whether a timeslot is allocated to the MFS or not.
Radio Resource Usage SPDCHs_Confirmation SPDCHs_Usage
TCH_INFO_PERIOD
Radio Resource Usage Indication message:

Periodically, every TCH_INFO_PERIOD or in response to a RR Allocation Indication, SPDCHs_Confirmation bitmap: indicates or confirms whether a timeslot is allocated or not to the MFS, SPDCHs_Usage bitmap: provides occupancy states of timeslots allocated to the MFS.
Radio Resource Allocation SPDCHs_Allocation Radio Resource Usage SPDCHs_Confirmation SPDCHs_Usage
MAX_SPDCH_LIMIT TS selection : ordering

Page 13
The way to set the priority of the PS capable TRX (TRX_PREF_MARK = 0) is slightly modified in B9 release with the introduction of a frequency band criterion:
PS_PREF_BCCH_TRX HW TRE capability (G4 HP -> G4 MP -> G3) DR TRE capability (FR TRX -> DR TRX) E-GSM TRX preference (new in B9, E-GSM TRX -> P-GSM/GSM850/DCS TRX) TRX having the maximum number of consecutive SPDCHs TRX identity (low TRX id -> high TRX id)
PS TS and TRX ordering:

First step : the TRX with lowest rank (see above) is selected first Second step: once the TRX has been selected, the TCH/SPDCH timeslots having the lowest timeslot index, e-g. located at the most left side is selected first
MAX_SPDCH_LIMIT TS selection : PS TS zones

Page 14
example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 10

PS traffic zone MAX_SPDCH_LIMIT zone Non pre-emptable PS zone PS 1 PS 2 CS 3 PS 4 5 TRX2 PS 6 CS 7 8 PS 9 PS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
MAX_SPDCH_HIGH_LOAD zone:
the MAX_SPDCH_HIGH_LOAD consecutive PS capable TS that are preferred for PS allocation
Non pre-emptable PS zone:

always inside MAX_SPDCH_HIGH_LOAD zone
MAX_SPDCH_HIGH_LOAD zone
example: MAX_SPDCH_HIGH_LOAD = 8, MAX_SPDCH_LIMIT = 3

PS traffic zone Non pre-emptable PS zone MAX_SPDCH_LIMIT zone PS 1 PS 2 3 CS CS PS 6 CS 7 8 CS 9 CS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
in this latter zone, we search for the rightest TS allocated to the MFS and used. Then, all the TS located at its left define the non pre-emptable PS zone
MAX_SPDCH_LIMIT zone:
the MAX_SPDCH_LIMIT consecutive PS capable TS preferred for PS allocation
4 5 TRX2
PS traffic zone:
the larger zone between the 2 above
Page 15
Impact on SPDCH capable TS carrying CS traffic:

If located inside the PS traffic zone, they are pre-reserved for PS.
No new incoming CS call can be served on this TS, if it becomes unused once it is pre-reserved for PS. Valid until the TS becomes not pre-reserved for PS again and of course still handled by the BSC
If located inside the Non pre-emptable PS zone and the MAX_SPDCH_LIMIT zone, an intracell Handover can be triggered
if EN_RETURN_CS_ZONE_HO = enabled, the BSC shall check whether TCHs are allocated in both the MAX_SPDCH_LIMIT zone and the non preemptable PS zone, and trigger the HO (cause 30) the TS will be considered as unused only once the handover will have been successfully performed. As the pre-reservation state of such a TS is set to pre-reserved for PS, no new incoming CS call can be allocated on it
Page 16
CS calls in the Non pre-emptable PS zone:

PS traffic zone MAX_SPDCH_LIMIT zone Non pre-emptable PS zone PS 1 PS 2 CS 3 PS 4 5 TRX2 PS 6 CS 7 8 PS 9 PS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
PS traffic zone Non pre-emptable PS zone MAX_SPDCH_LIMIT zone PS 1 PS 2 3 CS CS PS 6 CS 7 8 CS 9 CS 10 CS 11 CS 12 13 TRX1 14 15 CS 16
4 5 TRX2
MAX_SPDCH_HIGH_LOAD zone PS used by PS CS used by CS CS used by CS, candidate for HO cause 30
Page 17
Examples of SPDCHs_Allocation_bitmap building:

2 TRXs in the cell initial situation: TS1 and TS2 on TRX2 allocated to the MFS the non pre-emptable PS zone is always included in the MAX_SPDCH_LIMIT zone MAX_SPDCH_LIMIT = 5
TRX 2
MAX_SPDCH_LIMIT_ZONE PS traffic zone
TRX 1
PS PS CS
1 1 2 1 3 0 4 1
CS CS
5 0 6 0 7 1
CS
8 0 9 1 10 0
CS CS
11 0 12 0 13 0 14 0 0
CS
15 16 0
Page 18

MAX_SPDCH_LIMIT = 7
TRX 2
TRX 1
PS PS
1 1 2 1 3 1 4 1
CS CS
5 0 6 0 7 1
CS
8 0 9 1 10 1
CS CS
11 0 12 0 13 0 14 0
CS
15 16 0 0
Page 19

MAX_SPDCH_LIMIT = 4
TRX 2
TRX 1
PS PS
1 1 2 1 3 1 4 1
CS CS
5 0 6 0 7 0
CS
8 0 9 0 10 0
CS CS
11 0 12 0 13 0 14 0
CS
15 16 0 0
Agenda
Page 20


CS Preemption (1/2)
Page 21
BSC Radio Resource Allocation SPDCHs_Allocation
MFS
1)
MFS knows which SPDCHs shall be given back to the BSC
2)
T_PDCH_PREEMPTION
=TCH_INFO_PERIOD -1 sec
TCH_INFO_PERIOD
3)
4)
5)
Impacted SPDCHs not used are immediately given back to the BSC Note : SPDCHs considered not used if no TBF resources are allocated on these SPDCHs and their basic Abis nibbles are free) Remaining impacted SPDCHs, which are in use (at least one TBF is established on those SPDCHs or the basic Abis nibbles of those SPDCHs are used by a GCH channel), are marked as de-allocating the CS pre-emption process shall be completed before T_PDCH_Preemption timer (set to TCH_INFO_PERIOD - 1s) When T_PDCH_Preemption expires, the fast preemption is launched.
CS Preemption (2/2)
Page 22
TBFs candidate for T1 reallocation: PACCH impacted by the pre-emption (as in B8)
0 1 2 3 4 5 6 7
No T1 candidate T1 candidate
DL UL
0 1 2 3 4 5 6 7
TBFs for which the M-EGCH link size becomes too low to serve the Max_Allowed_(M)CS of the TBF (new in B9). Reallocated with a decrease of MaxMCS
Max_EGPRS_MCS = MCS9 5 GCHs needed
TRX EGPRS TBF M -EGCH 2 preempted GCHs 4 GCHs
Related Parameters
Page 23
HMI name
Definition
Subsystem BSC
Insta nce BSC
OMC-R access None (DLS) None (DLS)
Type
Def value 2
Range
Unit
NEW : RR_ALLOC_PERIOD NEW : THR_MARGIN_PRIO_P S NEW : EN_RETURN_CS_ZON E_HO
This parameter allows to tune the time between two sendings of the BSCGP RR Allocation Indication message Margin of radio timeslots reserved for PS traffic between two sendings of the BSCGP RR Allocation Indication message. The threshold is expressed in percentage of radio timeslots Flag enabling the intracell handovers allowing to move TCH from the PS zone to the CS zone of PDCH/TCH allocation
Numb er Perce ntage
[1,30]
Non e %
BSC
BSC
10
[0,100]
BSC
cell
Change able
flag
[0,1]
Non e
Removed parameters :
T_PDCH_PREEMPTION
Agenda
Page 24


Definitions
Page 25
TRX capabilities for GPRS (maximum CS) and for EGPRS (EGPRS possible or not, maximum MCS) are defined at MFS side using:
HW PS capability for each TRX, Max_GPRS_CS O&M parameter, En_EGPRS O&M parameter, Max_EGPRS_MCS O&M parameter.
TRE generation G2 (TRE in a DRFU BTS) G3 (TRE in an Evolium BTS) G4 (TRE in an Evolium BTS) HW PS capability of the TRX CS-1/2 CS-1/4 CS-1/4 + MCS-1/9
Definitions
Page 26
TRX is said established if there is an M-EGCH link associated to this TRX with GCHs. For each TRX, the following variables are defined:
Established_Nb_GCH: Number of GCHs that are activated in the M-EGCH link
Non CS Preemptable GCH:

GCH, whose Abis nibble is not CS preemptable (Extra Abis nibble, Bonus Abis nibble,Basic Abis nibble mapped on a RTS inside the Max_SPDCH_High_Load zone.
CS Preemptable GCH:
GCH, whose Abis nibble is CS preemptable (Basic Abis nibble mapped on a RTS outside the Max_SPDCH_High_Load zone)
M-EGCH link size : Target_Nb_GCH

Page 27
Target_Nb_GCH:
Estimation of the GCHs necessary in a given M-EGCH link to carry the traffic It may of course not be reached in case of congestion situations at transmission level (Abis and/or Ater). It is a function of:
-Number of PDCHs on the TRX, on which radio resources have been allocated for BE TBFs, -Max_GPRS_CS and Max_EGPRS_MCS O&M parameter values, -Number of GCH needed per PDCH for Max_GPRS_CS / Max_EGPRS_MCS -Whether Ater Usage in the GPU is high or not. If it is high, the value of Target_Nb_GCH is reduced so as to decrease the global Ater resource consumption in the GPU.
M-EGCH link size : Target_Nb_GCH

Page 28
Max_GPRS_CS CS-1 CS-2 CS-3 CS-4
Nb_GCH(Max_GPRS_CS) 0,73 1,00 1,25 1,64
Target_Nb_GCH is updated:
At TBF allocation / reallocation, At TBF release.
Max_EGPRS_MC S MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
Nb_GCH(Max_EGPRS_MCS) 0,89 1,00 1,33 1,50 1,86 2,36 3,49 4,14 4,49
Example of Target_Nb_GCH evaluation:

Target_Nb_GCH = 4 * 4.49 = 18 GCHs for the MEGCH link of a TRX supporting one 4-TS EGPRS TBF (Max_EGPRS_MCS = MCS-9), Target_Nb_GCH = 4 * 1.64 = 7 GCHs for the M-EGCH link of a TRX supporting one 4-TS GPRS TBF (Max_GPRS_CS = CS-4).
(In this example, it is supposed that the Ater usage of the GPU is not high)
Abis selection in M-EGCH link

Page 29
When establishing new GCHs in the M-EGCH link of a given TRX, the free Abis nibbles are selected with the following priorities:
1) Free basic Abis nibbles mapped to RTSs currently available for PS traffic and within the Max_SPDCH_High_Load zone of the cell,
2) Free extra Abis nibbles and free bonus Abis nibbles, 3) Free basic Abis nibbles mapped to RTSs currently available for PS traffic and out of the Max_SPDCH_High_Load zone of the cell. If not enough free Abis nibbles, or free Ater nibbles, use of GCH preemption: 4) Inter-cell GCH preemption,
5) Intra-cell GCH preemption.
M-EGCH link establishment or increase

Page 30
Triggers for M-EGCH link establishment or capacity increase: New TBF allocated on the TRX
And Target_Nb_GCH becomes strictly higher than Established_Nb_GCH.
Periodical GCH establishment process

Periodical attempt to increase the M-EGCH link size of TRXs, if its size is lower than Target_Nb_GCH. Addition of GCHs to the TRX of the cell (target TRX), whose deficit in terms of number of GCHs is the highest.
Fast Initial PS Access feature

O&M parameter at cell-level : EN_FAST_INITIAL_GPRS_ACCESS.
Ensures that one M-EGCH link is always established on the the most PS-prioritary TRX of the cell
Handling of unused GCHs

Page 31
When a TBF is released and Target_Nb_GCH becomes strictly lower than Established_Nb_GCH unused GCHs:
Triggers an inactivity timer (T_GCH_Inactivity) Anticipates new TBF arrival, GCH preemption. At timer expiry, if Target_Nb_GCH is still strictly lower than Established_Nb_GCH, the unused GCHs are released: Choice of GCHs to release is the reverse order than the one used for GCH establishment. If there is no TBF traffic in the cell and the TRX is the last established TRX of the cell:
Not all the GCHs are released (keep N_GCH_Fast_PS_Access GCHs),

Triggers T_GCH_Inactivity_Last timer. Only valid if Fast Initial PS Access is disabled.
Handling of unused GCHs

Page 32
At T_GCH_Inactivity timer expiry
M-EGCH link Established_Nb_GCH = 10

GCH10 B > HL GCH9 B > HL
3 unused GCHs Target_Nb_GCH = 7 Established_Nb_GCH = 7
B > HL: GCH uses a basic Abis nibble mapped on a RTS out of the Max_SPDCH_High_Load zone of the cell. Extra: GCH uses an extra Abis nibble or a bonus basic Abis nibble. B HL: GCH uses a basic Abis nibble mapped on a RTS within the Max_SPDCH_High_Load zone of the cell.
GCH8 B > HL GCH7 B > HL GCH6 B > HL GCH5 Extra GCH4 Extra GCH3 B HL GCH2 B HL GCH1 B HL
7 used GCHs
M-EGCH link capacity decrease

Page 33
M-EGCH link capacity decrease: GCHs are removed from an M-EGCH link of a TRX: When a TBF is released and Target_Nb_GCH becomes strictly lower than Established_Nb_GCH (unused GCHs and inactivity timer mechanism), GCH preemption: inter-cell and intra-cell, CS preemption: a basic Abis nibble used in the M-EGCH link is mapped on a RTS that must be given back to the BSC (CS preempted RTS).
Modification of the TBF allocation/re-allocation strategy
TBF Resource establishment process

Page 34
The TBF resource establishment process operates in two steps:
Radio Resource Allocation Algorithm
Find best candidate timeslot allocation Verify if enough transmission resource GCH reservation
If Allocation = OK
Two policies are defined ASAP, Optimal GCH establishment Maximum allowed (M)CS
TBF Establishment

Page 35
Two TBF allocation policies are defined:

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.
Type of request
TBF establishment (without concurrent)
TBF establishment (with concurrent) T1 TBF reallocation T4 TBF reallocation T3 TBF reallocation
Policy
ASAP
ASAP ASAP ASAP Optimal
Nb_GCH_For_Estab
1
1 to 5 (depending on the Max_Allowed_(M)CS of the concurrent TBF) 1 1 to 2 (depending on the Max_Allowed_CS of concurrent TBF) 1 to 5 (depending on the Max_Allowed_(M)CS of concurrent TBF)

Page 36
Determination of the Max_Allowed_(M)CS of a TBF:

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 Is limited by: GPRS / EGPRS TRX capability, Max_GPRS_CS and Max_EGPRS_MCS (O&M parameters).
Nb_GCH 1
Max_Allowed_CS CS-2 (UL) / CS-1 (DL)
Nb_GCH 1 2 3 4 5
Max_Allowed_MCS MCS-2 (UL) / MCS-1 (DL) MCS-5 MCS-6 MCS-7 MCS-9
CS-4
Transmission resources establishment

Page 37
3 cells @ 2 TRX:
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. Abis radio
Cell A
Cell B Basic nibbles Cell C
6x4 extra nibbles
C S

Page 38
First EDGE MS (MS1), class 8 in cell A -> Target_Nb_GCH = 18

GCH Allocation for MS1 4 basic Abis nibble in the Max_PDCH_High_Load zone, 14 extra Abis nibbles, Total = 18 GCHs.
basic Cell A
extra
Cell B
Cell C
C MS1 S
C Cell A S

Page 39
Second EDGE MS (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 extras Abis nibbles are pre-empted from Cell A to Cell B
Total = 18 GCHs.
Cell A
basic extra
Cell B
Cell C C Cell A S Cell B
C MS1 S MS2

Page 40
After GCH allocation of MS2 in cell B: In Cell A: Established_Nb_GCH = 16 Next Periodical GCH process in Cell A: 2 basic Abis nibbles outside the Max_PDCH_High_Load zone, Total = 16 + 2 = 18 GCHs.
basic Cell A
extra
Cell B
Cell C
C MS1 S MS2
C Cell A S Cell B
Agenda
Page 41


TRX List computing

Page 42
The goal of the TRX list computing step is to determine the TRX list on which the TBF or one UL block candidate allocations will be searched The conditions for a TRX to be inserted into the TRX list are:
the TRX shall be PS capable if the TRX is not already mapped to a DSP, and no DSP can be associated to the TRX, then the TRX shall not be considered
Difference with B8 release:

there are no longer some restricted EGPRS capable TRX lists (i.e. selection of the EGPRS TRX of highest class (that is which offer the highest throughput) as long as the maximum number of EGPRS TBF per PDCH on these TRX is not higher than a threshold). Indeed, all the EGPRS capable TRXs can offer the same potential throughput: they are all mapped on G4 TRE, and the B8 concept of TRX pool type has disappeared
Best candidate allocation computation

Page 43
Once all the usable PDCHs are determined, the different candidate timeslot allocations are sorted according to their respective available throughput, in order to choose the one offering the highest throughput to serve the considered request. This is a complete change compared to the previous BSS releases (B6, B7 and B8)
Definition : PDCH states

Allocated:
Page 44
new in B9: the PDCH is a SPDCH indicated as usable for PS traffic by the BSC B8 definition: radio resource allocated to the MFS, but associated transmission resources are not allocated
Active:
new definition in B9: an allocated PDCH is active if it supports at least one radio resource allocated for a TBF the B8 definition was considering the parameter N_TBF_PER_SPDCH which is removed in B9 release
Full : as in B8 release
EGPRS:
an allocated PDCH is in the EGPRS state if some radio resources are allocated in DL, for an EGPRS TBF. Only used when running the radio resource (re)allocation algorithm in GPRS mode and when considering the UL direction of the candidate TBF allocations Remark: the busy PDCH state (number of established TBF on the PDCH higher than N_TBF_PER_SPDCH) is no more used by the allocation algorithm

Page 45
Available throughput of a candidate timeslot allocation

New metric introduced in B9 release. It is the overall throughput provided by its PDCHs. Depends on two variables:
the potential throughput of its PDCHs the available capacity on each of its PDCHs
Note : in the past releases the idea was already to give the highest possible throughput to a TBF (allocating the highest number of TS, if possible not busy) but there was no explicit metric evaluating the throughput provided by a candidate TS allocation

Page 46
Potential throughput of a given PDCH

The potential throughput of a PDCH is calculated as follows according to O&M parameters for the Evolium BTS case: GPRS best effort TBF: R_AVERAGE_GPRS (default = 12kbit/s) EGPRS best effort TBF: R_AVERAGE_EGPRS (default = 30kbit/s) This potential throughput and its associated parameters are only used in the computation of the best allocation. No impact at all on the effective throughput !
Available capacity on a given PDCH

For a Best effort GPRS TBF, it takes into account all other BE GPRS TBF or EGPRS TBF on the same TS ( = 1 / Nb_BE_TBF_SAME_PRIOR_XL) For a Best effort EGPRS TBF, it takes into account only the other BE EGPRS TBF on the same TS ( = 1 / Nb_BE_EGPRS_ TBF_SAME_PRIOR_XL)
Available throughput of a given candidate timeslot allocation

Computed using available capacity and throughput for all PDCH of the allocation

Page 47
Candidate time slot allocations sorting : throughput-based:

[ALPHA]: For ASAP policy only: the candidate timeslot allocations, which are on some TRXs for which Established_Nb_GCH is greater than Nb_GCH_For_TBF_Estab are preferred. [A]: For UL GPRS TBF establishment / reallocation only: the candidate timeslot allocations, which have the lowest number of PDCHs in the EGPRS state are preferred. [B]: the candidate timeslot allocations, which have the highest available throughput in the direction of the bias are preferred. [C]: the candidate timeslot allocations, which have the highest available throughput in the direction opposite to the bias are preferred. [D]: the candidate timeslot allocations, which are on the TRX with the highest priority, are preferred. [E]: for EGPRS TBFs establishments only: the candidate timeslot 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.
Agenda
Page 48


TBF reallocation cases

Page 49
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
Provide a higher throughput, if it is possible, to a TBF, Establish a new M-EGCH link for one of the TRXs of the cell, Perform a radio de-fragmentation process.
T4: reallocation to move an 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.
T3 TBF reallocation cases

Page 50
Conditions for a MS to be candidate for T3 reallocation: the BSS systematically requests a T3 reallocation for any MS which has an established TBF in the direction of the bias verifying the following conditions:
more than N_CANDIDATE_FOR_REALLOC bytes have been sent on the DL TBF or received on the UL TBF since their establishment T3192 is not running
Principles of T3 TBF reallocation: 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%).
T3 TBF reallocation cases : example

Page 51
Initial situation:
3 MSs (MSa, MSb, and MSc), all GPRS and (4+1),
0 1 2 3 4 5 6 MSb 7 0 1 2 3 4 5 6 7
U L D L
MSa MSc
MSc MSc MSc MSc MSa MSa MSa MSa MSb MSb MSb MSb
U L D L
MSc is the most impacted by the multiplexing in terms of throughput.
In B8:
MSc is not candidate for T3 reallocation because its allocation is optimal (4 TS in DL),
In B9:
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 0 1 2 3 4 5 6 7
U L
MSa MSb
U L
MSc
D MSa MSa MSa MSa MSb MSb MSb MSb L
D MSc MSc MSc MSc L

Page 52
A T3 TBF reallocation can also be played for a radio defragmentation purpose:

TBF1 TBF2
Initial situation
Final situation

Page 53
T4 TBF reallocation: to avoid the UL GPRS - DL EGPRS TBF

multiplexing situations
triggering conditions
a GPRS MS becomes candidate for a T4 reallocation as soon as its UL GPRS TBF shares at least one PDCH with a DL EGPRS TBF the MS remains candidate for a T4 reallocation, after an UL TBF release, if a DL TBF is still ongoing => a DL TBF can be T4 reallocated even with no UL concurrent TBF
best candidate allocation computation

No need to have the same number of PDCHs than the current allocation in UL direction, the candidate TS allocations cannot contain PDCHs in EGPRS state. ASAP policy (favouring TRX with Nb_GCH_For_TBF_Estab already established GCHs)
Agenda
Page 54


Related Parameters
Page 55
HMI name Definition Subsystem
MFS MFS
Insta nce
cell cell
OMC-R access
Changea ble Changea ble
Type
Def value
12000 30000
Range
Unit
NEW : R_AVERAGE_GPRS NEW : R_AVERAGE_EGPRS
average bitrate per PDCH for non-Edge capable terminals in this cell average bitrate per PDCH for Edge capable terminals in this cell
Throu ghput Throu ghput
[0,2000 0] [0,5900 0]
Bit/s Bit/s
NEW : T_MAX_FOR_TBF_SC HEDULING
maximum time between two scheduling of a given NRT TBF (either between two DL block requests for a NRT DL TBF, or between two UL blocks received for a given NRT UL TBF)
minimum throughput gain required to be provided to the MS when performing a T2 or T3 TBF reallocation total number of (unsuccessful) T3 radio resource reallocation attempts that are allowed to be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer. As soon as a T3 radio resource reallocation attempt succeeds, no other attempt is performed (even if less than N_MAX_PERIODIC_REALLOC_T3 attempts have been performed so far). The UL-biased MSs and the DL-biased MSs are considered regardless of each other. As a result, in a given cell, up to 2 x N_MAX_PERIODIC_REALLOC_T3 T3 radio resource reallocation attempts will be performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer defines the total number of T4 radio resource reallocation attempts (successful or not) that are performed upon expiry of the T_CANDIDATE_TBF_REALLOC timer
MFS
MFS
None (DLS)
Time
0.3
[0.12,0. 3]
NEW : MIN_THROUGHPUT_G AIN NEW : N_MAX_PERIODIC_RE ALLOC_T3
MFS
MFS
None (DLS) None (DLS)
Numb er Numb er
0.4
[0.1,5]
None
MFS
MFS
20
[0,500]
None
NEW : N_MAX_PERIODIC_RE ALLOC_T4
MFS
MFS
None (DLS)
Numb er
[0,500]
None
Related Parameters
Page 56
Following B8 parameters are removed in B9 release:

N_TBF_PER_SPDCH EN_RES_REALLOCATION N_MAX_PERIODIC_REALLOC
B9 Channel allocation strategy for PS transfers
New BSC Counters

Page 57
Counter number
Name
Definition
MC480
MC481 MC924a
NB_TCH_HO_REQ_30_ReturnCSZon e
NB_TCH_HO_ATPT_30_ReturnCSZo ne TIME_SPDCH_LIMIT_HIGH_LOAD
Number of TCH intracell HO cause 30 requests

Number of TCH intracell HO cause 30 attempts. Time during which the cell is in high load situation for PS traffic. This situation impacts the number of slave PDCHs that can be allocated to the MFS.
Removed MFS Counters

Page 58
Counter number P1 Name TIME_HIGH_LOAD_GPRS Definition Time during which the cell is in a high load situation for PS traffic. This situation impacts the number of slave PDCHs that can be allocated to the MFS. This counter integrates over time the value of MAX_SPDCH_DYN during the whole granularity period. This counter gives the maximum value of MAX_SPDCH_DYN during the whole granularity period. This counter indicates the minimum value of MAX_SPDCH_DYN that has been observed over the whole granularity period. Number of times the MFS receives a BSCGP LOAD INDICATION message requesting the MFS to de-allocate at least one slave PDCH that is currently allocated to the MFS. Number of PDCH dynamic allocation requests. Number of PDCH dynamic allocation success. Number of downlink TBF establishment requests requesting 2 or 3 slots, which are only partially satisfied by the initial allocation. Number of uplink TBF establishment requests requesting 2 or 3 slots which are only partially satisfied by the initial allocation. Number of downlink TBF establishment requests requesting 4 or 5 slots which are only partially satisfied by the initial allocation. Number of uplink TBF establishment requests requesting 4 or 5 slots which are only partially satisfied by the initial allocation.
P414 P415 P416 P418
CUMULATED_MAX_PDCH_DYN_SECONDS MAX_MAX_PDCH_DYN MIN_OF_MAX_PDCH_DYN NB_SOFT_PREEMPTION
P54 P19 P166 P167 P168 P169
NB_PDCH_DYN_ALLOC_REQ NB_PDCH_DYN_ALLOC_SUCC NB_DL_TBF_2_3_partial_succ NB_UL_TBF_2_3_partial_succ NB_DL_TBF_4_5_partial_succ NB_UL_TBF_4_5_partial_succ
New MFS Counters

Page 59
Counter number P414bis P415bis P416bis P451a
Name CUMULATED_TIME_ALLOCATED_SPDC H MAX_OF_ALLOCATED_SPDCH MIN_OF_ALLOCATED_SPDCH CUMULATED_TIME_PDCH_UL_TBF_CE LL CUMULATED_TIME_PDCH_DL_TBF_CE LL CUMULATED_TIME_PDCH_DL_TBF_GM M_SIG_CELL CUMULATED_TIME_PDCH_USED_DL_C ELL CUMULATED_TIME_PDCH_USED_UL_C ELL
Definition This counter integrates over time the values of the allocated SPDCH during the whole granularity period. This counter gives the maximum value of allocated SPDCH during the whole granularity period. This counter gives the minimum value of allocated SPDCH during the whole granularity period. Cumulated time during which an UL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated time during which an DL TBF uses one PDCH, for all PDCHs of the TBF, and for all TBFs of the cell (in GPRS or EGPRS mode). Cumulated time during which a DL TBF established for GMM signalling purposes uses a PDCH (in GPRS or EGPRS mode), for all TBFs of the cell. Cumulated time during which a PDCH is used by at least one DL TBF (in GPRS or EGPRS mode), cumulated over all the PDCHs of the cell. Cumulated time during which a PDCH is used by at least one UL TBF (in GPRS or EGPRS mode), cumulated over all the PDCHs of the cell.
P451b
P452
P38e
P38f
RNO Indicators
Page 60
Ref. name HCRCARRN HCRCARAN HCRCARFN HCRCARFR
Name HO_Cell_Return_CS_Zone_request HO_Cell_Return_CS_Zone_allocated HO_Cell_Return_CS_Zone_prep_fail HO_Cell_Return_CS_Zone_prep_fail_rat e
Formula MC480 MC481 MC480 - MC481 (MC480-MC481) / MC480
Unit number number number %
HCRCARRR
QRPALCGT QRPALCGP QRPALSAT QRPALSAN QRPALSAR
HO_Cell_Return_CS_Zone_rate
GPRS_BSC_high_load_time GPRS_BSC_high_load_percent GPRS_MAX_PDCH_Dyn_cumulated_ov er_time GPRS_MAX_PDCH_Dyn_avg GPRS_MAX_PDCH_Dyn_reduction_rate
HO_Cell_Return_Cs_Zone_al located / CHO_all

MC924a MC924a / GPRS_obs_period P414bis P414bis / GPRS_obs_period ((P415bis * GPRS_obs_period ) P414bis) / (P415bis * GPRS_obs_period) P415bis P416bis
%
seconds % seconds % %
QRPALSAM_M A QRPALSAI_NA
GPRS_MAX_PDCH_Dyn_max GPRS_MAX_PDCH_Dyn_min
number number
RNO Indicators
Page 61
Ref. name ARPDCTUBUT ARPDCTUBUR ARPDCUUBUT TRPDCUUN ARPDCUUO TRPDUPDA
Name GPRS_PDCH_used_UL_TBF_overall_time GPRS_UL_TBF_occupancy_on_used_PDCH GPRS_PDCH_UL_traffic_time GPRS_PDCH_active_UL_avg GPRS_PDCH_UL_traffic_time_ratio GPRS_UL_useful_throughput_radio_PDCH_av g GPRS_UL_TBF_Pilled_avg
Formula P451a P451a / GPRS_obs_period P38f P38f / GPRS_obs_period P38f / P38b GPRS_UL_useful_throughput_bits_a ck / GPRS_PDCH_UL_traffic_time* 1000 P451a/P38f
Unit seconds number seconds number % kbits/s
ARPDCTUPIN
number
Example of UL TBF configuration :
After 10 seconds in the same configuration :

GPRS_PDCH_used_UL_TBF_overall_time = 4 * 20 s (MS1 -> MS4) + 10 s (MS5) = 90s. GPRS_UL_TBF_occupancy_on_used_PDCH = 90 /10 = 9 GPRS_PDCH_UL_traffic_time = 6 * 10 s = 60 s GPRS_PDCH_active_UL_avg = 60 / 10 = 6 GPRS_UL_TBF_Pilled_avg = 90 / 60 = 1,5
: MS1 : MS2 : MS3
: MS4
: MS5
RNO Indicators
Page 62
Ref. name ARPDCTDBUT ARPDCTDBUR ARPDCUDBUT TRPDCUDN ARPDCUDO TRPDDPDA
Name GPRS_PDCH_used_DL_TBF_overall_time GPRS_DL_TBF_occupancy_on_used_PDCH GPRS_PDCH_DL_traffic_time GPRS_PDCH_active_DL_avg GPRS_PDCH_DL_traffic_time_ratio GPRS_DL_useful_throughput_radio_PDCH_av g GPRS_UL_TBF_Pilled_avg GPRS_PDCH_used_DL_TBF_GMM_signalling _overall_time GPRS_PDCH_used_DL_TBF_GMM_signalling _time_ratio
Formula P451b P451b / GPRS_obs_period P38e P38e / GPRS_obs_period P38e / P38b GPRS_DL_useful_throughput_bits_a ck / GPRS_PDCH_DL_traffic_time* 1000 P451b/P38e P452 P452/P451b
Unit seconds number seconds number % kbits/s
ARPDCTUPIN ARPDCTDSGT ARPDCTDSGO
number seconds %
RNO Indicators
Ref. name TRXDTPRN QRPALPRR TRPALRQN QRPALSUN TRPALSUR QRPALUNN QRPALUNR QRDTEP3N QRDTEP3R QRUTEP3N QRUTEP3R Name GPRS_PDCH_soft_preemption_request GPRS_PDCH_soft_preempted_per_softpreemption GPRS_PDCH_dynamic_allocation_request GPRS_PDCH_dynamic_allocation_success GPRS_PDCH_dynamic_allocation_success_rate GPRS_PDCH_dynamic_allocation_unsuccess GPRS_PDCH_dynamic_allocation_unsuccess_rate GPRS_DL_TBF_2_OR_3_TS_partial_success GPRS_DL_TBF_2_OR_3_TS_partial_success_rate GPRS_UL_TBF_2_OR_3_TS_partial_success GPRS_UL_TBF_2_OR_3_TS_partial_success_rate Formula P418 P417/P418 P54 P19 P19/P54 P54-P19 (P54-P19)/P54 P166 P166 / (P166 + P162 ) P167 P167 / (P167 + P163)
Page 63 Unit
number % number number % number % number % number %
QRDTEP5N
QRDTEP5R QRUTEP5N QRUTEP5R
GPRS_DL_TBF_4_OR_5_partial_success
GPRS_DL_TBF_4_OR_5_partial_success_rate GPRS_UL_TBF_4_OR_5_TS_partial_success GPRS_UL_TBF_4_OR_5_partial_success_rate
P168
P168 / (P168 + 164) P169 P169 / (P169 +165)
number
% number %
Page 64
www.alcatel.com

3-Claro B9 RRM Algorithms

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3-Claro B9 RRM Algorithms

Enviado por

Direitos autorais:

Formatos disponíveis

Radio Resource Management Algorithms in B9

B9 Claro Workshop - February 14th 2006

All rights reserved 2005, Alcatel

Autonomous Packet Resource allocation

TBF allocation/re-allocation strategy

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation (RAE4)

In B9, the following new needs have appeared:

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation (RAE4)

Max_SPDCH_Limit = 8 TS allocated to BSC TS allocated to MFS

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

Autonomous Packet Resource Allocation (RAE4)

CS/PS sharing is based on the evaluation of Max_SPDCH_Limit. The Max_SPDCH_Limit value:

The evaluation of Max_SPDCH_Limit is based on:

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

RAE4 : Load evaluation

NB_USED_CS_TS(k) NB_USED_PS_TS(k) NB_USED_TS(k) NB_UNUSED_TS(k)

AV_USED_CS_TS(k) AV_USED_PS_TS(k) AV_UNUSED_TS(k)

AV_USED_CS_TS(k+2) AV_USED_PS_TS(k+2) AV_UNUSED_TS(k+2)

Modification of the PDCH allocation strategy

RAE4 : MAX_SPDCH_LIMIT Calculation

AV_USED_CS_TS AV_USED_PS_TS AV_UNUSED_TS

MIN_SPDCH MAX_SPDCH NB_TS Computation of Thresholds MAX_SPDCH_HIGH_LOAD Computation of MAX_SPDCH_LIMIT MAX_SPDCH_LIMIT

Computation of CS/PS Margin

= 100 HIGH_TRAFFIC_LOAD_GPRS O&M parameter

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

RAE4 : MAX_SPDCH_LIMIT Calculation

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

RAE4 : MAX_SPDCH_LIMIT Calculation

MIN_SPDCH MAX_SPDCH_HIGH_LOAD MAX_SPDCH_Limit MAX_SPDCH

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Autonomous Packet Resource allocation

TBF allocation/re-allocation strategy

B9 Claro Workshop / February 14th 06

All rights reserved 2005, Alcatel

Modification of the PDCH allocation strategy

BSC Radio Resource Allocation SPDCHs_Allocation

Radio Resource Allocation Indication message:

Radio Resource Usage SPDCHs_Confirmation SPDCHs_Usage

Radio Resource Usage SPDCHs_Confirmation SPDCHs_Usage

Radio Resource Usage Indication message:

Radio Resource Allocation SPDCHs_Allocation Radio Resource Usage SPDCHs_Confirmation SPDCHs_Usage

B9 Claro Workshop / February 14th 06

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection : ordering

PS TS and TRX ordering:

Modification of the PDCH allocation strategy

MAX_SPDCH_LIMIT TS selection : PS TS zones