Classification : Interne

CTS
Between EDCH/HSDSCH, FACH and DCH
 DCH  E-DCH
Classification : Interne
Classification : Interne

1 - Channel type switch from E-DCH to DCH

The channel type switch from E-DCH to DCH is necessary if E-DCH usage cannot be continued or if E-DCH
usage causes non-optimal use of radio resources. The following triggers can cause an E-DCH to
DCH channel type switch:
•HS-DSCH → DCH channel type switch
•HS-DSCH serving cell change
•PS streaming establishment
•NRT radio bearer establishment when a streaming radio bearer exists
•CS voice RAB establishment.
•E-DCH active set changes to unacceptable
•Soft handover branch addition fails
•BTS initiated E-DCH → DCH channel type switch
•Unsuccessful HSUPA TTI change from 2 ms to 10 ms
HS-DSCH → DCH channel type switch
If a channel type switch is triggered from HS-DSCH to DCH, a channel type switch E-DCH to DCH is also triggered. The reason for this is that E-DCH usage requires simultaneous HS-DSCH usage. For more
information on the reasons for HS-DSCH to DCH channel typeswitch, see HSDPA channel type selection.
When a channel type switch is completed, the RNC sets the EDCHCTSwitchGuardTimer timer.

HS-DSCH serving cell change

The E-DCH serving cell is always the same as the HS-DSCH serving cell. The E-DCH serving cell must always be E-DCH capable, and the E-DCH must be allocated for that cell.
When a HS-DSCH serving cell change is triggered, a check is performed whether the new HS-DSCH serving cell supports E-DCH. If the new HS-DSCH serving cell does not support E-DCH,
the channel type switch from E-DCH to DCH is necessary. If a new HS-DSCH serving cell supports E-DCH but the E-DCH active set changes to unacceptable, the channel type switch from E-DCH to DCH is
necessary.
When a channel type switch is completed, the RNC sets the EDCHCTSwitchGuardTimer timer.

Softer handover branch addition fails

Occasionally, a branch addition fails to DCH and E-DCH active sets. If an E-DCH active set update is not possible, the cell is added to the DCH active set if possible. However, if there is already another cell in
the E-DCH active set under the same LCG of the BTS, the cell cannot be added to the DCH active set. The reason is that the E-DCH active set and the DCH active set have to be identical in a softer handover
(under one LCG of the BTS). The E-DCH usage cannot be continued, and the channel type is switched to the DCH.
Classification : Interne

BTS initiated E-DCH → DCH channel type switch

Occasionally, the allocated HW resources for E-DCH in the BTS become fragmented. This can prevent the efficient usage of HW resources, and block some DCH allocations. To avoid this, the BTS may need
to cause some E-DCH resource to be released. The BTS that sends a Radio Link Failure message with the cause code ‘UL Radio Resources Not Available’ to the RNC. After receiving this, the RNC changes
the channel type from E-DCH to DCH. When channel the type switch is completed, the RNC does not set the EDCHCTSwitchGuardTimertimer, but it starts the DCH to the E-
DCH channel type switch immediately.
Channel type switching if UE leaves the HSDPA/HSPA cell
Channel type switching takes place if HSDPA/HSPA cannot be maintained any longer in the current cell, and a new serving cell cannot be found. The same criteria are used for single NRT RABs and multi NRT
RABs on HSPA. Multiplexing is performed as follows:

HS-DSCH/UL:DCH -> DCH/DCH: MAC-hs multiplexing of the DL logical channels is reconfigured to L1 multiplexing.

HSDSCH/E-DCH -> DCH/DCH: UL MAC-e and DL MAC-hs multiplexing is reconfigured to bidirectional L1 multiplexing.

HSDSCH/E-DCH -> HS-DSCH/UL:DCH: MAC-e multiplexing of UL logical channels is reconfigured to L1 multiplexing

HSPA to DCH switch triggered in case of CS voice RAB

If the UE has full HSPA configuration, a switch to another configuration is triggered in the following cases:
•CS voice RAB establishment (HSPA channels cannot be selected for new CS RAB)
•channel type selection, admission control
•full HSPA (including CS voice over HSPA) configuration cannot be kept anymore, for example, due to the following reasons:
•not successful HSUPA TTI switch from 2 ms to 10 ms
•quality reasons
•start of compressed mode
•a cell that does not support CS voice on HSPA is added to the active set
•a cell that is under the DRNC is added to the active set
•RAB combination not supported with full HSPA configuration (but supported with DCH)
The best possible configuration is selected from these alternatives.

Unsuccessful HSUPA TTI change from 2 ms to 10 ms

Unsuccessful HSUPA TTI change from 2 ms to 10 ms causes special actions. If a HSUPA TTI change from 2 ms to 10 ms is not successful, then a switch to full DCH configuration is triggered so that all RBs,
except RB with the best QoS priority, are mapped to DCH 0/0 right away. After that the switch is performed according to normal switch rules.
Classification : Interne

