05 - 6255 - NAK - Packet Scheduling

Contents
UMTS/HSPA Radio Resource Management & Parameter

 Introduction to Radio Resource Management
 Power Control
 Load Control
 Admission Control
 Packet Scheduling
 Code Tree Management
 PLMN and Cell Selection
 Handover Procedures
 HSDPA Protocol Features
 HSDPA Power Management
 HSDPA Code Resource Management
 HSDPA Mobility
 HSUPA Protocol Features
 HSUPA Power Management
 HSUPA Mobility
 HSPA+
00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Content
Packet Scheduling
 Introduction
 RRC Connection State Transitions
 Quality Triggered Bit Rate Adaptation
 RLC Buffer and Throughput Triggered Bit Rate Adaptation
 Cell Load Triggered Bit Rate Adaptation

Content
Packet Scheduling
 Introduction

Packet Scheduler Functionalities
- Distributes radio capacity not used for RT to NRT radio bearers

- Estimates load change caused by bit rate allocation / adaptation
- Adapts bit rate based on:
Traffic volume measurements / radio link quality / cell load /
Throughput measurements
- Determines the transport channel to be used
- Switches between RRC connection states based on:
Traffic volume measurements / inactivity
Uu
Packet
Allocation
Load
RNC Measurements
Iub
PS Packet Node B
Allocation
LC
Iu UE
AC Iub
Load Measurements
Content
Packet Scheduling
 Introduction
RRC Connection States
RRC Idle  RRC Connected
CELL_FACH  CELL_DCH
CELL_FACH  CELL_PCH
CELL_PCH  URA_PCH
CELL_PCH / URA_PCH  RRC Idle

RRC Connection States
Inactivity Cell_PCH
Cell_DCH • Cell of UE known
• DCH allocated • UE can be paged
• Cell of UE known (PICH)
•Not used by Ericsson
RRC Idle
Any data transfer /
initiate cell update
• no UE location Capacity
Inactivity
information request Inactivity /
in UTRAN RRC connection finish cell update
establishment /
• only LAI / RAI
release
in CN
• no data transfer
possible
Cell_FACH URA_PCH
Any data transfer /
• RRC connection • common channel initiate URA update • similar to Cell_PCH
allocated (FACH,
establishment via
RACH) • no Cell Update,
RACH/FACH but URA Update
• Cell of UE known
signaling Finish last of too
much cell updates /
finish URA update
RRC Connected
Inactivity • UE location known in UTRAN
• signaling link exists
• only 0 or 1 RRC connection between 1 UE & UTRAN

RRC Idle  RRC Connected
- When a RRC connection is set-up, usually the UE enters

directly the CELL_DCH state
- Nokia allows to start with the CELL_FACH state, if a very low data
rate is needed only
- When an RRC connection is released in either the CELL_DCH
or CELL_FACH state, the UE returns to the RRC idle state
RRC Idle Cell_DCH

• no UE location • DCH allocated
• Cell of UE known
information
• Handover
in UTRAN
• only LAI / RAI
in CN
• no data transfer
possible Cell_FACH
• RRC connection
• common channel
allocated
establishment • Cell of UE known
• Cell re-selection • Cell Re-Selection

CELL_FACH  CELL_DCH (1/4)
UE initiated CELL_FACH  CELL_DCH
- When the UE has received the RRC radio bearer set-up request,
it starts to perform traffic volume measurements
- If the amount of data in the UE RLC buffer exceeds a certain limit for
a certain time, it transmits a capacity request
- If there are enough resources in the cell, a radio bearer reconfiguration
is performed
UE Node B RNC
CELL_FACH
Capacity request
Radio link set-up
Radio bearer reconfiguration

CELL_DCH
Radio bearer reconfiguration complete

RNC initiated CELL_FACH  CELL_DCH
- When the RNC has transmitted the RRC radio bearer set-up request, it generates
a RLC buffer for this connection and starts to perform traffic volume measurements
- If the amount of data in the RLC buffer exceeds a certain limit for a certain time, the
RNC generates an internal capacity request
- If there are enough resources in the cell, a radio bearer reconfiguration is performed
UE Node B RNC
CELL_FACH
Internal capacity
request by MAC
Radio link set-up

CELL_DCH

CELL_DCH  CELL_FACH
- Buffers (almost) empty: If both the UE and RNC buffers are empty / almost empty for a certain
inactivity time, an absence of traffic is adopted (Nokia / Huawei)
- Low Throughput: If both on the UL and DL the throughput is a certain time below a critical
threshold, a very low activity is adopted (Ericsson)
- Radio bearer reconfiguration is performed
- Dedicated resources are released
Both buffers just (almost)

empty /
On both direction very low
CELL_DCH throughput
RNC Inactivity timer started
UE Node B
Inactivity timer expires
CELL_FACH
Radio link release

CELL_DCH inactivity timers inclusive Iub Settings per RNC only
and Buffer Threshold
CELL_FACH  CELL_DCH – Huawei (1/2)
D2F2PTvmThd D2FTvmTimeToTrig
RLC buffer threshold Time hysteresis to initiate downgrade procedure
8 byte..768 Kbyte, 64 byte 0..5000 ms, 5000 ms
D2F2PTvmThd MO = UUESTATETRANS
• Description: This parameter is used to check whether the UE in the low activity state. If the UE is on DCH channel,
the low activity counter increases by 1 every time traffic volume event 4B is reported. If the UE is on FACH
channel, the low activity counter increases by 1 if the traffic volume is 0 in the traffic volume event 4B report. The
parameter modification has no impact on the equipment. If this parameter is set to a small value, a UE is less likely
to be in the low activity state, channel transfer from the DCH channel to the FACH or RACH is less likely to occur,
and more DCH resources are occupied. If this parameter is set to a large value, the UE is more likely to be in the
low activity state, channel transfer from the DCH channel to the FACH or RACH is more likely to occur, the FACH
is more likely to become congested.
D2FTvmTimeToTrig MO = UUESTATETRANS
• Description: When the traffic volume is below the 4B threshold and remains so for the period specified by this
parameter, the event 4B is reported. This parameter can prevent unnecessary reports to be triggered, caused by
traffic volume variation. If this parameter is set to a small value, the UE with discontinuous data transmission will
mistakenly trigger event 4B, which increases state transition from the DCH channel to the FACH or RACH,
signaling messages over the air interface, and CPU usage. If this parameter is set to a large value, the UE is less
likely to trigger event 4B and stays in the CELL_DCH state even after data transmission ends. This wastes DCH
resources.

CELL_FACH  CELL_DCH – Huawei (2/2)
D2FTvmPTAT BeD2FStateTransTimer HiLdBeD2FStateTransTimerState
Time hysteresis to abort pending procedure Low activity time Transition Timer in High Load
0..16000 ms, 1000 ms 0..65535 s, 5 s 0..65535 s, 1 s
D2FTvmPTAT MO = UUESTATETRANS
• Description: Pending time after the traffic volume event 4B for state transition from DCH to FACH is reported. This
parameter is used to prevent too many traffic volume events 4B being reported. If this parameter is set to a small
value, the number of event 4B, procedure interactions, and call drop rate increase. If this parameter is set to a large
value, the UTRAN becomes insensitive to data transmission changes, which results in unnecessary state transitions
from the DCH channel to the FACH or RACH, and delayed data transmission.
BeD2FStateTransTimer MO = UUESTATETRANS
• Description: Timer for state transition from DCH to FACH of BE services, used to check whether the UE in the
CELL_DCH state with BE services is in the stable low activity state. If the value of this parameter is too small, the
UTRAN determines that DTX UEs or UEs with UL/DL alternate data transmission are in the low activity state. In this
case, D2F state transitions will be frequently triggered and air interface reconfiguration signaling will increase. After
transition to the CELL_FACH state, the air interface rate of these UEs is limited. If the value of this parameter is too
large, the D2F state transition takes a long time, wasting dedicated channel resources.
BeD2FStateTransTimer MO = UUESTATETRANSTIMER
• Description: Timer for load based state transition from DCH/HSDPA/HSUPA to FACH in cells with heavy load. A
DCH/HSDPA/HSUPA to FACH state transition is triggered for a UE when the UE's serving cell has heavy load and
the RNC detects that the UE is performing a BE service on a DCH/HSDPA/HSUPA channel in low-activity state for a
duration longer than the timer. The smaller the value of this parameter, the more air interface resources are saved.
This improves cell capacity, but causes more state transitions and more reconfiguration signaling messages. The
larger the value of this parameter, the easier the UE reconfiguration is performed. This, however, increases the time
for releasing DCH resources and affects cell capacity.
• 00-19 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved
CELL_FACH  CELL_DCH – Ericsson
downswitchThreshold downswitchTimer downswitchTimerThreshold
Throughput threshold to Time hysteresis Throughput threshold to abort pending
initiate downgrade procedure 0..100 s, 1 s procedure within time hysteresis
0..32 Kbit/s, 0 bit/s 0..64 Kbit/s, 0 kbit/s
downswitchThreshold MO: ChannelSwitching

