You are on page 1of 44

HSDPA Parameters

• General
• Power Allocation
• MAC-d flow utilization & throughput measurement
• Associated UL Channel Bit Rate
• Mobility
HSDPA Activation
• HSDPA is enabled with HSDPAenable parameter (Requires object locking)
• MAC-hs entity is created.

• HSDPAenabled
• Parameter enables / disables the use of HSDPA in the cell.
• When the value of the parameter is set to 1 (HSDPA functionality is enabled for the
cell) the system checks that maximum amount of HSDPA capable BTSs and cells is
not exceeded.
• If it is not possible to activate HSDPA for new BTS or cell then activation does not
succeed and error is printed out.

• When HSDPA is enabled following BTS resources are allocated:


• WSPC capacity for HSDPA (32CE)
• 5 HS-PDSCH codes (SF16)
• 1 HS-SCCH code (SF128)
Directed RRC Connection Setup for HSDPA
(1/2)
• DirectedRRCEnabled
The parameter enables/disables the use of directed RRC connection setup or
directed RRC connection setup for HSDPA layer in the cell.
0: Directed RRC connection setup is not enabled in the cell
1: Directed RRC connection setup is enabled in the cell
2: Directed RRC connection setup for HSDPA layer is enabled in the cell
DRRC
•The UE initiates an RRC connection setup by
MS UTRAN sending the RRC CONNECTION REQUEST
Frequency 1 message on the RACH of the cell (current cell) on
which it is camped in the idle mode.
RRC CONNECTION REQUEST
•The RRC connection setup procedure usually
establishes the RRC connection in the current cell.
Check UE is R99 or R5 •In case of Directed RRC connection setup, the
RNC does not establish the connection in the
current cell, but it establishes the RRC connection
RRC CONNECTION SETUP in another cell which is less loaded and belongs to
the same sector as the current cell.
Frequency 2
RRC CONNECTION SETUP COMPLETE
• General
• Power Allocation
• HSDSCH Release
• Associated UL Channel Bit Rate
• Mobility
Planning parameters in RAN05 for Power
allocation
• HSDPA power is defined by the PtxMaxHSDPA parameter. The value of
the parameter is signaled to the BTS with codes.
• The signaling takes place in a physical shared channel reconfiguration
procedure after cell setup in cells that support HSDPA and have HSDPA
enabled (parameter HSDPAenabled).
• Note that the HSDPA power can be used for Rel-99 channels when
there are no MAC-d flows in the cell.
• Related Parameters
• PtxMaxHSDPA =37.8dBm = 6W
• HSDPAPriority =1
• PtxTargetHSDPA =38.5dBm =7.1W
• PtxOffsetHSDPA = 0.8dBm
• General
• Power Allocation
• MAC-d flow utilization & throughput measurement
• Associated UL Channel Bit Rate
• Mobility
HS-DSCH & MAC-d release: low utilisation
PDUs in buffer

Throughput
Low utilization indication

MACdflowUtilRelThr (Def: 256bps)

MACdflowthrougputRelThr (Def: 0bps)

MACdflowUtilTimetoTrigger (0s)

When will be happened?


HS-DSCH & MAC-d release : low throughput
PDUs in buffer

Throughput
Low throughput indication

MACdflowUtilRelThr (Def: 256bps)

MACdflowthrougputRelThr (Def: 0bps)

HsdschGuardTimerLowThroughput,
(30sÎ maybe can set short, quick back the HSDPA)
MACdflowUtilTimetoTrigger
(Def: 0s) MACdflowThroughputTimetoTrigger
(5 s) maybe can set short, if no throughput can save the power)

When will be happened?


HS-DSCH & MAC-d release
L3 starts procedure to release UL NRT DCH and MAC-d flow if:
• MAC-d flow has low utilization and UL NRT DCH can be released
(InactivityTimer 20s).
Or
• MAC-d flow has low throughput and UL NRT DCH can be released
(InactivityTimer). In this case UE specific timer
HsdschGuardTimerLowThroughput 30s is started.
If MAC-d flow has both low utilization and low throughput conditions valid at
the same time, the functionality described in case of low utilization is
followed

