NSNPacketScheduling v1 R0

Packet Scheduling
1 © Nokia Siemens Networks RN31645EN40GLA1

Course Content
RRM Overview
Power Control
Load Control Recapitulation /
Admission Control Central Aspects of
RANPAR1
Packet Scheduling
Handover Control
HSDPA RRM & parameters
HSUPA RRM & parameters
HSPA+ features & parameters

Packet Scheduling
Module Objectives
At the end of the module you will be able to:

• Describe RRC states and their relationship to the packet scheduler
• Explain the RRC states and RRC state transition criteria
• Describe the process for bitrate allocation and de-allocation in detail
• Name and describe the Packet Scheduler features and the most important of the
related parameters

Packet Scheduler
Introduction
UE Specific PS
Cell Specific PS

Packet Scheduler
• Introduction
• Packet Scheduler Functions
• RRC states & transitions

Why Packet Scheduling?
• Suitable for controllable load (= best effort NRT)
• Requires fast resource allocation
Planned
Load Load/Power
(~ Power) Free Capacity Target
HSDPA
(dynamic power and
codes allocation
possible)
Non-Controllable Load
• CS real time traffic (also CS Voice over HSPA)
• UL: Interference from other cell users
• UL: Noise
• DL: Common channels
time
Packet Scheduler (PS) functions
PS consists of multiple different functions which can be categorised based on the scope of
the function
• UE-specific part: Functions working based on single radio link/bearer status, measurements &
conditions
• Cell-specific part: Functions working based on cell level measurements & conditions
UE Specific: Cell Specific:

• Capacity Request CR & Traffic • Cell Load measurement & averaging
Volume Measurements TVM • Queuing of capacity requests
• NRT DCH throughput measurements • Channel type selection
& minimum utilisation
• Power budget for packet scheduling
• Flexible upgrade of the NRT DCH &
• Bit rate allocation process/method
High throughput measurement
• Load increase - Bit rate upgrade
• Dynamic Link Optimisation DyLO for
• Load decrease - Overload control
NRT traffic coverage
• Enhanced Priority based Scheduling PBS

Bit rate upgrading & downgrading
• The DCH of a NRT RAB can be upgraded due to:
1) High amount of data in buffer – Capacity Request CR / Bit rate upgrade
2) High utilisation/throughput – Flexible upgrade of the NRT DCH data rate
• It is possible to upgrade the NRT DCH data rate from any bit rate below the maximum allowed bit rate
to the maximum allowed bit rate
• The DCH upgrade procedure is performed in CELL_DCH state and it requires the reconfiguration of
RL, transmission & RNC internal resources
• The DCH of a NRT RAB can be downgraded or released due to multiple causes:
1) Excessive DL power – DyLO for NRT traffic coverage feature
2) Different congestion situations – Enhanced PBS and overload control
3) Low utilisation/throughput – Throughput-based optimisation of the PS
4) Maximum bit rate limitation – Another RAB is setup for the same UE or during Mass Events
Handling UL DCH max bit rate is temporary limited
5) Inactivity of the radio bearer – possible specific handling of UE identified as Smartphone's by
Fast Dormancy Profiling
• The DCH downgrade procedure is performed in CELL_DCH state and it can be performed by
• RB Reconfiguration (also transmission, WBTS & RNC resources)
• Limitation of the maximum Transport Format Combinations TFC (temporary)
Packet Scheduler actions during call – Unloaded cell
AC - AC makes admission decision and allocates a 0 bit rate to the NRT radio bearer
PS1 - “Bit rate allocation”, after receiving a capacity request PS allocates initial bit rate
PS2 - “Flexible upgrade”, After receiving a capacity request PS allocates maximum (high) bit rate
PS3 - “Throughput-based optimisation“, PS performs RB reconfiguration to lower bit rate
PS4 - “Flexible upgrade”, PS performs RB reconfiguration to higher bit rate
PS5 - “RRC state transition”, PS initiates state transition to CELL_FACH due to inactivity
MaxBitRateDL/ ULPSNRT
[8, 16, 32, 64, 128, 256, 320, 384]
PS2 PS3 PS4 PS5 kbps, 384 kbps
Max. bit rate
Allocated bit rate
InitialBitRateUL/DL
8..384 kbps; 64 kbps
PS1
Initial bit rate
Actual throughput
AC
0 bit rate

Packet Scheduler actions during call – Loaded cell
Overload
Load Margin
Normal load
PS4 PS5
Allocated bit rate
Max. bit rate
PS2 PS3
InitialBitRateUL/DL
PS1 8..384 kbps; 64 kbps
Initial bit rate
AC Minimum bit rate

Actual throughput MinAllowedBitRateUL/DL
8..384 kbps; 8 kbps
PBS: Priority based scheduling
PBS FLXU EOLC FLXU FLXU: Flexible upgrade
EOLC: Enhanced Overload control
PS5: Inactivity  RRC state transition

Packet Scheduler
• Introduction
• Overview
• Packet Scheduler Functions
• Packet transfer states & transitions

RRC State Machine
UTRA RRC Connected Mode
UE in DRX mode UE in DRX mode

discontinuous reception URA_PCH CELL_PCH discontinuous reception
Dedicated resources Common resources

allocated (RACH-FACH)
allocated (DCH, HS) CELL_DCH CELL_FACH
Tx & Rx mode Tx & Rx mode
Common Channel
Setup
Cell selection
Cell re-selection Idle Mode
Listen to paging

PS Connection Establishment
CELL_
DCH UE RNC SGSN
RRC Connection Establishment (SRB)
MM, CC & SM (e.g. PDP Context Activation)

Traffic Volume RAB Assignment Request
Parameters
*RLC buffer level, reporting criteria, etc.
determination
Start
Measurement Control* [Traffic Volume Measurements] • UL_DLcapacityReqWait
• SignallingLinkInactivityTimer
UL_DLcapacityReqWait
RNC; 0..20; 0.5; 5 s UL_DLcapacityReqWait
expiry
SignallingLinkInactivityTimer yes
RNC; 0..20; 0.5; 2 s no
SignallingLinkInactivityTime
Capacity Request? expiry
yes
DCH for NRT RB(s) allocation CELL_
FACH

Transition: CELL_DCH to CELL_FACH InactivityTimerUplinkDCH
InactivityTimerDownlinkDCH
WAC; structured parameters
CELL_
DCH UE Node B RNC
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
PDU Transport on the DCH/DPCH
All data is sent and
RLC-U buffer is empty
RRC: RADIO BEARER RECONFIGURATION

Inactivity detected Start
message impacted if HS Cell_FACH activated in RNC
and UE is capable of HS RACH/HS FACH InactivityTimerUplinkDCH
InactivityTimerDownlinkDCH
SmartInactivityTimerDCH (for identified
Smartphone’s)
Radio Bearer Reconfiguration Expiry
Radio Bearer Reconfiguration Complete

SmartInactivityTimerDCH
CELL_ L2 configuration RNPS; 0 .. 20 s; Step: 0.2 s; 1.2 s;
FACH special value: 255 not used
Radio Link Release
AAL2 & RL resources!
Start
MAC: Inactivity detected
“FACH activation timer”
ExtendedULDLactivationTmr
Transition from .. / to .. RNC; 0..120; 1; 0 s
UL_DL_activation_timer
WAC; 0..10 s; 50 ms; 2 s
SmartInactivityTimerFACH
CELL_ RNPS; 0.5 .. 12 s; Step: 0.1 s; 1.5 s;
FACH UE RNC
Start
MAC: Inactivity detected
Cell Update
“FACH activation timer”
CELL_
PCH Physical Channel Reconfiguration
Expiry
“FACH activation timer” = ExtendedULDLActivationTmr for UEs NOT supporting CELL/URA_PCH