• Description: Throughput threshold for downswitching from dedicated channel to FACH/RACH.
Once the throughput on both the uplink and downlink has fallen below this threshold, a downswitch to FACH/RACH
is normaly requested after the length of time set in downswitchTimer. However, the downswitch is not requested if
the throughput has subsequently increased above the value of downswitchTimerThreshold.
downswitchTimer MO: ChannelSwitching

• Description: Time after which a connection with low throughput is switched down from a dedicated channel to
FACH/RACH. Once the throughput on both the uplink and downlink has fallen below the value of
downswitchThreshold, the RNC normally requests a downswitch to FACH/RACH after this length of time. If
CELL_FACH state is not available, the connection is switched down to IDLE state. However, the downswitch is not
requested if the throughput has subsequently increased above the value of downswitchTimerThreshold.
downswitchTimerThreshold MO: ChannelSwitching

• Description: Throughput threshold used to achieve hysteresis for downswitching from dedicated channel to
FACH/RACH. Once the throughput on both the uplink and downlink has fallen below the value of
downswitchThreshold, a downswitch to FACH/RACH is normally requested after the length of time set in
downswitchTimer. However, the downswitch is not requested if the throughput has subsequently increased above
this threshold value.

CELL_FACH  CELL_DCH – Nokia
InactivityTimerDownlink/UplinkDCH InactivityTimerUplinkDCH
0 ..20 s, 2 – 5s 0 ..20 s, 2 – 5s
depends on current data rate 8 – 384 kbps depends on current data rate 8 – 384 kbps
InactivityTimerDownlink/UplinkDCH
• Category: Advanced Parameters
• MO: WAC; structured parameter
• Children Parameters:
• InactivityTimerDownlink/UplinkDCH128
• This parameters define the time indicating how long the radio and transmission resources are reserved after the
silence detection on downlink DCH, before release procedures.
• Range: 0 .. 20 s; Step: 1 s; default: for 8, 16 & 32 kbps: 5 s ; for 64 kbps: 3 s ; for 128, 256, 320 & 384 kbps: 2 s

CELL_FACH  CELL_PCH
CELL_FACH  CELL_PCH / URA_PCH

- If both the UE and RNC buffers (still) are empty for a further inactivity time, an (ongoing)
absence of traffic is adopted
- (Further) radio reconfiguration is performed
- UE no longer has to listen permanently to the network, but at certain times only (PICH)
CELL_FACH inactivity timer

Settings per RNC only
CELL_PCH  CELL_FACH
- If any data is to be sent either on the UL or DL
- In case of a cell update, after finishing the procedure the UE returns to CELL_PCH (or enters
URA_PCH, see next slide)

CELL_FACH  CELL_PCH – Huawei
F2PTvmTimeToTrig F2PTVMPTAT BeF2PStateTransTimer
Time hysteresis to initiate Time hysteresis to abort pending Time hysteresis to execute
downgrade procedure procedure downgrade
0..5000 ms, 5000 ms 250..16000 ms, 1000 ms 0..65535 s, 180 s
F2PTvmTimeToTrig MO = UUESTATETRANS
• Description: When the traffic volume is below the 4B threshold and remains so for the period specified by this
parameter, the event 4B is reported. This parameter can prevent unnecessary reports to be triggered, caused by
traffic volume variation. If this parameter is set to a small value, the UE with discontinuous data transmission will
mistakenly trigger event 4B, which increases state transition from the FACH channel to the PCH, signaling
messages over the air interface, and CPU usage. If this parameter is set to a large value, the UE is less likely to
trigger event 4B and stays in the CELL_FACH state even after data transmission ends. This wastes FACH
resources.
F2PTVMPTAT MO = UUESTATETRANS
• Description: Pending time after the traffic volume event 4B for state transition from FACH to PCH is reported. This
parameter is used to prevent too many traffic volume events 4B being reported. If this parameter is set to a small
value, the number of event 4B, procedure interactions, and call drop rate increase. If this parameter is set to a large
value, the UTRAN becomes insensitive to data transmission changes, which results in unnecessary state transitions
from the FACH channel to the PCH, and delayed data transmission.
BeF2PStateTransTimer MO = UUESTATETRANS
• Description: Timer for state transition from FACH or E_FACH to PCH of BE services, used to check whether the UE
in the CELL_FACH state is in the stable low activity state.If this parameter is set to 65535, UEs processing BE
services are not allowed to switch from CELL_FACH or E_FACH to CELL_PCH. If the value of this parameter is too
small, the UTRAN determines that DTX UEs or UEs with UL/DL alternate data transmission are in the low activity
state. In this case, F2P state transitions and cell update will be frequently triggered, and air interface reconfiguration
signaling will increase. If the value of this parameter is too large, the F2P state transition takes a long time, wasting
FACH resources.

CELL_FACH  CELL_PCH – Ericsson
inactivityTimer Switching performed from

1..1440, 8 s CELL_FACH to URA_PCH !
No CELL_PCH in Ericsson
inactivityTimer
• MO: ChannelSwitching
• Description: Time after which an inactive connection in CELL_FACH state is switched down to URA_PCH state.
When no data has been transmitted for this length of time, the RNC requests a downswitch from CELL_FACH to
URA_PCH. If URA_PCH state is not available, the UE is switched down to IDLE state. Both the downlink and
uplink throughput must have been 0 kbps for the connection to be considered inactive.

CELL_FACH  CELL_PCH – Nokia
UL_DL_activation_timer
0..120 s, 2 s
UL_DL_activation_timer
• MO: WAC
• Description: This timer is used on MAC -c to detect idle periods on data transmission (NRT RBs and SRBs) for the
UE, which is in Cell_FACH state. Based on this timer, the MAC -c gives the No_Data indication to the RRC, which
further can change the state of the RRC from Cell_FACH state to the Cell_PCH state (or URA_PCH state)

CELL_PCH  URA_PCH
CELL_PCH  URA_PCH
- If too many cell updates have been performed within a certain time, after the last one the
UE enters URA_PCH
- If an URA update is performed, the UE enters CELL_FACH and then returns to URA_PCH
Maximum number of cell updates

Cell update observation time
URA_PCH  CELL_PCH
- If any data is to be sent either on the UL or DL, the UE returns to CELL_FACH
- If the UE becomes inactive again, it returns to CELL_PCH and the cell update observing
cycle starts again