HS-DSCH &
associated DCHs UE moved to Cell
released
FACH
• General
• Power Allocation
• MAC-d flow utilization & throughput measurement
• Associated UL Channel Bit Rate
• Mobility
Physical Channels for One HSDPA UE RAS 5.0
DL CHANNELS
• HS-PDSCH: High-Speed Physical Downlink Shared Channel
• Actual HSDPA data of HS-DSCH transport channel.
• 1-15 code channels (QPSK or 16QAM modulation)
BTS • Divided into 2ms TTIs
• Fixed SF16
• Doesn’t have power control

• HS-SCCH: High-Speed Shared Control Channel


• Informs UE how to receive HS-PDSCH in the next HS-
Rel99

Associated DPCH
Associated DPCH
DPSCH frame.
1-4 x HS-SCCH

• Fixed SF128
DCH
HS-DPCCH
1-15 x HS-

• Associated DPCH, Dedicated Physical Channel.


PDSCH

UL CHANNELS
• Associated DPCH, Dedicated Physical Channel
• HS-DPCCH: High-Speed Dedicated Physical Control Channel
• MAC-hs Ack/Nack information.
• Channel Quality Information (CQI reports) - sent in every
4ms
• SF 256

UE Associated DPCH, Dedicated Physical Channel


- DPCH needed for each HSDPA UE.
- Power control commands for associated UL DCH
-Transfer signalling (SRB) messages
-Uplink data 64, 128, 384kbps, e.g. TCP acks

Can R99 Node B know the DL quality ?


Associated UL Channel Bit Rate
- General

• In order to use HS-DSCH as a downlink transport channel, an HSDP Aassociated


uplink DCH return channel is needed.
• Supported data rates for a return channel are 64, 128 and 384 kbit/s.
• The RNC determines the initial bit rate to be used in the uplink return channel from
the measured traffic volume and the configured initial bit rate.
• If the traffic volume measurement indicates High traffic
volume(TrafVolThresholdULHigh 2048bytes), the RNC attempts to allocate a
return channel with the highest possible bit rate.
• If the traffic volume measurement indicates Low traffic
volume(TrafVolThresholdULLow 128byte), the RNC attempts to allocate a return
channel with configured initial bit rate(HSDPAinitialBitrateUL).
• If the HS-DSCH allocation is triggered by downlink, the RNC attempts to allocate
the uplink with HSDPAinitialBitrateUL.
• If the channel allocation fails due to congestion, the HS-DSCH allocation is not
possible and the RNC schedules a DCH to the UE.
Downlink traffic volume measurements

(transport channel traffic volume)


Traffic volume measurement
triggered, request for high bit rate

RLC buffer payload


TrafVolThresholdDLHigh 2048 byte

DL data transmission on
DCH in CELL_DCH state

Traffic volume measurement


triggered, request for low bit rate

TrafVolThresholdDLLow 128 byte


DL data transmission on
FACH in CELL_FACH state Traffic volume measurement not
triggered
Planning parameters in RAN05
UL return channel

• HSDPAinitialBitrateUL (RN301_64k, RN302_384K)


• Defines the initial bit rate for scheduling of the HSDPA associated UL DCH.
• Default, 64 kbps

• HSDPAminAllowedBitrateUL (RN301_64k, RN302_384K)


• Defines the minimum allowed bit rate in UL that can be allocated by the PS
to the HSDPA associated UL DCH when downgrading bit rate.
• Default, 64 kbps
Associated UL DPCH bitrate – use case 1/3
Associated UL DPCH bitrate – use case 2/3
Associated UL DPCH bitrate – use case 3/3

UL congestion first ?
• General
• Power Allocation
• MAC-d flow utilization & throughput measurement
• Associated UL Channel Bit Rate
• Mobility
HSDPA mobility in RAS05
• Serving Cell Change switches the user from
HS-DSCH to Cell_FACH then back to HS-
DSCH

Cell A Switching to Cell B


Cell_FACH UE on HS-
Service in within the SHO DSCH
HSDPA area

