Professional Documents
Culture Documents
WCDMA RAN
E
Copyright
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design, and manufacturing.
Ericsson shall have no liability for any error or damages of any kind resulting
from the use of this document.
Contents
1 Introduction 1
1.1 Scope 1
1.2 Target Groups 1
1.3 Revision Information 1
2 Overview 2
3 Capabilities 3
4 Function Description 3
4.1 Triggering Channel Switching 4
4.2 UE States in Connected Mode 4
4.2.1 CELL_DCH 4
4.2.2 CELL_FACH 4
4.3 Single RAB State Transitions 5
4.3.1 CELL_DCH to CELL_FACH 6
4.3.2 CELL_FACH to CELL_DCH 64/64kbps 7
4.3.3 CELL_FACH to Idle Mode 7
4.3.4 Dedicated to Dedicated Single RAB 7
4.4 Multi-RAB State 8
4.5 Channel Switching Algorithms 8
4.5.1 Common to Dedicated Evaluation 9
4.5.2 Dedicated to Common Evaluation 10
4.5.3 Common to Idle Evaluation 11
4.5.4 Coverage Triggered Downswitch Evaluation 11
4.5.5 Dedicated to Dedicated Upswitch Evaluation 12
4.5.6 Multi-RAB Downswitch Evaluation 13
5 Engineering Guidelines 14
5.1 Common to Dedicated Evaluation 14
5.2 Dedicated to Common Evaluation 14
5.3 Dedicated to Dedicated switching 15
6 Parameters 16
6.1 Descriptions 16
6.2 Values and Ranges 17
7 Glossary 18
Reference List 19
1 Introduction
Interactive RAB traffic causes large variations in the offered traffic over time
for a particular user. The packet switched Interactive RAB traffic transferred
through the WCDMA RAN is mainly generated by web browsing, E-mail, and
file transfer. Web browsing, in particular, causes large variations in the traffic
stream. After a web page has been downloaded and the user is reading the
page, there is very little data to transfer. This changes once the user requests
a new web page. Consequently, it is not efficient to reserve resources for
a dedicated channel continuously. The purpose of Channel Switching is to
optimize the use of the radio resources by dynamically changing the physical
resources allocated to the interactive RAB users.
1.1 Scope
This document provides a high-level description of Channel Switching.
Capabilities of the feature are explained. The document contains explanations
of algorithms and the logic of Channel Switching. The document also contains
parameter information related to the feature.
2 Overview
Channel Switching is applied only to interactive RAB packet data traffic. This
traffic has little or no quality of service attributes that apply. It belongs to
the Interactive and Background Quality of Service classes, which have no
guaranteed bit rates and no packet delay requirements. When there are
sufficient resources available, the interactive RAB user receives high bit rates
but when the system is heavily loaded and there are not many resources
available, the bit rates offered may be lower. An interactive RAB user may not
be given any bandwidth at all, since there are no guarantees.
3 Capabilities
4 Function Description
The Channel Switching function consists of two main parts: evaluation and
execution.
Soft Handover can initiate channel switching when it fails to add a radio link,
i.e if admission is denied when adding an radio link and there is transmission
ongoing on either 64/128kbps or 64/384kbps rate, a downswitch is triggered
(from 64/384 to 64/64 or from 64/128 to 64/64 kbps) by Soft Handover
functionality.
4.2.1 CELL_DCH
The Dedicated state is characterized by the allocation of Dedicated Transport
Channels (DCH) to the UE. Dedicated Control Channels (DCCH) are used for
control signaling and Dedicated Traffic Channels (DTCH) are used for user
data transmission. The logical channels, DCCH and DTCH, are mapped onto
the DCHs and further multiplexed onto Dedicated Physical Channels. These
physical channels use closed-loop power control, which makes them well suited
for high bit rate traffic. In release P2.1, 64/64kbps (UL/DL), 64/128 kbps, and
64/384 kbps channels are available for user data. For Multi-RABs, 64/64 kbps
data rate is supported for interactive RAB traffic.
4.2.2 CELL_FACH
In the Common state, the UE is able to transmit control signals and data
packets on the common transport channel Random Access Channel (RACH)
in the uplink direction and in the FACH for downlink direction. A DCCH or a
Common Control Channel (CCCH) is used for control signaling. A DTCH is
used for user data transmission. The logical channels, DCCH, CCCH, and
DTCH are mapped onto the RACH and the FACH. These channels are suitable
for carrying common control information and are shared by all users in the cell.
A maximum of 32 kbit/s is available for user data transmission. Thereafter, the
transport channel, RACH, is mapped onto the Physical RACH and the FACH
onto the Secondary Common Control Physical Channel (S-CCPCH), which
use open-loop power control.
When the UE is only handling a single RAB, the possible state transitions
triggered by Channel Switching Algorithms are shown in the Figure 1 on page 6.
Connected Mode
Dedicated State
Cell_DCH 64/384 kbps
Idle
Idle Mode
Mode
U 00 00243A
The Dedicated Channel (DCH) is well suited for high bit rate traffic, since it is
reserved for one user and provides closed-loop power control. High user bit
rates create a lot of interference and power control is essential to keep the
interference on an acceptable level.
When the traffic volume increases, the user is switched from a common to a
dedicated transport channel if there are resources available. The dedicated
transport channel provides the user with higher data rates. In addition, it is
important to keep the common transport channels free from everything but
control information and small portions of user data. Switching to a dedicated
transport channel is done when the amount of user data to transfer is large.
The use of a common transport channel would negatively affect the throughput
of other users.
necessary, this means that the actual measurements are processed before
reporting, and time driven measurements.
The Channel Switching Algorithms use buffer load, throughput, and transmitted
code power as input to the algorithms.
1 Buffer load: The buffer load is defined as the minimum of the Radio Link
Control (RLC) transmission window and the sum of bytes in the SDU
buffers and retransmission buffers of some of the RLC instances (each
interactive RAB connection consists of five RLC instances).
Not all Channel Switching algorithms are active in every state. An algorithm
corresponding to a certain state is started once the state is entered successfully
and stopped when a new state has been entered successfully.
The evaluation algorithm is activated at the entry of the common state, and it
uses RLC buffer loads in both the uplink and the downlink as input.
When the RLC buffer load in the uplink exceeds the threshold value set by the
parameter ulRlcBufUpswitch, a measurement report is sent. An upswitch
request is issued upon reception of the measurement report. A request is
also issued when the RLC buffer load in the downlink exceeds the threshold
value set by the parameter dlRlcBufUpswitch. Channel Switching execution
thereafter performs the upswitch when permission is given from Admission
Control. Only one radio link is set up, since it is the responsibility of Soft and
Softer Handover to add radio links after switching is complete.
Channel Switching execution does not report back to the evaluation algorithm
if the upswitch fails. When a measurement report is sent to the Common
to Dedicated Evaluation, a timer is started in the measurement filter. While
this timer is active, no measurement reports may be sent for this particular
interactive RAB. When the timer expires and any of the switching criteria are
still met, a measurement report is sent again; this must be repeated as long
as the switching criteria are met, so that upon failure of a channel switch new
requests are made.
The evaluation is activated once the dedicated state is entered and it uses
throughput measurements, performed in the SRNC, in both the uplink and
downlink for both control and user data as input.
When the throughput on both the uplink and downlink is below the
threshold value set by the parameter downswitchThreshold, the timer
downswitchTimer starts. If the throughput increases above a second
threshold set by the parameter downswitchTimerThreshold before the
timer expires, the timer is stopped and no switch is issued, this is done for
stability reasons, which prevents switches back and forth at momentary dips in
throughput, as shown in the Figure 2 on page 10.
UL/DL throughput
(kbps)
downswitch
TimerThreshold
downswitch
Threshold
Time
1 2 3 4 (ms)
U 00 00244
Figure 2
For information about the performance of the algorithm, which is useful for
supervising a live system on a long term basis, see Reference [7].
The Common to Idle Evaluation algorithm monitors whether a switch from the
common transport channels FACH/RACH to Idle mode is required, due to a lack
of transmission of user data during a certain time interval.
The Common to Idle Evaluation releases UEs with no activity in order to free
resources and decrease the power consumption of the UE, since the UE does
not have to monitor the FACH for long periods of time.
The algorithm is activated at the entry of the CELL_FACH state. Uplink and
downlink throughputs are monitored and the algorithm requests a switch to Idle
mode if uplink and downlink throughput is zero during 2 minutes. The request is
issued to the Signaling Connection Handling function, which handles the further
processing of the transition to Idle mode. Signaling Connection Handling issues
an Iu release request to the Core Network, which in turn decides whether the
connection should be released.
For information about the performance of the algorithm, which is useful for
supervising a live system on a long term basis, see Reference [7].
The algorithm monitors the downlink transmitted code power of all legs in
the active set and the code power is then filtered by each RBS in the active
set. A downswitch request is issued when all handover legs use a power
above the power alarm threshold, shown in Figure 3 on page 12. The power
alarm threshold is defined by the parameter downswitchPwrMargin. If the
transmitted downlink code power falls below the power alarm threshold with
a margin given by the parameter reportHysteres is during one second
after the request is issued, the request will be cancelled and no downswitch is
executed. The reason for this hyteresis is to prevent the algorithm to cancel the
downswitch due to small, momentary dips in transmitted downlink code power.
This evaluation algorithm is started at the entry of the CELL_DCH 64/384 state
and CELL_DCH 64/128 state.
dlMaxPwr
downswitchPowerMargin
Power alarm
threshold
reportHystersis
coverageTimer (1 s)
• The transmitted code power consumption on the current rate is below the
power upswitch threshold shown in Figure 4 on page 13.
The power upswitch threshold is defined from the power alarm threshold
(described in Section 4.5.4 Coverage Triggered Downswitch Evaluation on page
11) through the parameter upswitchPwrMargin and the estimated power
increase, as shown in Figure 4 on page 13. The estimated power increase is
based on the relative rate difference between the current and next higher rate.
For an upswitch from 64 to 128 kbps, the estimated power increase is 2.9 dB
and for the 128 to 384 kbps upswitch, the estimated power increase is 4.7 dB.
For information about the performance of the algorithm, which is useful for
supervising a live system on a long term basis, see Reference [7].
P code
dlMaxPwr
Power alarm threshold
upswitchPowerMargin
Power up-switch
threshold
reportHystersis
upswitchTimer (1 s)
Transmitted downlink code power
t
When the timer expires, the algorithm sends a request for releasing the
interactive RAB PS64/64 and the downswitchTimerMrab timer is restarted
and monitored again whether the throughput increases above zero. This is
necessary for stability.
For information about the performance of the algorithm, which is useful for
supervising a live system on a long term basis, see Reference [7].
5 Engineering Guidelines
When setting this parameter it is important to consider how much of the TCP
signalling that should be done on common and how much signalling that should
be done on DCH. For example, when a UE is used for web browsing, uplink
traffic is started by a short DNS message. If ulRlcBufUpswitch is set to a
value smaller than the size of the DNS look-up message, an upswitch to DCH
will be issued by the very first signalling from the UE which decreases the
response time. On the other hand, a low setting of this parameter could make
signalling from other applications trigger an upswitch when the UE is used as
a modem to a laptop.
The downswitchTimer defines the time a user will stay on DCH with low
throughput before being switched down to FACH. If this timer is set long, the
probability that a user is switched down to FACH during short periods of
inactivity decreases. This improves the user throughput, but also increases
resource utilization and thereby decreases system capacity. It is therefore not
recommended that this timer is used for generally improving user throughput.
There are however traffic cases that can be improved by a slightly increased
timer setting. For example, FTP transmissions can be split into several TCP
transmissions. If the UE (or the laptop when the mobileis used as modem) uses
this for FTP transmissions the user perception of the FTP transmission can be
improved by a small increase of this timer. It should however be remembered
that this then is done on the cost of system capacity.
The actual coverage of each rate is given by the dlMaxPower (see, Reference
[2]) for each rate. This means that by adjusting the dlMaxPower for a certain
rate, the coverage for that rate can be increased or decreased.
When adjusting the dlMaxPower for the different rates some restrictions apply.
For the coverage testing before upswitch, the dlMaxPwr shown inFigure 4 on
page 13 is the dlMaxPower of the current rate. This means that when coverage
is tested before an upswitch, this is done towards the maximum allowed
downlink code power of the current rate. Consequently, the dlMaxPower of a
higher rate cannot be set lower than the max power of the lower rate. If this is
done, the coverage tester functionality could fail and it could happen that the
link quality cannot be maintained after an upswitch have been granted.
decreased. From user throughput point of view it is therefore proposed that the
blerQualityTarget is kept to a low vale (e.g. 1%).
6 Parameters
These parameters can be set by the operator in the RNC. For more information,
range and default values, see Reference [9] and Reference [10].
6.1 Descriptions
dlRlcBufUpswitch Downlink threshold for channel switching from common
to dedicated substate for single RAB. If this parameter
is set to 0, upswitch from CELL_FACH toCELL_DCH
will never occur due to RLC buffer load.
7 Glossary
All acronyms and terms used in this document are listed in the Reference [4].
Reference List