CELL_PCH  URA_PCH – Huawei
CELLRESELECTCOUNTER CELLRESELECTTIMER
1..65535, 9 1..65535, 180 s
CELLRESELECTCOUNTER MO = UUESTATETRANS
• Description: Threshold for the number of cell reselections. If the number of cell reselections performed by a UE in
the CELL_PCH state during a specific period is equal to or larger than this threshold, the RNC determines that the
UE has performed frequent cell reselections. This period is equal to the period when the timer determining frequent
cell reselections is taking effect. When the UE reports another cell update after the timer expires, the RNC informs
the UE to enter the URA_PCH state by sending the UE a CELL_UPADATE_CONFIRM message. If this parameter
is set to a very small value, UEs can quickly enter the URA_PCH state. However, the number of reconfiguration
signaling messages for state transitions increases as well as paging messages. If this parameter is set to a very
large value, it is difficult for UEs to enter the URA_PCH state and the number of cell update messages with a cause
value of cell reselection greatly increases.
CELLRESELECTTIMER MO = UUESTATETRANSTIMER
• Description: Length of the timer determining frequent cell reselections. If the number of cell reselections performed
by a UE in the CELL_PCH state during a specific period is equal to or larger than the value for
"CellReSelectCounter", the RNC determines that the UE has performed frequent cell reselections. This period is
equal to the period when this timer is taking effect. When the UE reports another cell update after the timer expires,
the RNC informs the UE to enter the URA_PCH state by sending the UE a CELL_UPADATE_CONFIRM message.
If this parameter is set to a very small value, it is difficult for UEs to enter the URA_PCH state and the number of cell
update messages with a cause value of cell reselection greatly increases. If this parameter is set to a very large
value, UEs can quickly enter the URA_PCH state. However, the number of reconfiguration signaling messages for
state transitions increases as well as paging messages.

CELL_PCH  URA_PCH – Ericsson
Ericsson does not support this state transition due to mobility, as Cell_PCH is not available anyhow.

CELL_PCH  URA_PCH – Nokia
CellReselectionObservingTime MaxCellReselections:
0 .. 60, 16 min 0 .. 100, 3 times
CellReselectionObservingTime
• MO: RNMOBI
• Category: Basic Parameters
• Description: The timer is set when the first Cell Update message due to 'cell reselection' is received while the UE is
in CELL_FACH or CELL_PCH state. In the expiry of the timer, the counter MaxCellReselections is reset.
If there are too many reselections coming from the UE within the observation time, the UE is switched to the
URA_PCH state. Otherwise the Cell_PCH state is chosen.
MaxCellReselections:
• MO: RNMOBI
• Description: This parameter specifies the maximum allowed number of Cell Reselections in the CELL_FACH or
CELL_PCH state before transition to the URA_PCH state. The amount of cell reselection is counted in both the
CELL_FACH and CELL_PCH states. When the UE is in the CELL_FACH state, the value of the counter
MaxCellReselections cannot be used as a trigger for the CELL_FACH to URA_PCH transition, but it is used when
deciding a target state after the MAC-c entity has sent an inactivity indication to Layer 3.

CELL_PCH / URA_PCH  RRC Idle
- After entering CELL_PCH / URA_PCH, a third inactivity timer is

started
- If it expires, the RAB is released
CELL/URA_PCH inactivity timer Settings per RNC only
T305 The periodic cell update/URA update timer (MS timer)

Default value by Huawei, Ericsson and Nokia = 30 min

CELL_PCH / URA_PCH  RRC Idle – Huawei (1/2)
PsInactTmrForInt ProtectTmrForInt
1..14400, 20 s 1..14400, 20 s
PsInactTmrForInt MO = UCELLALTIMER
• Description: Interactive service T1. If a UE performing PS interactive services has no data transmission within a
period of time specified by this timer, the PDCP layer requests the RRC layer to release the UE's services. This
parameter and "ProtectTmrForInt" in the "SET UPSINACTTIMER" command must be both set to zero or a non-zero
value. Otherwise, the system uses the RNC-level parameter "PsInactTmrForInt" rather than this parameter.
• If this parameter is set to a small value, the RNC is likely to release the RAB of a UE that stops processing services.
This saves network resources. However, the RNC may falsely regard UEs that are engaged in intermittent data
transmission as having entered the inactivity state, leading to frequent RAB releases and RAB assignment requests.
As a result, the number of signaling messages increases, the CPU usage of signaling message processing boards
increases, and the service setup delay prolongs. If this parameter is set to a large value, the RNC holds radio links
for a UE that stop processing services. This wastes network resources, such as dedicated and public channels. This
also increases the call drop rate. However, UEs that are engaged in intermittent data transmission will not frequently
initiate RAB setups and RAB releases, reducing signaling overheads and the CPU usage.
ProtectTmrForInt MO = UPSINACTTIMER
• Description: Interactive service T2. After sending release request to RRC layer, if the Interactive Radio Access Bear
haven't been released until the Interactive service T2 timeout, the PDCP layer will resend release request indication.
If this parameter is set to a very small value, the signaling overheads for RAB or Iu releases increase. If this
parameter is set to a very large value, resources of the UEs that have stopped processing services cannot be
released for a long period of time, wasting dedicated and public channels.

CELL_PCH / URA_PCH  RRC Idle – Huawei (2/2)
PsInactTmrForBac PROTECTTMRFORBAC
1..14400, 20 s 1..14400, 20 s
PsInactTmrForBac MO = UPSINACTTIMER
• Description: Background service T1. If a UE performing PS background services has no data transmission within a
period of time specified by this timer, the PDCP layer requests the RRC layer to release the UE's services. If this
parameter is set to a small value, the RNC is likely to release the RAB of a UE that stops processing services. This
saves network resources. However, the RNC may falsely regard UEs that are engaged in intermittent data
transmission as having entered the inactivity state, leading to frequent RAB releases and RAB assignment requests.
As a result, the number of signaling messages increases, the CPU usage of signaling message processing boards
increases, and the service setup delay prolongs. If this parameter is set to a large value, the RNC holds radio links
for a UE that stop processing services. This wastes network resources, such as dedicated and public channels. This
also increases the call drop rate. However, UEs that are engaged in intermittent data transmission will not frequently
initiate RAB setups and RAB releases, reducing signaling overheads and the CPU usage.
ProtectTmrForInt MO = UPSINACTTIMER
• Description: Background service T2. After sending release request to RRC layer, if the Background Radio Access
Bear haven't been released until the Background service T2 timeout, the PDCP layer will resend release request
indication. If this parameter is set to a very small value, the signaling overheads for RAB or Iu releases increase. If
this parameter is set to a very large value, resources of the UEs that have stopped processing services cannot be
released for a long period of time, wasting dedicated and public channels.

CELL_PCH / URA_PCH  RRC Idle – Ericsson
inactivityTimerPCH
0..240, 29 min
inactivityTimerPCH
• Description: Inactivity timer for URA_PCH. Time after which a connection in URA_PCH state is switched down to
IDLE state, if no upswitches have been requested during that time. If the inactivity timer is set per cell, the value
used is the one defined in the cell where the supervision was started. This is not updated at mobility.
So if no activity/data is detected in cell A and the UE moves to cell B, still without any activity/data, the inactivitytime
used is the one from cell A, not cell B

CELL_PCH / URA_PCH  RRC Idle – Nokia
MSActivititySupervision
0..1440, 29 min
MSActivitySupervision
• MO: WAC
• Description: Time supervision of user inactivity (for NRT RBs). The MSActivitySupervision timer is used in the RRC
states CELL_PCH and URA_PCH for supervising the inactivity of NRT RAB(s). The timer starts when a state
transition to either state is executed. The MSActivitySupervision timer stops when any activity of NRT RAB(s) is
detected and the MS is moved to the CELL_FACH or CELL_DCH state. The timer restarts (from the initial value)
when the inactivity of the NRT RAB(s) is detected and the MS is moved back to the CELL_PCH or URA_PCH state
again. In the expiration of the MSActivitySupervision timer, when the first "inactive state indication" (that is, cell/URA
update which does not cause the (re)initiation of the signalling or data flow) is received from the MS, the RNC asks
SGSN to release the Iu connection.
Note: If the parameter value is set to zero, the state transition to CELL_PCH/URA_PCH is not allowed. When
inactivity is detected in the CELL_FACH state, the MS is switched to the idle mode