= UL_DL_activation_timer for UEs supporting CELL_PCH
or always if ExtendedULDLActivationTmr = 0
“FACH activation timer” for UEs recognized as Smartphone's = SmartInactivityTimerFACH
CELL_
PCH Start
Transition to CELL_PCH
Cell Update
MSActivitySupervision
RRC- Cell Update
IDLE Expiry
Cell Update Confirm
WAC; 0..1440; 1; 15 min
CellReselectionObservingTime
Transition from.. / to .. RNMOBI; 0 .. 60; 1; 16 min
High mobility UE is detected based on the frequency of cell reselections – if more than N reselections
occur within T seconds, RNC moves UE from Cell_FACH or Cell_PCH to URA_PCH:
CELL MaxCellReselections
or
PCH RNMOBI; 0 .. 100; 1; 3 times
CELL Inactivity detected
FACH Start
Cell Update (Cell reselection)
MaxCellReselections
URA_ CellReselectionObservingTime
PCH
Cell Update (Cell reselection)
Cell Update Confirm Expiry
The maximum time a UE can stay in UTRAN PCH states is limited by MSActivitySupervision parameter.
WAC; 0..1440; 1; 15 min
URA_
PCH Transition to URA_PCH
URA Update
RRC- URA Update
IDLE URA Update Confirm Expiry
T305
Periodic Cell/URA Updates
0 (no), 5, 10, 30..720 min; 30 min

Transition: CELL_DCH to CELL/URA_PCH
If UE has Multi-RAB allocated (voice + NRT
PS) & PS data inactivity detected (> 20 s)
 Reconfiguration Cell_DCH to Cell_PCH
or URA_PCH on voice call release “Slow mobility”
CELL_PCH
FastUECancel
RNMOBI; 1..59; 1; 1
Multi-RAB
(AMR + NRT PS)
CELL_DCH & PS data inactivity
(>20s)
before voice release “Fast moving UE”
( number of AS updates*) URA_PCH
FastUEPeriod
RNMOBI; 1..60; 1; 10s
FastUEThreshold
RNMOBI; 2..60; 1; 3
*complete Active Set cell change
DMCU: Data & Macro Diversity Combining Unit

Returning from Cell/URA_PCH to Cell_DCH
After transition: UE stays in Cell/URA_PCH until new data UL/DL in L2 buffers.
Direct return / reconfiguration to Cell_DCH possible, if traffic volume threshold TrafVolThrDLLowGTP
(non-configurable parameter) exceeded & CUCforPCHtoDCHallowed = true. Signaling procedure below.
RNC must send a paging notification to get in touch with UE.
UE answer with RRC: Cell Update (cause: paging response) CUCforPCHtoDCHallowed
defines if it is allowed to move UE directly
from Cell/URA_PCH to Cell_DCH
RNFC; false (0), true (1)
RNC initiated
TrafVolThrDLLowGTP
0..1024 Byte; 128 Byte
CELL_PCH or
URA_PCH
Data detected in GTP
Paging
CELL_ Cell Update (Paging Response)

FACH
UL & DL packet scheduling
Radio Link Setup

Cell Update Confirm
CELL_
DCH (SRB-DCH and 0/0 for PS)

Returning from Cell/URA_PCH to Cell_DCH
On reception on Cell Update message from UE, RNC checks if
a) CUCforPCHtoDCHallowed = 1 (true) and b) EcNo > CUCEcNoThreshold (default = – 8,5 dB)
 RNC sends Cell Update Confirm message.
If a) is <false> or b) reported EcNo < CUCEcNoThreshold>, RNC moves UE to Cell_FACH.
UE initiated CUCforPCHtoDCHallowed
0 = false, 1 = true
&
CELL_PCH or Ec/No > CUCEcNoThreshold
WCEL; 0..49; 1; 31 = -8.5 dB
URA_PCH
Data detected in UE L2
Rel5 UE Cell Update (Ec/No; Traffic Volume Indicator = TRUE)
& newer
CELL_ UL & DL packet scheduling
FACH
Radio Link Setup
Cell Update Confirm
CELL_DCH (SRB-DCH and 0/0 for PS)
CUC: Cell Update Confirm

Transition: Cell/URA_PCH to Cell_FACH
UE sends RRC: Cell Update message to RNC to inform about specific event.
Following trigger reasons for Cell Update procedure are 3GPP defined:
• Periodical Cell Update / URA Update (based on T305)
• Cell Update due to Cell Reselection (S-criteria)
• UL Data Transmission (L2 buffer data volume)
• RLC unrecoverable failure (L2 RLC procedure failure)
• Paging Response (answer to RNC paging)
• Re-entering service area (UE back in network coverage)
• Radio Link Failure (DL L1 fails in Cell_DCH)
CELL_PCH URA_PCH
Cell_FACH

Transition: CELL_FACH to CELL_DCH
UE initiated
Defined & discussed later
CELL_
FACH UE Node B RNC
Measurement Report (Traffic Volume Event; CR)

UL & DL packet scheduling
Radio Link Setup
Radio Bearer Reconfiguration

CELL_
DCH Radio Bearer Reconfiguration Complete

Transition: CELL_FACH to CELL_DCH
RNC initiated
CELL_
FACH UE Node B RNC
DL capacity need is
detected by MAC (CR)
Channel type selection
-> DCH
UL & DL
packet scheduling
Radio Link Setup
Radio Bearer Reconfiguration

CELL_ Radio Bearer Reconfiguration Complete
DCH

Common Channel CCH Setup: RAN1797
• RU20 feature
• supported by all UEs; no other features required CELL_DCH CELL_FACH
• No HW requirement in UTRAN
• Feature is part of basic software package (BSW)
• Available from RU10 on top onwards
RU20:
• RACH & FACH transport channels used for call setup
Common
• used for SRB setup & connection setup Channel
• Call setup on CCH faster than DCH
Setup
• Motivation: More efficient UTRAN resource allocation
• Less signaling processing power required
• No channel element (CE) required
• No dedicated transport resources on Iub interface Idle Mode
• Less spreading code resource used
• Allocation of RACH/ FACH or DCH based on
Establishment Cause EC received from UE (22 causes)
• Available SRB DCH bitrates: 3.4 kbps or 13.6 kbps CCHSetupEnabled
• RACH/FACH load is continuously monitored in RNC WCEL; 0 (Disabled), 1 (Enabled)
• CPICH EcNo criteria has impact on CCH allocation
• if Blind HO is activated (in MBLB) then CPICH RSCP criteria used for SRB mapping in
RRC setup instead of CPICH EcNo criteria

Common Channel CCH Setup RACHCapacity
BTS HW capacity reserved for
RACH (in 10 ms)
CPICHEcNoSRBMapRRC WCEL; 1..4; 1; 2 messages
Ec/No threshold for CCH setup RRC Connection Request rec. 4, when CCH call setup
WCEL; -24..0; 1; -8 dB enabled
CPICHRSCPSRBMapRRC + 3 other FACH/RACH load parameters*:

