13 6255 NAK HSUPA Protocol Features

Contents
UMTS/HSPA Radio Resource Management & Parameter

 Introduction to Radio Resource Management
 Power Control
 Load Control
 Admission Control
 Packet Scheduling
 Code Tree Management
 PLMN and Cell Selection
 Handover Procedures
 HSDPA Protocol Features
 HSDPA Power Management
 HSDPA Code Resource Management
 HSDPA Mobility
 HSUPA Protocol Features
 HSUPA Power Management
 HSUPA Mobility
 HSPA+
00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Content
HSPA+
 HSDPA Enhancements
64QAM
Flexible MAC-d PDU size
Dual Cell HSDPA
MIMO
 HSUPA Enhancements
 Fast Dormancy
 HS-Cell FACH

64QAM
- HSDPA+ uses for fast link adaptation not only QPSK and 16QAM, but also 64QAM
- Requires UEs of HS-DSCH category 13 and higher
- Requires flexible MAC-d PDU size and often also dynamic power / code resource allocation
I
100000 100010 101010 101000 001000 001010 000010 000000 TS 25.201
100001 100011 101011 101001 001001 001011 000011 000001
100101 100111 101111 101101 001101 001111 000111 000101

64QAM:
100100 100110 101110 101100 001100 001110 000110 000100 6-Bit
Keying Huawei
110100 110110 111110 111100 011100 011110 010110 010100
Q HspaPlusSwitch
MO: UCELLALGOSWITCH
110101 110111 111111 111101 011101 011111 010111 010101 Bit Field Type, 22 bits
64QAM activated
Nokia (per cell) Ericsson (per Node B)
110001 110011 111011 111001 011001 011011 010011 010001
HSDPA64QAMAllowed featureState64Qam
110000 110010 111010 111000 011000 011010 010010 010000
0,1, 0 = disabled Deactivated, activated

Adaptive Modulation & Coding
UE
4/4
5/6 3/4 1/2
3/4 2/4
3/4 2/4 1/4 1/6
Node B
64QAM 16QAM QPSK

Need CQI > 25 Need CQI > 15

Content
HSPA+
64QAM
Dual Cell HSDPA
MIMO
 Fast Dormancy
 HS-Cell FACH

Flexible RLC (DL) – Concept
• RLC supports Flexible RLC PDU size instead of fixed PDU size
• reduces the processing requirements and RLC layer overhead
• Flexible RLC enables achieving of significantly larger RLC PDU sizes (up to 1502 bytes according
to 3GPP specifications) comparing to the maximum fixed RLC PDU size of 82 bytes.
• From 3GPP specification point of view, enhanced layer 2 is a requirement for high HSPA+ bit
rates
RLC PDU size increased with Flexible RLC
3GPP Rel. 6 3GPP Rel. 7

Flexible RLC (DL) – Before and After
Without feature With feature
Before 3GPP Rel. 7
• the RLC layer within the RNC segmented large
higher layer packets into many small packets
(fixed RLC PDU sizes of 336 bits and 656 bits)
RNC RNC
• The Node B had to concatenate and pad these
small packets to fit within the variable size Segmentation
HSDPA transport block
With Flexible RLC in Rel. 7 the RNC becomes

relatively transparent:
Node B Node B
• The Node B segments the higher layer packets Concatenation / Segmentation /
such that they fit within the HSDPA transport Padding Concatenation
block

Flexible MAC-d PDU Size (1/2)
- Even with MAC-d PDUs of 656 bit (before the feature) there are 5% RLC header overhead
- HSDPA+ allows to put one IP packet into a single MAC-d PDU up to a certain limit
MAC-d PDU
RLC header RLC data Huawei (per RAB type)

16 bit Up to 12000 bit
HsdschMacdPduSize
1.5000, 336 bit
Flexible MAC-d PDU size activated Nokia (per cell) Ericsson (per cell)
FRLCEnabled featureStateEnhancedLayer2
Maximum MAC-d PDU size 0,1, 0 = disabled Deactivated, activated
Max. MAC-d PDU Max. MAC-d PDU

Hard coded 12000 bit Hard coded

Flexible MAC-d PDU Size (2/2)
- MAC-d PDUs too big for a single HSDPA packet are segmented
MAC-d PDU (segmentation into several HSDPA packets)
HSDPA packet
RLC
RLC data RLC data RLC data
h.
MAC-hs MAC-hs
header payload

Content
HSPA+
64QAM
Dual Cell HSDPA
MIMO
 Fast Dormancy
 HS-Cell FACH

Principles (1/3)
- 3GPP R8  two adjacent HSDPA carriers can be allocated to a single UE

- 3GPP R8  dual cell HSDPA can be combined with 64QAM, but not with MIMO
- 3GPP R9  dual cell HSDPA can be combined with MIMO as well
- Dual band HSDPA requires UE of category 21 to 24 (or beyond)
Huawei
HspaPlusSwitch
MO: UCELLALGOSWITCH
f1 5 MHz Bit Field Type, 22 bits
f2 5 MHz
Nokia (per cell) Ericsson (per Node B)
DCellHSDPAEnabled featureStatehsdpaMc
Dual cell HSDPA activated 0,1, 0 = disabled Deactivated, activated

Principles (2/2)
- Whether indeed both carriers are offered, depends on the quality of the air interface
- If one carrier offers good conditions only, just this is offered
f1
Both carriers good
f2
f1 good only
f1
f2
f1
f2 good only
f2

Practical Implementation
- The cells defined by the two carriers must fulfil the following settings
Adjacent UARFCN
Same sector ID
Same timing offset for P-SCH Tcell
- Each sector is controlled by one shared HSDPA scheduler
Sector 1
Tcell (1)
Sector 3 f1
Sector 2
Tcell (3)
Tcell (2)
Sector 1
Tcell (1)
Sector 3 f2 = f1  5 MHz
Sector 2
Tcell (3)
Tcell (2)

DC-HSDPA – Channels
• DC HSDPA UEs are assigned HS-DSCHs in the primary serving and secondary cell
• UL for DC HSDPA UEs transmitted via primary serving cell (no UL in secondary serving HS cell)
• the primary serving cell is carrying
• Full set of dedicated and common control channels
• UL transport channels E-DCH and control channels
• Secondary serving cell is having less signaling (maximum HS-DSCH capacity)
• Among common channels only CPICH is used
• E-AGCH, E-RGCH and E-HICH might by existent for dual cell HSUPA
+ Common CHs + E-AGCH, E-RGCH, E-HICH

Primary serving cell
HS-DPCCH HS-SCCH
E-DPDCH/E-DPCCH HS-PDSCH
DPDCH/DPCCH
F-DFCH
UL DPCCH
HS-SCCH
HS-PDSCH
Secondary serving cell

Content
HSPA+
64QAM
Dual Cell HSDPA
MIMO
 Fast Dormancy
 HS-Cell FACH

Principle (1/2)
- Base band Input split into M parallel data streams transmitted by M antennas
- N ≥ M receive antennas to recognize the individual data streams
Possible, as each of the M x N Tx-Rx paths has its own propagation characteristic due to
multi path
- Requires flexible MAC-d PDU size and often also dynamic power / code resource allocation
Signal from jth Tx antenna Sj h1,1 Yi Signal at ith Rx antenna
T1 hn,1 h2,1 h1,m R1

h1,2
h2,2
hn,2
h2,m
MIMO
Input T2 R2 Output
Processor
• •
• •
• hn,m •
MxN
Tm MIMO system Rn

Principle (2/2)
- Receiver determines channel matrix H giving the propagation characteristic of each

Tx-Rx path hi,j
- H gives received data streams yi as function of originally transmitted data streams sj
- To reconstruct the original data streams, H must be inverted
Huawei
h1,1 h1,2  h1,m HspaPlusSwitch

MIMO activated MO: UCELLALGOSWITCH
h2,1 h2,2  h2,m Bit Field Type, 22 bits
H= 




 Nokia (per cell)
  
MIMOEnabled
hn,1 hn,2  hn,m 0,1, 0 = disabled
Ericsson
m
yi   hi , j  s j  ni
featureStateMimo (per Node B)
ni = receiver noise Deactivated, activated
j 1 transmissionScheme (per cell)
0 (single ant.),1 (Tx div.), 2 (MIMO)

Practical Implementation
- Currently 2 x 2 MIMO is available only

- Requires UEs of category 15 to 18
UE of category 15 and 16 support
15 codes
16 QAM + MIMO
Peak data rate 28 Mbit/s
UE of category 17 and 18 support
15 codes
16 QAM + MIMO OR 64 QAM
Peak data rate 28 Mbit/s with 16 QAM + MIMO OR 21 Mbit/s with 64 QAM

Secondary CPICH
- To estimate the channel matrix H for 2 x 2 MIMO, a second CPICH is required

Primary CPICH for 1st data stream
Secondary CPICH for 2nd data stream
- The secondary CPICH is transmitted with same power and SF as the primary one
SF16 +15 x SF16

HS-PDSCH
SF32 32
SF64 64 64 64
FACH/PCH
SF128 128 128 128 128 128 128 128

HS-SCCH
SF256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256
P-CPICH, BCH, AICH, PICH E-RGCH E-AGCG (10ms) S-CPICH
E-HICH E-AGCH (2ms) F-DPCH

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
Continuous Packet Connectivity
Interference Cancellation
UL receiver improvements
 Fast Dormancy
 HS-Cell FACH

HSUPA 16QAM – General View (1/2)
• 3GPP Release 7 introduces 16QAM, whereas the existing power control algorithm cannot support the increased
peak rate.
• 3GPP Release 7 introduces also the E-DPCCH Boosting technology to enable a dramatic increase in the transmit
power of an E-DPCCH in a short period of time, which improves the signal-to-interference ratio (SIR) of services
that require a high transmission rate.
• When the EDPCCH Boosting feature is used together with the UL 16QAM feature, the theoretical uplink peak rate
of a single HSUPA user can reach 11.5 Mbit/s.
QPSK with 2 bits 16AM (4PAM) with

per symbol 4 bits per symbol
• 11.6 Mbps* is supported with 4 E-DCH channels in parallel (2xSF2 + 2xSF4)

• UE category 7, 9 enable transmission of 4 codes in parallel and support 11.6 Mbps at maximum with 16QAM
• In case of 4 code E-DCH transmission 3GPP defines that no DPDCH may be allocated simultaneously
• The SRB needs to be mapped on E-DCH.

