Dual Cell HSDPA

RAN1906

1 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Background (I)
• Prior to 3GPP Release 8, HSDPA channel bandwidths are limited to 5 MHz
• The release 8 version of the specifications allow 2 adjacent channels to be
combined to generate an effective HSDPA channel bandwidth of 10 MHz
• This is known as Dual Cell HSDPA
• RU20 implementation of Dual Cell HSDPA is based upon release 8 of 3GPP
• Release 8 version of the specifications allow Dual Cell HSDPA to be combined
with 64QAM but not with MIMO (Release 9 allows combination with MIMO)
Basic Approach Dual Cell Approach
2 UE, each using 5 MHz RF Channel 1 UE, using 2 × 5 MHz RF Channels
Peak Connection Throughput = 28 Mbps Peak Connection Throughput = 42 Mbps
5 MHz 5 MHz 10 MHz

F1 F2 F1 F2

MIMO (28 Mbps), or DC HSDPA and

64QAM (21 Mbps) 64QAM (42 Mbps)
2 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
Background (II)
• The release 9 version of the specifications allow 2 non-adjacent channels
(potentially in different operating bands) to be combined to generate an effective
HSDPA channel bandwidth of 10 MHz
• Discussions are ongoing within 3GPP for introducing the capability to combine 4
RF channels to provide a 20 MHz aggregate channel bandwidth
• The combination of multiple RF carriers provides greater flexibility to the HSDPA
Scheduler, i.e. the scheduler can allocated resources in the frequency domain as
well as in the code and time domains

Channel conditions good Channel conditions good Channel conditions good

on both RF carriers on RF carrier 1 on RF carrier 2

F1 F2 F1 F2 F1 F2

UE1 UE1 UEx UEx UE1

3 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Requirements
UE Requirements
• UE must support dual cell HSDPA

Network Hardware Requirements

• Flexi Node B must have release 2 hardware
• UltraSite Node B must have EUBB
• RNC must be equiped with CDSP-DH cards

Feature Requirements
• The following features must be enabled:
• Fractional DPCH, Downlink Flexible RLC, Shared Scheduler for Baseband
Efficiency, HSDPA 15 codes, HSDPA 14 Mbps per User, HSUPA

• The dual cell HSDPA feature is optional and requires a long term RNC
license for a specific number of cells

4 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Enabling the Feature (I)
• The DCellHSDPAEnabled parameter must be set to enabled for both cells
belonging to the cell pair

Name Range Default Description

DCellHSDPAEnabled 0 (Disabled), 0 (Disabled) The parameter indicates whether or not the DC
1 (Enabled) HSDPA feature is enabled in the cell. Before the
(WCEL) feature is enabled in the cell, the system checks
that the maximum amount of DC HSDPA-
capable cells is not exceeded. If it is not
possible to enable DC HSDPA for a new cell
then the cell setup does not succeed and error
is printed out.

• Two cells form a potential DC HSDPA cell pair when they have adjacent RF
carriers, belong to the same sector and have the same Tcell value
• WCEL - UARFCN parameter defines the downlink channel number and the downlink
carrier frequency of the cell
• WCEL - SectorID parameter gives a unique identifier to a sector of the base station where
the cell belongs to
• WCEL - Tcell parameter defines the start of SCH, CPICH, Primary CCPCH and DL
Scrambling Code(s) in a cell relative to BFN

5 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Enabling the Feature (II)
• The MaxBitRateNRTMACDFlow parameter should be configured to allow the
peak throughput

Name Range Default Description