HS-DSCH coverage HS-DSCH coverage

Throughput
HSDPA

128kbps or 384kbps according to parameter settings


DCH
64kbps

0
Mobility Parameters relevant to HSDPA

FMCS FMCI FMCG


Addition Window (1A) IFHO caused by CPICH Ec/No GSM HO caused by CPICH Ec/No
Addition Time (1A) IFHO caused by CPICH RSCP GSM HO caused by CPICH RSCP
Addition Reporting Interval (1A) IFHO caused by UE TX Power GSM HO caused by UE TX Power
CPICH Ec/No Filter Coefficient UE TX Power Filter Coefficient UE TX Power Filter Coefficient
CPICH Ec/NO HHO Threshold (1F) UE TX Power Threshold for NRT PS UE TX Power Threshold for NRT PS
CPICH Ec/NO HHO Time Hysteresis (1F)
CPICH RSCP HHO Filter Coefficient
CPICH RSCP HHO Threshold (1F)
CPICH RSCP HHO Time Hysteresis (1F)

HOPS
HHO Margin for Average Ec/No
HHO Margin for Peak Ec/No
Release Margin for Average Ec/No
Release Margin for Peak Ec/No
CPICH Ec/No Averaging Window
Enable RRC Connection Release
Measurement Events for HSDPA Mobility
• Triggering Events for Channel Type Switching

Event Description
1A A primary CPICH enters the reporting range
-channel switching to Cell_FACH
1F A primary CPICH goes below the absolute threshold
-channel switching to DCH 0/0 kbps
6A UE Tx power exceeds the absolute threshold
-channel switching to DCH 0/0 kbps

• A UE with a HS-DSCH transport channel allocated can have only one cell in the active set at a
time, that is, the size of active set limited to one.
• Because of this, the RNC does not ad cells to the active set based on reporting event1A when
a HS-DSCH transport channel is allocated to the UE, but utilizes the event 1A as a trigger for a
HS-DSCH MAC-d flow release and transition to the Cell_FACH state.
HSDPARRCdiversity (1/4)
- Diversity handover of stand-alone signalling link

•If the active set size is greater than one, allocation of a HS-DSCH transport channel to
the UE is prohibited.

•The operator can disable diversity handover of the RRC connection (stand-alone
signalling link) of a HSDPA-capable UE with the HSDPARRCdiversity parameter to
maximise the use of the HS-DSCH.

•The value of the parameter HSDPARRCdiversity shall be checked immediately after a


successful RRC connection setup procedure.

•If SHO of the RRC connection (stand-alone signalling link) of the HSDPA-capable UE is
not allowed, the active set size is limited to one for the RRC connection.

•Restriction is effective after RRC-connection establishment when SRB only or SRB and
DCH 0/0 is/are allocated.
HSDPARRCdiversity (3/4)
- Diversity handover of stand-alone signaling link

ReleaseMarginAverageEcNo 2.5dB
Ec/No ReleaseMarginPeakEcNo 3.5dB
DCH AdditionWindow

DCH DeletionWindow

P CPICH 2

P CPICH 1
DCH Addition Time
DCH Deletion Time

Periodic MR (e1A) MR (e1B)


Call Start
HSDPARRCDiversity: Not Allowed ASU ASU HSDPA
EcNo Filter coefficient (HSDPA FMCS) = 600ms
SHO of the HSDPA Capable UE (RNC) = disabled
Allocation
Enable RRC release (HSDPA HOPS) = enabled
Release Margin Average EcNo (HSDPA HOPS) = 2.5dB
Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB
2 Active Set Stand-alone
EcNo Averaging Window (HSDPA HOPS) = 8
Signalling
Link
EnableRRCrelease (2/4)- disabled

Ec/No HSDPA AdditionWindow 0dB

P CPICH 1

HSDPA AdditionTime
time

