Professional Documents
Culture Documents
Agenda
1. Overview
2. Schedulers description
1. Scheduler management
2. SPI management
3. UE category management
3. Parameters setting
Overview
Overview
ACK/NACK/CQI
from UE
#codes available,
remaining power
Mac-hs
Scheduler
Previous scheduled data
UE capabilities,
Configuration parameters
from RNC
Selection of the
users sub-flows to
schedule to
optimize the radio
resources
occupancy
between users
Overview
MAC-hs scheduling consists of choosing the Mac-d flow (QId) to serve according to 2 cost
functions (C1 and C2) and to the UE category
C1 depends on
the scheduler type
the radio condition
C2 depends on
the priority of the QId
the average CQI
Schedulers description
5 schedulers in UA5.0:
Round Robin
Max C/I
Pure Fair
Classical Proportional Fair
Nortel Proportional Fair
ROUND ROBIN
Goal
Cost function C1
MAX C/I
Goal
Cost function C1
costT = 30 - CQIinstT
PURE FAIR
Goal
Cost function C1
CLASSICAL
PROPORTIONAL FAIR
to favor mobiles that report a high CQI versus their averaged CQI to
take benefit from instantaneous good radio conditions vs average
conditions
Goal
Cost function C1
Goal
Cost function
C1
QId #i
Qid is characterized
by a SPI
SPI = [0 15]
SPI is chosen according
- the Traffic Class (TC)
- the Allocation/Retention Priority (ARP)
- the Traffic Handling Priority (THP)
(see QoS differentiation feature for more detail)
Principle: to share the HSDPA cell capacity between users so that throughput of each
QId is proportional to:
the weight of the SPI (via hsdpaSpiRelativeWeight)
the Transport Block Size of the averaged CQI reported by the UE
Example:
Th(QId #1)
Th(QId #2)
TBS(CQIav(QId #1))
x
TBS(CQIav(QId #2))
For RNC UA5.0 connected to NodeB UA4.2, the SPI management has to be disabled by setting SPI to 0
because SPI management is not supported by NodeB UA4.2.
SPI can be set to other values than 0 only if all the NodeB connected to RNC UA5.0 are upgraded in
UA5.0
UE category management
The throughput can be balanced between different categories when one of them is limited by the TBS
For example, above CQI 16, the TBS of a UE cat. 12 remains constant while for other categories, their TBS still increases with the CQI
Two behaviors are defined according to hsdpaUeCategoryThroughputWeighting:
ueCategoryEquity: same throughput in average at the same CQI for all the UE categories
ex: CQI 21, same throughput for UE category 6 and 12; even if category 6 experiences higher TBS, the category 12 is scheduled more often.
ueCategoryProportionality: UE throughput depend on their category. Their ratio throughput is proportional to the ratio of TBS of
corresponding CQI
ex: CQI 21, the cat. 6 has twice the throughput of a UE cat. 12 (6554/3440 = 1.91) even if they are scheduled as often (below CQI 15, their
throughput remains equal)
Parameters
Parameters
Value
hsdpaSchedulerAlgorithm
nortel
Range
Enum [nortel; proportionalFair;
roundRobin; maxCtoI; fair]
hsdpaSchedulerWeightingFactor
hsdpaSpiRelativeWeight
5
[2,4,6,8,10,12,14,16,
Integer [18]
Integer [116][1...100]
18,20,22,24, 26,28,30,32]
Only the relative weight is meaningful
100 for all the SPI means that the SPI management is disabled at NodeB level (same behavior as UA4.2 with Nortel PF scheduler)
Note that to disable the SPI management at RNC level, SPI value has to be set to 0 for each TC/ARP/THP
www.alcatel-lucent.com