MaxBitRateNRTMACDFlow 128..42112, 65535 The parameter can be used to limit the maximum bit
step 128, rate of NRT MAC-d flow. The bit rate used in the
(RNC) reservation of resources for the MAC-d flow is the
65535 (no
restriction) minimum of max. bit rate based on UE capability, max.
bit rate of RAB, activated HSDPA bit rate features and
the value of this parameter. This parameter does not
limit the max. instantaneous air interface bit rate.
Value of the parameter is compared to the user bitrate
excluding MAC-hs header, RLC header and padding
(includes just RLC PDU payload).
Maximum value depends on the features licensed:
- no license for HSDPA 15 Codes, max. is 3456 kbps
- license for HSDPA 15 Codes, max. is 6784 kbps
- license for HSDPA 15 Codes and 10Mbps per User,
max. is 9600 kbps
- license for HSDPA 15 Codes and 14Mbps per User,
max. is 13440 kbps
- license for HSDPA 15 Codes and 64QAM, max. is
21120 kbps
- license for DC HSDPA, max. is 42112 kbps
If the value 65535 is used, then this parameter does
not restict the maximum bit rate.
6 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
Enabling the Feature (III)
• HSDPA serving cell change must be enabled using the HSDPAMobility
parameter
• Downlink Flexible RLC must be enabled using the FRLCEnabled parameter
• MIMO must be disabled for all cells belonging to the Node B using the
MIMOEnabled parameter
• HSDPA 14 Mbps per User must be enabled using the HSDPA14MbpsPerUser
parameter
• The HSDPA 15 codes feature must be enabled with at least a 10 code license
and these codes must be enabled using the HSPDSCHCodeSet parameter
• HSUPA must be enabled for at least one of the RF carriers using the
HSUPAEnabled parameter
• F-DPCH must be enabled for at least one of the RF carriers using the
FDPCHEnabled parameter (if enabled for only one RF carrier, must be same as
that used for HSUPA)
• The HSPAQoSEnabled parameter must be configured with the same value in
both cells of a cell pair

7 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
SectorID Configuration
• Cells which are paired for DC-HSDPA must belong to the same sector

SectorID = 1 SectorID = 3

SectorID = 2
RF Carrier 2

SectorID = 1 SectorID = 3

SectorID = 2
RF Carrier 1

8 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Tcell Configuration (I)
Tcell Groups
• 2+2+2 Node B with DC-HSDPA • Group 1: Tcell values 0, 1, 2
requires:
• Group 2: Tcell values 3, 4, 5
• each cell belonging to the • Group 3: Tcell values 6, 7, 8
same sector must have the • Group 4: Tcell value 9
same Tcell value
• Tcell values belonging to
different sectors must belong
to different Tcell groups Tcell = 0 Tcell = 6
• Configuration requires 3 Tcell = 3
HSDPA Efficient Baseband RF Carrier 2
Schedulers
• RF carriers 1 and 2 must be Tcell = 0 Tcell = 6
adjacent Tcell = 3
RF Carrier 1

9 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Tcell Configuration (II)
• 3+3+3 Node B with DC-HSDPA
requires:
• each DC-HSDPA cell belonging
to the same sector to have the
Tcell = 0 Tcell = 1
same Tcell value
• DC-HSDPA Tcell values Tcell = 2
belonging to different sectors RF Carrier 3
must belong to different Tcell
groups Tcell = 3 Tcell = 6
• Configuration requires 4
HSDPA Efficient Baseband Tcell = 9
RF Carrier 2
Schedulers
• RF carriers 1 and 2 must be Tcell = 3 Tcell = 6
adjacent
Tcell = 9
• Cells belonging to RF carriers 1 RF Carrier 1
and 2 must be within the same
LCG
• Cells belonging to RF carrier 3
must be within a second LCG
10 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
Physical Channels
• The serving cell provides the full set of physical channels
• Inner loop power control is driven by the serving cell
• HARQ ACK/NACK and CQI are reported to the serving cell
• Uplink data is sent to the serving cell
• The secondary serving cell provides only the downlink HS-SCCH and HS-PDSCH
• The return channel must be HSUPA
Downlink Uplink
Channels Channels

HS-SCCH E-DPDCH Primary RF Carrier

HS-PDSCH E-DPCCH Serving cell
F-DPCH HS-DPCCH
DPCCH

HS-SCCH
HS-PDSCH
Secondary RF Carrier
Secondary Serving cell

11 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Flexible Configuration
• The flexible configuration requires the HSUPA and F-DPCH features to be enabled
on both RF carriers belonging to a cell pair
• The flexible configuration allows both cells to simultaneously act as:
• primary serving HSDPA cell for some DC-HSDPA capable UE
• secondary HSDPA serving cell for other DC-HSDPA capable UE
• single carrier HSDPA/HSPA serving cell for non DC-HSDPA capable UE
• member of the Active Set for other UE

DC-HSDPA
Serving Cell Serving Cell HSPA UE1
UE1

Sec. Serving Cell

Sec. Serving Cell DC-HSDPA

UE2

Serving Cell Serving Cell HSPA UE2