Addition Window (HSDPA FMCS) = 0dB HSDPA allocation FACH cell update
Addition Time (HSDPA FMCS) = 1280ms
EcNo Filter coefficient (HSDPA FMCS) = 600ms RB_Reconfigurat
SHO of the HSDPA Capable UE (RNC) = disabled
Enable RRC release (HSDPA HOPS) = disabled MR(e1A) ion (FACH)
Release Margin Average EcNo (HSDPA HOPS) = 2.5dB
Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB
EcNo Averaging Window (HSDPA HOPS) = 8
Any problem when we set the
EnableRRCrelease -disabled ?
EnableRRCrelease (4/4)
- enabled
Ec/No
HSDPA
AdditionWindow
ReleaseMarginAverageEcNo
ReleaseMarginPeakEcNo

P CPICH 1

HSDPA AdditionTime

time

Addition Window (HSDPA FMCS) = 0dB HSDPA allocation FACH cell update
Addition Time (HSDPA FMCS) = 1280ms
EcNo Filter coefficient (HSDPA FMCS) = 600ms
SHO of the HSDPA Capable UE (RNC) = disabled
Enable RRC release (HSDPA HOPS) = enabled
Periodic MR(e1A)
RB_Reconfiguration (FACH)
Release Margin Average EcNo (HSDPA HOPS) = 2.5dB
Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB
EcNo Averaging Window (HSDPA HOPS) = 8
EnableRRCrelease enabled

Periodic
MR(e1A)

GO to FACH
HSDPA mobility in RAS05 NEMO

Throughput gap around 2 s


HSDPA mobility in RAS05 NEMO Message
1. Measurement report, e1a

SC 210 to SC205
HSDPA mobility in RAS05 NEMO Message
2. From HSDPA to FACH
3. Cell reselection

From HSDPA to FACH


3
Cell reselection

SC 210 to SC205
HSDPA mobility in RAS05 NEMO Message
4. From FACH to HSDPA

From FACH to HSDPA


4
HsdschGuardTimerHO
HS-DSCH guard time after switching to DCH due to HO
The parameter determines a period of time during which the HS-DSCH
allocation is denied after successful channel type switching from HS-DSCH
to DCH 0/0 kbps due to handover reasons(e1F, e6A).
Timer is not applied if UE is transferred directly to the CELL_FACH state due
to reporting event 1A.
Range and step 0...30 s, step 1 s
Default value 5 s ( maybe can set 2 s)
Mobility in RAS05+CD1
• Mobility in RAS05
• Serving cell change via FACH
• HSDPA selection in call setup

• Mobility in RAS05+CD1
• Resumption timer
• Improvement in HS-DSCH to FACH transition (target cell information)
Resumption timer (RAS05+CD1)
The conditions preventing HSDPA allocation in
• HSDPA resumption timer switches HSPDA coverage area to HSDPA capable UE are:
the user from DCH to HS-DSCH, • More than one serving cell (Soft Handover)
when UE enters HSDPA area • Multi-RAB combination (not supported)
• Lack of HSDPA capacity in the cell

Cell A Switching to Cell B


HS-DSCH
Service when not in
NRT DCH SHO area

R99 coverage HS-DSCH coverage

Throughput
Download
complete
HSDPA

128kbps or 384kbps according to parameter settings


DCH
64kbps (initial bitrate)

0
Resumption timer
• RNP parameter in RNC.
• Timer started when HSDPA
capable UE having DCH NRT
enters into HSDPA capable
cell and Active set size=1.
• Switching to HS-DSCH is tried
after the timer expires, if the
Active set size is still 1.
• Switching happens via
DCH0/0.
• Normal HSDPA selection
procedure is applied after a
capacity request, when
DCH0/0 is allocated.
From DCH AS 2 to 1 HSDPA
Resumption timer =4s

From HSDPA to FACH E1b, AS from 2 to 1

1
Wait Resumption
timer=4 2
Radio Bearer to
3
DCH 0/0

4
From DCH 0/0 to
HSDPA
From DCH AS 2 to 1 HSDPA
Resumption timer =4s
DCH to HS-DSCH switch
• Resumption timer started Application throughput
1500000
when Active set size =1.
1000000
• Resumption timer value in

bps
DCH NRT HS-DSCH
this case 4s. 500000