Content
Packet Scheduling
 Introduction

Motivation
- High bit rates require high transmission power

- When moving away from Node B
 degrade of link quality due to lack of power
 decrease of bit rate required
UE
UE 384 K
128 K Node B
64 K

DL Quality Power Thresholds (1/2)
- DL RL power allocated to the service checked against maximum value allowed by AC

- If service power comes closer to max. value than an offset, bit rate is decreased
Radio link power

Max DPDCH power
Bad quality (e.g. e.g. 38 dBm)
Bad radio link quality
Bit rate decrease, no increase power offset
(2 dB) Bad quality power
Acceptable radio link quality Good quality threshold (e.g. 36 dBm)
No bit rate decrease power offset
Nokia allows already bit rate increase (4 dB)
Good quality power
threshold (e.g. 34 dBm)
Good radio link quality
All vendors allow bit rate increase
Bad quality power offset

Downgrade triggered if
actual RL power + bad quality power offset > maximum RL power

DL Quality Power Thresholds (1/2) – Huawei (1/2)
ThdEa
0~28 dB; None
EventAThred
• MO = UTYPRABQUALITYMEAS
• Description: Relative threshold for event Ea. Event Ea is reported when the absolute threshold for event Ea is
exceeded. Once the event is reported, operations related to the QoS control algorithm will be triggered in the
downlink. The following formula is used to calculate the absolute threshold for event Ea:
Absolute threshold for event Ea = Maximum downlink transmit power for RLs - Relative threshold for event Ea.
If this parameter is set to a large value, the absolute threshold for event Ea is low and operations related to the
QoS control algorithm will be easily triggered in the downlink. In such a case, UEs' data rates may be falsely
decreased or handovers may be falsely initiated. If this parameter is set to a small value, the call drop rate
increases, and the event can hardly be triggered as well as the preceding operations in the downlink

DL Quality Power Thresholds (1/2) – Huawei (2/2)
EventAThred
Reduction of the Power/Data Rate is triggered by Huawei also based on the RLC retransmission rate
0~1000; 160 per mill
EventAThred
• MO = UTYPRABRLC
• Description: Threshold of event A, that is, the upper limit of RLC retransmission rate. When the RNC detects the
RLC retransmission rate exceeds this threshold for a period of time, event A is triggered. In this case, the quality of
the radio link is poor or Iub interfaces are congested. Therefore, DCCC based on link stability is enabled to
decrease the rate and improve downlink coverage or congestion control measures are taken to decrease the rate
and relieve the congestion on the Iub interfaces. If this parameter is set to a large value, event A for the RLC
retransmission rate will hardly be triggered. In this case, the DCCC-based data rate decreasing or rate decreasing
based on Iub congestion control algorithm cannot be triggered in time. As a result, users in weak coverage areas
are likely to experience call drops due to poor downlink coverage or users' throughput decreases because of
congestion on the Iub interfaces. This affects user experience. If this parameter is set to a small value, event A for
the RLC retransmission rate will easily be triggered. In this case, the DCCC-based data rate decreasing or rate
decreasing based on Iub congestion control algorithm is likely to be triggered, leading to more unnecessary DCCC-
based rate decreasing procedures or congestion control based rate decreasing procedures due to improper
triggering of the algorithm. This results in a high risk of call drops of users in weak coverage areas and low downlink
throughput, affecting user experience.

DL Quality Power Thresholds (1/2) – Ericsson
downswitchPwrMargin
0..20, 2 dB Settings per RNC only
downswitchPwrMargin
• Description: Margin on transmitted code power in the downlink, for triggering a downswitch to a lower DCH rate
when the transmitted power is too high. Expressed relative to the maximum allowed code power.
When the difference between the downlink transmitted code power and the maximum allowed code power has
been less than the value of this margin for the length of time set in coverageTimer, a downswitch from DCH to a
lower DCH rate is requested.
Power Ptx Maximum of a certain data rate

downswitchPwrMargin
Triggering of Downgrade
Ptx of a certain data rate

DL Quality Power Thresholds (1/2) – Nokia (1/2)
DLOptimisationPwrOffset DLOptimisationProhibitTime DLORLAveragingWindowSize
0..6, 2 dB + + 0...10 s, 4s
0...120 s, 2s
DLOptimisationPwrOffset
• MO: RNPS
• Description: Power offset for dynamic link optimization. The parameter is used to define the DL transmission power
level that triggers the dynamic link optimisation. The value defines a power level relative to the maximum DL
transmission power (Ptx,max). Dynamic link optimisation is triggered if the measured average RL transmission
power (Ptx,average) added to the value of the parameter exceeds the maximum DL transmission power. Only the
cells under the SRNC can trigger dynamic link optimisation.
Power Ptx Maximum of a certain data rate
DLOptimisationPwrOffset
Triggering of Downgrade
Ptx of a certain data rate

DL Quality Power Thresholds (1/2) – Nokia (2/2)
DLOptimisationPwrOffset DLOptimisationProhibitTime DLORLAveragingWindowSize

0..6, 2 dB + + 0...10 s, 4s
0...120 s, 2s
DLoptimizationProhibitTime
• MO: RNPS
• Description: The parameter determines a period of time during which a downgrade due to Dynamic Link
Optimisation is not allowed. NRT user bitrate is not downgraded due to Dynamic Link Optimisation procedure
during the guard time period after a successful upgrade of a user bitrate or allocation of a DCH greater than 0 kbps.
Successive downgrades due to Dynamic Link Optimisation are also prohibited during this period of time.
DLORLAveragingWindowSize
• MO: WBTS
• Description: This parameter defines the use of transmitted code power of radio link averaging in RNC for dynamic
link optimisation functionality. The parameter defines how many measured radio link specific average transmission
powers of the DPDCH bits (Ptx_average) are included in the sliding measurement window. Averaged Ptx_average
in RNC is used in dynamic link optimisation functionality. Dynamic link optimization functionality is triggered if the
sum of the averaged Ptx_average in RNC and the value of the DLOptimisationPwrOffset parameter exceeds the
maximum DL transmission power. The special value 0 means that this parameter does not affect measurement
averaging in RNC. The recommended value is 4 when the radio link/dedicated measurement reporting period is 500
ms.

DL Quality Power Thresholds (2/2)
- Bit rate upgrade not triggered, if RL power low enough again

Upgrade performed upon capacity request only
- But upgrade allowed only, if afterwards RL power not too high again
Good quality power offset
Upgrade allowed if actual RL power + good quality power offset < maximum RL power

DL Quality Power Thresholds (2/2) – Huawei
BePwrMargin
Hysterese to avoid ping-pong
0..10, 1 dB
BePwrMargin
• MO = UDCCC
• Description: Relative power margin for event F triggering threshold. This relative power margin is only for the
scenario where only one BE service is going on. Without this parameter, after the DCCC function increases UEs'
data rates, their data rates are decreased again once event F is reported. This parameter helps prevent such
frequent data rate increases and decreases. The following formula specifies the relationship between this parameter
and the event F triggering threshold:
Event F triggering threshold = Maximum downlink transmit power of a radio link specific to the target data rate -
"ThdEa" - "BePwrMargin".
• If this parameter is set to a very large value, the event F triggering threshold will become very low and as a result
more UEs will experience low data rates. This causes the QoS to deteriorate. If this parameter is set to a very small
value, the event F triggering threshold will become very high and as a result many UEs' data rates will be increased.
This may lead to a high call drop rate.