12 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Fixed Configuration
• The fixed configuration applies when the HSUPA and F-DPCH features are
enabled on only 1 of the 2 RF carriers belonging to a cell pair

• In the case of the fixed configuration, the RF

carrier with HSUPA and F-DPCH enabled DC-HSDPA
can act as: Serving Cell UE1
• primary serving HSDPA cell for DC-HSDPA
capable UE Sec. Serving Cell
• single carrier HSDPA/HSPA serving cell for
non DC-HSDPA capable UE
• member of the Active Set for other UE HSPA UE1
Serving Cell
• The RF carrier with HSUPA and F-DPCH
disabled can act as:
• secondary serving HSDPA cell for DC-HSDPA
capable UE
• single carrier HSDPA/HSPA serving cell for
non DC-HSDPA capable UE
• member of the Active Set for other UE
Serving Cell HSPA UE2

13 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
HSDPA Scheduler (I)

• A single HSDPA shared scheduler for baseband efficiency is required per

DC-HSDPA cell pair
• 3 HSDPA shared schedulers are required for a 2+2+2 Node B configuration
with DC-HSDPA
• Each scheduler is able to serve both HSDPA and DC-HSDPA UE on both
RF carriers
• Link Adaptation is completed in parallel for each RF carrier

HSDPA UE on f2

Shared Scheduler DC-HSDPA UE with

per DC-HSDPA serving cell on f2
cell pair
HSDPA UE on f1

DC-HSDPA UE with
serving cell on f1

14 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
HSDPA Scheduler (II)
• A scheduler metric is calculated for each RF carrier
• Round Robin, Proportional Fair or PF-RAD-DS schedulers can be used
• The instantaneous Transport Block Size (TBS) is generated separately for
each cell by Link Adaptation
• The Average TBS is based upon the previously allocated TBS in both cells
belonging to the DC-HSDPA cell pair, i.e. it represents the total average
throughput allocated to the UE
• Thus, a UE which is scheduled high throughput in cell 1 (possibly because it
is the only active UE) will have a reduced scheduling metric for being
allocated resources in cell 2

TBS Cell1
Metric Cell1 
Average TBS Cell1Cell2
Shared Scheduler
per DC-HSDPA DC-HSDPA
cell pair UE
TBS Cell2
Metric Cell2 
Average TBS Cell1 Cell2

15 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
UE Categories Extracted from Rel. 8 version of 3GPP TS 25.306

• HSDPA UE categories
21 to 24 support DC-
HSDPA
• Maximum transport
block sizes are
supported by UE
categories 22 and 24
• Maximum transport
block sizes are the
same as those used
for MIMO
• Peak throughput of
dual cell HSDPA
equals peak
throughput of dual
stream MIMO (when
using same
modulation scheme)

16 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
DC-HSDPA Throughputs (I)
Physical Layer (based upon Physical Channel capability)
• Chip Rate = 3.84 Mcps
• Spreading Factor = 16
=> Symbol Rate = 240 ksps
• Number of HS-PDSCH codes = 15
=> Aggregate Symbol Rate per RF Carrier = 3.6 Mbps
• Number of bits per Symbol = 6
=> Aggregate Bit Rate per RF Carrier = 21.6 Mbps
• Number of RF Carriers = 2
=> Bit Rate = 43.2 Mbps (peak)
Physical Layer (based upon UE maximum transport block size)
• Category 24 maximum transport block size = 42 192 bits
• Transmission Time Interval = 2 ms
=> Bit Rate per transport block = 21.096 Mbps
• Number of Transport Blocks = 2
=> Bit Rate = 42.192 Mps (peak)

17 © Nokia Siemens Networks RU20 Feature Training / CJo

coding rate of 0.98
 DC HSDPA
MAC-ehs PDU
• MAC-ehs header fields
• Logical Channel Identifier (LCH-ID) – 4 bits
• Transmission Sequence Number (TSN) – 6 bits
24 bits total, or
• Segmentation Index (SI) – 2 bits 16 bits without the TSN and SI
• Length (L) – 11 bits
• Flag (F) – 1 bit
• TSNn and SIn fields are only required if LCH-Idn <> LCH-Idn-1

Total header size = 72 bits when MAC-ehs PSU accomodates 4 re-ordering PDU with the
same LCH-Id
TSN1 L12 F1 L2 F2 L3 F3 L4 F4