HSUPA 16QAM – General View (2/2)
E-DPCCH Boosting
• high-speed data transmission has higher requirements for the uplink SIR
• 3GPP Release 7 introduces the E-DCH Dedicated Physical Control Channel (E-DPCCH) Boosting technique
• When a user initiates high-speed data transmission, E-DPCCH Boosting quickly increases the transmit power on
the E-DPCCH and NodeB uses this channel for multipath searching and channel estimation.
• This increases the accuracy of channel estimation and therefore improves the high-speed transmission
performance, allowing for higher peak throughput and cell throughput in the uplink.
• E-DPCCH Boosting is essential for high-speed data transmission using uplink 16QAM, which requires strictly
accurate channel estimation.
• When used together with uplink 16QAM, EDPCCH Boosting allows for a theoretical peak rate of 11.5 Mbit/s for a
single user in the uplink.
• UEs in HSUPA data transmission mode decide whether

to use E-DPCCH Boosting according to the E-DCH
Transport Format Combination Indicator (E-TFCI) size
and E-TFCI threshold chosen by each TTI..
UE
Node B

HSUPA 16QAM – Huawei
UL16QAM • MO = ULOCELL
FALSE~0, TRUE~1; FALSE • Description: Indicates whether the UL 16QAM feature is supported by the cell.
BOOST • MO = ULOCELL
FALSE~0, TRUE~1; FALSE • Description: Indicates whether the BOOST feature is supported by the cell.
HsupaUl16QamTotalRateThs EcBoostingTotalRateThd
0~11480; 3640 kbps 0~11000; 40 kbps
HsupaUl16QamTotalRateThs MO = UFRC
• Description: This parameter specifies the threshold for triggering the 16QAM for the HSUPA traffic. The 16QAM
data transmission is performed in the uplink only when the total rate of the HSUPA traffic (including the SRB uplink
rate) reaches the threshold specified by this parameter. The larger the value of this parameter, the more the UEs
that cannot use 16QAM. As a result, the peak rates for these UEs are limited. The smaller the value of this
parameter, the more the UEs that can use 16QAM and the more the used resources. As a result, the peak rates
for the UEs requiring 16QAM are limited.
EcBoostingTotalRateThd MO = UFRC
• Description:The total rate threshold of HSUPA traffic for Boosting. If this parameter is set to a very large value,
only a small number of UEs whose uplink data rate exceeds the value of "EcBoostingTotalRateThd" can use E-
DPCCH Boosting. In addition, the resource utilization of E-DPCCH Boosting is low and the cell throughput cannot
greatly increase. If this parameter is set to a very small value, a large number of UEs preempt limited resources of
E-DPCCH Boosting. For UEs without such resources, the uplink transmission performance deteriorates and as a
result uplink cell capacity decreases.

HSUPA 16QAM – Ericsson
Feature not yet available (2016-08-22)

HSUPA 16QAM – Nokia
HSUPA16QAMAllowed (on cell level) HSUPAUserLimit16QAM
Disabled (0), Enabled (1); Disabled (0) 1...10, step 1; 2
ETFCIBoost (non configurable) • See Frequency domain equalizer

RNC; 0..127 ;1 102  UE selects 16QAM when E-TFCI is >103 – E-DPCCH Boosted Mode
HSUPAUserLimit16QAM MO: WCEL Category: Basic parameter

• Description: This parameter defines the limit for the amount of active HSUPA users in a cell in the process of
determining the usage of HSUPA 16QAM with both fixed and flexible UL RLC. It is also used to determine the fixed
UL RLC PDU size with MAC-es. For flexible UL RLC: If the amount of active HSUPA users in a cell is lower than or
equal to the threshold, defined by this parameter, the HSUPA 16QAM usage is allowed with flexible UL RLC PDU
size. In case the parameter is set to special value 127, the amount on active HSUPA users shall be considered
fulfilled as part of HSUPA 16QAM usage criteria (i.e. the amount of active HSUPA users shall not be verified).
For fixed UL RLC: If the amount of active HSUPA users in a cell is lower than or equal to the threshold defined by this
parameter, the fixed UL RLC PDU size must be 656 bits. Otherwise an UL RLC PDU size of 336 bits can be used.
The HSUPA 16QAM usage is allowed if the UL RLC PDU size is 656 bits. In case the parameter is set to special
value 127, the amount on active HSUPA users shall be considered fulfilled as part of HSUPA 16QAM usage criteria
(i.e. the amount of active HSUPA users shall not be verified) and the fixed UL RLC PDU size is set to 656 bits.
MaxTotalUplinkSymbolRate
0 (960 kbps, SF4), 1 (1.92 Mbps; 2xSF4), 2 (3.84 Mbps; 2xSF2), 3 (5.76 Mbps; 2xSF2 + 2xSF4); if HSUPA
16QAM is active then the parameter value 3 is allowed;

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
 Fast Dormancy
 HS-Cell FACH

DC-HSUPA – General View
• 3GPP Release 9 DC-HSUPA uses the multi-carrier technology in the uplink, allowing a UE to establish uplink
connections with two cells simultaneously on two intra-band adjacent carriers that provide the same coverage.
Node B
UE
UEs point of view: two carriers

• primary uplink carrier= the carrier on which the serving E-DCH cell corresponding to the serving HS-DSCH cell is transmitted.
• secondary uplink carrier = carrier on which the serving E-DCH cell that corresponds to the secondary serving HS-DSCH cell is
transmitted.

DC-HSUPA – used Channels
E_AGCH E-DPDCH
HS-SCCH
E-RGCH E-DPDCH Secondary
HS-PDSCH
E-HICH E-DPCCH Carrier
F-DPCH
E-DPCH UL-DPCCH
E-DPDCH
E_AGCH
HS-SCCH E-DPDCH
E-RGCH
HS-PDSCH HS-DPCCH (Ack/Nack/CQI)
Primary
E-HICH Carrier
F-DPCH E-DPCCH
E-DPCH
UL-DPCCH
• In DC-HSUPA operations, two E-DCH transport channels and two HS-DSCH transport channels need to be
configured for the UE because DC-HSUPA requires that DC-HSDPA be used in the downlink.
Soft Handover
• DC-HSUPA UE performs a soft handover based on the measurement result of the primary carrier
• Mobility events are measured and triggered on the primary carrier
• All intra-frequency measurement events are supported on the primary carrier.
• There is an E-DCH active set for each uplink carrier of DC-HSUPA
• The E-DCH active sets for the two carriers must be paired, that is, if a cell is in the primary E-DCH active set (E-
DCH active set on the primary carrier), the cell which has the same coverage with this cell and is on secondary
carrier must be in the secondary E-DCH active set (E-DCH active set on the secondary carrier).

DC-HSUPA – Huawei (1/2)
ULSECCELLDEACTCOVTHR ULSECCELLACTOPTSW
0~1000, unit 10 kbps; 0 OFF~0, ON~1; OFF
ULSECCELLDEACTCOVTHR MO = ULOCELLMACEPARA
• Description: Secondary DC-HSUPA Cell Deactivation Rate Threshold. Indicates the minimum rate threshold
supported by the uplink transmit power for ensuring the minimum coverage of activated DC-HSUPA UEs on the
secondary carrier. To be specific, to meet the minimum coverage requirements of activated DC-HSUPA cell edge UEs
(CEUs) on the secondary carrier, the maximum rate threshold supported by the uplink transmit power cannot be
lower than this threshold. Otherwise, the CEUs on the secondary carrier need to be deactivated. A large value of this
parameter indicates a high probability of uplink transmit power-based deactivation of UEs on the secondary carrier.
This operation improves the edge throughput of DC-HSUPA UEs (reaching SC-HSUPA performance), but decreases
the number of activated DC-HSUPA UEs on the secondary carrier. A small value of this parameter indicates a low
probability of uplink transmit power-based deactivation of UEs on the secondary carrier. There are available loads on
the secondary carrier, which ensures data transmission of DC-HSUPA UEs and maximizes the usage of air interface
resources on the secondary carrier.
ULSECCELLACTOPTSW MO = ULOCELLMACEPARA
• Description: Secondary DC-HSUPA Cell Activation and Deactivation Switch Based on RTWP. If this parameter
is set to OFF, DC-HSUPA UEs experience improves. If this parameter is set to ON, the secondary DC-HSUPA
cell throughput increases.

DC-HSUPA – Huawei (2/2)
DCHsupaHRetryPenaltyTime
1~255; 10 s
DCHsupaHRetryPenaltyTime MO = UCOIFTIMER
• Description: Penalty time of periodical retries to DC-HSUPA after DC-HSUPA falls back to SC-HSUPA when
the DC-HSUPA independent active set function is enabled. Periodical retries include blind periodical retries and
measurement-based periodical retries. It is recommended that the parameter value be greater than the value of
the "ChannelRetryTimerLen" parameter.
• The larger the value of this parameter, the later the UEs having fall backed to SC-HSUPA attempt to switch to
DC-HSUPA, affecting user experience. The smaller the value of this parameter, the smaller the effect of the
penalty mechanism.

DC-HSUPA – Ericsson (1/2)
Feature name: EUL Multi-Carrier
• The feature introduces support for the UE to use EUL on two adjacent carriers.
• Simultaneous UL Enhanced Dedicated Channel (E-DCH) transmission on two adjacent carriers is
supported from a given UE unit.
eulMultiCarrierSupport eulMcSohoSupp hsIflsPrio.eulMc

OFF = 0, ON = 1 FALSE = 0 TRUE = 1 1..8; -1
eulMultiCarrierSupport MO: MultiCarrier

• Description: Indicates if all conditions to support EUL Multi-Carrier connections in the RBS are met for this cell.
Read only.
eulMcSohoSupp MO: Handover

• Description: Indicates if the RNC supports soft(er) handover for UE connections using EUL Multi-Carrier. When set
to False, a reconfiguration to EUL single-carrier takes place before handover when a new soft(er) handover
attempt is made for UE, if the UE is using EUL Multi-Carrier.
hsIflsPrio.eulMc MO: Handover

• Description: IFLS priority for the EUL Multi-Carrier (EUL MC) capability. 1 is the highest priority. Higher values
have lower priority. When set to -1, IFLS does not consider this capability. If this feature is not activated, IFLS
always uses the same value as the default value, regardless of the configured value.

DC-HSUPA – Ericsson (2/2)
eulMcServingCellUsersAdmTti2 reportingRange1aOffsetSecondary -
0..200; 3 -20..20; -2 dB (Unit: 0.5 dB)
eulMcServingCellUsersAdmTti2 MO: UtranCell