DL Quality Power Thresholds (2/2) – Ericsson
upswitchPwrMargin
0..10, 3 dB upswitchPwrMargin – downswitchPwrMargin  Hysterese to avoid ping-pong
1 dB bigger than bad quality power offset
upswitchPwrMargin
• Description: Margin on transmitted code power in the downlink, used to prohibit upswitches when the transmitted
power is too high. Expressed relative to the maximum allowed code power.
Before an upswitch from DCH to a higher DCH rate is requested, an estimate of the power increase due to the
upswitch is made. The upswitch is prohibited if the difference between the the maximum allowed code power, and
the sum of the current transmitted code power and the estimated increase in power, is less than the sum of this
margin and the value of downswitchPwrMargin.

DL Quality Power Thresholds (2/2) – Nokia
• Bit rate upgrade is based on DL traffic volume measurement reports (capacity requests):
• The change of the radio link power conditions does not trigger upgrade
• Normal PS bit rate allocation and upgrade methods applied (e.g. Flexible Upgrade)
• Possible triggering of Dynamic Link Optimization is checked before bit rate is upgraded, in order
to avoid ping-pong effect:
• New maximum Ptx is calculated by AC according to the new requested bit rate
• Initial transmission power Ptx for the new bit rate is calculated by AC.

UL Quality Power Thresholds – Huawei
- In case of Nokia and Ericsson the UE autonomously decreases bit rate in case of too
high Tx power
- In case of Huawei the events 6A and 6B are used to decide about bit rate downgrade
and upgrade
Bit rate downgraded

ULTHD6A1 ULTRIGTIME6A1 if UE power higher
0..82, 2 dB 0..5000, 320 ms If already minimum bit rate or most robust AMR codec
UE put into compressed mode
ULTHD6B1 ULTRIGTIME6B1 Downgrade stopped

0..82, 2 dB 0..5000, 320 ms if UE power lower
ULTHD6A2 ULTRIGTIME6A2 Upgrade stopped

0..82, 10 dB 0..5000, 320 ms if UE power higher
ULTHD6B2 ULTRIGTIME6B2 Bit rate upgraded upon request

0..82, 10 dB 0..5000, 320 ms if UE power lower

Content
Packet Scheduling
 Introduction
Principle of Buffer Triggered Bit Rate Adaptation
UL RLC Buffer Thresholds
DL RLC Buffer Thresholds
Throughput Triggered Bit Rate Adaptation

Principle of Buffer Triggered Bit Rate Adaptation
- Packet scheduler offers bit rates upon request

- Bit rate request generated, if amount of data in RLC buffer
exceeds certain thresholds
UE buffer  UL bit rate request

UE RNC buffer  DL bit rate request
- Bit rate can be requested both in CELL_FACH and CELL_DCH RNC

UE
RLC Buffer state corresponding to the following transitions
RNC
CELL_FACH  CELL_DCH low or high bit rate RLC Buffer
CELL_DCH low bit rate  CELL_DCH high bit rate

UL RLC Buffer Thresholds (1/2)
UE RLC buffer data

UL High traffic
volume threshold
(e.g. 1024 byte)
UL Traffic volume
time hysteresis (1 s)
UL Low traffic
volume threshold
(e.g. 128 byte)
UL Traffic volume
Time
UE capacity request to RNC for UE capacity request to RNC for CELL_DCH
CELL_FACH  CELL_DCH low rate low  CELL_DCH high rate (not used by
Ericsson)
UL low traffic volume threshold

UL high traffic volume threshold
UL traffic volume time hysteresis

UL RLC Buffer Thresholds (1/2) – Huawei (1/2)
BeF2DTvmThd (= low threshold) BeF2D/ETvmTimeToTrig (2 parameters)
16 byte…768 Kbyte, 256 bytes 0..5000, 0 ms
BeF2DTvmThd
• MO = UUESTATETRANS
• Description: This parameter specifies the traffic volume threshold of event 4A for triggering a FACH-to-DCH
transition for BE services. It is recommended that the value of this parameter be larger than that of the
"D2F2PTvmThd" parameter in the "SET UUESTATETRANS" command. If the configured value of this parameter
is smaller than that of the "D2F2PTvmThd" parameter in the "SET UUESTATETRANS" command, use a value
which is one level higher than the value of the "D2F2PTvmThd" parameter as the actual value of the
BeF2DTvmThd parameter. If this parameter is set to a small value, the UE is more likely to trigger state transition
from the FACH or RACH channel to the DCH channel, which wastes DCH resources. If this parameter is set to a
large value, the UE is less likely to trigger state transition from the FACH or RACH channel to the DCH channel.
As a result, the FACH is congested and user experience deteriorates
BeF2D/ETvmTimeToTrig
• MO = UUESTATETRANS
• Description: This parameter specifies the occurrence time of 4A event for triggering the transition of BE services
from FACH to DCH/E-DCH. This parameter can prevent unnecessary reports to be triggered, caused by traffic
volume variation. If the value of this parameter increases, event 4A reporting triggered by the BE service will be
delayed and the probability of triggering event 4A will increase. If UEs in the CELL_FACH have data
transmission, more common channel resources are consumed.
• See also BeF2ETvmTimeToTrig

UL RLC Buffer Thresholds (1/2) – Huawei (2/2)
Event4aThd(= high threshold) TimetoTrigger4A

16 byte…768 Kbyte, 1024 byte 0..5000, 240 ms
Event4aThd
• MO = UTYPRABDCCCMC
• Description: Traffic upper limit for the DCH to trigger event 4A. If this parameter is set to a large value, event
4A for DCH traffic can hardly be triggered. As a result, the DCH data rate can hardly be increased and user
experience deteriorates. If this parameter is set to a small value, event 4A for DCH traffic can be easily
triggered. In such a case, the DCH data rate can be easily increased and user experience improves. However,
more cell resources are consumed.
TimetoTrigger4A
• Description: Holding period before triggering event 4A for DCH traffic. This parameter ensures event 4A is not
repeatedly reported when DCH traffic fluctuates. Event 4A is reported when the DCH traffic volume exceeds
the value for "Event4aThd" for a period of time longer than the value for "TimetoTrigger4A". If this parameter is
set to a large value, the holding period prolongs. In such a case, event 4A for DCH traffic can hardly be
triggered and user experience deteriorates. However, less cell resources are consumed. If this parameter is
set to a small value, event 4A for DCH traffic can be easily triggered and user experience improves. However,
more cell resources are consumed.

UL RLC Buffer Thresholds (1/2) – Ericsson (1/2)
ulRlcBufUpswitch (only low threshold) upswitchTimerUl
8 .. 8192, 256 byte 0..10, 0.5 s
ulRlcBufUpswitch
• Description:Uplink RLC buffer threshold for triggering an upswitch from CELL_FACH or URA_PCH to CELL_DCH.
If the RLC buffer load of a UE exceeds this threshold while the UE is in CELL_FACH, causing the UE to send a
measurement report, an upswitch request is issued by the RNC upon reception of the measurement report.
If the RLC buffer load of a UE exceeds this threshold while the UE is in URA_PCH, causing the UE to send a Cell
Update message with cause "Uplink Data Transmission" and the Traffic Volume Indicator IE set, an upswitch
request is issued by the RNC upon reception of the Cell Update message. The upswitch from URA_PCH is only
applicable if RncFeature=DirectUpswitchUra is activated.
upswitchTimerUl
• Description:Time after which an uplink radio bearer on DCH with high throughput is upswitched to a higher DCH
rate. When the uplink throughput has been above the percentage defined by bandwidthMarginUl for this length of
time, an upswitch from DCH to a higher DCH rate is normally requested. However, the upswitch is not requested
after a throughput-based downswitch unless the uplink throughput has fallen below the value of
ulThroughputAllowUpswitchThreshold at least once since the downswitch. The upswitch is also not requested if it
would cause the transmitted power to become too high, as defined using upswitchPwrMargin.