LCH-ID1 SI1 LCH-ID2 LCH-ID3 LCH-ID4

Maximum transport block size = 42192 bits; Maximum RLC PDU size = 11216 bits
So total payload size = 3 × 11216 + 8472 = 42120 bits

18 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
DC-HSDPA Throughputs (II)
RLC Layer (based upon maximum transport block size payload)
• Maximum transport block size payload = 2 × 42120 bits
• RLC header size per transport block = 4 × 16 = 64 bits
=> RLC payload = 2 × 42056 bits
• Transmission Time Interval = 2 ms
=> Peak instantaneous bit rate = 42.056 Mbps
• MAC-ehs re-transmission rate = 10 %
• RLC re-transmissions rate = 1 %
=> Net Bit Rate = 37.43 Mbps

Application Layer (based upon TCP/IP protocol stack)

• IP header size = 20 bytes
• TCP header size = 36 bytes
• MTU Size = 1500 bytes
=> TCP/IP overhead = 3.7 %
=> Application throughput = 36.032 Mbps
19 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
Connection Establishment (I)
• RRC Connection Request message includes a flag to indicate whether or not
the UE supports DC-HSDPA

• RRC Connection Setup Complete message includes UE HSDPA Category

information
Used by
network when
DC-HSDPA is
disabled

Used by
network when
DC-HSDPA is
enabled

20 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Connection Establishment (II)
• Connection establishment from CELL_DCH shown below
• Message flow is the same as for a single cell HSDPA connection
UE Node B RNC CN

UE in CELL_DCH with standalone SRB on DCH/DCH, DCH/HSDPA or SC HSPA

RAB Assignment Request

DC-HSDPA is possible with current HS-DSCH
serving cell becoming primary serving cell

RL Reconfiguration Prepare
MAC-ehs resources reserved for DC-HSDPA

RL Reconfiguration Ready
[Additional HS Cell Information Response IE]
Radio Bearer Setup
[primary cell HSPA information, Downlink Secondary Cell Info FDD IE]

RL Reconfiguration Commit

Radio Bearer Setup Complete

RAB Assignment Response

UE in CELL_DCH with DC-HSDPA

21 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Connection Establishment (III)
• Connection establishment from CELL_FACH shown below
• Message flow is the same as for a single cell HSDPA connection
UE Node B RNC CN

UE in CELL_FACH with standalone SRB on RACH/FACH

RAB Assignment Request

DC-HSDPA is possible with current HS-DSCH
serving cell becoming primary serving cell

RL Setup Request
MAC-ehs resources reserved for DC-HSDPA

RL Setup Response
[Additional HS Cell Information Response IE]
Radio Bearer Setup
[primary cell HSPA information, Downlink Secondary Cell Info FDD IE]

RL Restore Indication
Radio Bearer Setup Complete

RAB Assignment Response

UE in CELL_DCH with DC-HSDPA

22 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Downlink Secondary Cell Information
• A secondary H-RNTI is
allocated to the UE for use
within the secondary serving cell
• Modulation Scheme, Transport
Block Size Table, and CPICH
information is specified
• HS-SCCH channelisation code
information is provided
• 3GPP TS 25.214 states that a
UE can be configured to monitor
a maximum of 6 HS-SCCH
across the serving and
secondary serving cells
• Measurement power offset for
the secondary serving cell is
specified
• Downlink RF carrier is specified

23 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Supported RAB Combinations
• DC-HSDPA is not allocated to a standalone SRB
• DC-HSDPA supports up to 3 Interactive or Background RAB mapped to HSPA
• Streaming RAB can be configured but must be mapped to DCH 0/0 kbps
instead of HSPA
• A maximum of 4 MAC-d flows per UE can be configured
• Establishment of a conversational or streaming RAB triggers the release of the
DC-HSDPA configuration
• DC-HSDPA can be configured after the release of a conversation or streaming
RAB

24 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Maximum Number of Connections (I)
• DC-HSDPA connections are only counted within the Serving Cell, i.e. they do not impact the number of
connections within the Secondary Serving Cell
• The MaxNumberHSDPAUsers parameter defines the maximum number of HSDPA connections per cell
• The MaxNumbHSDPAUsersS parameter defines the maximum number of HSDPA connections per
scheduler

