Direct HS-DSCH to DCH switch

In direct HS-DSCH to DCH switch radio bearer that is mapped to HS-DSCH is

reconfigured to DCH so that use of DCH 0/0 is tried to be avoided.
The following situations may cause HS-DSCH reconfiguration:

Serving cell cannot be found (quality reasons, needed feature not supported).

CS voice RAB establishment (HSPA channels cannot be selected for new CS

RAB)

channel type selection, admission control

Full HSPA configuration cannot be kept anymore, for example:

not succesfull HSUPA TTI switch from 2 ms to 10 ms
for quality reasons (F-DPCH)
initiation of compressed mode
When a cell not supporting CS voice on HSPA or F-DPCH is added to
active set.
A new RAB combination is not supported with full HSPA configuration
(but supported with DCH).

A UE with PS RABs mapped to HS-DSCH moves to another cell although

HSDPA mobility is disabled.
For NRT services, the HS-DSCH may be switched to DCH or FACH. The switch to
FACH is however not supported for streaming services.

Other than SRBs and CS voice RB are not directly affected about DCH switch, if only
SRBs and RB for CS voice are switched to DCH, PS services still use HSPA, and if no
reconfiguration needs to be performed for the PS services.
Phases of the channel type switch
The successful HS-DSCH to DCH switch contains the following phases:
1. The RNC and AAL2 resources are reserved for DCH.
2. Radio links, transport channel and radio bearer are reconfigured
3. Radio bearer is mapped to DCH
4. The RNC and AAL2 resources for HS-DSCH are released
5. DCH-specific measurements are configured to the UE
DCH reservations are executed in the following order in HSPA to DCH switch for RBs
(and SRBs):
1. RB with the highest QoS priority passing admission control and all possible other PS
RBs passing the admission control
o
resources other than power resources for SRBs and CS RBs are checked (if
switch is executed also for SRBs)
o
PS RBs with a negative admission decision are dropped (DCH 0/0) in this step
in the order of QoS priority
o
The next step is taken stright away (without a.n attepmt for resource

reservation) if the conditions for this step are not fulfilled

2. RT-over-RT , RT-over-NRT or pre-emption only for the RB with the highest priority
(+ SRBs)
3. SRBs/RBs are dropped
o
in case of CS RB problem, its RAB is released
o
in case of SRB problem, RRC re-establishment may happen
Other than SRBs and CS voice RB are not directly affected by DCH switch, if only SRBs
and RB for CS voice are switched to DCH and PS services still use HSPA.
RT-over-RT , RT-over-NRT and pre-emption is executed in accordance with DCH rules
described in Code tree optimisation section in WCDMA RAN RRM admission control.
AMR codec set configuration of the HSPA is preserved when the channel type is
switched from HSPA to DCH. Load-based AMR codec mode selection is not applied at
the channel type switch. For more information, see WCDMA RAN RRM admission
control.
Bit rate allocation after the channel type switch
In the general, the following applies: for NRT services, on the one hand, DCH is tried to
be reserved in the next scheduling period with the initial bit rates defined by
the InitialBitRateUL and InitialBitRateDL RNP parameters. If the initial bit rates cannot
be allocated, then zero bit rates are used instead (DCH 0/0).
Some special cases/exceptions exist, however:

If the active set contains more than one branch, the lowest initial bit rate of all
branches is used.

Whenever no AMR multi-RAB configuration is used, ongoing HS-PDSCH code

downgrades are completed before resources are tried to be reserved for DCH. If an
AMR RAB exists in parallel, however, DCH resources are tried to be reserved
immediately.

If the selected initial bit rate of the DCH is larger than the RAB's maximum bit
rate, however, the DCH will be tried to be reserved with the supported bit rate that is
smaller than or equal to the RAB's maximum bit rate.
For streaming services, on the other hand, the packet scheduler tries to allocate UL and
DL DCH bit rates which are equal to GBR or the next higher supported DCH bit rate.
Allocation is done for both UL and DL and is performed immediately. In the event of
unsuccessful allocation, however, the RB is mapped to DCH 0/0. If a particular UE has
allocated one or more PS streaming RB(s) and at least one NRT RAB, all PS RBs are
switched simultaneously. The bit rates are however allocated in the next scheduling
period.
Some special cases exist:

If the DCH's initial bit rate is larger than the RAB's maximum bit rate, the DCH is
tried to be reserved with a bit rate corresponding to the RAB's maximum bit rate.

If more than one NRT RB had been mapped to a HS-DSCH with active PS
streaming RB, DCH with bit rates equal to 8/8 kbit/s is tried to be reserved for the
active NRT RB with highest priority (HSPAQoSMapping). If 8/8 kbit/s is not possible,
DCH 0/0 is used. All other NRT RBs are put to DCH 0/0 by default.
If many active RBs have identical priority values, the RB with the longest allocation
time is selected.

If the sum of non-controllable and semi-controllable downlink transmission power

has crossed the respective threshold, PtxTarget, streaming RBs will be mapped to
DCH 0/0, as well.
Unsuccessful combined serving cell change and channel type switch
In case of combined HSPA to DCH switch (full HSPA to HSPA) and serving cell change,
only the best serving cell candidate is attempted. If the change does not succeed, all but
the highest priority service can be mapped to DCH 0/0 and the switch is reattempted as
full HSPA to full DCH switch. After that actions defined for normal switch cases are
taken depending on RAB combination.