RSCP threshold for CCH setup see Packet Scheduling / Channel type
WCEL; -115..-25; 1; -92 dB Check: selection (FACH or DCH)
• CPICH Ec/No or CPICH RSCP**
RRCSetupCCHEnabledR99
CCH setup allowed for R99 UEs • RACH & FACH load & Ptx_Total good Ec/No,
WCEL; 0 (Disabled), 1 (Enabled) • Rel99 UE: CCH Setup allowed? CCH setup allowed &
no “high load”*
bad Ec/No,
CCH setup not
allowed or
high load*
CCH preferred for this
RRC Setup on
Establishment Cause?
Cell_DCH
SRBMapRRCSetupEC
Establishment Causes EC preferring CCHs
WCEL; default: 0001101111000000000000 (bin)
RRC Setup & initial

SRBBitRateRRCSetupEC
NAS signalling on
preferred bit rate for the SRB DCH
WCEL; values: 0 / 1: 3.4 / 13.6 kbps
CCHs
DCH DCH default: 0001101111000000000000 (bin)
* RachLoadThresholdCCH
3.4 kbps 13.6 kbps FachLoadThresholdCCH
* on RACH, FACH & Ptx_Total
PtxThresholdCCH
** CPICHRSCPSRBMapRRC & CUCRSCPThreshold used if RACHIntraFreqMesQuant
(WCEL, EcNo (0), RSCP (1), EcNo (0)) is set to 1

Common Channel Setup
RACH & FACH load + Ptx_total
RNC continuously monitors the load for RACH & FACH transport channels (on MAC-c entity inside RNC)
RACHCapacity
defines the HW capacity reserved for a RACH transport channel in the BTS. RACH Capacity is indicated as the number of
decoded RACH messages in a 10 ms radio frame.
WCEL; Range & Step: 1, 2, 3, 4; Default: 2 messages; Recommended when CCH call setup is enabled & used: 4 messages
Further Load Parameter taken into account for CCH or DCH setup decision
(for detailed discussion see: Packet Scheduling / Channel type selection: FACH or DCH)
The measurements are also used for the channel type selection for the SRB in the RRC connection setup phase and for the NRT
RB in the RRC state CELL_FACH.
RachLoadThresholdCCH
defines the threshold for the RACH load for DL channel type selection. If the threshold is exceeded, a DCH or HS-DSCH is
allocated. The RACH load is measured as the average number of acknowledged PRACH preambles over 2 radio frames, in
proportion to the RACH capacity which is given by the management parameter RACHCapacity multiplied by 2.
WCEL; Range: 0..100 %, step 1 %; default: 75 %
FachLoadThresholdCCH
defines the threshold for the total throughput of S-CCPCH (FACH/PCH) channel for DL channel type selection. If the threshold is
exceeded, DCH or HS-DSCH is allocated.
WCEL; Range: 0..100 %, step 1 %; default: 75 %
PtxThresholdCCH
defines the threshold for the total DL transmission power for DL channel type selection. If the threshold is exceeded, a DCH/HS-
DSCH is allocated. WCEL; Range: -5..0 dB; step 0.1 dB; Default: -1 dB

Common Channel Setup SRBMapRRCSetupEC
Establishment Cause Mapping Establishment Causes EC preferring CCHs
WCEL; default: 0001101111000000000000 (bin)
• 22-bit mapping coding various establishment reasons

Bit Cause Bit Cause
0 Originating conversational call 11 Inter-RAT cell change order
1 Originating streaming call 12 Registration
2 Originating interactive call 13 Detach
3 Originating background call 14 Originating high priority signalling
4 Originating subscribed traffic call 15 Originating low priority signalling
5 Terminating conversational call 16 Call re-establishment
6 Terminating streaming call 17 Terminating high priority signalling
7 Terminating interactive call 18 Terminating low priority signalling
8 Terminating background call 19 Terminating cause unknown
9 Emergency call (always 0) 20 MBMS reception
10 Inter-RAT cell re-selection 21 MBMS ptp RB request
Access causes in green prefer CCH – Access causes in black prefer DCH or HSPA

Common Channel Setup SRBBitRateRRCSetupEC
preferred bit rate for the SRB DCH
DCH Bitrate selection WCEL; values: 0 / 1: 3.4 / 13.6 kbps
default: 0001101111000000000000 (bin)
• 22-bit mapping coding various establishment reasons
Bit Cause Bit Cause
0 Originating conversational call 11 Inter-RAT cell change order
1 Originating streaming call 12 Registration
2 Originating interactive call 13 Detach
3 Originating background call 14 Originating high priority signalling
4 Originating subscribed traffic call 15 Originating low priority signalling
5 Terminating conversational call 16 Call re-establishment
6 Terminating streaming call 17 Terminating high priority signalling
7 Terminating interactive call 18 Terminating low priority signalling
8 Terminating background call 19 Terminating cause unknown
9 Emergency call (always 0) 20 MBMS reception
10 Inter-RAT cell re-selection 21 MBMS ptp RB request
Access causes in red use 13.6 kbps – Access causes in orange use 3.4 kbps

• URA reselection
• Periodic URA update Summary • Inactivity detection • Cell reselection
(stationary UE) during last 20sec (moving UE)
• Paging response (DL • RNC L2 resources at • Periodic cell update
• Fast UE with L2 inactivity (stationary UE)
data / signalling) low level
• UL Access (UL data / • Paging response (DL
signalling) • Activity supervision data/ signalling)
• Completion of Cell • UL Access (UL
URA_ Update procedure Cell_ data/signalling)
• Data in GTP buffer
PCH PCH
• Inactivity detection
of NRT RB • Completion of URA Update
• Release of RT RB procedure
• Max. # cell updates in
Cell_FACH / Cell_PCH
exceeded
Cell_ Cell_
DCH FACH
• Setup of RT/NRT RB
• RAB reconfiguration
RRC Connection
• DCH Up or Downgrade
Release
• Bit rate reduction due to • UL/DL data or
load reasons signalling
Idle • RT RB setup
• CN originated paging (MT Call)
Mode
• Random Access (MO Call) • SRB & Connection setup

Packet Scheduler
Introduction
UE Specific PS Procedures
Cell Specific PS Procedures
Cell_
DCH

Packet Scheduler
• UE SPECIFIC PS PROCEDURES
• Capacity Request (CR) & Traffic Volume Measurements (TVM)
• Throughput-based optimisation of the packet scheduler algorithm
• Flexible upgrade of the NRT DCH and High throughput measurement
• Dynamic link optimisation (DyLO) for NRT traffic coverage

Traffic Volume Measurement TVM reporting event (UL)
• Reporting criteria are signalled to the UE using an RRC: MEASUREMENT CONTROL message at
RB setup or when parameters are modified
• Event-triggered TVM reporting is used in NSN RAN TrafVolThresholdULLow
• Reporting event 4A WAC; 8 .. 1024 byte; 128 byte
• Reporting threshold (TrafVolThresholdULLow, HSRACHVolThrUL with High Speed Cell_FACH RAN1913
activated, SmartTrafVolThrUL with Fast Dormancy Profiling activated and TrafVolThresholdULHigh)
• Time-to-trigger (TrafVolTimeToTriggerUL and HSRACHTimeToTrigger
with RAN1913 activated) HSRACHVolThrUL
• Pending time (TrafVolPendingTimeUL used also with RAN1913 activated) WCEL; 0 .. 16384 byte; 512 byte
with Mass Event Handler
• in RU30 EP2 TrafVolPendingTimeUL = 8 s SmartTrafVolThrUL
• In RU40 RNPS: MEHTVMPendingTime is used WCEL; 8 .. 1024 byte; 256
byte
• An event-triggered report is sent when TCTV exceeds a threshold as follows
1. In CELL_FACH
• TCTV of RACH > TrafVolThresholdULLow
• TCTV of HS-RACH > HSRACHVolThrUL
2. In CELL_DCH without DCH or E-DCH for NRT RB x TrafVolThresholdULHigh
RNPS; 8..24576 byte; 1024 byte
• TCTV of NRT RB x > 8 bytes
3. In CELL_DCH with allocated bit rate is lower than maximum bit rate for NRT RB x
• TCTV of NRT RB x > TrafVolThresholdULHigh
TVM: Traffic Volume Measurement