Name Range Default Description

MaxNumbHSDPAUsersS 1 to 511, step 1, 0 Defines the maximum number of SC HSDPA
0 and DC HSDPA users in the MAC-hs/ehs
(WCEL) (unrestricted) specific BTS scheduler. Certain SC HSDPA
and certain DC HSDPA user are counted once
per scheduler. SC HSDPA and DC HSDPA
user is a user that has one or more HS-DSCH
MAC-d flows established. RNC does not
exceed the maximum number but admission of
SC HSDPA and DC HSDPA user is inhibited in
the scheduler if the maximum number is to be
exceeded. This parameter is defined per cell
and because scheduler consists of several
cells, lowest parameter values of cells forming
scheduler shall be used.

25 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Maximum Number of Connections (II)
• MAC-d flows are only counted within the Serving Cell, i.e. they do not impact
the number of MAC-d flow within the Secondary Serving Cell
• The MaxNumbHSDSCHMACdFS parameter defines the maximum number of
MAC-d flows per cell

Name Range Default Description

MaxNumbHSDSCHMACdFS 1 to 1023, step 1, 0 Defines the maximum allowed number of HS-
0 DSCH MAC-d flows of SC HSDPA and DC
(WCEL) (unrestricted) HSDPA users in the MAC-hs/ehs specific BTS
scheduler. HS-DSCH MAC-d flow of the certain
SC HSDPA and DC HSDPA user is counted
once per scheduler. Each HS-DSCH MAC-d
flow of each SC and DC HSDPA user is
counted when the total number of HS-DSCH
MAC-d flows in the scheduler is calculated.
RNC does not exceed the maximum number
but admission of SC HSDPA and DC HSDPA
user is inhibited in the scheduler if the
maximum number is to be exceeded. This
parameter is defined per cell and because
scheduler consists of several cells, lowest
parameter values of cells forming scheduler
shall be used.

26 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
HS-DPCCH
• HS-DPCCH is responsible for signalling
• CQI reports
• HARQ ACK/NACK
• For DC-HSDPA there is a requirement to signal CQI and ACK/NACK
information for both cells with the cell pair
• Physical channel capacity of the HS-DPCCH remains the same so the level of
redundancy is reduced
• ACK/NACK coding is modified to encorporate
information applicable to second cell ACK / NACK CQI
• CQI raw data increases from 5 to 10 bits a0..a9
meaning that coding rate increases from rate
Channel Channel
1/3 to rate ½ Coding Coding
• Coding is different to MIMO although MIMO w0..w9 b0..b19
can also involve 2 CQI reports and 2
ACK/NACK Physical Channel Mapping

27 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
HARQ ACK/NACK
• Coding is the same as for single cell HSDPA when data is transferred only from
the serving cell
• Coding has a time shift when data is transferred only from the secondary cell

• Coding is similar
(but not
identical) to dual
stream MIMO
when data is
transferred from
both the serving
and secondary
serving cells

28 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
CQI Reporting (I)
• CQI reports for each cell are concatenated to
generate a bit string of length 10 bits CQI1 CQI2
• CQI feedback cycle remains as 4 ms
• CQI repetition is increased from 1 to 2 Bit Mapping Bit Mapping

• Thus, CQI reports are sent during every TTI cqi0..cqi4 cqi0..cqi4
• Repetition replaces the redundancy which
Concatenation
was lost by sending CQI reports for each cell
• Similar repetition cannot be used for the
a0..a9
HARQ ACK/NACK without having an impact
upon the maximum throughput capability

Name Range Default Description

CQIrepetition 1 to 4, step 1 SC HSDPA: CQI repetition factor indicates the number of
non-SHO SHO consecutive repetitions of the CQI. Parameter
(RNC) 1 1 value depends on SHO state of the UE and
whether SC or DC HSDPA is configured for the
DC HSDPA:
UE.
non-SHO SHO
2 2

Non-Configurable
29 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
CQI Reporting (II)

• UE categories 21 to
24 are specified to use
CQI mapping tables C
and D when 64QAM is
not configured
• Otherwise CQI
mapping tables F and
G are used

30 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
CQI Reporting (III)
Table F Table G

• CQI mapping
tables do not
include the
maximum
transport block
sizes
• Table F does not
include the use
of 15 codes
• Node B is left
with the decision
of when to
schedule the
maximum
transport block
sizes