• Switching to HS-DSCH 0
0 10 20 s 30 40 50
tried after the timer
Active expires.
set size=1 after this Active Set EventId Time Subchannel Message
Update (no SHO anymore).
RRCD 08:24.8 DCCH "ACTIVE_SET_UPDATE"
Resumption timer started.
RRCU 08:24.8 DCCH "ACTIVE_SET_UPDATE_COMPLETE"
RRCD 08:25.1 DCCH "MEASUREMENT_CONTROL"
RB reconfiguration to DCH0/0.
RRCD 08:29.3 DCCH "RADIO_BEARER_RECONFIGURATION"
4s resumption timer applied before. RRCU 08:30.5 DCCH "RADIO_BEARER_RECONFIGURATION_COMPLETE"
RRCD 08:30.7 DCCH "MEASUREMENT_CONTROL"
~2.5 seconds gap according
RRCU 08:30.7 DCCH "MEASUREMENT_REPORT"
signaling. The data gap is about 6s
RRCD 08:31.7 DCCH "RADIO_BEARER_RECONFIGURATION"
when measured with Ethereal.
RRCU 08:32.8 DCCH "MEASUREMENT_REPORT"
RRCU 08:32.8 DCCH "RADIO_BEARER_RECONFIGURATION_COMPLETE"
RB reconfiguration to HS-DSCH
RRCD 08:33.1 DCCH "MEASUREMENT_CONTROL"
Improved HS-DSCH to cell_FACH switching
(RAS05+CD1)
• Target cell (cell with
best CPICH Ec/No in
the measurement set)
informed in the RB
reconfiguration
message, when UE is
commanded to
cell_FACH
• There is no need for
cell reselection in
cell_FACH, as the UE
goes directly to
strongest cell in
cell_FACH.

Scrambling code of the strongest cell


in the measured set informed to UE.
Inter Node-B Serving HS-DSCH Cell Change,RAN5.1

Serving RNC

Iub Iub

Node B Source Node B


cell

1 2 3 1 2 3
Target
cell

UE moves to
cell #3 under UE
another Node B
SharedHSDPAFlowControlAllocation
Black area: capacity used by HSDPA connections
Red area: SharedHSDPAAllocation reservation from the
VCC
Blue area: RNC CAC view of the capacity reserved from
the VCC for R99 connections
White area: unused capacity (in fact part of the blue can be
unused as well as it illustrates only the reservation)

SharedHSDPAAllocation

SHFCA *
UserPlane VCC Size
R99 reservation level from the VCC

The SharedHSDPAFlowControlAllocation *) SHFCA= SharedHSDPAFlowControlAllocation


sets an upper limit to the allowed HSDPA
bandwidth – even if there was capacity available
at the VCC
SharedHSDPAAllocation and ReleaseTimer
Black area: capacity used by HSDPA connections
Red area: SharedHSDPAAllocation reservation from the
t2-t1 = ReleaseTimerForSharedHSDPAallocation VCC
3min Blue area: RNC CAC view of the capacity reserved from
the VCC for R99 connections
White area: unused capacity (in fact part of the blue can be
t1: the last MAC-d flow from t2: the SharedHSDPAAllocation
unused as well as it illustrates only the reservation)
a the ATM route is removed is released

SharedHSDPAAllocation

SHFCA *
UserPlane VCC Size
R99 reservation level from the VCC

no transport is set up for the


new MAC-d users on that ATM
*) SHFCA= SharedHSDPAFlowControlAllocation
route
SharedHSDPAallocation and
SharedHSDPFlowControlAallocation
• If the Iub interface is using 1 E1:
• SharedHSDPAFlowControlallocation =1.5 Mbits/s
• SharedHSDPAallocation: 0.6Mbit/s

• If the Iub interface is using 2 E1 :


• SharedHSDPAFlowControlallocation =3 Mbits/s
• SharedHSDPAallocation: 1Mbit/s
• If the Iub interface is using 3 E1 :
• SharedHSDPAFlowControlallocation =3.4 Mbits/s
• SharedHSDPAallocation: 1.8Mbit/s