UL RLC Buffer Thresholds (1/2) – Ericsson (2/2)
bandwidthMarginUl
0..10o%, 90%
bandwidthMarginUl
• Throughput threshold for triggering an upswitch of an uplink radio bearer on DCH to a higher DCH rate. Expressed
relative to the maximum allowed rate for the currently allocated radio bearer.
When the uplink throughput has been above this threshold for the length of time defined by upswitchTimerUl, an
upswitch from DCH to a higher DCH rate is normally requested. However, the upswitch is not requested after a
throughput-based downswitch unless the uplink throughput has fallen below the value of
ulThroughputAllowUpswitchThreshold at least once since the downswitch. The upswitch is also not requested if it
would cause the transmitted power to become too high, as defined using upswitchPwrMargin.

UL RLC Buffer Thresholds (1/2) – Nokia (1/2)
TrafVolThresholdULLow TrafVolThresholdULHigh
8 .. 1024, 128 byte 8..24576, depends on the bit rate
TrafVolThresholdULLow MO: WAC Category: Advanced Parameters

• Description: This parameter defines (in bytes) the threshold of data in the RLC buffers of SRB3, SRB4, and all NRT
RBs that trigger the cell update message with traffic volume indicator (TVI) when the UE is in URA_PCH or
CELL_PCH state or the uplink traffic volume measurement report when the UE is in Cell_FACH state.
If the threshold is exceeded, UE is directly transferred to Cell_DCH state. Otherwise, the UE sends data on RACH.
TrafVolThresholdULHighBit Rate MO: RNPS Category: Advanced Parameters

• Description:Traffic volume threshold for uplink NRT DCH bit rates. Structure PSParameters. Defaults:
• TrafVolThresholdULHighDCH256 - 2048 bytes
• TrafVolThresholdULHighDCH64 - 1024 byte
• TrafVolThresholdULHighDCH32 - 1024 byte
• The parameter defines the threshold of data in RLC buffer of RB in bytes. This threshold triggers the uplink traffic
volume measurement report when the UE is in a Cell_DCH state and DCH is allocated for the radio bearer.

UL RLC Buffer Thresholds (1/2) – Nokia (2/2)
TrafVolTimeToTriggerUL
0.5000, 0 s
TrafVolTimeToTriggerUL
• MO: RNPS
• Description: This parameter defines the time period between the timing of event detection and the timing of sending
a traffic volume measurement report.
This parameter is sent to the UE using the RRC: MEASUREMENT CONTROL message.

UL RLC Buffer Thresholds (2/2)
No capacity request, as
pending time still running
UE RLC buffer data (not used by Ericsson)

UL High traffic
volume threshold
(1024 byte)
UL Traffic volume
UL Low traffic
volume threshold
(128 byte)
UL Traffic volume UL Traffic volume
time hysteresis (1 s) pending time (2 s)
Time
UE transmits capacity UE transmits capacity
request to RNC for request to RNC for
CELL_FACH  current state 
CELL_DCH low rate CELL_DCH high rate
UL traffic volume pending time

UL RLC Buffer Thresholds (2/2) – Huawei
PendingTime4A
0.25..16, 4 s
PendingTime4A
• Description: Period during which event 4A for DCH traffic cannot be reported again after one such event is
reported. If this parameter is set to a large value, the reporting interval between two such events prolongs and
user experience deteriorates. After one such event is reported, UEs' data rates cannot be quickly increased if
the UEs have experienced data rate increase failures and restrictions imposed on data rate increases have
been lifted. If this parameter is set to a small value, event 4A will be reported many times, which increases
RNC computation.

UL RLC Buffer Thresholds (2/2) – Nokia
TrafVolPendingTimeUL
0.25..16, 4 s
• MO: WAC
• Description: This parameter indicates the time (in seconds) during which UE is forbidden to send any new traffic
volume measurement reports with the same traffic volume event identity, even if the triggering condition is fulfilled
again. This parameter also indicates the time during which the UE blocks DTCH transmissions on the RACH after a
measurement report is triggered. The parameter is sent to UE using an RRC: MEASUREMENT CONTROL
message. This parameter also indicates the time (in seconds) during which MAC-D of RNC is for bidden to send
any new uplink release/downgrade request due to low utilized NRT DCH with same dedicated transport channel,
even if the triggering condition is fulfilled again.

DL RLC Buffer Thresholds
- Exactly the same algorithm for bit rate adaptation as on UL

- Completely analogue parameters to UL
- If bit rate is requested for one direction only, the reverse direction just gets a DCH with
minimum bit rate
Nokia Huawei Ericsson

TrafVolThresholdDLLow BeF2DTvmThd (= low dlRlcBufUpswitch (only low threshold)
8 .. 1024, 128 byte threshold) 16 byte…768 Kbyte, 0..2000, 500 byte
256 bytes
TrafVolThresholdDLHigh downswitchTimer
8..24576, depends on the eF2D/ETvmTimeToTrig 0..10, 1 s
data rate 0..5000, 0 ms
Event4aThd (= high threshold)

TrafVolTimeToTriggerDL
16 byte…768 Kbyte, 1024 byte
0.5000, 0 s
TimetoTrigger4A
0..5000, 240 ms
TrafVolPendingTimeDL
0.25..16, 4 s PendingTime4A
0.25..16, 4 s

Event 4B RLC Buffer Thresholds – Huawei
- If in Cell_DCH traffic volumes falls below specific threshold again for a certain time
Generate event 4B
Perform bit rate downgrade to next lower level
Event4bThd TimetoTrigger4B
8 byte…512 Kbyte, None (128 byte) 0..5000, 2560 ms
Event4bThd MO = UTYPRABDCCCMC
• Description: Traffic lower limit for the DCH to trigger event 4B. If this parameter is set to a large value, event
4B for DCH traffic can be easily triggered but user experience deteriorates. If this parameter is set to a small
value, event 4B for DCH traffic can hardly be triggered. In such a case, user experience improves but more
cell resources are consumed.
TimetoTrigger4B MO = UTYPRABDCCCMC
• Description: Pending Time After Triggering of Event 4B[ms]. Holding period before triggering event 4B for DCH
traffic. This parameter ensures event 4B is not repeatedly reported when DCH traffic fluctuates. Event 4B for
DCH traffic is reported when the DCH traffic volume does not exceed the value for "Event4bThd" for a period
of time longer than the value for "TimetoTrigger4B". If this parameter is set to a large value, the holding period
prolongs. In such a case, event 4B for DCH traffic can hardly be triggered and more cell resources are
consumed. However, user experience improves. If this parameter is set to a small value, user experience
deteriorates but less cell resources are consumed.

Throughput Triggered Bit Rate Adaptation (1/4)
- Main criterion of the user activity is the throughput

- Throughput very close to scheduled bit rate  upgrade to target bit rate
Throughput far below scheduled bit rate  downgrade to target bit rate
Throughput
128K
High throughput threshold e.g. 120K
64K
High throughput threshold e.g. 60K
Low throughput threshold e.g. 56K
Downgrade e.g. Upgrade e.g. Upgrade e.g.

Time
128K  64K 64K  128K 128K  256K
High throughput threshold for UL/DL

Target bit rate for upgrade on UL/DL
Low throughput threshold for UL/DL

Target bit rate for downgrade on UL/DL

- Huawei
For upgrade and downgrade
1 parameter to define utilization threshold per bit rate level (8 levels 8..384 Kbit/s available)
1 parameter to define time hysteresis (not shown here)
Within 1 cell only 3 of the 8 bit rate levels can be selected

Minimum, intermediate and maximum level (e.g. 64,128 and 384 Kbit/s)
If actual utilization very close to actual level → upgrade attempt
If actual throughput significantly below next lower level → downgrade
RATIOFORRATE8/16/32/64/128/144/256/384
0..100, 90/90/90/90/80/80/80/75%