• Description: Admission threshold for the number of EUL Multi-Carrier users having this cell as primary serving cell.
For EUL/HS Cell Change, this parameter is applicable only if RncFunction::eulUsersAdmEulHsCcEnabled is set to
true.
reportingRange1aOffsetSecondary MO: UeMeasControl

• Description: Used by UE functions for intra-frequency measurement reporting (in CELL_DCH) on Secondary UL
frequency. System constant for the reporting range for the secondary event 1a, defining an offset to be added to
the reporting range for the (primary) event 1a. Reporting range for secondary event 1a = reportingRange1a +
reportingRange1aOffsetSecondary

DC-HSUPA – Nokia
Nokia supports up to 11.5 Mbps per UE (2x QPSK) with DC-HSUPA feature
• DC-HSUPA is enabled using the WCEL parameter DCellHSUPAEnabled.

• Power offset between the initial DPCCH power level on secondary UL frequency when it is activated and the
current DPCCH power level on primary UL frequency can be defined with DPCCHPwrOffsetSecULFreq
• MaxNumberEDCHS defines the maximum allowed number of SC-E-DCH and DC-E-DCH users in the MAC-i/is
specific BTS scheduler.
DCellHSUPAEnabled (on cell level) DPCCHPwrOffsetSecULFreq (on cell level)

0 (Disabled), 1 (Enabled) ; 0 (Disabled) 0..7 dB, step 1 dB; 3 dB
MaxNumberEDCHS (on cell level)

1..1023, step 1; 0 Not restricted

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
 Fast Dormancy
 HS-Cell FACH

Continuous Packet Connectivity (1/2)
- Consider HSUPA service with low data rate

E-DPDCH occasionally present only
Huge overhead due to permanent present DPCCH
- Reduce UE activity
Transmit DPCCH only, when HSUPA data have to be sent
Listen to E-AGCH / E-RGCH only when needed
- If HSDPA data rate low also

Reduce SQI reporting (HS-DPCCH overhead)
Listen to HS-SCCH only when needed
- Node B can reduce activity as well
Listen periodically to UE only

Continuous Packet Connectivity (2/2)
DPDCH
R99 voice
DPCCH
HSUPA voice E-DPDCH

2ms TTI DPCCH
HSUPA voice E-DPDCH

2ms TTI
With CPC DPCCH

Continuous Packet Connectivity (CPC) – Nokia (1/7)
CPC hat the following functionalities:
• UL DPCCH Gating (UL DTX)
• CQI Reporting reduction
• Discontinuous UL Reception (MAC DTX)
• Discontinuous DL Reception (DL DRX)

UL DPCCH Gating (UL DTX) - Parameters
• UE specific Packet Scheduler provides CPC parameters

• These are service & UL TTI specific & part of parameter groups
• Voice 2ms, 10ms; RNHSPA: CPCVoice10msTTI, CPCVoice2msTTI
• Streaming 2ms, 10ms; RNHSPA: CPCStreaming10msTTI, CPCStreaming2msTTI
• Interactive, Background 2ms, 10ms; RNHSPA: CPCNRT10msTTI, CPCNRT2msTTI
Following parameters are parameters from CPCNRT2msTTI group (per sub-feature):

DPCCH Gating (UL DTX):
• N2msInacThrUEDTXCycl2: number of consecutive E-DCH TTIs without an E-DCH transmission, after which the UE
should immediately move from UE DTX Cycle 1 to UE DTX Cycle 2. RNHSPA; Range:1 (0), 4 (1), 8 (2), 16 (3), 32
(4), 64 (5), 128(6), 256 (7); default: 64 (5) TTIs
• N2msUEDPCCHburst1: UL DPCCH burst length in subframes when UE DTX Cycle 1 is applied. RNHSPA; Range:1
(0), 2 (1), 5 (2); default: 1 (0) subframes
• N2msUEDPCCHburst2: UL DPCCH burst length in subframes when UE DTX Cycle 2 is applied. RNHSPA; Range:1
(0), 2 (1), 5 (2); default: 1 (0) subframes
• N2msUEDTXCycle1: UL DPCCH burst pattern length in subframes for UE DTX Cycle 1. RNHSPA; Range: 1 (0), 4
(1), 5 (2), 8 (3), 10 (4), 16 (5), 20 (6); default: 8 (3) subframes
• N2msUEDTXCycle2: UL DPCCH burst pattern length in subframes for UE DTX Cycle 2. RNHSPA; Range: 4 (0), 5
(1), 8 (2), 10 (3), 16 (4), 20 (5), 32 (6), 40 (7), 64 (8), 80 (9), 128 (10), 160 (11); default: 16 (4) subframes

UL Gating, E-DCH 2ms TTI example: CPCNRT2msTTI
N2msInacThrUEDTXCycl2
RNHSPA; 1, 4, 8, 16, 32, 64, 128, 256; 64 TTIs
CFN 10ms Radio Frame 10ms Radio Frame 10ms Radio Frame
Inactivity Threshold for UE cycle 2

E-DPDCH
Tx, 2ms TTI
no data on E-DPDCH
N2msUEDPCCHburst1
DPCCH RNHSPA; 1, 2, 5; 1 subframe(s)
pattern
N2msUEDTXCycle1 N2msUEDPCCHburst2
synch reference RNHSPA; 1, 4, 5, 8, 10, 16, RNHSPA; 1, 2, 5; 1 subframe(s)
UE_DTX_Cycle_1
20; 8 subframes
UE_DTX_Cycle_2 UE_DTX_Cycle_2
N2msUEDTXCycle2
RNHSPA; 4, 5, 8, 10, 16, 20,
DPCCH with 32, 40, 64, 80, 128, 160; 16
E-DCH, 2ms TTI subframes
2ms subframe cycle 1 cycle 2
UE_DTX_DRX_offset is UE specific offset granted from BTS switch to UE cycle 2

CFN: Connection Frame Number; used for any synchronized procedure in UTRAN
Pre/Postambles not shown here