TCTV: Transport Channel Traffic Volume
Capacity Request (CR) types
TVM reports are classified into the following 3 CR types:

1.Initial request for low bit rate (UL/DL); when
• The NRT RB in question has no previous DCH allocation
• RLC buffer payload < TrafVolThresholdDLHigh or TrafVolThresholdULHigh
• Low bit rate means minimum bit rate TrafVolThresholdULLow
WAC; 8 .. 1024 byte; 128 byte
TrafVolThresholdDLLow
2.Initial request for high bit rate (UL/DL); when WCEL; 8 .. 1024 byte; 128 byte
• The NRT RB in question has no previous DCH allocation

• RLC buffer payload => TrafVolThresholdDLHigh or TrafVolThresholdULHigh
TrafVolThreshold UL/DL High

3.Upgrade request for high bit rate (DL); when
• The NRT RB in question has a lower than RB maximum bit rate DCH allocated

Traffic volume measurement TVM reporting event (UL)
Reporting event:
4A: Transport Channel Traffic Volume becomes larger than an absolute threshold
UE in CELL_DCH: TrafVolThresholdULHigh (1024 Bytes) 3GPP

Transport Channel TS25.331
UE in CELL_FACH: TrafVolThresholdULLow (128 Bytes)
Traffic Volume
(= UE Buffer Load)
4A 4A
Measurement 4A
report has
information about
current
UE buffer load
time
TrafVolTimeToTrigger DL/UL
RNC; 0.5000 ms; 0 s
Measurement Report (Traffic Volume Event) RNC

UE

TVM reporting event (UL)
• If the UE does not receive DCH allocation nor bit rate upgrade (RRC message)
• It retransmits the TVM report to the network after UL TVM pending time
(TrafVolPendingTimeUL)
Transport Channel
Traffic Volume
(= UE Buffer Load)
No report
4A 4A
time
TrafVolPendingTimeUL
RNC; 0.25..16s; 2 s
TrafVolPendingTimeUL

Traffic volume measurement (DL, RNC)
• RNC performs traffic volume measurements TVM for each UL NRT RB when:
1. UE is in CELL_FACH state
2. UE is in CELL_DCH state but DCH or HS-DSCH is not allocated for the NRT RB
3. UE is in CELL_DCH state; allocated bit rate is lower than max. RB bit rate
• In the CELL_FACH state the UE has FACH as an DL transport channel
• DL TCTV measurement measures the total sum of buffer occupancies of
• All user plane radio bearers
• Signalling radio bearers SRB3 & SRB4, multiplexed onto the FACH
• DL TVM reports are RNC internal messages
• Reporting criteria sent from L3 to MAC entities when entity initialised or parameters modified
• Traffic volume measurements TVM are sent to higher layers: TrafVolThreshold DLLow
WCEL; 8 .. 1024 byte; 128 byte
1. In CELL_FACH:
• DL TCTV > TrafVolThresholdDLLow SmartTrafVolThrDL
• DL TCTV > SmartTrafVolThrDL Fast Dormancy Profiling activated WCEL; 8 .. 1024 byte; 256 byte
2. In CELL_DCH without DCH for NRT RB x:
• TCTV of NRT RB x > 0 bytes TrafVolThreshold DLHigh
3. In CELL_DCH: allocated bit rate < max. bit rate for NRT RB x
• TCTV of NRT RB x > TrafVolThresholdDLHigh TrafVolPendingTimeDL
WAC; 0.25..16s; 2 s
• If UE does not receive a DCH or HS-DSCH allocation or bit rate upgrade, UE specific
entity within RNC reports TVM again after TrafVolPendingTimeDL (with MEH in RU30 EP2 default
is 8s, in RU40 RNPS: MEHTVMPendingTime is used)
TCTV: Transport Channel Traffic Volume

Packet Scheduling
• Capacity Request & Traffic Volume Measurements
• Throughput-based optimisation of the packet scheduler algorithm
• Flexible upgrade of the NRT DCH and High throughput measurement
• Dynamic link optimisation for non-real time traffic coverage

Throughput based optimisation
PSOpThroUsage
RNFC; 4 bit for BG / IA THP3 / IA THP2 / IA THP1
• Feature working in parallel with Values: OFF (0); ON (1);
by default feature is OFF for non-GBR services
“classical” inactivity timers
• for Interactive & Background services
• reducing capacity loss
100%
• sometimes bottlenecks in IP networks 
• average throughput changing over time a ve_th rou gh pu t
• low utilization of resources
• 3 different thresholds defined d ow n gra d e_u pper
th re sh old
• Upper, Lower, Release
d ow n gra d e_low er
th re sh old
rele a se_th reshold
sen d dow n gra d e req u est to PS sen d relea se req u est to PS

• Motivation: control of lowly utilised NRT DCH
• frequent transmission of small packets  Inactivity timers do not expire
• typical DCH utilisation < 20 % of allocated bit rate
• DCH resource reservation adapted to meet the actual utilisation (i.e. the used bit rate of the DCH)
• lowly utilised DCH allocations downgraded or released
• Utilisation is measured as average throughput
• feature decreases significantly the capacity loss caused by too high bit rate allocations
• BTS HW, transmission & DL spreading code capacity mainly

Throughput based optimisation (Concept)
L2 MAC
MAC-d
throughput
[kbps]
TTI Transmission Time Interval entity
e.g. 384 kbps DCH is downgraded to 256 kbps

DCHUtilUpper
TimeToTrigger*
Upper downgrade
RNPS; 0..20 s; 0.2 s; 4 s
threshold
e.g. 128 kbps DCH is downgraded to 64 kbps
avg. L2 throughput
Lower downgrade DCHUtilLower
threshold TimeToTrigger*
RNPS; 0..10 s; 0.2 s; 1.4 s
DCHUtilRelTimeToTrigger
Sliding measurement window WAC; 0..10; 0.2; 0.2 s
Release threshold
DCHUtilRelThrUL/DL
WAC; 0..8000; 32; 256 bps
DCH is released – FACH allocated
Parameters introduced to control the downgrade/release of DCH

*structured parameters; can be tuned
individually for each data rate [32..384 kbps]

Throughput based optimisation (TTI)
Different measurement window sizes can be defined for Upper, Lower or Release threshold:
TTI Transmission Time Interval

TTI (64kbps) = 40 ms
TTI (384kbps) = 10 ms
DCHUtilUpperAveWinBitRate
DCHUtilLowerAveWinBitRate
RNPS; Range & Step: 500 ms .. 10000 ms, 500 ms
Default: 2000 ms -common for all bitrates-
Note: Value “0” means that throughput measurements
are not activated.
DCHUtilRelAveWin
WAC; Range & Step: 500 ms .. 10000 ms, 500 ms
Default: 1000 ms
DL measurements: all transmitted bits are measured

UL measurements: all correctly received bits are measured