- Nokia
For upgrade
1 parameter to define utilization threshold of current bit rate
For downgrade
2 parameters to define target bit rates for moderate / strong downgrade per source bit rate
2 parameters to define corresponding time hysteresis per source bit rate (not shown here)
1 parameter to define utilization threshold of target bit rate
DCHUtilUpperDowngradeThrBitRate
Target bit rate for moderate downgrade
16,32,64,128,256 kbps for 32,64,128,256,384 kbps NRT
DCHUtilLowerDowngradeThrBitRate
Target bit rate for moderate downgrade Settings per RNC only
8,8,16,32,64 kbps for 32,64,128,256,384 kbps NRT
DCHUtilBelowDowngradeThr DCHutilHighBelowNRTDataRateThr
0 .. 20%, 6 % i.e. (100-6)% = 94% utilization 0 .. 20%, 6 % i.e. (100-6)% = 94% utilization

- Ericsson
For upgrade
2 parameter to define utilization threshold
For downgrade
1 parameter to define utilization threshold
Only the bit rate levels 64, 128 and 384 Kbit/s are supported
If actual utilization very close to actual level → upgrade attempt
If actual throughput significantly below next lower level → downgrade
ulDownswitchBandwidthMargin BandwidthMargin dlThroughputAllowUpswitchThreshold

0..100, 80% 0..100, 90% (general threshold) 0..100, 0% = not used
dlDownswitchBandwidthMargin BandwidthMarginUl Threshold after previous downgrade due
0..100, 80% 0..100, 90% (general threshold) to throughput
ulThroughputAllowUpswitchThreshold
0..100, 0% = not used
Threshold after previous downgrade due
to throughput

Content
Packet Scheduling
 Introduction
 RLC Buffer Triggered Bit Rate Adaptation
Bit Rate Increase
Bit Rate Decrease

Bit Rate Increase (1/4)
- Decision to serve capacity request completely analogue to admission of RAB

- Especially for PS many different service profiles have to be taken into account
Traffic class
Traffic handling priority (low / intermediate / high priority for interactive services) THP
Allocation retention priority (for all services) ARP which covers the following properties
- Low / intermediate / high priority to allocate / retain the service
- Pre-emption capability
- Pre-emption vulnerability
- Queuing allowed or not
ARP1
Streaming ARP2
ARP3
ARP1
ARP2
ARP3
THP1 ARP1
Service Interactive THP2 ARP2
THP3 ARP3
ARP1
ARP2
ARP1 ARP3
Background ARP2
ARP3
Nokia
- Three possible scenarios
Load both on UL and DL remains < load target → any capacity request served
Load both on UL and DL remains < load target + offset → priority based scheduling
Load either on UL or DL becomes > load target + offset → any request rejected
- Priority based scheduling
Downgrade running user to serve incoming user, so that load remains < load target
One can select among the following scenarios
- Priority of incoming user must be > than priority of running user
- Priority of incoming user must be just = priority of running user
- Priority of incoming user not taken into account at all
- Queuing
Rejected capacity requests queued for a configurable time
Queued requests can be ranked
- Just by time
- First by priority, than by time
- Pre-emption (only for incoming RT service)
Release of RT RAB (for incoming emergency call only)
Switchback to Cell_FACH of NRT service
Bit Rate Increase – Nokia
• The packet scheduling allocates in the following way:
– initial bit rate is allocated in Dl and UL when DCH is not allocated for NRT RB and PS receives an UL or a DL
capacity request where low data amount is reported
– maximum bit rate in UL and initial bit rate in DL. Are allocated when DCH is not allocated for NRT RB and PS
receives an UL capacity request where high data amount is reported
– maximum bit rate in DL and initial bit rate in UL when DCH is not allocated for NRT RB and PS receives a DL
capacity request where high data amount is reported
– maximum bit rate for UL or DL is allocated when the bit rate in UL or DL is lower than the maximum and the
PS receives a Capacity reguest for UL or DL where high amount is reported.
InitialBitRateUL InitialBitRateDL MaxBitRateULPSNRT MaxBitRateDLPSNRT
8..384 kbps; 64 kbps 8..384 kbps; 64 kbps 8..384 kbps; 384 kbps 8..384 kbps; 384 kbps
Allocated
Bit Rate
Maximum bit Rate
Capacity request Allocation to Maximim Bit Rate if high data

is transmitted amount reported and if conditions allow
Initial Bit Rate
0 bit rate
AC accepts the connection

All cell level parameters
Bit rate Increase - Scheduling Period – Nokia
SchedulingPeriod
50...2000 ms; 100 ms
• MO: WBTS
• Description: This parameter defines the period of the resource allocation for the resource requests of the PS
interactive and background services. The PS interactive and background service resource requests, which result in
the allocation of a DCH in either of the two transfer directions, are processed each scheduling period. If the HSPA
channels are selected only for the resource request, then the MAC-d flows are established without waiting for the
next scheduling moment.
All RT type of resource requests are handled without waiting for the next scheduling moment.

Bit rate Increase - Scheduling targets in UL – Nokia 1/2
• Packet Scheduler applies scheduling targets (as in the case of RT Admission Control) to ensure that existing
services do not experience quality degradations
• ΔLoad is the portion of new scheduled load
– calculations of load change follow same formulas used in AC
Condition to be fullfield for the scheduling:

[(Load produced by DCHs in the cell) + (non controllable Load by HSUPA users) + Load
produced by streaming services over HSUPA) + ΔLoad < (min Load produced by DCH)]
or
[Prx_total + ΔPrx < Prx_target and
(Load produced by DCHs in the cell) + (non controllable Load by HSUPA users) + Load
produced by streaming services over HSUPA) + ΔLoad < (max allowed Load produced by
DCH)]
Load in %
PrxLoadMarginDCH
0..30; 0.1; 2 dB =1.585  (min Load produced by DCH) = 37%
PrxLoadMarginMaxDCH
0..30; 0.1; 0 dB  < (max allowed Load produced by DCH) not checked

Bit rate Increase - Scheduling targets in UL – Nokia 2/2
PrxLoadMarginDCH
0..30; 0.1; 2 dB =1.585  (min Load produced by DCH) = 37%
PrxLoadMarginDCH
• MO: WCEL
• Description: Interference margin for the minimum UL DCH load. This parameter defines the minimum capacity that
is allowed for the uplink DCH traffic in the cell without considering the received wide band interference for the
throughput based traffic load. The parameter introduces a safety margin for the received interference power: it
defines how close to the planned target the interference power caused by the own cell DCH users is allowed to
increase without changing the network stability when the permitted DCH load is achieved. When the DCH traffic
load exceeds the threshold defined with the parameter, the RNC applies the interference based power estimations
in the DCH resource allocations.
• If the actual load is less then PrxLoadMarginDCH UL power estimation is not done for UL scheduling

Ericsson
- Two scenarios only
All load thresholds remain fulfilled → any capacity request served
One load threshold exceeded → consider priorities
- Incoming non-guaranteed request
Downgrade running non-guaranteed user to serve incoming user
Priority of incoming user must be > than priority of running user
- Incoming guaranteed request
Any running non-guaranteed service can be downgraded, independent on priority
Additionally pre-emption possible
- Release of guaranteed RAB of lower priority
- Switchback to Cell_FACH of non-guaranteed RAB of minimum bit rate

