Anda di halaman 1dari 12

Limited Number of Resources

users congestion of the

logical channels
carried on FACH are
Raise the ceiling Decrease congested (CCCH,
simultaneous DCCH & DTCH)
number of FACH
Step#1: Increases users
number of users from Enable FACH flow
30 to 60 users on control for the
FACH 4B decrease FACH FC: needed logical
P2D & channel type.
Step# 2:
number of FACH
What is the cons of having limitation in number of FACH
1. If D2F failed (due to max number of FACH users are reached) then
UEs in the CELL_DCH state, having little or no data to transmit, may
continuously occupy the dedicated channels and cell resource
utilization may decrease as a result
2. If P2F failed then CELL_PCH UEs fail to perform data transmission or
respond to paging messages and finally enter the idle state, leading
to PS service drops plus paging failure.
3. If the number of UEs in the CELL_FACH state reaches the upper limit,
cell updates may fail, including those triggered by radio link setup
failures. As a result, call drops may occur.

Step#1: Increase number of FACH users from 30 to 60 (but take care
of FACH resource congestion) FACH_60_USER_SWITCH-1
Step#2: FACH FC P2D and D2Idle:

D2Idle transition SET UCORRMALGOSWITCH command.

P2D transition SET URRCTRLSWITCH command. During a P2D
transition, the RNC delivers the UE a cell update confirm message on
the CCCH, which prevents call drops because the delivery does not
use up resources designated for UEs in the CELL_FACH state.
Step#2: FACH FC P2D and D2Idle.
Step#3: If the number of UEs in the CELL_FACH state reaches the
upper limit, cell updates may fail, including those triggered by
radio link setup failures. As a result, call drops may occur. To
prevent this, you can reserve some UEs in the CELL_FACH state for
cell updates. To set the number of reserved users, run the SET
UCORRMALGOSWITCH command and modify
the ReservedU32Para1 parameter.
If the maximum number of UEs in the CELL_FACH state is 30 and
the number of reserved UEs in the CELL_FACH state is 5, the D2F
transition shown in Figure 4-2 will not be implemented when the
number of UEs in the CELL_FACH state reaches 25. Instead, the
D2Idle transition may be triggered. The resources for reserved
UEs are for the users who send cell update messages.
Step#4: Unrestricted number of FACH users not recommended
as the FACH resource congestion may increase dramatically.
Note: from counters we cant decide that there is congestion due to
number of FACH users are congested, but we can decide the
number of simultaneous FACh users per cell from VS.CellFACHUEs
(it is better to use this counter from LMT monitor to get it per 1sec)
New congestion H
NG.TIME only
enabled on 7-11-
What is the benefit of relieving the DTCH
1. Better user experience.
2. Less PS Call Drop
Optimized DTCH P2D D2Idl FACH efficiency
congestion e boost

DTCH Congestion depend on

The RNC considers the DTCH
congested if the following
conditions are met:
FACHAdmCondSDUDelaySwitch i
s set to ON.
There are 10 or more PDUs
whose SDU delay is greater
than FACHAdmSDUDelayThd in the
DTCH buffer.
The DTCH queue is congested.
Data TVM-based F2P Transition by Mean
Transmission P2D Transition of Physical Channel
Suspension Reconfiguration

the RNC suspends RLC data This function enables F2P transitions by means
transmission when triggering an UEs in the CELL_PCH of physical channel
F2D state transition. The RNC state to enter the reconfiguration reduce
keeps RLC data transmission CELL_DCH state when FACH bandwidth
suspended until the F2D state the amount of data to consumption, because
transition is complete or the UE be transmitted exceeds physical channel
returns to the CELL_FACH state. the 4A threshold. This reconfiguration messages
This ensures that user-plane data eliminates the need for generate 50% less air
is transmitted over the DCH P2F transitions prior to interface traffic than RB
whenever possible. F2D transitions and reconfiguration
SET thereby improves the messages.
H3 RNC_F2D_RLC_SUSPEND_SWI utilization efficiency.
When the DTCH is congested, RNC triggers P2D
transition. The trigger conditions and how
DTCH flow control is implemented are as follows:
When a UE with PS services in the CELL_PCH state
initiates a cell update, a P2D transition is triggered if
the following conditions are met:
1. The PROCESSSWITCH2 parameter is set
2. The UE is of Release 5 or a later version.
3. The DTCH is congested but the CCCH and DCCH
are not.
4. In the cell update message triggered by PS data
transmission, the value of IE "Cell update cause"
is "uplink data transmission" or "paging
response", and the IE "Establishment cause" is not
The following describes how a D2Idle procedure is
triggered for UEs processing PS services when the
DTCH is congested:
selected under PerfEnhanceSwitch, the RNC initiates a
D2F transition request. If the DTCH is congested, the
RNC evaluates the measurement quantities
(indicating the traffic volume or throughput)
contained in the uplink and downlink 4B
measurement reports. If the measurement quantities
are all 0, a D2Idle transition starts. If the
measurement quantities are not all 0, the UE remains
in the CELL_DCH state.
DTCH flow control stops once the DTCH is no longer
FACH Efficiency
P2D (for DTCH boost Data D2Idle

21 3
11/1 13/1
13/1 15/1
15/1 18/1
/ /
1 11 11 1 1

FACH 60 FACH Efficiency

Decrease 4B
users boost TVM
based P2D