CQI Reporting reduction:
• CQI Reporting Reduction reduce the Tx power of the UE by reducing the CQI reporting; this means to reduce the interference from HS-
DPCCH in UL when no data is transmitted on HS-PDSCH in DL
• Reduced CQI reporting takes place only if the CQI reporting pattern defined by the last HS-DSCH transmission and CQI cycle overlaps the
UL DPCCH burst of the UE DTX pattern
• N2msCQIDTXTimer: defines the number of subframes after an HS-DSCH reception, during which the CQI reports
have higher priority than the DTX pattern. RNHSPA; 0 (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256
(9), 512 (10), Infinity (11); 64 (7) subframes
• N2msCQIFeedbackCPC: defines the CQI feedback cycle for HSDPA when the CQI reporting is not reduced
because of DTX. RNHSPA; 0 (0), 2 (1), 4 (2), 8 (3), 10 (4), 20 (5), 40 (6), 80 (7), 160 (8); default: 8 (3) ms; Note:
Bigger CQI reporting cycles 10ms are not recommended.
CQI transmission time defined by
HS-DSCH reception CQI_DTX_TIMER CQI_DTX_Priority set to 0 CQI period, but not overlapping with
DPCCH transmission no CQI transmission
ACK/NACK CQI Transmission
7.5
transmission slots
CQI_DTX_Priority set to 1
DPCCH
pattern
UE_DTX_cycle_1 UE_DTX_cycle_1
UE_DTX_cycle_2 UE_DTX_cycle_2 UE_DTX_cycle_2

CQI transmission
CQI period 2ms
CQI period 4ms
CQI period 8ms

Discontinuous UL & DL Reception: MAC DTX & DL DRX
During E-DCH inactivity, E-DPCCH detection happens at the BTS only every MAC_DTX_Cycle subframes. It is
stopped at Node B after MAC_inactivity_threshold subframes of E-DCH inactivity. As a consequence, the UE
experiences a delay regarding the transmission start time. The UE-specific offset parameter UE_DTX_DRX_Offset
allows to stagger the processing of several UEs in time to save the BTS resources.
Discontinuous UL Reception (MAC DTX):
• N2msMACDTXCycle: length of MAC DTX Cycle in subframes. This is a pattern of time instances where
the start of the UL E-DCH transmission after inactivity is allowed. RNSHPA; Range: 1 (0), 4 (1), 5 (2), 8 (3), 10 (4),
16 (5), 20 (6); default: 8 (3) subframes
• N2msMACInacThr: E-DCH inactivity time in TTIs after which the UE can start E-DCH transmission only at
given times. RNHSPA; Infinity (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256 (9), 512 (10) TTIs;
default: Infinity (0)
Discontinuous DL Reception (DL DRX):
• N2msInacThrUEDRXCycle: number of subframes after an HS-SCCH reception or after the first slot of an
HS-PDSCH reception, during which the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set
continuously. RNHSPA; Range: 0 (0), 1 (1), 2 (2), 4 (3), 8 (4), 16 (5), 32 (6), 64 (7), 128 (8), 256 (9), 512 (10);
default: 64 (7) subframes
• N2msUEDRXCycle: HS-SCCH reception pattern (UE DRX Cycle) length in subframes. This parameter is a
multiple or a divisor of the parameter UE DTX Cycle 1. If the value is not allowed, the parameter value minus
1 is used to calculate a new value, and so on. RNHSPA; Range: 0.5 (0), 1 (1), 2 (2), 3 (3), 4 (4); default: 2 (2)
subframes

Discontinuous UL Reception (MAC-DTX) – Nokia implemented parameters
N2msMACInacThr
RNHSPA; Infinity, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512; Infinity subframes
N2msMACDTXCycle
UE can transmit E-DPDCH data length of MAC DTX Cycle
only at predefined time instances. RNHSPA; Infinity, 1, 4, 5, 8, 10,
16, 20; 8 subframes

Discontinuous DL Reception (DL DRX)
• When the UE DRX is enabled, the UE may turn off the receiver when there is no need to receive anything in DL
• The DL DRX can be enabled only in conjunction with UL DTX
N2msInacThrUEDRXCycle
UE DRX Inactivity threshold
RNHSPA; 0, 1, 2, 4, 8, 16, 32, 64, 128,
256, 512; 64 subframes
DRX
N2msUEDRXCycle
length of UE DRX Cycle
RNHSPA; 0.5, 1, 2, 3, 4; 2 subframes DL DRX
only with UL DTX !
• N2msInacThrUEDRXCycle: number of subframes after an HS-SCCH reception or after the 1st slot of an HS-
PDSCH reception during which the UE is required to monitor the HS-SCCHs in the UE's HS-SCCH set
continuously; UE DRX Inactivity threshold; RNHSPA; 0, 1, 2, 4, 8, 16, 32, 64, 128, 256, 512; 64 subframes
• N2msInacThrUEDRXCycle: HS-SCCH reception pattern (UE DRX Cycle) length in subframes; RNHSPA; 0.5, 1,
2, 3, 4; 2 subframes

Continuous Packet Connectivity – Power Control - Nokia
• New parameter introduced to control step size for DL Inner Loop PC
DLInLoopPCStepSizeCPC
RNSPA: 0.5..2; 0.5; 1.5 dB
DLInLoopPCStepSizeCPC:
• used by the WCDMA BTS to calculate the power increase/decrease step size when receiving TPC
commands. It is applied when CPC (UE DTX, etc.) is activated for the UE.
• if CPC is not used for a UE, BTS applies DownlinkInnerLoopPCStepSize
DownlinkInnerLoop PCStepSize
RNAC: 0.5..2; 0.5; 1 dB

Continuous Packet Connectivity – Inactivity Timer – Nokia
CPC: Extra-inactivity timer for transition from CELL_DCH to CELL_FACH
InactivityTimerUL_DLDCH
RNHSPA; structured parameters
CELL_ Range: 0 .. 20 s; Step: 1 s; default:
DCH
UE Node B RNC • for 8, 16 & 32 kbps: 5 s
• for 64 kbps: 3 s
• for 128, 256, 320 & 384 kbps: 2 s
PDU Transport on the DCH/DPCH
All data sent &

RLC-U buffer empty
Start
Inactivity detected
InactivityTimerULDCH
InactivityTimerDLDCH
Expiry
Radio Bearer Reconfiguration
CELL_
FACH Radio Bearer Reconfiguration Complete InactCPCNoBatOptT: 180 s
InactCPCBatOptT: 0 s
• as soon as L2 in RNC indicated RB inactivity, RNC allocates “extra InactNonCPCNoBatOptT: 0 s
- inactivity timer” to keep the UE in Cell_DCH InactNonCPCBatOptT: 0 s
• This depends on: all parameters: RNHSPA; 0s..48h
• CPC is allocated for a UE or not (CPC or NonCPC) & infinity; several steps;
• UE Device Type – RNC knows from UE capabilities
– UE benefits / does not benefit from Power Consumption
Optimization (BatOpt / NoBatOpt)

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
 Fast Dormancy
 HS-Cell FACH

Interference Cancellation – General Idea
- Subtract first contribution of users with high data rate from RTWP
Then decode users with low data rate
Lower interference level for the latter ones
- Start with total signal arriving at Node B
Perform demodulation, de-spreading and turbo decoding to obtain strongest user(s)
Reconstruct their signals by turbo encoding, spreading and modulation
Subtract reconstructed signal from total one
Perform demodulation, de-spreading and turbo decoding of residual signal to obtain
weaker user(s)
Energy Energy Wanted

Wanted Energy
signal
signal
other cells
Thermal noise
Spread Signal bandwidth bandwidth bandwidth

MAI: Multiple Access Interference
Interference Cancellation - Principles – Nokia
• Users with low level services (usually with 10ms TTI) strongly interfered by users with high level
services (usually with 2ms TTI)
Feature introduced in RU30
• Interference contribution of 2ms TTI users subtracted from total signal arriving at BTS before
demodulating and decoding the signals of 10ms TTI users
• Less power needed by 10ms TTI users due to cancelled interference of 2ms TTI users
• 2ms TTI users less interfered by 10ms TTI users due to lower power
• Optionally interference contribution of individual 2ms TTI users subtracted before demodulating and
decoding other 2ms TTI users
Beneficial features:
• The following features are more efficient, if interference cancellation is applied
• RAN 981 HSUPA 5.8Mbps
• RAN 1645 HSUPA 16QAM
• RAN 1702 Frequency Domain Equalizer (FDE)

HSUPA interference cancellation receiver – Types of
Users – Nokia
• IC users
• Users whose interference contribution is cancelled from the total signal
• Users mapped on E-DCH with 2ms TTI (usually those with highest power)
• Do not get any direct benefit from interference cancellation
• Non-IC users
• Users for which interference is reduced, as the contribution of the non IC users is cancelled from the total
signal
• Remaining users mapped on E-DCH with 2ms TTI (usually such ones with lower power)
• All 10ms TTI E-DCH users
• All DCH users
RTWP
IC Users = interferers to be cancelled
Non IC Users = users for which

interference is reduced
Time

HSUPA interference cancellation receiver – PIC – Nokia
Parallel interference cancellation PIC
• Total UL signal received with rake receiver or frequency domain equalizer
• Turbo decoding to obtain (strongest) 2 ms TTI E-DCH signals
• Decoded data used to reconstruct original 2 ms TTI signals (= interferers for other users)
Reconstruction includes turbo encoding, spreading and modulation
• Cancel interference from (strongest) 2 ms TTI user: Reconstructed signals are summed up and
subtracted from the original total antenna signal  non-IC users’ signal (residual signal)
• Individual non-IC user signals demodulated on the residual signal, benefiting from lower
interference level  improving cell coverage and capacity
Total UL signal
from antenna
Non-IC users
10ms HSUPA,
De-modulate Re-modulate De-modulate
2ms HSUPA
 DCH
2ms HSUPA other
user data
IC users
2ms HSUPA
2ms HSUPA Interference cancelled
user data  Non-IC users signal
(Residual signal)
HSUPA interference cancellation receiver – Benefit –
Nokia
• Part of received total wideband power is cancelled
• RTWP = PNoise + PR99 + P10ms + P2ms
• Residual RTWP = PNoise + PR99 + P10ms + (1-β) * P2ms
• Achievable interference reduction factor β highly dependent on
• Quality of signal that should be cancelled
• Data rate of UE to be cancelled
• Radio channel of the UE (multi-path profile, velocity) RTWP
Residual
PIC HSUPA 2 ms RTWP
• IC users do not benefit directly from the reduced HSUPA 2 ms
interference
HSUPA HSUPA
• Their signals are demodulated in parallel on the original
antenna signal 10 ms 10 ms
R99 users R99 users
Noise Noise

HSUPA interference cancellation receiver - Parameters –
Nokia
Parameter
• Enabling HSUPA 2ms TTI by setting HSUPA2MSTTIEnabled (WCEL) to enabled
• Assignment of desired IC cells to PIC pools
• Activation of PIC
PIC activation
• The PIC state of a cell within a PIC pool can be changed by AdminPICState
• “PIC-deactivated” = IC not activated at all
• “PIC-activated” = IC activated generally
• “PIC-automatic” = IC state controlled by BTS
• Cells with highest traffic shall be selected for IC
• Cell are deselected for IC if traffic has decreased
AdminPICState
WCEL Active / de-active / automatic
Default = de-active

HSUPA interference cancellation receiver – 2RX and
4RX Diversity – Nokia
With 2x diversity
• Up to 6 cells per PIC pool (6x2 antennas)
• Up to 3 of them can perform IC simultaneously (3x2 antennas)
With 4x diversity
• Up to 3 cells per PIC pool (3x4 antennas)
• Only 1 of them can perform IC simultaneously (1x4 antennas)
f1
2 Rx f1 f2 4 Rx
Cells in PIC pool

Cells in PIC pool
Cells performing IC Cells performing IC

HSUPA interference cancellation receiver – New Load
Targets – Nokia
• The total traffic is checked against the following thresholds
• Total RTWP before IC against PrxMaxOrigTargetBTS
• Residual RTWP after IC against PrxMaxTargetBTS
• The R99 RT traffic is checked against
• PrxTargetOrig before IC
• PrxTarget after IC
PrxMaxOrigTargetBTS
RTWP (WCEL) 0..30 dB in steps of 0.1 dB
Default = 8 dB
PrxMaxTargetBTS
(WCEL) 0..30 dB in steps of 0.1 dB
HSUPA 2 ms Default = 6 dB
HSUPA 2 ms PrxTargetOrig (WCEL) PrxTarget (WCEL)
0..30 dB in steps of 0.1 dB & 0..30 dB in steps of 0.1 dB
HSUPA HSUPA
10 ms 10 ms Default = 4 dB Default = 4 dB
R99 users R99 users PrxNoise

Frequency domain equalizer – Motivation
Problem with Rake Receiver:

• With HSUPA very short spreading codes (SF down to 2) introduced
• Very sensitive to inter-symbol interference introduced by time delay
• Maximum data rate of e.g. 5.8 Mbit/s not achieved, saturation at e.g. ≈ 4 Mbit/s even under
very good signal-to-noise-ratio conditions
FDE
• Reduce inter-symbol interference by combination of
• Linear equalization
• Fast convolution
• Obtain peak data rates closer to the limits of
• HSUPA 5.8 Mbit/s (2xSF2 + 2xSF4 with QPSK
• HSUPA 11.5 Mbit/s (2xSF2 + 2xSF4 with 16QAM)

Frequency domain equalizer – FDE – Concept (1/3)
• Frequency domain equalizer FDE is a combination of linear equalization and fast convolution
• Linear equalization → current and the past values of received signal linearly weighted by equalizer
coefficients and summed up to produce output
• Fast convolution → filtering of signal not done in time domain, but after FFT by multiplication in frequency
domain (low pass filter)
• Reduces effects of inter-symbol-interference arising from user’s own signal due to multipath
propagation
• Applied to users with granted 2xSF2 + 2xSF4 (QPSK or 16-QAM)
Time domain
signal FFT Frequency
domain
Despreading
IFFT bits
and detection
MMSE filter
pilot Channel coefficient
estimation calculation
• Frequency domain equalizer is prerequisite for HSUPA 16QAM

Frequency domain equalizer – FDE – Concept (2/3)
noise
h(k)
channel
x(k) y(k)
fading
Handling of distortive
y(k )  x(k )  h(k )  n(k )
channel effects
transmitted noise
signal
Low pass filtering to minimize

the negative effects of inter- r (k )  y(k )  e(k )  x(k )  h(k )  e(k )  n(k ) * e(k )
symbol interference
Low pass Noise filtered

filter by low pass
Frequency domain equalizer – FDE Concept (3/3)
• Fourier transformation
• Convolution in time domain = Multiplication in frequency domain
• Reduction of computational complexity
zero
x(k) FFT X(n)
padding
Element wise
multiplication
Y(n) IFFT y(k)
zero H(n)
h(k) FFT
padding
After filtering
Before filtering x(k) h(k) High frequencies removed by low pass

Frequency domain equalizer – E-DPCCH Boosted Mode
Nokia
• Frequency domain equalizer requires reliable decoding of E-DPCCH with 16QAM in UL
• In case of 2xSF2 + 2xSF4 E-DPCCH very strongly interfered by E-DPDCH
• Boosted mode
• Power of E-DPCCH not related to power of DPCCH
• But related to power of E-DPDCH
Non-boosted Mode Boosted Mode
E-DPCCH power goes parallel to DPCCH power E-DPCCH power proportional to E-DPDCH power
E-DPDCH
E-DPDCH
E-DPDCH
E-DPDCH E-DPCCH
E-DPCCH E-DPCCH E-DPCCH
DPCCH DPCCH DPCCH DPCCH
low E-TFC high E-TFC low E-TFC high E-TFC

Frequency domain equalizer – E-DPCCH Boosted Mode
Nokia
• Starting at a particular E-TFCI 95, the FDE is enabled
• Reaching the next switching point 104, the E-DPCCH is given a fixed relation to E-DPDCH instead of DPCCH
(boosted mode) and 16QAM modulation is used
2xN2+2xN4
+ 16QAM
Code and Modulation Combination
E-TFCI 103 According to 2ms E-DCH

Transport Block Size Table 2
TS 25.321 (only supported
table in Nokia)
2xN2+2xN4
E-TFCI 84
2xN2
Switch to
2xN4
boosted mode
N4
N8, N16, N32
0 2000 4000 6000 8000 10000 12000
RLC bitrate [kbps]

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
 Fast Dormancy
 HS-Cell FACH

Fast Dormancy – Nokia

Fast Dormancy & Fast Dormancy Profiling – Nokia
Fast Dormancy (FD) – RAN2136, RU30
Basic FD feature driving smartphones to stay in Cell_FACH and Cell_PCH through

preventing of going to Idle
FastDormancyEnabled
RNFC; 0 (Disabled), 1 (Enabled)
Fast Dormancy Profiling (FDP) – RAN2451, RU40
Provides identification of UEs causing unnecessary signaling load.
With this feature RNC recognizes UE which sent empty SCRI as LegacyFDPhone and
stores IMSI number.
New shorter idle timer is used to avoid signaling connection release for this UE.
The target is to move this UE to Cell_PCH before it initiates the connection release.
The threshold for moving to Cell_DCH state can be increased (e.g., to 256 bytes) to
ensure that small keep-alive messages from identified UEs are served in Cell_FACH state.

Fast Dormancy FD - Functionality 1/2
• UE sends signaling connection release indication with cause UE requested PS data
session end (fast dormancy request)
• the UE is not shifted to idle mode, but to Cell_PCH
• To prevent too many such requests a new timer is introduced:
• T323 is minimum time between last user data transmission and request or
between consecutive requests (broadcast in SIB1)
SIB1 with T323

RNC 0,5,10,20,30,60,90,120 s, Default 0 s
Last user data or signaling

T323 connection release indication
UE
signaling connection RNC
release indication
With timer T323 in system information message the network informs the UE that the rel.8 Fast Dormancy feature is supported in the
RNC. The UE is inhibited from sending the SIGNALLING CONNECTION RELEASE INDICATION message whilst timer T323 is running.
The use of 0 s indicates no need to apply the inhibit timer.

Fast Dormancy FD – Functionality 2/2
• RNC reacts due to a fast dormancy request depending on the current RAB:
• if the UE had an single or multiple PS RAB + CS RAB
• PS resources are released and UE stays in cell_DCH

• if the UE had an single or multiple PS RAB
• PS resources are released and UE goes to cell_PCH or URA_PCH

• if the UE had a CS RAB
• Fast Dormancy not supported
SCRI with cause …
Check RANAP messages if RAB

Go to Cell_PCH/URA_PCH released by CN?
Iu
X
Prevent going to Idle mode
Counters with this feature:
• M1006C243 SIG CONN REL IND DUE PS SESSION END

EFD – Fast Dormancy Profiling (1/2)
RNC checks if the

SIB1: T323 FDP license is ON
SCRI without any cause R

N
If the FDP license is ON  Physical Channel rec. To Cell_PCH
C
UE
• Fast Dormancy Profiling Nokia feature Identifies LFD (Legacy Fast Dormancy) phones which
cause unnecessary signaling load
• The UE is detected as LFD phone when network receives an SCRI message without any cause
• Based on regular FD functionality, such phones would be moved to Idle mode, hence causing
unnecessary signalling when starting following activity
• Less signaling load because LFD (Legacy Fast Dormancy) Phones are being forced
to stay in Cell_PCH

EFD – Fast Dormancy Profiling (2/2)
Shorter Inactivity Timers for LFD Phone and Smartphones:
• Shorter inactivity timers are used for moving smartphones and LFD Phones to Cell_PCH state -
saving UE battery
• It gives possibility to avoid unnecessary movement to IDLE_mode  less signaling load

Higher Traffic Volume Thresholds for LFD Phone and Smartphones:
• Higher traffic volume thresholds are used for moving smartphones and LFD Phones to
Cell_DCH state
• It gives possibility to avoid unnecessary movement to Cell_DCH avoids blocking of dedicated

resources only for sending keep-alive message
• Stored IMSI in RNC gives possibility to faster usage of higher traffic volume thresholds

Fast Dormancy – Huawei

Enhanced Fast Dormancy (EFD)
Smartphones with background applications (like e-

mail) periodically change mode from idle to
connected to refresh application status.
After these short operations are completed the UE is
transited back to idle mode.
This saves UEs battery but generates a lot of
signalling traffic.
EFD reduces RNC signalling load, NodeB signalling

load, and NodeB CE resource consumption caused
by intelligent UEs.
EFD prevents against signalling storms while setting
up PS services (switch to the CELL_DCH state) for
multiple UEs.

PS data UE sends a Signaling RNC switches the UE’s

transmission is Connection Release Indication state to reduce battery
complete (SCRI) message to the RNC consumption
Details about the SCRI message are
described in 3GPP TS 25.331 V10.7.0
Transition to idle mode Transition to the CELL_FACH or

Intelligent UEs that can use EFD are (by default) CELL_PCH/URA_PCH state
called fast dormancy UEs (EFD feature)
release the signaling
Other UEs are called non-fast connection maintain the signaling connection
dormancy UEs
UEs are recognized based on Type
Allocation Code (TAC) read from the
first 8 digits of IMEI
Details about the structure of IMEI are
described in 3GPP TS 23.003 V8.15.0

EFD feature activation:

Add a second S-CCPCH (Mandatory)
Activate the EFD feature (Mandatory)
enable the EFD function switch – select the FAST_DORMANCY_SWITCH check box
under the Process switch parameter
enable the state transition switch for PS services


If the Enhanced Fast Dormancy (EFD) feature is disabled (SCRI message switches the UE to
idle mode)
• Activity as sending heartbeat messages by the UE starts the procedures for RRC connection setups,
authentication, encryption, and RAB setups.
• The RNC processing and signaling load increases.
If the EFD feature is enabled (SCRI message switches the UE to the CELL_FACH or
CELL_PCH/URA_PCH state)
• The signaling procedure between the UE and RNC is simplified for heartbeat messages.
• RRC connection is maintained.
• RNC CPU resources can be saved.
• UE consumes less battery power.

Enhanced Fast Dormancy (EFD) – Impact and
Recommendations
Observed EFD impact on network performance
Reduced RRC connection setup success rate due to decreased RRC connection setup attempts -
the number of RRC connection setup failures does not increase
Reduced PS RAB setup success rate due to decreased number of PS RAB setup attempts
Reduced paging success rate due to decreased number of paging attempts in idle mode
Longer FACH congestion duration due to increased number of UEs in the CELL_FACH state and
increased traffic volume on FACH
Increased PS call drop rate due to increased duration of PS services
Network planning recommendations

Load balancing among all frequencies in the network when using this feature.
FACH congestion optimization and combined services optimization used.
For a service-layered network set in the SET USTATETIMER command
Wait RB reconfiguration response timer = 11000
RL restoration timer = 15000
to reduce the number of call drops for fast dormancy UEs in the CELL_FACH or
CELL_PCH state.

State Transitions for Fast Dormancy UEs
4A
4B
CELL_DCH PS Inact Time out CELL_FACH
SCRI
PS Inact Time out
FACH Congestion
PS Inact Time out

PS Data
SCRI
SCRI
4B
FACH
Congestion
CELL_PCH / URA_PCH
PS Inact
Time out
IDLE

EFD – State Transition Parameters
RNC_EFD_D2F_SWITCH
under the OptimizationSwitch
parameter in the
SET URRCTRLSWITCH
command is turned on
CELL_DCH or CELL_FACH
FD_TAC_FORCE_D2F_SWITCH
under the PROCESSSWITCH
parameter in the
ADD UIMEITAC
command is turned on
RNC_EFD_D2F_SWITCH
under the OptimizationSwitch
parameter in the
SET URRCTRLSWITCH
command is turned off
CELL_PCH /
CELL_DCH or
FD_TAC_FORCE_D2F_SWITCH URA_PCH
parameter in the
ADD UIMEITAC
command is turned off

RNC_DF_2_URA_PCH_SWITCH
parameter in the
CELL_PCH /
CELL_FACH SET URRCTRLSWITCH command
controls whether the UE is switched to URA_PCH
the CELL_PCH (turned off) or
URA_PCH (turned on) state
RNC_FD_SCRI_FORCE_REL_SWITCH
under the PROCESSSWITCH2
CELL_DCH / parameter in the IDLE
CELL_FACH SET URRCTRLSWITCH command
is turned on
FD_P2D_SWITCH
CELL_PCH / parameter in the
ADD UIMEITAC command CELL_DCH
URA_PCH
is turned on
(UE's TAC = TAC added to the EFD list)

UE sends messages whose traffic

CELL_FACH volume is higher than CELL_DCH
FastDormancyF2DHTvmThd (event 4a)
FastDormancyF2DHTvmThd Threshold set to a value greater than the traffic volume of most heartbeat
messages to prevent state transitions from being triggered by small-sized
heartbeat messages, recommended value: 512 bytes
Range: {16, 32, 64, 128, 256, 512, 1024, 2k, 3k, 4k, 6k, 8k, 12k, 16k, 24k, 32k, 48k, 64k,
96k, 128k, 192k, 256k, 384k, 512k, 768k}, Unit: byte, Default Value: 1024
PS inactivity timers:
PsInactTmrForFstDrmDch(1) for CELL_DCH, recommended value: 2s
PsInactTmrForFstDrmFach(2) for CELL_FACH, recommended value: 5s
PsInactTmrForPreFstDrm(3) for CELL_PCH/URA_PCH, recommended value: 1800s
Range: 0~64800, Unit: sec, Default Value: 4(1), 5(2), 1800(3)

Fast Dormancy – Ericsson

Fast Dormancy Handling
• This feature is used to control whether the UE is switched to URA instead of Idle during fast
dormancy signaling.
• Subsequent data can then be handled by an upswitch to FACH when the amount of data is lower,
and to HSPA when the amount is higher.
• As an overall result, the signaling load is improved for chatty applications with fast dormancy that
otherwise are typically switched between HSPA and Idle Mode.
fastDormancyMethod (per RNC)

RELEASE = 0 SWITCH_TO_URA = 1; RELEASE
t323 (per RNC)

0..0 5..5 10..10 20..20 30..30 60..60 90..90 120..120
s; 5 s

Fast Dormancy Handling
fastDormancyMethod (per RNC) t323 (per RNC)
RELEASE = 0 SWITCH_TO_URA = 1; RELEASE 0..0 5..5 10..10 20..20 30..30 60..60 90..90 120..120
s; 5 s
fastDormancyMethod
• MO: RncFunction
• Description: Indicates if there will be an attempted direct downswitch to URA_PCH after reception of an
RRC:Signalling Connection Release Indication message when the IE Signalling Connection Release Indication
Cause is missing. If the parameter value = SWITCH_TO_URA a downswitch attempt to URA_PCH shall be
performed when the IE Signalling Connection Release Indication Cause is not included in RRC:Signalling
Connection Release Indication message If the parameter value = RELEASE the connection shall be released
when the IE Signalling Connection Release Indication Cause is not included in the RRC:Signalling Connection
Release Indication message. When the IE Signalling Connection Release Indication Cause is included in
RRC:Signalling Connection Release Indication message the parameter has no effect.
t323
• MO: RRC
• Description: UE timer that serves two purposes:
- The network uses it to indicate that the Fast Dormancy Handling feature is supported.
- The UE uses it to limit the frequency ar which the UE sends Signalling Connection Release Indication messages.
The timer is started in the UE when transmitting a SIGNALLING CONNECTION RELEASE INDICATION message
that includes the IE Signalling Connection Release Indication Cause. When T323 expires, the UE may determine
whether there have been any subsequent indications from upper layers that there is no more PS data for a
prolonged period, in which case it triggers the transmission of a single SIGNALLING CONNECTION RELEASE
INDICATION message. The use of 0 seconds indicates no need to apply the timer.

Device Optimized Fast Dormancy
• This feature makes it possible to reconfigure the release 8 or higher User Equipment (UE) from
CELL_DCH to CELL_FACH based on the International Mobile Equipment Identity and Software
Version Number (IMEISV) at reception of Signalling Connection Release Indication with cause
value UE requested PS data session end.
• This feature makes it possible to switch selected UE from CELL_DCH to CELL_FACH instead of
URA_PCH for avoiding crashing selected UE.
• This feature introduces no new parameters
• The event parameter EVENT_PARAM_CHANNEL_SWITCH_REASON_EXT of the General

Performance Event Handling (GPEH) event INTERNAL_CHANNEL_SWITCHING is updated in
the RNC to observe the behavior of the Device Optimized Fast Dormancy feature.

Fast Dormancy for Pre-Rel-8 UEs
General info:
• This feature enables the reconfiguration, based on IMEISV, of certain pre-rel-8 UE units that
transmit a SIGNALING CONNECTION RELEASE INDICATION to URA_PCH.
• This feature enables selected pre-rel-8 UE units to use Fast Dormancy with all its benefits
Functionality:
• This feature makes it possible to reconfigure a certain subset of pre-release 8 User Equipment (UE)
to URA_PCH based on International Mobile Equipment Identity and Software Version Number
(IMEISV) at reception of Signaling Connection Release Indication message without Information
Element (IE) Signaling Connection Release Indication Cause from UE.
• Note: The optional IE value Signaling Connection Release Indication Cause is introduced in
3GPP Release 8, so the feature also applies to a certain subset of release 8 or higher
compatible UE that sends message without the IE.
The feature Fast Dormancy for pre-rel-8 UEs overrides the parameter fastDormancyMethod for certain
UE when IMEISV of the UE matches the TAC/SVN configured for the Fast Dormancy for pre-rel-8 UEs
feature.
The event parameter EVENT_PARAM_CHANNEL_SWITCH_REASON_EXT of the General

Performance Event Handling (GPEH) event INTERNAL_CHANNEL_SWITCHING is updated in the
RNC to observe the behavior of the Fast Dormancy for per-rel-8 UEs feature.

Content
HSPA+
HSUPA 16QAM
DC-HSUPA
 Fast Dormancy
 HS-Cell FACH

HS-Cell FACH – Principles
Without the feature:
HSPA is offered only on dedicated channels in DCH state
• more users can be supported in HS Cell FACH state and smooth

data transmission can be provided for users not requiring large
data volumes.
• Services for sending frequent but small packets can be handled
more efficiently.
• Fast Cell_PCH to Cell_FACH switch
• Reduced signalling load
With the features: UE <-> BTS
BTS <-> RNC
• Code tree occupation reduction
• BTS baseband resources saving
• High number of smartphones can be supported
• Higher throughputs possible on common channels
• Up to 1.80 Mbps in DL
• Up to 1.45 Mbps in UL
HSPA also possible on common channels
RACH/FACH is also further possible

HS-Cell FACH – Principles - UEs
• 3GPP Rel8 UEs required

• Only UE categories that supports continuous HS-DSCH data reception are able to support HS
Cell_FACH feature
• UEs 1-4 and 11 Categories are not HS Cell_FACH capable

• UEs 5-10,12 and higher Categories are HS Cell_FACH capable
UE Rel8
UE Rel7
In DL - HS-DSCH In DL - HS-DSCH
In UL - RACH IN UL - E-DCH

HS Cell_FACH only on DL – Channels Mapping
• Low UL performance because RACH is used
• No ACK/NACK and CQI sending
• Blind repetition for HARQ
• A default or an estimated CQI value for link adaptation used
• Mobility based on cell reselection as usual in Cell_FACH (Cell Reselection)
Channel Maping:
BCCH CCCH DCCH DTCH PCCH
Logical channels
BCH FACH FACH FACH HS-DSCH FACH PCH Transport channels
3GPP Rel7
Physical channels
P-CCPCH S-CCPCH HS-PDSCH S-CCPCH S-CCPCH
• With the Downlink Enhanced CELL_FACH data carried on the BCCH, CCCH, DCCH, and DTCH is mapped to the
transport channel HS-DSCH, and then transmitted over the air interface to UEs through the HS-PDSCH or HS-
SCCH. In this way, UEs in the CELL_FACH state can use the HS-PDSCH and HS-SCCH's code and power
resources as HSDPA UEs in the CELL_DCH state, thereby accelerating downlink data transmission.

HS Cell_FACH only on DL – Huawei Parameters
• Enable the feature by running the MML command MOD UCELLALGOSWITCH and select the E_FACH check box
under the HspaPlusSwitch parameter.
MAXEFACHHARQRT EFachSwitch
0~10; 2 OFF~0, ON~1; ON
MAXEFACHHARQRT
• MO = ULOCELLMACHSPARA
• Description: EFACH HARQ Retransmission Times. It indicates the maximum number of blind HARQ
retransmissions for E-FACH users. When this parameter is set to a small value, HARQ retransmissions cannot
ensure reliable data transmission for E-FACH users. In this case, RLC layer retransmissions are required, which
lowers the user throughput. When this parameter is set to a large value, a fixed number of HARQ
retransmissions ensure reliable data transmission for E-FACH users. In this case, a large amount of cell
resources is consumed, and the cell throughput is low.
EFachSwitch
• MO = URRCESTCAUSE
• Description: Switch for RRC established on E-FACH. When this switch is turned off, the RRC connection cannot
be established on the E-FACH or FACH. When this parameter is set to ON, services are established on the E-
FACH rather than the FACH, which shortens the establishment delay. When this parameter is set to OFF,
services are established on the DCH, improving the service setup success rate.

HS Cell_FACH only on DL – Huawei TFRC Selection
TFRC Selection
In each TTI, the Transport Format and Resource Combination (TFRC) entity on the NodeB selects user queues and
performs the following based on the scheduling results:
• Determines the queues' modulation scheme based on the amount of data to be transmitted in the queues, the UE
category, and the CQI.
• Allocates appropriate power and code resources to the queues.
The NodeB needs to obtain CQI before performing TFRC selection. If E-FACH UEs do not report CQI on the HS-
DPCCH, the NodeB converts Ec/N0 into CQI. E-FACH UEs can choose to include Ec/N0 in the "measured results on
RACH" IE in the following messages:
• CELL UPDATE
• MEASUREMENT REPORT
• RRC CONNECTION REQUEST
• INITIAL DIRECT TRANSFER
• UPLINK DIRECT TRANSFER
Link Adaptation (link quality estimation):

• For the E-FACH UEs' signaling data, the RNC uses the value of the MinEcN0Value parameter as the Ec/N0 and
sends this Ec/N0 to the NodeB.
• For the E-FACH UEs' service data, the RNC dynamically adjusts the Ec/N0 based on the Radio Link Control (RLC)
retransmission rate.

Huawei TFRC Selection – Parameters
The RNC uses the latest Ec/N0 reported by the UE as the initial value and calculates the Ec/N0 using the following formula:
ΔEc/N0=EcN0AdjStep* & Ec/N0new=Ec/N0old+ΔEc/N0
When the measured RLC retransmission rate is greater than the target value for the RLC retransmission rate, the RNC reduces the
Ec/N0. Otherwise, the RNC increases the Ec/N0.
TagetRlcRetrans MinEcN0Value MaxEcN0Value EcN0AdjStep

1~1000 per mill, 10 -24.5~0; -14 dB -24.5~0; 0 dB -0~5 dB; 0.5 dB
MinEcN0Value MO = URACHMEASUREPARA
• Description: This parameter specifies the minimum value of Ec/No in the E-FACH Ec/No adjustment algorithm. If this
parameter is set to a large value, upward power control is disabled when the signal becomes poor. As a result, the
block error rate (BLER) of data services decreases.
MaxEcN0Value MO = URACHMEASUREPARA
• Description: This parameter specifies the maximum value of Ec/No in the E-FACH Ec/No adjustment algorithm.
EcN0AdjStep MO = URACHMEASUREPARA
• Description: Ec/N0 Adjustment Step. Adjusted step of Ec/No in the link quality adjust algorithm for the E-FACH. The
larger the value of this parameter, the larger the adjusted step of Ec/N0 in the link quality adjustment algorithm for the
E-FACH and the more significantly the downlink transmit power of the E-FACH fluctuates. This affects the air
interface capacity. The smaller the value of this parameter, the slower the adjustment in the step of Ec/N0. As a
result, consecutive error blocks occur and user experience deteriorates.

HS Cell_FACH only on DL – Ericsson Parameters (1/2)
• hsFachEnabled: enables or disables the HS-FACH feature on RNC level.
featureStateHsFach (on cell) featureStateHsFach MO: RbsLocalCell

ACTIVATED, DEACTIVATED • Description: Radio Node Feature state for licensed feature 'HS-FACH'
(High Speed Downlink for FACH), indicating if the feature is ACTIVATED or
DEACTIVATED for this cell.
Link Adaptation (link quality estimation)

• HS-FACH user in CELL_FACH state does not send any CQI reports and any ACK/NACK, CQI directly adjustment
cannot be used.
• Instead the DL channel quality is given by the CPICH Ec/No reported by the UE in the IE Measured Results on
RACH.
• The CPICH Ec/No is stored and if there is an RLC retransmission, this value is reduced to adapt this value to the
DL channel quality.
• The maximum allowed compensation (reduction) of the latest reported CPICH Ec/No is specified by the parameter
rachMeasCompLimitHsFach.
• the compensated CPICH Ec/No value is transformed to a CQI, that is the converted CQI.
rachMeasCompLimitHsFach MO: PowerControl

rachMeasCompLimitHsFach
• Description: Total amount of compensation for the RACH Measurement
0..20 dB, 2 dB
Result during the CELL_FACH state, for HS-FACH.

HS Cell_FACH only on DL – Ericsson Parameters (2/2)
Link Adaptation (link quality estimation) (continued)
• The converted CQI does not give as accurate and frequent information on the DL channel quality as the CQI does.
• There are also no HARQ retransmissions since there is no HARQ acknowledgement information in CELL_FACH
state.
So, additional compensation of the converted CQI is done in the Transport Format and Resource Combination (TFRC)
selection algorithm and additional power is applied to the HS-SCCH. For BCCH data transmission, the CQI is set by
the parameter defaultCqiHsFach.
The converted CQI is compensated when used for TFRC selection as follows:
• For user data transmissions: By subtracting the parameter extraCompHsFach.
• For signalling data transmissions: By subtracting the parameters extraCompHsFach and
extraCompForSigHsFach to provide more robustness than in the previous case.
defaultCqiHsFach extraCompHsFach extraCompForSigHsFach

1..30; 1 0..20 dB, 10 dB 0..10 dB, 1 dB

HS Cell_FACH only on DL – Nokia (1/3)
To enable HS Cell_FACH on the DL, this settings are required: FRLCEnabled (RNFC) = enabled &
HSFACHEnabled (WCEL) = enabled.
• For user data and higher layer signaling same power management as in Cell_DCH
• Slow power adjustment for HS-PDSCH due to dynamic share with R99
• Fast CQI based power control for HS-SCCH
If BCCH information shall be transmitted via HS-DSCH, the power for both HS-PDSCH and HS-SCCH is fixed
relative to CPICH
• Parameter PtxBCCHHSPDSCH for HS-PDSCH
• Parameter PtxBCCHHSSCCH for HS-SCCH
PtxBCCHHSPDSCH PtxBCCHHSSCCH
-35..15 dB, step 0.1 dB; 7 dB -35..15 dB, step 0.1 dB; 2
above CPICH dB below CPICH
• It can be can selected by the 22 bit parameter HSFACHRel7ConSetupEC for which RRC establishment cause
HS Cell_FACH or HS Cell_DCH is preferred
HSFACHRel7ConSetupEC
0 or 1 for each RRC EC;
0001101111110110001100

Link Adaptation:
• Based on a default CQI value for HS Cell_FACH state
The default value is a special value, this means that BTS uses Nokia recommended default value of current SW
release. In SW upgrade the new default value is taken into use without the need for recommissioning.
If the value is set to 0...35 the commissioned value persists over SW upgrades.
cqiDefaultHsCellFach
0...35, step 1, default 255 = BTS uses Nokia
recommended default value of current SW release
• Based on the Number Of Blind Repetition Hs Cell_Fach state:

Default value is same than special value, this means that BTS uses Nokia recommended default value of current SW
release. In SW upgrade the new default value is taken into use without the need for recommissioning.
If the value is set to 1...4 the commissioned value persists over SW upgrades.
numberOfBlindRepetitionHsCellFach
1...4, step 1, default 255 = BTS uses Nokia
recommended default value of current SW release

Transition from Cell_FACH to Cell_DCH triggered by high activity of the connection
• Higher amount of data in RLC buffer or a high average data rate
If the amount of data in the buffer is higher then HSFACHVolThrDL at least during the time
HSFACHTimeTrigger then the transition from HS-Cell FACH to Cell- DCH is triggered
HSFACHVolThrDL (on WCEL) HSFACHTimeTrigger (RNPS)

0,8,16,32..2048 Byte; 512 Bytes 0..5000 ms; 0 ms
If the average data rate is higher as HSFACHActivityThr at least during the time
HSFACHActTimeToTrigger then the transition from HS-Cell FACH to Cell- DCH is triggered.
• The data rate is averaged on basis of a sliding window configured by HSFACHActivityAveWin and
updated with each packet sent to the UE.
HSFACHActivityThr (on WCEL) HSFACHActTimeToTrigger (on WCEL)

8..1024 Kbps, step 8 Kbps; 128 Kbps 0..5000; 0 ms
HSFACHActivityAveWin (on WCEL)

0.2..5 s in step 0.2 s: 0.2 s

HS Cell_FACH in UL (&DL) – Channels Mapping
CCCH DCCH DTCH
Logical channels
RACH E-DCH Transport channels
3GPP Rel8
Physical channels
PRACH E-DPDCH
• This feature enables UEs in the CELL_FACH state to transmit uplink data on common
E-DCHs.
• An enhancement to Uplink Enhanced CELL_FACH in allows E-RACH UEs to send
ACK/NACK responses and channel quality indicator (CQI) information to the NodeB
over the HS-DPCCH.
• multiple common E-DCH resources can be configured in a cell to serve more UEs in
the CELL_FACH state.
• The configuration information about each common E-DCH resource is broadcast in
SIB5. UE Rel8
• The configuration information includes the number of common E-DCH resources,
In DL - HS-DSCH
Guaranteed Bit Rate (GBR) and Maximum Bit Rate (MBR) of E-RACH UEs, and TTI for
IN UL - E-DCH
the common E-DCH in a cell.

HS Cell_FACH in UL (&DL) – Huawei (1/3)
ERACHHSDPCCH- MAXEFACHHSHARQRT ERACHCQIFdbkCycle
FALSE~0, TRUE~1 0~10; 4 0, 2, 4, 8, 10, 20, 40, 80, 160, 16, 32, 64; 8 ms
ERACHHSDPCCH
• MO = ULOCELL
• Description: Indicates whether to enable E-RACH over HS-DPCCH. If this parameter is set to TRUE, the NodeB
supports feedbacks over HS-DPCCH on the E-RACH, improving the transmission efficiency on the E-FACH over
the air interface. If this parameter is set to FALSE, the NodeB does not support feedbacks over HS-DPCCH on the
E-RACH.
MAXEFACHHSHARQRT
• MO = ULOCELLMACHSPARA
• Description: Indicates the maximum number of HARQ retransmissions when the UE in CELL_FACH supports
the feedbacks over the HS-DPCCH. When this parameter is set to a small value, HARQ retransmission cannot
ensure reliable data transmission for UEs in the CELL_FACH state, and therefore, RLC layer retransmission is
required. This reduces the UE throughput.When this parameter is set to a large value, HARQ retransmission
ensures reliable data transmission for UEs in the CELL_FACH state and expands E-FACH coverage. However,
UEs experiencing poor channel quality consume more cell resources.
ERACHCQIFdbkCycle
• MO = UCELLERACHHSDPCCH
• Description: Specifies the channel quality indicator (CQI) feedback cycle for a UE. A smaller parameter value
indicates more timely E-FACH CQI feedbacks from the UE. However, setting the parameter to a too small value
will increase the control channel overhead and therefore affect the uplink capacity. A larger parameter value
indicates less timely E-FACH CQI feedbacks from the UE. This affects the downlink E-FACH throughput.

CommonEdchResourceNum ERACHGBR
0~32; 8 8, 16, 32, 64, 128, 144, 256, 384, 608,
1280, 2048, 2720, 5440; 32 kbps
CommonEdchResourceNum
• MO = UERACHBASIC
• Description: Number of common E-DCH resources of a cell. Both the common E-DCH resources and dedicated
E-DCH resources consume code number and signatures for E-RGCHs and E-HICHs. The smaller the value of
this parameter, the higher the probability of preamble access contention between ERACH UEs and the lower the
access success rate. The larger the value of this parameter, the smaller the number of online HSUPA UEs
supported by a cell. If this parameter is set to 0, the ERACH function will be unavailabale.
ERACHGBR
• Description: GBR available when ERACH UEs occupy common E-DCH resources. The smaller the value of this
parameter, the lower the uplink rate for ERACH UEs. The larger the value of this parameter, the stronger the
uplink interference caused by ERACH Ues.

CommonEdchTTISelect ERACHGBR
TTI_2MS, TTI_10MS; TTI_10MS 8, 16, 32, 64, 128, 144, 256, 384, 608,
1280, 2048, 2720, 5440; 32 kbps
CommonEdchTTISelect
• Description: Transmission Time Interval (TTI) for the common E-DCH. If the TTI is set to 2 ms, the downlink
coverage for ERACHs shrinks. If the TTT is set to 10 ms, the peak rate for ERACH UEs cannot exceed 500 kbit/s
ERACHGBR
• Description:GBR available when ERACH UEs occupy common E-DCH resources. The smaller the value of this
parameter, the lower the uplink rate for ERACH UEs. The larger the value of this parameter, the stronger the
uplink interference caused by ERACH UEs.

HS Cell_FACH in UL (&DL) – Ericsson (1/2)
The High Speed Downlink for FACH feature enables the activation of the Enhanced Uplink for
FACH feature if the Enhanced Uplink for FACH feature is supported by the cell and the UE.
The number of preamble signatures to be used for EUL-FACH in a cell is defined by the parameter
numPreambleSignatures.
numPreambleSignatures eulFachInitialRate maxCollisionResTime
1..15; 4 0..1376; 34 kbps 8..24; 8 ms
numPreambleSignatures MO: EulFach

• Description: Number of signatures to be used for EUL-FACH in the cell. The rightmost of the available signatures,
defined by Rach::preambleSignatures, will be allocated to EUL-FACH.
If the cell is EUL-FACH capable, but not Extended Acquisition Indicator capable (when eAiCapable is FALSE),
numPreambleSignatures is also used to set the number of C-EDCH resources used for EUL-FACH in the cell.
Changing this attribute affects the number of available signatures for PRACH. There will always be at least one
signature assigned to PRACH.
eulFachInitialRate MO: NodeBFunction
• Description: Initial granted rate to EUL FACH users.
maxCollisionResTime MO: EulFach

• Description: For EUL-FACH users, maximum TTI (Transmission Time Interval) that a user can transmit E-DPDCH
without receiving an absolute grant for resolving collision resolution phase.

HS Cell_FACH in UL (&DL) – Ericsson (2/2)
ulRlcBufUpswitchEulFach initInterferenceUl cEdchResourcesEai
8..131072; 1024 bytes -110 … -70 dBm. step 0.1 dB; 0 1..32; 8
initInterferenceUl MO: EulFach

• Description: Uplink interference to be used by EUL-FACH users for initial power settings in preamble ramping. The
uplink interference value broadcast in SIB5. If set to 0, no value is included in SIB5 for the uplink interference.
cEdchResourcesEai MO: EulFach

• Description: Number of C-EDCH resources used for EUL-FACH in the cell, if the cell is Extended Acquisition
Indicator capable as indicated by attribute eAiCapable. If the value of eAiCapable is FALSE,
numPreambleSignatures is used to set the number of C-EDCH resources instead
ulRlcBufUpswitchEulFach MO: ChannelSwitching

• Description: Uplink RLC buffer threshold for upswitching from CELL_FACH to CELL_DCH for EUL-FACH users.
When the RLC buffer load in the uplink exceeds this threshold, a measurement report is sent from the UE. An
upswitch request is issued upon reception of the measurement report. Also, uplink RLC buffer threshold for
upswitching from URA_PCH to dedicated channel when EUL FACH is in use. (SIB12)
maxCcchTime initInterferenceUl MO: EulFach

8 12,16,20, 24, 32, • Description: Maximum TTI (Transmission Time Interval) during which a user is allowed
40, 80; 12 ms to transmit E-DPCCH for CCCH transmissions.

HS Cell_FACH in UL (&DL) – Nokia (1/3)
HSRACHEnabled (on cell level) HSRACHMaxTotSymbolRate
Disabled (0), Enabled (1); Disabled (0) SF32 (1) …2*SF4 (5); SF4 (4) ( 672 kbps with 10 ms TTI)
HSRACHMaxTotSymbolRate MO: WCEL Category: Basic parameter

• Description: This parameter determines the planned maximum total uplink symbol rate of the HS-RACH (maximum
total symbol rate of the E-DPDCH(s) in CELL_FACH state) of the UE in the cell. The information is signaled to the
UE using the RRC SIB5/5bis.
HSRACHMaxAllocTimeCCCH HSRACHMaxPeriodCollis
8 (0) … 80 (7); 8 TTIs 8 (0), 12 (1), 16 (2), 24 (3); 12 TTIs
HSRACHMaxAllocTimeCCCH MO: WCEL Category: Advanced parameter

• Description: This parameter determines the maximum E-DCH resource allocation for CCCH. The time has been
defined as the terms of TTIs. (SIB5). 8 TTIs equals to reservation time of 80 ms with E-TTI=10ms.
HSRACHMaxPeriodCollis MO: WCEL Category: Advanced parameter

• Description: This parameter determines the maximum period for collision resolution phase. The time has been
defined as the terms of TTIs. (SIB5) 12 TTIs equals to reservation time of 120 ms with E-TTI=10ms.

HSRACHCommonEDCHRes HSRACHActivityAveWin HSRACHActivityThr
1...32, 3 0.2...5 s; 0.2 s 8000...1400000 bps; 256000 bps
HSRACHCommonEDCHRes MO: WCEL Category: Advanced parameter

• Description: This parameter defines the number of Common E-DCH Resources of the HS-RACH configuration in the
cell. Common E-DCH resource(s) is(are) setup in the cell when the HS-RACH is setup in the cell. Common E-DCH
resources configured during HS-RACH setup are under direct control of the Node B and are shared by UEs in
CELL_FACH and IDLE mode.
HSRACHActivityAveWin MO: WCEL Category: Basic parameter

• Description: This parameter defines the size of the sliding averaging window for the activity measurement of the E-
DCH MAC-d flow of PS RB when the UE is on CELL_FACH state using HS-RACH.
HSRACHActivityThr MO: WCEL Category: Basic parameter

• Description: This parameter defines the activity threshold for the activity measurement of the E-DCH MAC-d flow of
PS RB on CELL_FACH state using HS-RACH. The threshold is defined as the number of bits per second. The
activity measurement measures the number of bits transmitted by the E-DCH MAC-d flow during the sliding
measurement window.
HSRACHActivityThr MO: WCEL Category: Basic parameter

HSRACHVolThrU • Description:This parameter defines, in bytes, the threshold of data in the RLC
0 bytes…16 kbytes; 1 Kbyte buffers of SRB0, SRB1, SRB2, SRB3, SRB4 and all NRT RBs that trigger the
uplink traffic volume measurement report, when the UE is in Cell_FACH state
and using HS-RACH. Otherwise, the UE sends data on HS-RACH.

PrxTargetPSMaxtHSRACH PtxTargetPSMaxtHSRACH
0...30 dB, step 0.1; 0...40 dBm; 32767 (Value set by the PtxTargetPSMax parameter is used)
PrxTargetPSMaxtHSRACH MO: WCEL Category: Advanced parameter

• Description: Max PS target interference level with HS-RACH. This parameter defines the maximum allowed target
level for the UL PS NRT DCH packet scheduling when the HS-RACH has been set up in the cell. Value of the
parameter is defined in relation to the parameter PrxNoise.
PtxTargetPSMaxtHSRACH MO: WCEL Category: Basic parameter

• Description: Max PS target power level with HS-RACH. This parameter defines the maximum allowed target level for
the DL PS NRT DCH packet scheduling when the HS-RACH has been set up in the cell.
InactHSRACH HSFACHRel8ConSetupEC22
0...60 s; 0 s bits; 0001101111110110001100
InactHSRACH MO: WAC Category: Advanced parameter

• Description: The parameter defines how long inactive HS-RACH capable UE is kept in Cell_DCH state after trigger
times for HSDPA low utilization and E-DCH low throughput have triggered when the HS-RACH is configured in the
main cell of the UE active set cells. The main cell is the cell having best CPICH EcNo value reported by the UE.
When low utilization is detected for HSDPA MAC-d flow (MACdflowutilTimetoTrigger) and low throughput for E-DCH
MAC-d flow (EDCHMACdFlowThroughputTimetoTrigger), the RB can be released. When this has happened to all
the RBs of the user, the user can be transferred to Cell_FACH state. Instead of state transition the user can be kept
longer in the Cell_DCH state. This timer defines how much longer the user can be kept in Cell_DCH state even if it
is inactive all the period. This timer is applicable only if UE is HS-RACH capable and the HS-RACH has been
configured in the "main cell" of the active set of the UE.

13 6255 NAK HSUPA Protocol Features

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

13 6255 NAK HSUPA Protocol Features

Diunggah oleh

Hak Cipta:

Format Tersedia

Contents

UMTS/HSPA Radio Resource Management & Parameter

00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-3 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

100001 100011 101011 101001 001001 001011 000011 000001

100101 100111 101111 101101 001101 001111 000111 000101

00-4 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

64QAM 16QAM QPSK

00-6 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-9 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

RLC PDU size increased with Flexible RLC

3GPP Rel. 6 3GPP Rel. 7

00-10 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

With Flexible RLC in Rel. 7 the RNC becomes

00-11 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

RLC header RLC data Huawei (per RAB type)

Max. MAC-d PDU Max. MAC-d PDU

00-12 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

MAC-d PDU (segmentation into several HSDPA packets)

00-14 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-17 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- 3GPP R8  two adjacent HSDPA carriers can be allocated to a single UE

Nokia (per cell) Ericsson (per Node B)

00-18 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-20 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-22 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

+ Common CHs + E-AGCH, E-RGCH, E-HICH

Secondary serving cell

00-23 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-26 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Signal from jth Tx antenna Sj h1,1 Yi Signal at ith Rx antenna

T1 hn,1 h2,1 h1,m R1

00-27 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- Receiver determines channel matrix H giving the propagation characteristic of each

h1,1 h1,2  h1,m HspaPlusSwitch

00-29 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- Currently 2 x 2 MIMO is available only

00-31 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- To estimate the channel matrix H for 2 x 2 MIMO, a second CPICH is required

SF16 +15 x SF16

SF128 128 128 128 128 128 128 128

00-33 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-36 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

QPSK with 2 bits 16AM (4PAM) with

• 11.6 Mbps* is supported with 4 E-DCH channels in parallel (2xSF2 + 2xSF4)

00-37 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

• UEs in HSUPA data transmission mode decide whether

00-38 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-39 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Feature not yet available (2016-08-22)

00-40 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

ETFCIBoost (non configurable) • See Frequency domain equalizer

HSUPAUserLimit16QAM MO: WCEL Category: Basic parameter

00-41 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-42 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

UEs point of view: two carriers

00-43 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-44 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-45 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-46 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

eulMultiCarrierSupport eulMcSohoSupp hsIflsPrio.eulMc

eulMultiCarrierSupport MO: MultiCarrier

eulMcSohoSupp MO: Handover

hsIflsPrio.eulMc MO: Handover