Example for upper downgrade trigger DCHUtilMeasGuardTime
L2 MAC throughput [kbps] / DCH Bitrate [kbps] RNPS; 0..30 ; 1; 6 sec
Guard Timer:
384 Downgrade requests
Measurement Window are rejected
TimetoTrigger
Upper downgrade 256
threshold
or Downgrade
Lower downgrade Upper Threshold = UpperDowngradeBitrate * ( 1 – DCHUtilBelowDowngradeThr)

threshold 240.64 kbps = 256 kbps * ( 1 – 0.06 )
DCHUtilBelowDowngradeThr
RNPS; 0 .. 20%; 2%; 6 %
Operator sets target bitrates:
DCHUtilUpperDowngrade DCHUtilLowerDowngrade
ThrBitRate; RNPS ThrBitRate; RNPS
16 kbps for 32 kbps NRT 8 kbps for 32 kbps NRT
32 for 64 kbps NRT 8 for 64 kbps NRT
t

Time to Trigger
DCHUtilUpperTimeToTriggerBitrate (one parameter setting per supported Bitrate)
RNPS; Range & Step: 0..20000 ms, 200 ms
Default: 32 kbps: 4000ms, 64 kbps: 4000ms, 128 kbps: 4000 ms, 256 kbps: 4000 ms, 384 kbps: 4 000 ms
DCHUtilLowerTimeToTriggerBitrate (one parameter setting per supported Bitrate)

RNPS; Range & Step: 0..10000 ms, 200 ms
Default: 32 kbps: 1400ms, 64 kbps: 1400ms, 128 kbps: 1400 ms, 256 kbps: 1400 ms, 384 kbps: 1400 ms
DCHUtilRelTimeToTrigger Time to Trigger is used to delay the sending of

WAC; 0..10000 ms, 200 ms; 200ms MAC-d utilization information from L2 -> L3
Guard Timer
DCH Bitrate [kbps] After DCH downgrade a guard timer is started – during that
time it is not allowed to further downgrade the DCH bitrate
384 [..] due to L2 throughput measurements
256 DCHUtilMeasGuardTime
Guard Timer applied RNPS; 0..30 ; 1; 6 sec

Packet Scheduling
• NRT DCH throughput measurements and minimum utilisation
• Flexible upgrade & High throughput measurement
• Dynamic link optimisation for NRT traffic coverage

Traffic volume measurement
Algorithm for upgrading NRT DCH bit rate from any bit rate up to max. RB bit rate
•TVM reporting thresholds are modified when
• FlexUpgrUsage is ‘On’ FlexUpgrUsage
• DCH bit rate lower than the radio bearer maximum bit rate has been allocated 1: ON; 0: OFF
•New reporting threshold is set when 0 < DCH bit rate < RB maximum bit rate
• UL: MEASUREMENT CONTROL message to modify Event 4a reporting
•The bit rate dependent high traffic threshold is selected
• On basis of TrafVolThresholdULHighBitRate or
TrafVolThresholdDLHighBitRate
• Structured parameter: Values for 8, 16, 32, 64, 128, 256 kbit/s TrafVolThreshold UL/DL
HighBitRate
& High Throughput
TrafVolThresholdUL/DLHighBitRate: Measurement > Threshold
RNPS; CR triggered if RLC buffer exceeds: (next Slide)
512 bytes for 8 & 16 kbps  Upgrade
1024 bytes for 32 & 64 kbps
2048 bytes for 128 kbps (& UL 256 kbps )
3072 bytes for 256 kbps NRT (DL only) Remark: both criteria –
to avoid ping-pong effects
when the DL RL power varies a lot
Soc Classification level

High throughput measurement
• High throughput measurement performed by RNC MAC-d entity

• When NRT DCH throughput exceeds High threshold:
• RNC MAC-d entity sends high throughput indication to UE-specific PS
• Window size & time to trigger are common parameters for both UL & DL
directions:
DCHUtilHighAveWin
• Window size: RNC: DCHUtilHighAveWin RNPS; 0.5..10; 0.5; 1 s
• Default value is 1 sec (1000 ms)
• The special value 0 means that high throughput measurement is not active
• Time to trigger: RNC: DCHutilHighTimeToTrigger
DCHUtilHighTimeToTrigger
• Default value is 0.2 sec (200 ms) RNPS; 0..10; 0.2; 0.2 s
DCHUtilHighBelowNRTDataRateThr
• High threshold value = Current NRT DCH bit rate * RNPS; 0..30%; 6%
(1 – DCHutilHighBelowNRTDataRateThr )
• RNC: DCHutilHighBelowNRTDataRateThr is common for UL/DL and all bit rates
• Default 6 % (range 0 - 30 %)

Flexible Upgrade for NRT DCH Bitrates
Traffic Volume [Bytes]

DCH Bitrate [kbps] / L2 MAC throughput [kbps]
Maximum Bit Rate

384
DCHUtilHighAveWin
RNPS; 0.5..10; 0.5; 1 s
256 Note: If value = “0”, no throughput
measurements active
4096
MAC-d
Measurement Window entity 2048
TimetoTrigger
“High Bitrate detected”
128 [..] 1024
512
64
128
32
Capacity Request in RNC MAC layer
DCHUtilHighTimeToTrigger
DCHUtilHighBelowNRTDataRateThr RNPS; 0..10; 0.2; 0.2 s
RNPS; 0..30%; 6%
(128 kbps – 128kbps * 6%) ~ 120 kbps

Packet Scheduling
• NRT DCH throughput measurements and minimum utilisation
• Flexible upgrade & High throughput measurement
• Dynamic link optimisation DyLO for NRT traffic coverage

Dynamic Link optimisation (DyLo) for NRT Traffic Coverage
• Cell coverage area is typically planned for AMR and/or low data rate service
• High DL RB data rates can not be sustained over the coverage area due to RL power
limitation of BTS
• Solution to decrease RB bit rate when near the power limitation  Dynamic Link
Optimisation
• Maximum RL power defined by Admission Control
• DL power allocation
• Dynamic Link Optimisation is activated by DLOptimisationUsage parameter
• DLORLAveragingWindowSize parameter can be used to activate/configure the
sliding window averaging of the dedicated RL transmission power measurement
received from BTS
• In the UL direction, the UE reconfigures the radio link independently of the
network
• No need for a corresponding link optimisation in the UL direction.

Dynamic Link optimization DyLo for NRT Traffic Coverage
Improved NRT traffic coverage
128kbps
384kbps
UE
BTS
distance
Radio link is modified to use lower bit rate
when Tx power of the radio link is getting
close to maximum

Triggering of DyLO DLOptimisationUsage
0: Feature is not activated
1: Feature is activated with SF step 1
2: Feature is activated with SF step 2
Ptxave is averaged radio link power,

measured & reported to RNC by BTS and
averaged in RNC over:
DLORLAveragingWindowSize
PtxRL distance
WBTS; 1 .. 10, 1; def.: 0*; rec.: 4
Ptxmax: defined by Admission Control

Ptxmax
Offset Offset defined by:
DLOptimisationPwrOffset
RNPS; 0..6; 0.1; 2 dB
Triggering of DyLO
Ptxave DyLO triggered if:

Ptxave + DLOptimisationPwrOffset > Ptxmax
time
* 0 = no effect for measurement averaging in RNC; recommended: 4

Packet Scheduler
Introduction
UE Specific PS Procedures
Cell Specific PS Procedures

Packet Scheduling
• Cell Specific PS Procedures
• Queuing of Capacity Requests & SPI definition
• Channel type selection

Processing of Capacity Request CR
Maximum time in queue:
New CR CrQueuingTimeUL ; RNPS; 1…30s,1s,4s
TrafficVolPendingTime DL/UL: CrQueuingTimeDL; RNPS; 1…30s,1s,4s
0.25..16s; 2s
No Add the new CR Queue ordered based on
(A)
to the queue • SPI of the request
(A) CR for same • Arrival time
Yes
NRT RB already
in a queue?
Yes
(B) Is new CR same (B) Delete the new CR
as original?
No • separate queues for UL & DL CR messages

• time limit how long CR can stay in queue
New CR for a change • CrQueuingTimeUL &
in data rate? CrQueuingTimeDL
• limit exceeded  permanently removed
from queue
Modify the content type of • new CR required when allocation
the original CR in a queue needed
CR: Capacity Request

Delete the new CR SPI: Scheduling Priority Indicators

Definition of Scheduling Priority Indicator SPI
• For each combination of RAB QoS parameters operator can define service priority
• Traffic class
• Traffic handling priority
• Allocation and retention priority
• Service priorities and scheduling priority indicators SP defined by QoSPriorityMapping
• Also used for HSPA scheduling
Mapping defined by
SchedulingWeightList Priority Based Scheduling
QoS parameter Service
Queuing
RAB profile priority
Overload Control
If AppAwareRANEnabled = 1 then dynamic
Mapping defined
SPI setting based on the application type
by QoSPriorityMapping and initial SPI
QoSPriorityMapping
Priority for Streaming traffic class with ARP1/2/3 for HS-DSCH/E-DCH or HS-DSCH/DCH QoS
PriForStreamARP1/2/3 (RNPS) (0..15) ( = 1) (13/13/13) parameters are mapped to scheduling weights
Priority for Interactive TC with THP 1 & ARP 1/2/3
PriForIntTHP1ARP1/2/3 (RNPS) (0..11) ( = 1) (11/11/11) SchedulingWeightList
Priority for Interactive TC with THP 2 & ARP 1/2/3 • is BTS commissioning parameter
PriForIntTHP2ARP1/2/3 (RNPS) (0..11) ( = 1) (8/8/8) • defining Mapping QoSPriorityMapping to
Priority for Interactive TC with THP 3 & ARP 1/2/3 SchedulingWeight
PriForIntTHP3ARP1/2/3 (RNPS) (0..11) ( = 1) (5/5/5)
THP: Traffic Handling Priority
Priority for Background TC with ARP 1/2/3 ARP: Allocation & Retention Priority
PriForBackARP1/2/3 (RNPS) (0..11) ( = 1) (0/0/0)
Packet Scheduling
• Queuing of capacity requests & SPI definition

DL & UL Channel Type Selection (with HSDPA & HSUPA)
Data arrives to the DL RLC
buffer in RNC
UE in UE in
Cel_FACH Cel_DCH
MAC-c/sh handles MAC-d sends capacity
Data in RLC buffer of UE
channel type selection request (CR) to PS
UE in UE in
Cel_FACH Cel_DCH
Decides UE basing on network
controlled parameters
Capacity request to RNC by

RRC: MEASUREMENT
REPORT
Involved: UE,
Handover Control,
Cell PS
E-DCH only with

DL HS-DSCH

Channel Type Selection – UE in Cell_FACH state
In case if UE is HS- Channel type selection on Channel type selection on
FACH capable and HS- MAC-sch/MAC-c/MAC-d MAC-c yellow – changes due to
FACH is in use in the RAN1637 (RACH/HS-FACH)
cell turquoise – changes due to
RAN1913 (HS-RACH/HS-
Maximum allowed user data FACH)
Maximum allowed user data YES
amount on HS-FACH exceeded
amount on FACH exceeded
green – existing
implementation of Rel99
common channels
NO
NO (RACH/FACH)
TrafVolThresholdDLLow
UL Transport channel RACH WCEL; 8 .. 1024 byte; 128 byte
with HS-FACH FACH in overload YES
YES SmartTrafVolThrDL
WCEL; 0 .. 1 kbyte; 256 byte
NO YES
NO HSFACHVolThrDL
In case if UE is WCEL; 8 .. 49152 byte; 512 byte
HS-RACH HS-FACH usage with RACH
capable and HS- forbidden by PS FACH usage forbidden by PS YES
RachLoadThresholdCCH
RACH is in use YES
WCEL; 0..100; 1; 75%
in the cell
NO NO PtxThresholdCCH
WCEL; -5..0; 0.1; -1 dB*
Request DCH/ Request DCH/
Initiate data Initiate data DCH, DCH/HS- Initiate data * relative to PtxTarget
DCH, DCH/HS-
transmission on transmission on DSCH or E-DCH/ transmission on
DSCH or E-DCH/
HS-FACH HS-FACH HS-DSCH from PS FACH Threshold &
HS-DSCH from PS
hysteresis parameters
exist
end

DL Traffic Type Selection FACH load measurements
are performed by MAC-c/sh
B) FACH overload
WCEL; 0..100; 1; 75%
Load
FACH in FachLoadMarginCCH
WCEL; 0..10; 1; 5%
overload
time
FACH usage
ok
PtxThresholdCCH
C) FACH forbidden WCEL; -5..0; 0.1; -1 dB*
Powe RachLoadThresholdCCH
r/ WCEL; 0..100; 1; 75%
Load
PtxMarginCCH
FACH in WCEL; 0..2; 0.1; 0.5 dB
overload
RachLoadMarginCCH
time WCEL; 0..10; 1; 5%
FACH
usage ok
* relative to PtxTarget
Packet Scheduling
• Process description
• Enhanced priority based scheduling
SchedulingPeriod Scheduling
WBTS; 100..2000; 100; 100 ms Period
LoadControlPeriodPS Overload Control

WBTS: 100..2000; 100; 1200 ms Period

General definitions
Prx _ total  Prx _ nc  Prx _ sc  Prx _ nrt Prx _ total _ new  Prx _ total  Prx _ total _ change
Ptx _ total  Ptx _ nc  Ptx _ sc  Ptx _ nrt Ptx _ total _ new  Ptx _ total  Ptx _ total _ change
_ Prx/tx_total_change:
Prx _ allowed  MAX ( Prx _ target  P rx _ total  Prx _ nrt _ inactive  Prx _ rt _ inactive ,0) power change estimation
Ptx _ allowed  Ptx _ target  Ptx _ total  Ptx _ nrt _ inactive  Ptx _ rt _ inactive = ΔPrx/tx
• Prx_total / Ptx_total: total received interference power / total transmitted power of a cell
• PrxNc / PtxNC: non-controllable power; RT users power (for Rx-direction: + other-cell users + noise)
• Prx_nrt / Ptx_nrt: NRT / controllable power; ruled by PS
• Prx_sc / Ptx_sc: semi-controllable power; PS Streaming service
• PrxRtInactive: estimated received power of admitted RT bearers, which are not active yet because establishment
phase is still ongoing
• PrxNRTInactive: estimation of the received power that inactive bearers would cause when they are active
• For details about their determination, please refer to NOLS Packet Scheduler ‘power Budget for Packet Scheduling’.

Packet Scheduling

Bit Rate Allocation in DL- Overview
PtxAllowed is the DL
power budget.
Remember ?!
PtxTarget:
WCEL; -10 .. 50; 0.1; 40 dBm
PtxOffset:
WCEL; 0 .. 6; 0.1; 1dB
Increase loading Priority Decrease loading

scheduling

Bit Rate Allocation in UL- Overview
PrxAllowed is the
Remember ?! UL power budget.
PrxLoadMarginDCH
0..30; 0.1; 2 dB  1.585
 LminDCH  37%
the minimum &
PrxTarget maximum available
WCEL; 0 .. 30; 0.1; 4dB UL load in the UL
PrxOffset DCH scheduling.
WCEL; 0 .. 6; 0.1; 1dB
PrxLoadMarginMaxDCH
0..30; 0.1; 0 dB
0 dB  OFF / not used
Increase loading Priority Decrease loading

scheduling

Packet Scheduling
SchedulingPeriod
WBTS; 50..2000; 50; 100 ms

Initial bit rate allocation
• The basic idea of the packet scheduling method is:

(PS 1) When DCH is not allocated for NRT RB and PS receives an UL CR where low
data amount is reported, it allocates initial bit rate in both directions.
(PS 1) When DCH is not allocated for NRT RB and PS receives a DL CR where low data
amount is reported, it allocates initial bit rate in both directions.
PS2 PS3 PS4 PS5

Max. bit rate
Allocated bit rate
InitialBitRateUL/DL
PS1 8..384 kbps; 64 kbps
Initial bit rate
AC
0 bit rate

Maximum bit rate allocation
(PS 1) When DCH is not allocated for NRT RB and PS receives an UL CR where high data
amount is reported, it allocates maximum bit rate in UL and initial bit rate in DL.
(PS 1) When DCH is not allocated for NRT RB and PS receives a DL CR where high data
amount is reported, it allocates maximum bit rate in DL and initial bit rate in UL.
(PS 3) When bit rate lower than the maximum is allocated for NRT RB on a certain direction
and the PS receives a CR for that direction where high amount is reported, it allocates
maximum bit rate for that direction  it upgrades the bit rate.
Max Bit Rate DL / UL PS
[8, 16, 32, 64, 128, 256, 320, 384]
PS1 PS2 PS3 PS4 kbps, 384 kbps
Max. bit rate
Allocated bit rate
Initial bit rate
AC
0 bit rate

Bit rate Upgrade Process
DL process similar.
PtxTotalNew estimated.
Condition for DL simply:

PtxAllowed (PtxTotalNew) > 0
DeltaPrxMaxUp
WCEL; 0 .. 5; 0.2; 1.2 dB
DeltaPtxMaxUp
WCEL; 0 .. 5; 0.2; 0.8 dB
DeltaPrxMaxUp: defines the max. received UL

power increase in a cell, used when bit rates are
allocated or increased by the PS, relative to PrxTotal
DeltaPtxMaxUp; defines the max. transmitted DL
power increase in a cell, used when bit rates are
allocated or increased by the PS, relative to PtxTotal

Bit rate upgrade process, checking
Expression:
PrxAllowed(PrxTotalNew,ΔL) > 0
in the box aside is denoting the condition:
Lallowed_min_DCH (LnewDCH,CELL) ≥ 0
OR
PrxAllowed (PrxTotalNew) > 0 AND
Lallowed_max_DCH (LnewDCH,CELL) ≥ 0
Where:
PrxAllowed (PrxTotalNew) = PrxTarget – PrxTotalNew – PrxNRTinactive – PrxRTinactive
Lallowed_min_DCH = LminDCH – LnewDCH,CELL
Lallowed_max_DCH = LmaxDCH – LnewDCH,CELL
with LnewDCH,CELL = LDCH,CELL + ΔL

Bit rate allocation, example
Target exceeded,
allocation according to
Step 4, check against
DyLO is made
LminDCH OR (PrxTarget AND LmaxDCH)

256 (2)
256 (2)
128 (2)
128 (2) 384 (1)
256 (1) 256 (1)
128 (1) 128 (1)
Step 1 Step 2 Step 3 Step 4 Step 5

Packet Scheduling
Overload Control
Period
LoadControl
PeriodPS
WBTS: 100..2000;
100; 1200 ms

Overload Control LoadControlPeriodPS
WBTS: 100..2000; 100; 1200 ms
Overload Control
Period LoadControlPeriodPS: defines how often PS can perform load control actions
for each bearer.
Note: Value must not be smaller than scheduling period.
• Load too high  PS starts modification or reconfiguration in Advantage

DCH(s) of the Interactive or Background class radio bearers. Enhanced
Overload
• PS supports different overload control methods: Control:
handles not only
UL: Air Interface
- Transport Format Combination Control (TFCC) RRC overload
procedure used but also
overload on
DL: Node B, Iub &
- TFC subset method# RNC
- Enhanced overload control (RB reconfiguration procedure)
#
once the overload situation is over, the system automatically reverts to the original TFC set

UL Load decrease algorithm
Candidate selection
based on SPI
LoadControlPeriodPS
bit rates can not be
WBTS: 100..2000; 100; 1200 ms
decreased <
MinAllowedBitRate
UL/DL
8..384 kbps; 8 kbps
If every lower priority

bearer has been already
downgraded or released.
*LnewDCH,Cell
or PrxTotalNew <
PrxTotalChange <
DeltaPrxMaxDown
DeltaPrxMaxDown
WCEL; 0..5; 0.2; 0.8 dB
defines max. received UL power decrease in a cell, used

when bit rates are decreased by PS, relative to PrxTotal SPI: Scheduling Priority Indicators  Sl. 90

Selection of the radio bearer to be downgraded
Overload Control – Example Selection of the RBs to be downgraded, is done based on:
1. QoS priority value (lowest priority)
2. Connection allocation time (longest allocation
time)
• In case of 3 bearers
3. Bit rate (highest bit rate)
Ptx_Target_BS
256
PrxTarget
256
256
384 Step 1: 384 -> 256 (TFCC)
256
256
Step 2: 384 -> 256 (TFCC)
384 384
256 Allocation according to step 3
Step 1 Step 2 Step 3
• In case of 6 bearers
Ptx_Target_BS 128
128 128 PrxTarget
128 128 128
128 128 128 128 Step 1: 256 -> 128 (TFCC)
256
128 128 128 Step 2: 256 -> 128(TFCC)
128 128 128
128 128 Step 3: 128 -> CCH (RB Reconfiguration)
256 256
128 128 Allocation according to step 4
Step 1 Step 2 Step 3 Step 4
Assumptions for this example (for simplicity):

• all Bearer of same priority
• MinAllowedBitRateUL/DL = 128 kbps

Enhanced overload control in DL
Enhanced overload control: OCdlNrtDCHgranted
• Candidate selection based on SPI MinAllocT
• modifies DCH bit rate & spreading factor NRT DCH allocation time > parameter
• reconfigures L2 by sending the new TFC set to the UE  DCH rate decreased or released
0..60; 1; 60 s = Enhanced Overload Control not
specific MAC-d entity of RNC activated; if activated Rec. 10s
• RRC initiates RB Reconfiguration procedure
• Original bit rate of DCH(s) not automatically returned back
once overload situation is over
• new CR required  Normal scheduling Overload detection
LoadControl
Bit Rate
PeriodPS
DL DCH Allocation Bit rate upgraded DCH modification not allowed WBTS: 100..2000;
for NRT RB  LoadControlPeriod timer 100; 1200 ms
Inactivity time
Minimum
allowed
Bit Rate
Scheduling and Bit rate decreased due to overload. Bit rate decreased and spreading
RRind Period factor increased, RL
TFC subset method is used. RL
reconfiguration is used (or
reconfiguration is not allowed switched to CCH)

Enhanced overload
control - algorithm
Candidate selection
based on SPI
see next slide for better understanding of

OCdlNrtDCHgrantedMinAllocT
impact.
OCdlNrtDCHgrantedMinAllocT
NRT DCH allocation time > parameter
 DCH rate decreased or released
0..60; 1; 60 s = Enhanced Overload
Control not activated;
if activated Rec. 10s

Enhanced Overload Control – Example
Ptx_Target_BS
128
128
PtxTarget
128 128
128 128
128
128 128 Step 1: 256 -> CCH
256 128 Step 2: 256 -> 128
128
Allocation according to step 3
Service of lower SPI 128
than the other ones 256 256
128
Step 1 Step 2 Step 3

Packet Scheduling

Enhanced Priority Based Scheduling PBS
• Enhanced PBS allows the operator to select alternative methods for the PS
• PBS is based on the radio bearer reconfiguration procedures
• Existing NRT allocations can be downgraded or released if there are higher/higher or
equal/any priority users requesting capacity in the congested situation, activated & steered
by PBSpolicy*
• Congestion of the following resources can trigger the enhanced PBS function*
• DL power
Only for allocation of
• UL interference
• DL spreading code Initial Bit Rate*
Marginal load
• BTS HW (WSP) case Reconfiguration of RB1
• Iub AAL2/IP transmission bit rate
NRT RB 2
* Note: NRT RB 1
1) No bit rate upgrades
2) If only candidates with bit rate > initial, allocate initial bit rate. RT traffic
If only candidates with bit rate ≤ initial bit rate, allocate min. bit rate.
3) From RU30 onwards an attempt for the NRT DCH allocation with
min. bit rate is automatically performed before PBS starts
time
Capacity request RB2

Enhanced PBS
• PBS operation performed only for 1 CR per scheduling period, i.e. for the first in queue
• PBS not for bit rate upgrades
Scheduling Period
• PBS function is not performed during CM WBTS; 100..2000;
• Minimum allocation time can be configured via parameters 100; 100 ms
PBS - Priority PBSpolicy options:

• Priority 1 (highest) • 1: PBS not active (default)
• Interactive bearer
• Traffic handling priority is 1 • 2: Higher THP*
• Priority 2 • RAB of the incoming CR must have higher THP than the RAB of
• Interactive bearer the DCH to be downgraded or released
• Traffic handling priority is 2 • 3: Higher or equal THP
• Priority 3 • RAB of the incoming CR must have higher or equal THP than the
• Interactive bearer RAB of the DCH to be downgraded or released
• Traffic handling priority is 3 • 4: Higher or equal THP (not THP 1)
• Priority 4 (lowest)
• same as 3, but DCHs of the RABs that have THP 1 are excluded .
• Background bearer
• 5: Any THP
• Any CR can cause downgrade or release of existing
• 6: Any THP (not THP 1)
* when the feature is active, the recommended value is 2

Enhanced PBS – Timers
• Set of timers are applied to PBS operations in order to:
• guarantee min. total allocation time before downgrade or release due to PBS
• limit time between consecutive PBS operation to prevent frequent
reconfigurations
• The min. total allocation time & time between PBS operations PBSgrantedMinDCH
depend on: allocThigherP
• Priority of the radio bearer to be released or downgraded WCEL; 0..60; 1; 30s
• Priority of the incoming RB

PBSgrantedMinDCH
• The min. total allocation time is controlled by
allocTequalP
• PBSgrantedMinDCHallocThigherP
WCEL; 0..60; 1; 20s
• Priority of the RBs to be released or downgraded is higher than incoming
• PBSgrantedMinDCHallocTequalP
PBSgrantedMinDCH
• Priority of the RBs to be released or downgraded is equal to incoming
allocTlowerP
• PBSgrantedMinDCHallocTlowerP
WCEL; 0..60; 1; 15s
• Priority of the RB to be released or downgraded is lower than incoming
• The min. time between PBS operations is defined respectively as:
• FactorMinPBSInterval * PBSgrantedMinDCHallocTxxxxP FactorMinPBSInterval
RNPS; 0..1; 0.1; 0.2

NSNPacketScheduling v1 R0

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

NSNPacketScheduling v1 R0

Uploaded by

Copyright:

Available Formats

Packet Scheduling

1 © Nokia Siemens Networks RN31645EN40GLA1

2 © Nokia Siemens Networks RN31645EN40GLA1

At the end of the module you will be able to:

3 © Nokia Siemens Networks RN31645EN40GLA1

4 © Nokia Siemens Networks RN31645EN40GLA1

5 © Nokia Siemens Networks RN31645EN40GLA1

UE Specific: Cell Specific:

7 © Nokia Siemens Networks RN31645EN40GLA1

Max. bit rate

Allocated bit rate

9 © Nokia Siemens Networks RN31645EN40GLA1

AC Minimum bit rate

10 © Nokia Siemens Networks RN31645EN40GLA1

11 © Nokia Siemens Networks RN31645EN40GLA1

UTRA RRC Connected Mode

UE in DRX mode UE in DRX mode

Dedicated resources Common resources

12 © Nokia Siemens Networks RN31645EN40GLA1

MM, CC & SM (e.g. PDP Context Activation)

13 © Nokia Siemens Networks RN31645EN40GLA1

RRC: RADIO BEARER RECONFIGURATION

Radio Bearer Reconfiguration Complete

“FACH activation timer” = ExtendedULDLActivationTmr for UEs NOT supporting CELL/URA_PCH

16 © Nokia Siemens Networks RN31645EN40GLA1

DMCU: Data & Macro Diversity Combining Unit

17 © Nokia Siemens Networks RN31645EN40GLA1

CELL_ Cell Update (Paging Response)

Radio Link Setup

18 © Nokia Siemens Networks RN31645EN40GLA1

CUC: Cell Update Confirm

19 © Nokia Siemens Networks RN31645EN40GLA1

20 © Nokia Siemens Networks RN31645EN40GLA1

Defined & discussed later

Measurement Report (Traffic Volume Event; CR)

Radio Link Setup

Radio Bearer Reconfiguration

21 © Nokia Siemens Networks RN31645EN40GLA1

Radio Link Setup

Radio Bearer Reconfiguration

22 © Nokia Siemens Networks RN31645EN40GLA1

23 © Nokia Siemens Networks RN31645EN40GLA1

CPICHRSCPSRBMapRRC + 3 other FACH/RACH load parameters*:

RRC Setup & initial

24 © Nokia Siemens Networks RN31645EN40GLA1

25 © Nokia Siemens Networks RN31645EN40GLA1

• 22-bit mapping coding various establishment reasons

1 Originating streaming call 12 Registration

2 Originating interactive call 13 Detach

3 Originating background call 14 Originating high priority signalling

4 Originating subscribed traffic call 15 Originating low priority signalling

5 Terminating conversational call 16 Call re-establishment

6 Terminating streaming call 17 Terminating high priority signalling

7 Terminating interactive call 18 Terminating low priority signalling

8 Terminating background call 19 Terminating cause unknown

9 Emergency call (always 0) 20 MBMS reception

10 Inter-RAT cell re-selection 21 MBMS ptp RB request

26 © Nokia Siemens Networks RN31645EN40GLA1

1 Originating streaming call 12 Registration

2 Originating interactive call 13 Detach

3 Originating background call 14 Originating high priority signalling

4 Originating subscribed traffic call 15 Originating low priority signalling

5 Terminating conversational call 16 Call re-establishment