Parameter: E-DCH channel type switch guard timer

Description: This parameter determines the time that must be waited after an E-DCH to DCH channel type
switching before a DCH to E-DCH channel type switching can be done.

Managed Object: RNHSPA

Related parameter: HSDSCHCTSwitchGuardTimer of RNHSPA - If HSDSCHCTSwitchGuardTimer has
smaller value than in this parameter the channel type switch from DCH to E-DCH can be done before this timer
has expired.

RncId RNHSPAId EDCHCTSwitchGuardTimer

1 1 4 (2 s )
2 1 4
3 1 4
4 1 4
5 1 4
6 1 4
8 1 4
10 1 4
11 1 4
Classification : Interne

2- Channel type switch from DCH to E-DCH

A channel type switch from DCH to E-DCH is required to ensure that E-DCH can be allocated even if it was not possible in the initial channel allocation (the initial channel type selection between DCH and
E-DCH). Triggers for channel type switching can be divided into two categories.
•The initial triggers are those that can trigger channel type switching each time trigger conditions become valid.
•The secondary triggers are E-DCH quality- and capacity-related triggers. These can trigger channel type switching only if the initial trigger triggered a DCH to E-DCH channel type switch, or the
initial channel type selection would have selected E-DCH, but for the quality or capacity reason that was not possible.

The initial triggers are:

•DCH → HS-DSCH channel type switch
•HS-DSCH serving cell change
•PS streaming establishment
•E-DCH active set update
•EDCHCTSwitchGuardTimer expires
•If the HSPA can select the CS voice RAB, but the UE does not have a full HSPA configuration, then the CS voice RAB establishment determines whether it is
possible toswitch to the full HSPA configuration. The following are the triggers for the switch:
•CS voice RAB establishment
•Active set updating so that the full HSPA configuration becomes possible
•RAB combination change to a combination where CS voice over HSPA is supported
The secondary triggers are:
•E-DCH active set changes to acceptable
•DCH → E-DCH channel type switching retry timer expires
Additionally, the following prerequisites need to be fulfilled before the DCH to E-DCH channel typeswitch is executed: EDCHCTSwitchGuardTimer is currently
not running, the only exception from that rule being the case that a DCH to HS-DSCH channel type switch also triggers the DCH to E-DCH channeltype switch.
Furthermore, no active inter-frequency or inter-system handover causes need to exist. As soon as all these causes are eliminated, DCH to E-
DCH channel type switching is again possible.
 Classification : Interne

DCH → HS-DSCH channel type switch

If in the initial channel allocation the HS-DSCH cannot be allocated (initial channel type selection between DCH and HS-DSCH), the E-DCH is not allocated either. If
a channel type switch is triggered from DCH to HS-DSCH, a channel type switch from DCH to E-DCH is also triggered.
If HS-DSCH allocation fails, the E-DCH cannot be allocated either. If HS-DSCH is allocated, but the E-DCH cannot be allocated for the cell selected for serving the HS-DSCH cell, the E-
DCH cannot be allocated. The E-DCH active set must be acceptable to enable the DCH to E-DCH channel type switch.
A channel type switch from DCH can be performed only to the HS-DSCH/E-DCH configuration for CS voice over HSPA. A channel type switch from the DCH can be done only to the HS-
DSCH/E-DCH configuration, if flexible RLC (FRLC) is applied (see WCDMA RAN RRM HSDPA to find the conditions under which FRLC is applied). If the configuration HS-DSCH/E-DCH
is not possible, a fixed RLC PDU size is applied.

E-DCH active set update

When DCH is allocated for streaming and NRT services and a soft handover branch is deleted from the active set, the RNC checks whether all cells support E-DCH. The RNC triggers channel type switching
from DCH to E-DCH if all of the following conditions are true:
•All cells support E-DCH.
•The HSPAQoSEnabled parameter is set to ON for the serving HS-DSCH cell

EDCHCTSwitchGuardTimer expires
Whenever an E-DCH to DCH channel type switch is performed, the EDCHCTSwitchGuardTimer timer is set. The only exception is the BTS-initiated E-DCH → DCH channel type switch, in which case the timer is
not set.
When EDCHCTSwitchGuardTimer timer expires, it triggers a DCH to E-DCH channel type switch. This is done to enable the UE to return to E-DCH as fast as possible after the safety period (used to avoid too
frequent channel typeswitches) defined with the timer.
A check is performed to determine if the HS-DSCH serving cell supports the E-DCH, and if the E-DCH active set is acceptable to enable the DCH to E-DCH channel type switch.

E-DCH active set changes to acceptable

If in the initial channel allocation (initial channel type selection between DCH and E-DCH), or in a channel type switchfrom DCH to E-DCH, the E-DCH cannot be allocated because the E-DCH active set is not acceptab
the RNC starts to follow if E-DCH active set changes to acceptable. An E-DCH active set can change to acceptable if the cell not in E-DCH active set becomes ‘weak enough’ or is removed from the DCH active set. ‘W
enough’ is defined relative to serving HS-DSCH cell. The parameter EDCHAddEcNoOffset defines the threshold for the DCH to E-DCH channel typeswitch trigger. E-DCH active set is acceptable (a non-E-DCH capab
cell is ‘weak enough’) if the following equation is true.
CPICHEcNoNonEDCHNCell < CPICHEcNoEDCHServingCell + EDCHAddEcNoOffset
Where,
•CPICHEcNoNonEDCHNCell is the CPICH EcNo measurement result of the non-E-DCH cell in question,
•CPICHEcNoEDCHServingCell is the CPICH EcNo measurement result of the serving E-DCH cell,
•EDCHAddEcNoOffset is the radio network planning parameter that defines the addition offset for CPICH EcNo measurement results.
Classification : Interne

DCH → E-DCH channel type switching retry timer expires

Occasionally, in the initial channel type selection or in the DCH to E-DCH channel type switch, the E-DCH cannot be allocated, because the maximum number of E-DCH users are reached in the cell or local
cell group. In a soft handover situation a check is performed to determine whether the cell makes the E-DCH active set unacceptable. If it does not, the E-DCH can be allocated.
When the maximum number of E-DCH users prevents channel type switching, the internal channel type switch DCH to E-DCH retry timer is set. The timer gets the following value:
INTERVAL = min (10 seconds, NUMBER_OF FAILS * 2 seconds) (1)
When the timer expires, the RNC attempts a DCH to E-DCH channel type switch. A check is performed to determine whether the HS-DSCH serving cell supports E-DCH, whether the E-DCH
active set is acceptable, and whetherEDCHCTSwitchGuardTimer is not running, to enable DCH to E-DCH channel type switch.
Note that if the E-DCH active set is acceptable without the cell where E-DCH allocation failed because of the maximum number of E-DCH users reached in the cell or local cell group, the
E-DCH can be allocated. The RNC tries to add that cell to the E-DCH active set later.

Channel type switching if the UE enters an HSDPA/HSPA cell

Channel type switching takes place if HSDPA/HSPA becomes available in a cell in the active set current cell while the UE moves towards the area where HSDPA or HSPA is supported. The same criteria
apply for multi-NRT RABs and for single-NRT RAB on HSPA.
Multiplexing is performed as follows:
•DCH/DCH -> HS-DSCH/UL:DCH: L1 multiplexing of DL logical channels is reconfigured to MAC-hs multiplexing.
•DCH/DCH -> HSDSCH/E-DCH: bidirectional L1 multiplexing is reconfigured to UL MAC-e multiplexing and DL MAC-hs multiplexing.
•HS-DSCH/UL:DCH -> HSDSCH/E-DCH: L1 multiplexing of UL logical channels is reconfigured to MAC-e multiplexing.
The HSPA multi NRT RABs feature is enabled by the HspaMultiNrtRabSupport management parameter.
Normal serving cell selection, admission control, and resource reservations are made for SRBs and RBs to beswitched.
RT-over-NRT, RT-over-RT or pre-emption actions are not used in a DCH to HSPA switch. If HSPA resources are not found in all switched RBs and/or SRBs, the switch is aborted and DCH resources are
used. When the switch retry timer expires, and the conditions for the HSPA usage are still fulfilled, another switch attempt is performed.
Classification : Interne
Classification : Interne

Parameter Name: HsdschGuardTimerHO (HS-DSCH guard time after switching to DCH due to
HO).
Description: The parameter determines a period of time during which the HS-DSCH allocation is
denied after successful
channel type switching from HS-DSCH to DCH 0/0 kbps due to handover reasons. When DCH 0/0
kbps has been allocated to the UE due to any intra-frequency, inter-frequency or inter- RAT
handover reasons, HS-DSCH transport
channel is not allowed to be allocated during the guard time period. The restriction concerns the
particular UE and it is
effective in all the cells under RNC. The restriction is effective for the UE in the CELL_DCH and
CELL_FACH states. Timer is not applied if UE is transferred directly to the CELL_FACH state due to
Requête1
reporting event 1A when HSDPAMobility is
Disabled
RncId RNHSPAId
HSDSCHGuardTimerLowThr HSDSCHCTSwitchGuardTim
oughput er
HSDSCHQoSclasses HsdschGuardTimerHO

Object: RNHSPA 1 1 30 1 31 5
2 1 30 5 31 5
3 1 30 5 31 5
4 1 30 5 31 5
5 1 30 5 31 5
6 1 30 5 31 5
8 1 30 5 31 5
10 1 30 5 31 5
11 1 30 5 31 5
Classification : Interne

Parameter Name: HSDSCHGuardTimerLowThroughput (HS-DSCH guard timer due to low throughput)

Description: HSDSCHGuardTimerLowThroughput is a Uespecific timer. It is started after a release of the

MAC-d flow, which was triggered by low throughput. The timer is started just if DCH 0/0 is allocated. When the
timer is running HS-DSCH allocation is not allowed to the UE.

Parameter: HS-DSCH channel type switch guard timer

Description: This parameter determines the time that must be waited after an HS-DSCH to DCH channel type
switching before an DCH to HS-DSCH channel type switching can be done.
Classification : Interne

Parameter: HSDPAMaxCellChangeRepetition (Max number of repetitive serving HS-DSCH cell changes)

Description: This parameter determines the maximum number of repetitive serving HS-DSCH cell changes during a predefined time period. If the maximum number of serving HS-
DSCH cell changes is exceeded, HS-DSCH is released. When this parameter is set to 0, the CTS to DCH due to repetitive SCC's is disabled.
This parameter is overruled if Fast HSPA Mobility is enabled in the serving HS-DSCH cell with the WCEL parameter FastHSPAMobilityEnabled and the maximum number of repetitive serving HS-
DSCH cell changes is determined on cell level with the WCEL parameter HSDPAMaxCellChangeRepetition of the serving HS-DSCH cell.
The RNHSPA parameter HSDPACellChangeRepetitionTime determines the time period during which the maximum number of repetitive serving HS-DSCH cell changes is counted.

Parameter: HSDPACellChangeRepetitionTime
Description: This parameter determines the time period for calculation of the maximum number of repetitive serving HS-DSCH cell changes.
Classification : Interne

Requête1
RncId RNHSPAId HSDPACellChangeRepetitionTime HSDPAMaxCellChangeRepetition
1 1 10 4
2 1 10 4
3 1 10 4
4 1 10 4
5 1 10 4
6 1 10 4
8 1 10 4
10 1 10 4
11 1 10 4
Classification : Interne
Classification : Interne

MACdflowthroughputAveWin
This parameter defines the averaging window size for the throughput measurement of the MAC-d
flow. The throughput measurement measures the number of bits transmitted by MAC-d during the
sliding measurement window. The sliding measurement window is defined with the parameter
MACdflowthroughputAveWin. Value 0 means that the MAC-d flow throughput measurement is not
activated.
EDCHMACdFlowThroughputAveWin
Description: This parameter defines the size of the sliding averaging window for the throughput
measurement of
the E-DCH MAC-d flow. The throughput measurement measures the number of bits transmitted by
the E-DCH MAC-d flow during the sliding measurement window. The value 0 of the parameter
means that the E-DCH MAC-d flow throughput measurement is not performed.
MACdflowthroughputAveWin : current value : 6/4 (3 sec/2 sec),
EDCHMACdFlowThroughputAveWin : current value : 6/4 (3 sec/2 sec),
Classification : Interne
Classification : Interne
Classification : Interne
MACdflowutilRelThr (Low utilisation threshold of the MAC-d flow):
Description: This parameter defines the low utilisation threshold of the throughput
measurement of the MAC-d flow. The threshold is defined as a number of bits per second.
The throughput measurement measures the number of bits transmitted by MAC-d during
the sliding measurement window.
Default value: 256
Current set 1 (256bps)/2(500bps), default value: 256.
Object: WAC
MACdflowutilTimetoTrigger (Low utilization time to trigger of the MAC-d flow):
This parameter defines the low utilisation time to trigger the timer of the throughput measurement
of the MAC-d flow.
Object: WAC
MACdflowthroughputRelThr (Low throughput threshold of the MAC-d flow)
This parameter defines the low throughput threshold of the throughput measurement of the MAC-d
flow. The threshold is defined as a number of bits per second. The throughput measurement
measures
the number of bits transmitted by MAC-d during the sliding measurement window.
Default value: 0
Current value: 0
Object: RNHSPA
MACdflowthroughputTimetoTrigger (Low throughput time to trigger of the MAC-d flow)
This parameter defines the low throughput time necessary to trigger the timer of the throughput
measurement of the MAC-d flow.
Classification : Interne

HSDSCHguardTimerlowthroughput:
HSDSCHGuardTimerLowThroughput is a Uespecific timer. It is started after a release of the MAC-
d flow, which was triggered by low throughput. The timer is started just if DCH 0/0 is allocated.
When the timer is running HS-DSCH allocation is not allowed to the UE.
Default value: 30 sec
Current value: 30 sec
Classification : Interne
Classification : Interne
Classification : Interne

All
parameters
are set to
their default
values.