31 © Nokia Siemens Networks RU20 Feature Training / CJo

 r s b
DC HSDPA
HS-SCCH Signalling RV
coding

Xrv
• HS-SCCH can be used to provide ‘orders’ Xccs Xms Xtbs Xhap Xnd

(instructions) to the UE
• In the case of DC-HSDPA, the HS-SCCH can mux mux

activate/deactivate the secondary serving cell

X1 X2
• This provides a mechanism for ‘fast’ control of the Xue
UE specific
secondary serving cell, compared to CRC
attachment
activating/deactivating by RRC signalling Y

• Primary purpose is to help save UE battery life Channel

Coding 1
Channel
Coding 2

• HS-SCCH ‘orders’ to activate/deactivate the Z1 Z2

secondary serving cell are not supported in RU20
• For an HS-SCCH order, Rate
matching 1
Rate
matching 2

• xccs,1, xccs,2, …, xccs,7, xms,1 is set to ‘11100000’ R1 R2

• xtbs,1, xtbs,2, …, xtbs,6 is set to ‘111101’
• xhap,1, xhap,2, xhap,3, xrv,1, xrv,2, xrv,3 is set to Xue UE
specific
xodt,1, xodt,2, xodt,3, xord,1, xord,2, xord,3 masking

S1
• xnd,1 is reserved
• xodt,1, xodt,2, xodt,3 define the order type, and Physical
channel
xord,1, xord,2, xord,3 define the order itself mapping

32 © Nokia Siemens Networks RU20 Feature Training / CJo HS-SCCH

 DC HSDPA
T1 Timer
• The value allocated to T1 is reduced when DC-HSDPA is enabled
• This allows allows less time for re-transmissions

Name Range Default Description

T1 0....10 ms SC HSDPA: UE timer (in milliseconds) when MAC-hs PDUs in re-ordering
1....20 ms 120 ms buffer are released to the upper layers even though there are
(RNC) 2....30 ms outstanding PDUs with lower TSN values. BTS uses T1 timer
DC HSDPA:
3....40 ms to stop retransmissions of expired PDUs.
100 ms
4....50 ms
5....60 ms
6....70 ms
7....80 ms
8....90 ms
9....100 ms
10...120 ms
11...140 ms
12...160 ms
13...200 ms
14...300 ms
15...400 ms

Non-Configurable

33 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
MAC-ehs Transmit Window Size
• The value allocated to MAC-ehs transmit window size is increased when DC-
HSDPA is enabled
• This helps to provide support for the increased throughputs

Name Range Default Description

MAChstxwindowsize 0: 4 Default value per Parameter produces a look-up table to
1: 6 HSDPA UE category define the MAC-hs/MAC-ehs
(RNC) 2: 8 transmitting window size signalled to
1: 0 13: 4
3: 12 2: 0 14: 4 BTS. Input parameter to the look-up
4: 16 3: 2 15: 4 table is HS-DSCH physical layer
5: 24 4: 2 16: 4 category.
6: 32 5: 4 17: 4
6: 4 18: 4 HS-DSCH category values 21 ... 24
7: 4 19: 4 are used only if DC HSDPA is
8: 4 20: 4 configured in use. Otherwise, the
9: 4 21: 5 values of lower categories are used.
10: 4 22: 5
11: 2 23: 5
12: 4 24: 5

Non-Configurable

34 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
MAC-ehs Receive Window Size
• The value allocated to MAC-ehs receive window size is increased when DC-
HSDPA is enabled
• This helps to provide support for the increased throughputs

Name Range Default Description

MAChsrxwindowsize 0: 4 Default value per Parameter produces a look-up table to
1: 6 HSDPA UE category define the MAC-hs/MAC-ehs receiving
(RNC) 2: 8 window size signalled to UE. Input
1: 0 13: 4
3: 12 2: 0 14: 4 parameter to the look-up table is HS-
4: 16 3: 2 15: 4 DSCH physical layer category.
5: 24 4: 2 16: 4
6: 32 5: 4 17: 4 HS-DSCH category values 21 ... 24
6: 4 18: 4 are used only if DC HSDPA is
7: 4 19: 4 configured in use. Otherwise, the
8: 4 20: 4 values of lower categories are used.
9: 4 21: 5
10: 4 22: 5
11: 2 23: 5
12: 4 24: 5

Non-Configurable

35 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Inter-System & Inter-Frequency Handover
• RU20 does not support inter-frequency nor inter-system handover
measurements for UE which are configured with DC-HSDPA
• Channel type switching is initiated if inter-frequency or inter-system handover
is triggered
• Channel type switching targets either DCH/HSDPA or DCH/DCH connection
types
• The network behaviour is the same when UE are anchored via a Drift RNC

36 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Directed RRC Connection Setup

• In the case of DC-HSDPA capable UE, Directed RRC Connection Setup

targets cells which can be used as the primary serving cell, i.e. those cells
with F-DPCH and HSUPA enabled
• If there are multiple F-DPCH capable cells, the RNC targets cells which have
not reached the maximum number of HSUPA connections and which have
DC-HSDPA enabled
• The RNC only accounts for the F-DPCH capability if the
DirectedRRCForHSDPALayerEnhanc parameter is set to ‘Enabled’
• Similar rules apply to the state transition from CELL_FACH to CELL_DCH,
i.e. when using the HSPA Layering for UE in Common Channels feature

37 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
HSPA Capability based Handover
Cu
r r
• DC-HSDPA
en
parameter
Capability based Handover is enabled using the DCellHSDPACapaHO

• SupportedtlRAB
y
parameter un
combinations are defined using the DCellHSCAHORabComp

• DC-HSDPA capability clbased

e handover can only be enabled if both periodic and
ar based handovers are disabled in the source cell
event triggered HSPA capability
if t Handover shall be enabled when:
• Thus DC-HSDPA Capability based
• his
WCEL - HSCapabilityHOPeriod is set to ‘0’
• wi
ll b
WCEL - DCellHSDPACapaHO is set to ‘Enabled’
• ADJI - AdjiNCHOHSPASupport is set to ‘HSPASupport’ in at least one neighbour cell
ei
• DC-HSDPA capability based handover
m no periodic triggering
• uses only the event triggered handover mechanism, i.e. p
• targets UE which support DC-HSDPA and are using HSDPA leormHSPA services
• Event triggered DC-HSDPA Capability based Handover is based upon enperiods of
inactivity ted
38 © Nokia Siemens Networks RU20 Feature Training / CJo
 DC HSDPA
Power Saving Mode
• DC-HSDPA has an impact upon the Power Saving Mode for BTS (RAN955)
• The number of DC HSDPA users in a cell must be lower than or equal to the
value of the PWSMSDLimitDCHSDPA parameter before shutdown is possible
• Each DC HSDPA user is counted separately in the primary and secondary cells
• This new criteria is an addition to the existing crieteria, and all criteria must be
fulfilled to shutdown a cell
• The PWSMAVLimitDCHSDPA parameter defines the corresponding threshold
for activating a cell in terms of the minimum number of DC-HSDPA capable UE

Name Range Default Description

PWSMSDLimitDCHSDPA 0 to 300, 5 This parameter defines the limit for DC
step 1 HSDPA user amount for cell shutdown
(WCEL) decision.

Name Range Default Description

PWSMAVLimitDCHSDPA 0 to 300, 10 This parameter defines the limit for DC
step 1 HSDPA user amount for cell activation
(WCEL) decision.

39 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
RNC Counters

• The M1000 Cell Resource counters which record the quantity of HSDPA users
and MAC-d flows per cell, are updated only for the primary serving cell of the
DC-HSDPA connection, not for the secondary cell
• All M1002 Traffic counters related to measuring HS-DSCH MAC-d flows, are
updated only for the primary serving cell of the DC-HSDPA connection, not for
the secondary cell.

40 © Nokia Siemens Networks RU20 Feature Training / CJo

 DC HSDPA
Other Parameters
• The parameters listed below are referenced within the documentation but do
not yet appear within the online parameter dictionary
• It is currently unclear whether or not these parameters will appear within the
RU20 implementation
• DCellHSDPACapaHO (WCEL)
• DCellHSCAHORabComp (RNC)
• DCellHSDPAFmcsId (WCEL)
• DCellHSDPAFmcsId (VCEL)
• DCellHSDPAEnabled (VCEL)

41 © Nokia Siemens Networks RU20 Feature Training / CJo

The End

42 © Nokia Siemens Networks RU20 Feature Training / CJo