Selection between DCH and HS-DSCH

HS-DSCH is selected if all of the following conditions are met:

1. Traffic class and traffic handling priority are allowed on HS-DSCH.
The operator can configure which traffic classes and traffic handling priorities are allowed with HSDPA
with the HSDSCHQoSclasses parameter. The FDPCHAndSRBOnHSPATC management parameter can also
restrict the use of SRBs on HSPA configuration for the certain traffic class.
As all transport channel-type combinations are not allowed, a switch to DCH may, thus, become
necessary for existing RABs if one RAB is not allowed to use the HSDSCH. A new RT RAB can, however,
also trigger a DCH to HS-DSCH channel type switch (see Direct DCH to HS-DSCH switch). Notice that CS
voice can be also switched to DCH, because the use of HSDPA for CS voice means full HSPA configuration.
2. UE capability supports HS-DSCH, as defined by the following UE radio access capability parameters:
Support of HS-PDSCH, indicating whether or not the UE supports HS-PDSCH UE informs in RRC
Information Element Multi cell support whether it support DC-HSDPA. Information is received in RRC
CONNECTION REQUEST message.
HS-DSCH physical layer category, providing the UE capability in terms of maximum number of received
HS-DSCH codes, minimum inter-TTI interval, maximum number of bits of an HS-DSCH transport block
received within an HSDSCH TTI, and total number of soft channel bits. The RNC receives the value from
the UE (REL-5 HS-DSCH physical layer category, REL-7 HS-DSCH physical layer category extension, REL-8
HS-DSCH physical layer category extension 2). The information is received in RRC CONNECTION SETUP
COMPLETE message. The RNC stores the received RRC Information Elements Multi cell support, HS-
DSCH physical layer category, HS-DSCH physical layer category extension, and HS-DSCH physical layer
category extension 2 and uses them during the lifetime of the RRC connection.
DL capability with simultaneous HS-DSCH configuration, defining the modification of reception
capabilities in the downlink direction in terms of DPCH when an HS-DSCH is configured simultaneously
support of CS voice over HSPA, indicating wheather or not UE supports CS voice mapped to HSPA
(Information on CS voice over HSPA support is sent by the UE during RRC connection setup procedure in
RRC: RRC CONNECTION SETUP COMPLETE message.)
Note that the information related to HS-DSCH physical layer category is not used to define SRB RLC PDU
size and maximum bit rate of SRBs/MAC-d flow of HSDPA.
3. The cell supports HSDPA.
The support of HSDPA in a particular cell is enabled or disabled with the HSDPAenabled managing
parameter.
A cell is considered to support HSDPA if its HSDPA Capability information element (IE) is set to HSDPA
Capable and the Resource Operational State IE in the HSDSCH Resources Information IE is not set to
Disabled. The RNC stores the information about each cell's HSDPA capability and updates the
information upon receipt of NBAP: Audit Response and NBAP: Resource Status Indication
messages.DN0638161 71
WCDMA RAN RRM HSDPA UE-specific resource handling
4. HS-DSCH is enabled in the cell.
A HS-DSCH is considered enabled when its Resource Operational State IE in the HS-DSCH Resources
Information IE is not set to Disabled.
5. Multi-RAB combination of the UE is supported with HS-DSCH.
With the restriction that the support for AMR speech CS RAB (HSDPA with simultaneous AMR Voice call),
CS voice over HSPA (CS voice over HSPA), multiple (more than one) NRT RABs (HSPA Multi NRT RAB),
and HSPA streaming (Streaming QoS for HSPA) are optional features, a number or multi-RAB
combinations are supported. For details, see RAB combinations for HSDPA.
6. The number of simultaneous HS-DSCH MAC-d flows or HSDPA users is below the maximum number of
HS-DSCH allocations. The maximum number of simultaneous HS-DSCH MAC-d flows and HSDPA users is
defined by the MaxNumberHSDSCHMACdFlows and MaxNumberHSDPAUsers WCEL parameters,
respectively, and depends on the active licenses, see Maximum number of HSDPA users per cell.
7. The UE is not performing inter-frequency or inter-system measurements.
8. The HsdschGuardTimer and HsdschGuardTimerLowThroughput guard timers are not running.
9. There is no HSDPA scheduler congestion in BTS. For more information, see HSDPA prevention in case
of BTS HSDPA scheduler (MAC-hs/ehs entity) congestion.
10. The active set size is equal to one. This condition is only checked if the HSDPAMobility parameter
value is Disabled.
11. The UE does not have DCHs scheduled with bit rates higher than zero.
12. The HS-DSCH physical layer category is supported.
13. HSDPA Dynamic Resource Allocation is disabled:
If there is no existing HS-DSCH MAC-d flow in the cell, depending on the HSDPApriority parameter,
Condition 1 or Condition 2 has to be valid before HS-DSCH can be selected.
If HSDPA Dynamic Resource Allocation is enabled, admission decision is made without taking downlink
power and HSDPApriority parameter into account.
14. In case of a PS streaming and CS voice RB, resource checks for HS-DSCH have to be passed as well to
get the HS-DSCH, see Admission decision.
If any of the conditions is not met, DCH packet scheduling is initiated, which may also mean using DCH
0/0 kbit/s.
In case of CS service all the following conditions must also (in addition to general conditions) be fulfilled:
mapping of priority service to HS-DSCH is allowed by the operator (with the RNP
parameter FDPCHSetupEC), if the CS RAB is pre-emption capable.
CS voice over HSPA is supported by the UE
MAC-ehs is supported by the BTS
full HSPA configuration is possible (F-DPCH)
all cells in the active set must support CS voice over HSPA
Flexible RLC is enabled (MAC-ehs)72 DN0638161