Bit Rate Increase – Ericsson
rateSelectionPsInteractive.dlPrefRate rateSelectionPsInteractive.dlPrefRate maxRate
0..2048, 16 kbps 0..384, 16 kbps 0..1600000, 10 bps, 406900
rateSelectionPsInteractive.dlPrefRate
• MO: UtranCell
• Description: Preferred target rate in the downlink for PS interactive RABs. Used both when setting up a non-
HSDPA PS interactive RAB, and when increasing the downlink rate of a PS interactive RAB from a rate below the
preferred rate. Only used if the flexible initial rate selection feature is active for PS interactive RABs. Otherwise 64
kbps is used as the preferred rate, regardless of the configured value.
rateSelectionPsInteractive.ulPrefRate
• MO: UtranCell
• Description Preferred target rate in the uplink for PS interactive RABs. Used both when setting up a non-EUL PS
interactive RAB, and when increasing the uplink rate of a PS interactive RAB from a rate below the preferred rate.
Only used if the flexible initial rate selection feature is active for PS interactive RABs. Otherwise 64 kbps is used as
the preferred rate, regardless of the configured value.
maxRate
• MO: UtranCell
• Description Maximum rate for maximum power mapping. Unit: 10 bps Intervall 0..1600000, default value 40690

Huawei
- Two scenarios only
All load thresholds remain fulfilled → any capacity request served
One load threshold exceeded → consider priorities
No downgrade of running user, but queuing and pre-emption only
- Typically three types of users (gold, silver, bronze)
Gold and silver pre-emption capable
Silver and bronze pre-emption vulnerable
Priority of incoming user must be > than priority of running use
- Queuing
As long queue not full, users just ordered by time
If queue full, users of lower priority deleted first

Bit Rate Decrease (1/5)
Nokia
Bit rate decrease is triggered, if
Power and throughput based downgrades:
• Power of the connection approaches the maximum allowed power for the actual bit rate
minus the offset.
• moderate / strong downgrade per source bit rate is the actual bit rate is going under a
certain threshold
Load dependent downgrades:
• Either UL or DL load > load target + offset

• Bit rate decrease is stopped if
• UL and DL load < load target

• Users to be downgraded are selected according
- Traffic class + traffic handling priority
- Allocation time
- Bit rate
Bit Rate Decrease – Nokia (1/2)
• MinAllowedBitRateDL parameter value defines the minimum possible bit rate for the conncetions.
• Reduction of the bit rate due to power used by the connection (Dynamic Link Optimization feature) can be
started only if the current bit rate is higher than HHoMaxAllowedBitRate parameter value
• If the data rate of the connection is already by HHoMaxAllowedBitRate then the compressed mode will be
started if power used by the conncetion approaches the maximum allowed minus the offset
MinAllowedBitRateDL HHoMaxAllowedBitrateDL
8..384 kbps; 8 kbps 8..384 kbps; 32 kbps
MinAllowedBitRateDL MO: WCEL Category: Basic Parameters

• Description: The parameter defines the minimum allowed bit rate in the downlink that PS can downgrade to the
NCR DCH bit rate in congestion situations. The allocated bit rate corresponds to the highest bit rate in the TFS from
which the TFCS is constructed.Note: If the maximum bit rate of the RAB is below the value of the minimum allowed
or initial bit rate parameter, it is allowed to schedule a lower NRT DCH bit rate. The maximum bit rate of the RAB is
used as a new minimum or initial bit rate for the RRC connection in question. The value should not be greater than
the value of MaxBitRateDLPSNRT, InitialBitRateDL of WCEL
MinAllowedBitRateDL MO: WCEL Category: Basic Parameters
• Description: This parameter defines the bit rate threshold that the maximum allocated user bit rate on the downlink
DPCH cannot exceed, so that the inter-frequency or inter-RAT (GSM) handover is possible due to high downlink
DPCH power level. The highest value of the parameter (512 kbps) represents all the supported bit rates above 384
kbps.

Bit Rate Decrease – Nokia (2/2)
DeltaPtxMaxDown
0..5, 0.2 dB, 0.8 dB
DeltaPtxMaxDown
• MO: WCEL
• Description: Defines the maximum transmitted downlink power decrease in a cell, used when bit rates are
decreased by the packet scheduler, relative to PtxTotal.

Ericsson
- Bit rate decrease is triggered, if
DL load > pwrAdm + pwrOffset
- Bit rate decrease is stopped if
DL load < pwrAdm
- In case of too high UL load > iFCong
No bit rate decrease
Just all new request rejected (HO still admitted), until UL load < iFCong again
- Users to be downgraded are selected according
Allocation and retention priority
AMR speech equivalents
Ericsson
iFCong MO: UtranCell
-112..-49.9, -49.9 dBm Threshold at which the cell is considered to be congested in the uplink.
The default setting disables uplink congestion measurements, in order to prevent
Settings per cell
problems during upgrading.

Huawei
- Distinguishes between load reshuffling and overload control
- Load reshuffling
Triggered already if load is moderate
Preventive actions to avoid overload
- Overload control
Triggered if load is high
Bit rate downgrade or even pre-emption

Huawei – load reshuffling

- Several possible trigger UlLdrTrigThd
UL load threshold to trigger reshuffling
UL / DL power
0..100, 55%
Code tree occupation UlLdrRelThd
Channel card occupation UL load threshold to stop reshuffling
Iub bandwidth 0..100, 45%
- Possible actions (operator can set priority order) DlLdrTrigThd
Inter-frequency HO (load balancing between carriers) DL load threshold to trigger reshuffling
Code reshuffling (reduce fragmentation of code tree) 0..100, 70%
Bit rate decrease (best effort users only) DlLdrRelThd
AMR bit rate decrease (more robust codec) DL load threshold to stop reshuffling
Inter-RAT HO 0..100, 60%
RT QoS renegotiation Settings per cell

Huawei – overload control

- Triggered by UL / DL power only
Other potential bottlenecks ignored
- Possible actions
Bit rate decrease (best effort users first)
Pre-emption (best effort users only)
UlOlcTrigThd DlOlcTrigThd
UL load threshold to trigger overload control DL load threshold to trigger overload control
0..100, 95% 0..100, 95%
UlOlcRelThd DlOlcRelThd
UL load threshold to stop overload control DL load threshold to stop overload control
0..100, 85% 0..100, 85%
Settings per cell

05 - 6255 - NAK - Packet Scheduling

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

05 - 6255 - NAK - Packet Scheduling

Uploaded by

Copyright:

Available Formats

Contents

UMTS/HSPA Radio Resource Management & Parameter

00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-2 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-3 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- Distributes radio capacity not used for RT to NRT radio bearers

00-7 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-8 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- When a RRC connection is set-up, usually the UE enters

RRC Idle Cell_DCH

00-10 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

UE initiated CELL_FACH  CELL_DCH

Radio link set-up

Radio bearer reconfiguration

00-12 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

RNC initiated CELL_FACH  CELL_DCH

Radio link set-up

Radio bearer reconfiguration

00-14 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Both buffers just (almost)

Radio link release

00-18 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

downswitchThreshold MO: ChannelSwitching

downswitchTimer MO: ChannelSwitching

downswitchTimerThreshold MO: ChannelSwitching

00-20 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-21 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

CELL_FACH  CELL_PCH / URA_PCH

CELL_FACH inactivity timer

00-23 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-24 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

inactivityTimer Switching performed from

00-25 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-26 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Maximum number of cell updates

00-28 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-29 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-30 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-31 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- After entering CELL_PCH / URA_PCH, a third inactivity timer is

CELL/URA_PCH inactivity timer Settings per RNC only

T305 The periodic cell update/URA update timer (MS timer)

00-33 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-34 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-35 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-36 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-37 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-40 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- High bit rates require high transmission power

00-41 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- DL RL power allocated to the service checked against maximum value allowed by AC

Radio link power

Bad quality power offset

00-43 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-44 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-45 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Power Ptx Maximum of a certain data rate

Ptx of a certain data rate

00-46 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Ptx of a certain data rate

00-47 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

DLOptimisationPwrOffset DLOptimisationProhibitTime DLORLAveragingWindowSize

00-48 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved