Professional Documents
Culture Documents
Describe the criteria for RRC connection state change and their relationship to the
packet scheduler
Identify the transport channels used for NRT traffic
Explain how packet scheduler influences the controllable load
Explain the capacity request procedure
Identify the reasons for TFCS modification
Name and describe the main RAN parameters related to packet scheduler
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
Non-Controllable Load
real time traffic
interference from other cell users
noise
time
4 NOKIA 31/10/2003 RANPAR Version 1.0
Why Packet Scheduling?
It is characteristic for RT traffic that its load cannot be controlled in efficient way. Load caused by RT
traffic, interference from other cell users and noise together is called non-controllable load. The
available capacity, which is not used by non-controllable load, can be used for NRT radio bearers
on best effort basis. To fill the whole load budget and achieve the maximum capacity, the
allocation of NRT traffic needs to be fast.
The Packet scheduler is a general feature, which takes care of scheduling radio resources for NRT radio
bearers for both uplink and downlink directions; Packet scheduling happens periodically (with the
period of tens of milliseconds) and is implemented for both dedicated (DCH) and common control
transport channels (RACH/FACH).
Scheduled capacity depends on the UE capabilities, Node B capabilities, current load of the cell as well
as the availability of the physical radio resources.
Packet scheduler and MAC layer together make the decision of the used channel type for downlink
direction, data transmission on dedicated channel is initiated when MAC layer requests
transmission capacity
For uplink direction the decision of the used channel type is based on UE measurements and
parameters controlled by network. Data transmission on dedicated channels is initiated when a
capacity request is received from UE.
The selection of the channel type is done fast - taking into account the data amount in the buffers
and the current radio conditions
5 NOKIA 31/10/2003 RANPAR Version 1.0
Packet Scheduling principles
Packet Scheduler switches between common channels (FACH/RACH =
low capacity) and dedicated channels (DCH = higher bit rates)
Packet Scheduler allocates to RABs temporarily dedicated channels
with a set of maximum bit rates
For instance within an allocation for 384kbit/s, the instantaneous
bit rate can be {0, 64, 128, 384} kbit/s
Packet Scheduler allocates DCH based on Capacity Requests
A Capacity Request (Nokia term) is triggered based on traffic
volume measurement info: the sender (UE or RNC) has data in
buffer and no sufficient dedicated channel
Packet Scheduler releases DCH upon inactivity
Packet Scheduler re-schedules continuously DCH to serve all requests
equally, and take into account changes in non-controllable load
Desired
Prx/Ptx
Values
PtxRt PrxRt
controllable load
i.e. non RT Traffic
non-controllable load
i.e. RT Traffic
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
UL Tx
UL_DL_activation_timer
CELL_DCH CELL_FACH
Tx/Rx Tx/Rx FACH/RACH
inactivityTimer trafficVolume
Establish RRC
Connection
Idle Mode
10 NOKIA 31/10/2003 RANPAR Version 1.0
RRC Modes and Packet Scheduling
The packet access procedure in WCDMA should keep the interference caused to other users as small as
possible.
Since there is no connection between the base station and the UE before the access procedure, initial
access is not closed loop power controlled and thus the information transmitted during this period
should be kept at minimum.
Since the establishment of a dedicated transport channel itself requires signalling and thus consumes
radio resources, it is reasonable to transmit infrequent and small NRT user data packets using
common transport channels without closed loop power control.
Then the random access channel (RACH) in uplink and the forward access channel (FACH) in
downlink are the transport channels used for packet access
When the packet data is transferred on common channels, the UE is in CELL_FACH state.
Large or frequent user data blocks are transmitted using dedicated transport channels (DCH).
When the packet data is performed on dedicated channels, the UE is in CELL_DCH state.
11 NOKIA 31/10/2003 RANPAR Version 1.0
PS Connection Establishment
In the RRC connection setup procedure the UE is always transferred directly to CELL_DCH state in RAN1
(see previous slide).
The RRC connection setup and a service establishment for NRT RAB(s) is performed as follows:
After the UE has completed a RRC Connection setup procedure with the RNC, dedicated channel
resources are allocated to the UE (a DCH for the signalling link is setup).
The UE performs a NAS connection establishment to the PS CN.
After the service negotiation has been carried out between the UE and PS CN, the PS CN sends a RAB
assignment to the RNC.
The RNCs RRC signalling entity performs a radio bearer setup with a RRC:Radio Bearer Setup
procedure.
The traffic volume measurement parameters (RLC buffer level, reporting criteria, etc.) are sent to the UE
by using a RRC:Measurement Control procedure
Based on this information the UE is able report the need of UL capacity (request the allocation of the
DCH) by sending a RRC:MEASUREMENT REPORT message to the RNC
The RNCs RRC signalling entity starts a supervision timers RB_InactivityTimer and
SignallingLinkInactivityTimer
If the capacity request is received from the UE or from the RNCs within the RB_InactivityTimer, the DCH
for NRT RB(s) is allocated.
If there is no activity in RB(s) within the RB_InactivityTimer and the inactivity of signalling link is
detected (SignallingLinkInactivityTimer has also expired), the state transition from CELL_DCH to
CELL_FACH is initiated
12 NOKIA 31/10/2003 RANPAR Version 1.0
PS Connection Establishment
CELL_
DCH UE RNC SGSN
RRC Connection Establishment (SRB)
The inactivity timers for uplink and downlink are RNC configuration parameters
InactivityTimerUplinkDCH and InactivityTimerDownlinkDCH.
When UE is in CELL_DCH state the UL and DL data streams are monitored by the RNC.
In case the RNC detects inactivity (nothing sent or received), it will indicate this to the RRM and
RRC signalling entities of the RNC.
After receiving the inactivity indication, the RRC signalling entity defines and starts an inactivity timer
(InactivityTimerUplinkDCH or InactivityTimerDownlinkDCH).
(continued)
Radio link and AAL2 resources are then released and UE is changed to CELL_FACH state.
In case the UE is having RT RB which has become inactive and at the same time it is having inactive
NRT RB then RADIO BEARER RELEASE procedure is used (instead of RADIO BEARER
RECONFIGURATION).
InactivityTimerUplinkDCH
InactivityTimerDownlinkDCH
Radio Bearer Reconfiguration Expiry
CELL_
FACH Radio Bearer Reconfiguration Complete
L2 configuration
(continued)
When the UE is transferred to CELL_PCH/URA_PCH state, the RNCs RRC signaling entity shall start a
state supervision timer MSActivitySupervision.
The RRC signaling entity stops the state supervision timer when state transition from
CELL_PCH/URA_PCH state is initiated. The state supervision timer is reset when a periodic Cell
Update is received and a RRC:CELL UPDATE CONFIRM message is sent to the UE.
After expiry of the supervision timer (no periodic Cell Update received from the UE, or any other UL
activity detected) all reserved resources for this UE are released.
In uplink direction the need for the capacity is detected by the MAC of UE.
UE makes the decision whether the common or dedicated channel type is used in uplink.
UE requests dedicated capacity by sending an RRC: MEASUREMENT REPORT message on RACH to the
RRC signaling entity of RNC, which forwards the message to the RRM.
After the procedure, data transmission on DCH can begin and UE is in CELL_DCH state.
In downlink direction the capacity need is detected by the UE MAC entity of RNC. It sends downlink
capacity request directly to RRM.
After uplink and downlink packet scheduling, due to Uplink or Downlink capacity request PS requests
resources from the RM.
PS requests the RRC signaling entity of RNC to start transport channel reconfiguration procedure
The RRC signaling entity sends an RRC: TRANSPORT CHANNEL RECONFIGURATION message to
the UE on FACH, which is acknowledged with an RRC: TRANSPORT CHANNEL
RECONFIGURATION COMPLETE
After the procedure, data transmission on DCH can begin and UE is in CELL_DCH state.
CELL_
FACH UE Node B RNC
Measurement Report (Traffic Volume Event)
UL & DL packet scheduling
DL capacity need is
detected by MAC
Channel type selection
-> DCH
UL & DL
packet scheduling
SignallingLinkInactivityTimer
The timer is used for inactivity detection of the signaling link in CELL_DCH and CELL_FACH
states. The timer is set after inactivity of the signaling link is detected and reset when any
activity detected. In expiry of the timer, a state transition from CELL_DCH to CELL_FACH (or
from CELL_FACH to CELL_PCH) state is initiated when also the corresponding RB inactivity
timer(s) expired.
default value: 2s;
range: 0 ... 20 s; step 0.5 s
InactivityTimerDownlinkDCH
The time indicating how long the radio and transmission resources are reserved after silence
detection on downlink DCH before release procedures
range: 8 kbps: 5 s, 16 kbps: 5 s, 32 kbps: 5 s, 64 kbps: 3 s, 128 kbps: 2 s, 256 kbps: 2 s, 320
kbps: 2 s, 384 kbps: 2 s
Recommendation is to use 20 s for all services
MSActivitySupervision
The RNC supervises traffic of MS with only NRT RABs. When no data transfer is performed
during the defined time period, the RNC asks SGSN to release Iu
default value: 30 min;
range: 0 ... 1440 min; step 1 min
Inactivity detection
of NRT RB Completion of URA Update
Release of RT RB
procedure
Max. number of periodic cell
updates in Cell_FACH /
Cell_ Cell_ Cell_PCH exceeded
DCH FACH
Setup of RT/NRT RB
RAB reconfiguration
DCH Up or Downgrade
Bit rate reduction due to
RRC Connection
load reasons
Release
Idle
Mode UL/DL data
CN originated paging (MT Call) or signalling
Random Access (MO Call) RT RB setup
27 NOKIA 31/10/2003 RANPAR Version 1.0
RRC State Transition
Exercise: Add parameters to all transitions!!!!
URA_ Cell_
PCH PCH
Cell_ Cell_
DCH FACH
Idle
Mode
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
The bit rate allocation algorithm includes load increase and load decrease algorithms, which are
the same in both uplink and downlink directions
NO
Ptx _ allowed = Ptx _ t arg et Ptx _ total Ptx _ nrt _ inactive Ptx _ rt _ inactive
where
PrxRtInative is the estimated received power of admitted RT bearers, which are not active yet
because establishment phase is still ongoing.
PrxNRTInative is the estimation of the the received power that inactive bearers would cause
when they are active.
In the second phase the PrxTotal is compared to the PrxTarget and PtxTotal to PtxTarget
In case PrxTotal < PrxTarget then loading in UL is increased
In case PtxTotal < PtxTarget then loading in DL is increased
In case above two cases are full-filled either bitrate of existing NRT users is increased or new NRT
user will get allocated bitrate.
In case PrxTotal > PrxTarget then next checking is performed PrxTotal < PrxTarget + PrxOffset
In case PtxTotal > PtxTarget then next checking is performed PtxTotal < PtxTarget + PtxOffset
n = PSAveragingWindowSize
Radio Resource Indication
Radio Resource Indication
Averaged PrxTotal:
RRIndPeriod Prx _ total (t ) + Prx _ total (t 1) + ... + Prx _ total (t (n 1))
Prx _ total =
n
Averaged PtxTotal: (analog to averaged PrxTotal)
34 NOKIA 31/10/2003 RANPAR Version 1.0
Packet Scheduling and Load Control
Averaged PrxTotal and PtxTotal values are used by PS.
PSAveragingWindowSize is a BTS specific RNC configuration parameter that defines how many
PrxTotal/PtxTotal measurements, which are received in the NBAP: RADIO RESOURCE INDICATION
messages, are included in the sliding window used in averaging of PS
PrxTotal used in PS estimations is averaged using the following formula:
MinAllowedBitRateDL
This parameter defines the minimum allowed bit rate in downlink that can be allocated by
the PS.
default value: 32 kbps;
range: 8 kbps, 16 kbps, 32 kbps, 64 kbps, 128 kbps, 256 kbps, 384 kbps
RRIndPeriod
The parameter defines the reporting period of the Radio Resource Indication messages,
which are used for cell based load measurements.
default value: 200 ms;
range: 0 ... 2000 ms, step 100 ms.
With the Radio Resource Indication message the BTS reports periodically the total uplink
interference power of the cells and the total transmitted power of the cell and RACH.
37 NOKIA 31/10/2003 RANPAR Version 1.0
Parameters for Packet Scheduling
PSAveragingWindowSize
The parameter defines how many PrxTotal/PtxTotal measurements, which are received in
the NBAP: RADIO RESOURCE INDICATION - messages, are included in the sliding window
averaging
default value: 5;
range: 1 ... 20 , step 1
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
4A: Transport Channel Traffic Volume becomes larger than an absolute threshold
UE in CELL_DCH: TrafVolThresholdULHigh (1024 Bytes)
Transport Channel
Traffic Volume
UE in CELL_FACH: TrafVolThresholdULLow (128 Bytes)
(= UE Ruffer Load)
4A 4A 4A
Measurement
report has
information about Thresholds
current
UE buffer load
time
UE
Measurement Report (Traffic Volume Event) RNC
TrafVolPendingTimeUL (2s)
Measurement Report (Traffic Volume Event)
41 NOKIA 31/10/2003 RANPAR Version 1.0
DL Traffic Volume Based RRC State Transition
In the downlink the process is the same:
When the data amount in the RLC buffer exceeds TrafVolThresholdDLLow, the UE specific entity
within the RNC reports a traffic volume measurement.
When the amount in the RLC buffer exceeds TrafVolThresholdDLHigh the UE specific entity
within the RNC reports a traffic volume measurement.
If the UE does not receive a DCH allocation or bit rate upgrade, UE specific entity within the
RNC reports the traffic volume measurement after a time period defined by
TrafVolPendingTimeDL again.
4A
TrafVolThresholdULLow (Cell parameter)
UL data transmission
on RACH in Traffic volume measurement
CELL_FACH state not triggered
Preconditions Postconditions
Channel
Case Channel allocation Trigger
UE state UE state allocation
UL DL UL DL
Data arrives to UE RLC buffer
1 Cell_FACH - - data_amount < TrafVolThresholdULLow Cell_FACH RACH FACH
(ul capacity request not triggered)
Data arrives to RNC RLC buffer
2 Cell_FACH - - data_amount < TrafVolThresholdDLLow Cell_FACH RACH FACH
(dl capacity request not triggered)
Preconditions Postconditions
Channel
Case Channel allocation Trigger
UE state UE state allocation
UL DL UL DL
Data arrives to UE RLC buffer
DCH DCH
7 Cell_DCH - - data_amount < TrafVolThresholdULHigh Cell_DCH
low low
(ul capacity request triggered)
Data arrives to RNC RLC buffer
DCH DCH
8 Cell_DCH - - data_amount < TrafVolThresholdDLHigh Cell_DCH
low low
(dl capacity request triggered)
Data arrives to UE RLC buffer
DCH DCH
9 Cell_DCH - - data_amount > TrafVolThresholdULHigh Cell_DCH
high low
(ul capacity request triggered)
Data arrives to RNC RLC buffer
DCH DCH
10 Cell_DCH - - data_amount > TrafVolThresholdDLHigh Cell_DCH
low high
(dl capacity request triggered)
Preconditions Postconditions
Channel
Case Channel allocation Trigger
UE state UE state allocation
UL DL UL DL
Data arrives to UE RLC buffer
DCH DCH DCH DCH
11 Cell_DCH data_amount > TrafVolThresholdULHigh Cell_DCH
low low high low
(ul capacity request triggered)
Data arrives to RNC RLC buffer
DCH DCH DCH DCH
12 Cell_DCH data_amount > TrafVolThresholdDLHigh Cell_DCH
low low low high
(dl capacity request triggered)
Data arrives to UE RLC buffer
DCH DCH DCH DCH
13 Cell_DCH data_amount > TrafVolThresholdULHigh Cell_DCH
low high high high
(ul capacity request triggered)
Data arrives to RNC RLC buffer
DCH DCH DCH DCH
14 Cell_DCH data_amount > TrafVolThresholdDLHigh Cell_DCH
high low high high
(dl capacity request triggered)
TrafVolTimeToTriggerUL
This parameter defines, in ms, the period of time between the timing of event detection and
the timing of sending a traffic volume measurement report.
This parameter is sent to the UE using an RRC: MEASUREMENT CONTROL message.
default value: 0 ms;
range: 0 ms, 10 ms, 20 ms, 40 ms, 60 ms, 80 ms, 100 ms, 120 ms, 160 ms, 200 ms, 240 ms,
320 ms, 640 ms, 1280 ms, 2560 ms, 5000 ms
51 NOKIA 31/10/2003 RANPAR Version 1.0
DL Traffic Volume Based RRC State Transition
TrafVolThresholdDLLow
This parameter defines, in bytes, the threshold of data in the RLC buffer of RB that triggers
the downlink traffic volume measurement report (capacity request) on MAC, when UE is in
Cell_FACH state. Otherwise, RNC sends data on FACH
default value: 128 bytes;
range: 0 bytes, 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024
bytes (1 KB)
TrafVolThresholdDLHigh
This parameter defines the threshold of data in the RLC buffer of RB in bytes which triggers
downlink traffic volume measurement report (capacity request) on MAC, when UE is in a
Cell_DCH state and the initial bit rate DCH is allocated for the radio bearer
default value: 1024 bytes;
range: 0 bytes, 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024
bytes (1 KB), 2048 bytes (2 KB), 3072 bytes (3 KB), 4096 bytes (4 KB)
TrafVolPendingTimeDL
This parameter indicates the period of time, in ms, during which it is forbidden to send any
new downlink capacity requests with the same RB id, even if the triggering condition is
fulfilled again.
default value: 2000 ms;
range: 250 ms, 500 ms, 1000 ms, 2000 ms, 4000 ms, 8000 ms, 16000 ms
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
FACH usage is forbidden by PS when RACH load exceeds RachLoadThresholdCCH or when PtxTotal
exceeds PtxThresholdCCH. When one or both of the conditions are fulfilled, PS indicates that FACH
usage is forbidden.
FACH usage is possible again when the RACH load and PtxTotal are decreased below thresholds set by
margins RachLoadMarginCCH and PtxMarginCCH.
FACH in
overload FachLoadMarginCCH/
RachLoadMarginCCH
time
FACH
usage ok
FACH forbidden
PtxThresholdCCH
Power
/ Load
FACH in PtxMarginCCH
overload
time
FACH
57 NOKIA 31/10/2003 RANPAR Version 1.0 usage ok
FACH/RACH Load Related Parameters
FachDataAllowedTotal
This parameter defines the maximum amount of user data in all RLC buffers that can be
transmitted at any given time on FACH (FACH is already selected).
default value: 1024 bytes;
range: 0 bytes, 8 bytes, 16 bytes, 32 bytes, 64 bytes, 128 bytes, 256 bytes, 512 bytes, 1024
bytes (1 KB), 1536 bytes, 2048 bytes (2 KB), 3072 bytes (3 KB), 4096 bytes (4 KB), 6144
bytes (6 KB), 8192 bytes (8 KB), 12288 bytes (12 KB), 16384 bytes (16 KB), 24576 bytes (24
KB), 32768 bytes (32 KB)
RachLoadMarginCCH
The margin for the RACH load for downlink channel type selection
When the measured load is below the set threshold by this margin, FACH usage is
possible.
default value: 5%;
range: 0 ... 100%; step 1%
FachLoadMarginCCH
The margin for the total load of SCCPCH (FACH/PCH) for downlink channel type selection.
When the measured load is below the threshold by at least this margin, FACH usage is
possible.
default value: 5%;
range: 0 ... 100%; step 1%
PtxMarginCCH
The margin for the total downlink transmission power for downlink channel type selection
When the measured load is below the threshold by this margin, FACH usage is possible.
default value: 0.5dB;
range: 0 ... 2 dB; step 0.1 dB
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
When the arrival time of the capacity request is taken into account, the oldest capacity
request, which has been in the queue longest is treated first (First in First out).
Bearer class may be taken into account, so that interactive class bearers always have higher
priority than background class bearers and should be scheduled first.
Traffic handling priority within bearer class may be taken into account to distinguish
bearers within same bearer class. Traffic handling priority is defined for interactive class
bearers only. It has a following range: 1(highest), 2,3,14(lowest), 15 (no priority used).
The policy how the capacity requests should be handled can be set by the operator using
parameters CrHandlingPolicyUL and CrHandlingPolicyDL.
TrafVolPendingTimeUL
This parameter indicates the period of time, in seconds, during which it is forbidden
to send any new traffic volume measurement reports with the same measurement
ID, even if the triggering condition is fulfilled again. Parameter is sent to UE using
an RRC: SYSTEM INFORMATION or an RRC: MEASUREMENT CONTROL message.
default value 4000 ms;
range: 250 ms, 500 ms, 1000 ms, 2000 ms, 4000 ms, 8000 ms, 16000 ms
Note: This value should be set the same in all cells within a BTS
66 NOKIA 31/10/2003 RANPAR Version 1.0
Processing of Capacity Request
CrQueuingTimeDL
This parameter defines how long an downlink capacity request can stay in the
queue before it is permanently removed.
default value:4 sec;
range: 1 ... 30 sec; step 1 sec
Note: This value should be the same as TrafVolPendingTimeDL
TrafVolPendingTimeDL
This parameter indicates the period of time, in milliseconds, during which it is
forbidden to send any new downlink capacity requests with the same RB id, even if
the triggering condition is fulfilled again.
default value: 4000 ms;
range: 250 ms, 500 ms, 1000 ms, 2000 ms, 4000 ms, 8000 ms, 16000 ms
Note: This value should be set the same in all cells within a BTS
CrHandlingPolicyDL
This parameter defines the criteria which are taken into account when the capacity
requests are arranged for DCH scheduling.
default value: 2
range: 1 (arrival time only), 2 (arrival time and bearer class), 3 (arrival time,
bearer class and traffic handling priority)
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
Note : the upgrade will happen in the case of RLC buffer payload =>
TrafVolThresholdDLHigh or TrafVolThresholdULHigh
Example: DL
Bit rate = Start from
Any CRs in queue MinAllowedBitRate CR #1
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
No Yes
End More bearers (A)
No
Supported Peak Bitrate Sheduled TFS for RT RB TFS subset TFCS (SL & RT RB)
Bitrates In Bearer Bitrate intermediate For TFCS
Parameters Bitrates construction
UE in CELL_DCH state
BTS provides
periodical cell load
information to RRM
packet scheduling
PS indicates UE about
the modified capacity
and selected UL TFC
subset
Capacity_modify
[DCH] RRC: TRANSPORT FORMAT COMBINATION CONTROL
In the next step the following checks are done to see whether performed bitrate modifications
are enough to decrease the loading below the PtxTarget + PtxOffset / PrxTarget + PrxOffset
PrxTotalNew > PrxTarget
PtxTotalNew > PtxTarget
&
PrxTotalChange < DeltaPrxMaxDown
PtxTotalChange < DeltaPtxMaxDown
In case the above equations are true then more bearers' bitrates should be decreased (in case no
more bearers available then ModificationPeriod time must be expired before new modification
can be done for the bearers in question).
In case of 3 bearers
256 PrxTarget
256
256
384
256 Step 1: 384 -> 256 (TFCC)
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
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 (Radio Bearer Reconfiguration)
256 256
128 128 Allocation according to step 4
Step 1 Step 2 Step 3 Step 4
Bitrate Upgrade
Overload Control
Dynamic Link Optimisation (DyLo)
128kbps
384kbps
UE
BTS
distance
Radio link is modified to use lower
bit rate when WBTS Tx power is
getting close to maximum
86 NOKIA 31/10/2003 RANPAR Version 1.0
Triggering of Dynamic Link Optimisation
time
No
DyLO is possible for NRT DCH allocations that have
lasted at least 2 seconds (fixed guard time)
Yes Guard timer active
Not applicable in RAN1.5 (only 1 NRT DCH possible
No per UE)
Select DCH(s) to be
downgraded
SF is doubled (physical channel bit rate reduced
to half of the original)
Requirements OK Additional puncturing is not allowed
(min allowed bitrate, No DyLO cannot reduce bit rate below the Initial and
minimum allowed bit rate in downlink
SF, puncturing)
Transmission resources
The reconfiguration of Iub AAL2 transmission resources is not
performed due to DyLO
Compressed mode
DyLO is not allowed during the compressed mode measurements
SF32(64k) SF8(384k)
Call can go back to SF8 when
- Downgrade to SF32 takes place due to DyLO
-Inactive timer expires and moves to Cell-FACH
PtxTotalMax 43dBm
Ptx,max
Calculated max RL pwr
Calculated max RL pwr - DLOptimisationPwrOffset
Ptx, threshold
DL pwr (dBm)
Default hidden
value is 2dB
PtxPrimaryCPICH 33dBm
Ptx ,ref
PtxPrimaryCPICH CPICHtoRefRABoffset = 31 dBm
PtxTotalMax 43dBm
Ptx,max
Calculated max RL pwr
PtxDLabsMax 38 dBm
DL pwr (dBm)
1. Which channel types the PS selects based on traffic load and parameters?
5. If RT RABs require temporarily the target transmission power of the node B, what will happen
to the NRT RABs on the same node B at that time?