HSDPA Parameters Partner v1

1 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential

HSDPA ParametersVer. 1

Nokia RNWP2006 Sept


• 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• 5 HS-PDSCH codes (SF16)• 1 HS-SCCH code (SF128)

HSDPA Activation


Directed RRC Connection Setup for HSDPA (1/2)• DirectedRRCEnabledThe 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 cell1: Directed RRC connection setup is enabled in the cell2: Directed RRC connection setup for HSDPA layer is enabled in the cell

Wei Yun

Note

only between 2 carriers with same sectorID; if 3 carriers or 2 carriers with different sectorID, then cannot DRRC


Directed RRC Connection Setup for HSDPA (2/2)• Directed RRC connection setup for HSDPA layer cannot be used

simultaneously in the cell with Directed RRC connection setup feature (load based).

• (Load based) Directed RRC connection setup would move also potential HSDPA users away from HSDPA supporting cell.

• When Directed RRC connection setup for HSDPA layer is used, the maximum number of cells (layers) in one sector of the base station that can be configured is two.

• If three-layer network is used one of the DCH layers (not supporting HSDPA) has to have different Sector Identifier in base station than in layers (DCH layer and HSDPA layer) where the Directed RRC connection setup for HSDPA layer is supported.


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• HSDPAPriority• PtxTargetHSDPA• PtxOffsetHSDPA• WinLCHSDPA

Wei Yun

Highlight


Power Allocation

PtxMaxHSDPAThe parameter defines the maximum allowed HSDPA transmission power.

Range and step 0...50 dBm, step 0.1 dBmDefault value 37.8 dBm (6W)Modification Requires object locking

Wei Yun

Note

CHT set 8W


Power AllocationPtxTargetHSDPADepending on the setting of the parameter HSDPAPriority, either the total transmitted carrier power or the

total non-controllable transmitted power has to be below or equal to PtxTargetHSDPA before the first MAC-d flow can be allocated in the cell.

If at least one MAC-d flow is allocated in the cell, PtxTargetHSDPA is used instead of PtxTarget as a target of PtxnonHSDPA in NRT DCH scheduling.

Range and step -10...50 dBm, step 0.1 dBmDefault value 38.5 dBm

PtxOffsetHSDPAThe target value of the transmitted non-HSDPA power (PtxTargetHSDPA) can be exceeded by the value of this

parameter before the cell is considered to be overloaded in the downlink.If the averaged PtxnonHSDPA exceeds or equals PtxTargetHSDPA+ PtxOffsetHSDPA, depending on the setting

of the parameter HSDPAPriority, overload control actions targeted either to MAC-d flows or NRT DCHs are started.

Range and step 0...6 dB, step 0.1 dBDefault value 0.8 dB


HSDPA PriorityThe parameter defines the relative priority between NRT DCHs and MAC-d flows.HSDPAPriority=1When the first MAC-d flow in the cell is allocated, the total non-controllable

transmitted power has to be below or equal to PtxTargetHSDPA, before the HS-DSCH can be selected.

If the averaged PtxnonHSDPA exceeds or equals PtxTargetHSDPA+ PtxOffsetHSDPA, the overload control actions are targeted primarily to NRT DCH(s). Only if there are no more NRT DCH(s) in the cell, all MAC-d flows in the cell are released.

HSDPAPriority=2When the first MAC-d flow in the cell is allocated, the total transmitted carrier power

has to be below or equal to PtxTargetHSDPA, before the HS-DSCH can be selected.If the averaged PtxnonHSDPA exceeds or equalsPtxTargetHSDPA+ PtxOffsetHSDPA,

the overload control actions are targeted to MAC-d flows and all MAC-d flows in the cell are released.


Power allocation

Max power

Node-B Tx powerHSDPAPriority =1

• Event A: First MAC-d flow entering the cell

PtxNC<=PtxtargetHSDPA-> HS-DSCH is selected, otherwise

DCH scheduling.• When HSDPA power is in use:

PtxNC target is Ptxtarget. NRT DCH scheduling uptoPtxtargetHSDPA.

• Event B:PtxnonHSDPA>=PtxtargetHSDPA

+PtxoffsetHSDPA- Overload control actions for NRT DCH(s) started

• Event C:PtxnonHSDPA>=PtxtargetHSDPA

+PtxoffsetHSDPA- No more NRT DCHs, all MAC-d flows in the cell are released

A

Ptx_offset_HSDPAPtxnonHSDPA

PtxNC

Ptx_target_HSDPA

B

Ptxtotal

Ptx_target

C

PtxMaxHSDPA

Wei Yun

Note

can be understand as priority RT > HSDPA > NRT


Power allocationHSDPAPriority =2

• Event A: First MAC-d flow entering the cell

Ptxtotal<=PtxtargetHSDPA-> HS-DSCH is selected, otherwise

DCH scheduling.• When HSDPA power is in use:

PtxNC target is Ptxtarget. NRT DCH scheduling uptoPtxtargetHSDPA.

• Event B:PtxnonHSDPA>=PtxtargetHSDPA

+PtxoffsetHSDPA- All MAC-d flows in the cell released

• Event C: (normal NRT DCH overload control)

Ptxtotal>=Ptxtarget+Ptxoffset- Overload control actions for NRT DCH(s) started

A B C

Max power

Node-B Tx power

Ptx_offset_HSDPA

PtxnonHSDPA

PtxNC

Ptx_target_HSDPA

Ptxtotal

Ptx_target

Ptx_offset

PtxMaxHSDPA

Wei Yun

Note

can be understand as HSDPA having the lowest priority

Wei Yun

Note

release HSDPA means release the while MAC-d


PtxtargetHSDPA AND PtxoffsetHSDPA

STRATEGY: 1) The ratio between PC headroom and Variable Power shall remain the same after the introduction of HSDPA becauseHSDPA does not require any power control headroom

2) When HSDPA power is allocated DCH Power increases to to keep BLER targets, so in order to avoid HSDPA power to be allocated and soon released DCH power increase << PtxoffsetHSDPA


Power Allocation (CHT)

PtxmaxHSDPA

CPICHCPICH

20W

12W

43dBm

40.8dBm

39.8dBm

33dBm2W

9.5W

8W

PtxoffsetHSDPA

2W 33 dBm

15.8W

20W

42 dBm

43 dBm

DCH + Variable part of CCHs

PtxTargetHSDPADCH + Variable part of CCHs

Ptxoffset

PtxTarget

HSDPAPriority =1


HS-DSCH & MAC-d release• HS-DSCH (HSDPA Transport Channel) is released when either UTILIZATION

or THROUGHPUT indicates inefficient use of resources.• Low Utilisation indication is send when

• MAC-d flow throughput is below MACdflowutilRelThr• And there is no more data in the BTS buffer (normal release).

• Low Throughput indication is send when• MAC-d flow throughput is below MACdflowthroughputRelThr• Even when there is still data in the BTS RLC buffer but it cannot be sent

(abnormal release).• If the release of the MAC-d flow is caused by low throughput, the UE is not

allowed to use HS-DSCH until the HS-DSCH guard timer has expired due to low throughput (RNP parameter HsdschGuardTimerLowThroughput, def. 30s)

• Associated UL DCH needs to released also (InactivityTimer), when HS-DSCH is released


HS-DSCH & MAC-d release: low utilisation

Throughput

PDUs in buffer

MACdflowUtilRelThr (Def: 256bps)

MACdflowthrougputRelThr (Def: 0bps)

MACdflowUtilTimetoTrigger (Def: 0s)

Low utilization indication


HS-DSCH & MAC-d release : low throughput

Throughput

PDUs in buffer

MACdflowUtilRelThr (Def: 256bps)

MACdflowthrougputRelThr (Def: 0bps)

MACdflowUtilTimetoTrigger(Def: 0s)

Low throughput indication

MACdflowThroughputTimetoTrigger(Def: 0s)

HsdschGuardTimerLowThroughput, (Def: 30s, CHT: 5s)

Wei Yun

Note

after the guard time, can ask for HSDPA reestablishment if buffer still not empty


HS-DSCH & MAC-d release

UE moved to Cell FACH

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). Or

• MAC-d flow has low throughput and UL NRT DCH can be released (InactivityTimer). In this case UE specific timer HsdschGuardTimerLowThroughput 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 released


MACdflowutilRelThr(Low utilization threshold of the MAC-d flow)

• This parameter defines the low utilization threshold of the throughput measurement of the MAC-d flow.

• The threshold is defined as a number of bits per second.• The throughput measurement measures the number of bits transmitted

by MAC-d during the sliding measurement window. The sliding measurement window is defined with the parameter MACdflowthroughputAveWin.

• If the result of the throughput measurement is lower than or equal to the threshold, the MACdflowutilTimetoTrigger timer is started.

• Range and step 0...64000 bps, step 256 bps• Default value 256 bps


MACdflowutilTimetoTrigger(Low utilization time to trigger of the MAC-d flow )

• This parameter defines the low utilization time to trigger timer of the throughput measurement of the MAC-d flow.

• If the result of the throughput measurement is lower than or equal to the MACdflowutilRelThr, the MACdflowutilTimetoTrigger is started.

• If the result of the throughput measurement is higher than the MACdflowutilRelThr, the MACdflowutilTimetoTrigger is stopped and reset.

• If the MACdflowutitTimetoTrigger expires, the number of RLC PDUs in the transmission windows is checked:

• If the sum of the RLC PDUs in the transmission windows of the NRT RBsmapped to the MAC-d flow equals zero, L2 sends a low utilisationindication to L3 and resets the MACdflowutilTimetoTrigger.

• If there are any RLC PDUs in the transmission windows, L2 keeps checking the transmission windows until they are empty or the downlink throughput goes above MACdflowutilRelThr.

• Range and step 0...300 s, step 0.2 s• Default value 0 s


MACdflowthroughputRelThr(Low throughput threshold of the MAC-d flow)

• This parameter defines the low throughput threshold of the throughput measurement of the MAC-d flow.

• The threshold is defined as a number of bits per second.• The throughput measurement measures the number of bits transmitted

by MAC-d during the sliding measurement window. • The sliding measurement window is defined with the parameter

MACdflowthroughputAveWin. • If the result of the throughput measurement is less than or equal to the

threshold, the MACdflowthroughputTimetoTrigger timer is started.• Range and step 0...64000 bps, step 256 bps• Default value 0 bps


MACdflowthroughputTimetoTrigger(Low throughput time to trigger of the MAC-d flow)

• This parameter defines the low throughput time to trigger timer of the throughput measurement of the MAC-d flow.

• If the result of the throughput measurement is lower than or equal to the MACdflowthroughputRelThr, the MACdflowthroughputTimetoTrigger is started.

• If the result of the throughput measurement is higher than the MACdflowthoughputRelThr, the MACdflowthroughputTimetoTrigger is stopped and reset.

• If the MACdflowthroughputTimetoTrigger expires, L2 sends the low throughput indication to L3 and resets the MACdflowthroughputTimetoTrigger.



MACdflowthroughputAveWin(Window size of the MAC-d flow throughput measurement)

• This parameter defines the averaging window size for the throughput measurement of the MAC-d flow.

• The throughput measurement measures the number of bits transmitted by MAC-d during the sliding measurement window.

• The sliding measurement window is defined with the parameter MACdflowthroughputAveWin.

• Value 0 means that the MAC-d flow throughput measurement is not activated.



HSDSCHGuardTimerLowThroughput(HS-DSCHguard timer due to low throughput)

• HSDSCHGuardTimerLowThroughput is a UE-specific timer. • It is started after a release of the MAC-d flow, which was triggered by low

throughput. • When the timer is running HS-DSCH allocation is not allowed to the UE.• Range and step 0...240 s, step 1 s• Default value 30 s• Proposed Value: 5s


• General• Power Allocation• MAC-d flow utilization & throughput measurement• Associated UL Channel Bit Rate• Mobility


Physical Channels for One HSDPA UE

UE

BTS

Asso

ciat

edDP

CHAs

soci

ated

DPCH

1-15

x H

S-PD

SCH

1-4

x HS

-SCC

H

HS-D

PCCH

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)• 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-

DPSCH frame.• Fixed SF128

• Associated DPCH, Dedicated Physical Channel.

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

Rel99 DCH

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


Associated UL Channel Bit Rate- General

• In order to use HS-DSCH as a downlink transport channel, an HSDP Aassociateduplink 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), the RNC attempts to allocate a return channel with the highest possible bit rate.

• If the traffic volume measurement indicates Low traffic volume(TrafVolThresholdULLow), 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.


Planning parameters in RAN05UL return channel

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

• HSDPAminAllowedBitrateUL• 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






HSDPA mobility in RAS05 CD1 (1)- HSDPA Serving Cell Change

• HSDPA Serving Cell Change

•HSDPA (serving cell) -> MR(e1a, serving cell) -> Cell_FACH (Target Cell) -> HSDPA (Target Cell)

HS-DSCH coverage HS-DSCH coverage

Service in HSDPA

(Serving Cell)

Switching to Cell_FACH (Target

Cell) within the SHO area

UE on HS-DSCH(Target Cell)

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps

128kbps or 384kbps according to parameter settings


Details on Cell Change via cell-FACH• HSDPA Serving Cell Change via Cell-FACH feature is used only in intra

frequency handover cases, in case of IFHO or ISHO the original DCH switching procedures are used

• If the user was moved to Cell-FACH because of intra frequency handover no HSDPA user penalty timers are used on Cell-FACH, the user will be immediately switched to a new HSDPA connection when there is a data volume request either from the UE or RNC

• If the user was moved to Cell-FACH because of low throughput then the HSDPA user penalty timers are used on Cell-FACH

• If the HSDPA user moves to non-HSDPA cell, the user in HO area will be moved to Cell-FACH. The user will be immediately switched to the DCH of the requested bit rate when there is a data volume request either from the UE or RNC (no need for first DCH0/0 DCH Initial bit rate DCH Final bit rate)


CHANNEL TYPE SELECTIONHS-DSCH is selected if all of the following conditions are met:1. Traffic class and traffic handling priority are allowed on HS-DSCH

• The operator can configure which traffic classes and handling priority are allowed to be used with HSDPA with HSDSCHQoSclasses parameter.

• RAN05 only interactive and background traffic classes are supported2. UE capability supports HS-DSCH3. The cell supports HSDPA and HS-DSCH is enabled in the cell4. No multi-RAB (RAN05) or supported multi-RAB combination (RAN05.1)

• No multiRAB in RAN05• AMR + HSDPA possible in RAN05.1

5. The number of simultaneous HS-DSCH allocations in the BTS/cell is below the maximum number.6. HsdschGuardTimerHO and HsdschGuardTimerLowThroughput guard timers are not runnig

• Both guard timers are operator-configurable parameters7. UE is not performing inter-frequency or inter-system measurements8. Active set size = 1 (RAN05)9. UE does not have DCHs scheduled with bit rates higher than 0kbps.10. HS-DSCH physical layer category is supported11. If there is no existing MAC-d flow in the cell, condition (A or B, depending on the HSDPApriority parameter)

has to be valid.A) PtxNC<=PtxtargetHSDPAB) Ptxtotal<=PtxtargetHSDPA


Planning parameters in RAS05 for Mobility control• HSDPAFMCS/I/Gidentifier

• Identifies parameter set for inter-/intra-frequency and inter-system measurements of a user having HS-DSCH transport channel allocated through RRC: Measurement Control message.

• HSDPA Addition Window• HSDPA Addition Time

• HSDPAHOPSidentifier• Identifies parameter set for intra-frequency HOs of a user having HS-DSCH transport

channel allocated through RRC: Measurement Control message .

• HSDPA Enable RRC Release• HSDPA Release Margin Average EcNo• HSDPA Release Margin Peak EcNo

• HsdschGuardTimerHO• Defines time when HS-DSCH allocation is not allowed for a UE, after successful

channel type switching to DCH due to any HO reasons.• Default, 5s.

• HSDPARRCdiversity (SHO of HSDPA capable UE)• Enables/disables diversity HO of the stand-alone signalling link after successful RRC

connection setup for the HSDPA capable UE.

Wei Yun

Note

need to set for slower HO as no SHO supported, when cell change is needed, throughput will need to downgrade to 0kbps 1st


Mobility Parameters relevant to HSDPA

FMCS FMCI FMCGAddition Window (1A) IFHO caused by CPICH Ec/No GSM HO caused by CPICH Ec/NoAddition Time (1A) IFHO caused by CPICH RSCP GSM HO caused by CPICH RSCPAddition Reporting Interval (1A) IFHO caused by UE TX Power GSM HO caused by UE TX PowerCPICH Ec/No Filter Coefficient UE TX Power Filter Coefficient UE TX Power Filter CoefficientCPICH Ec/NO HHO Threshold (1F) UE TX Power Threshold for NRT PS UE TX Power Threshold for NRT PSCPICH Ec/NO HHO Time Hysteresis (1F)CPICH RSCP HHO Filter CoefficientCPICH RSCP HHO Threshold (1F)CPICH RSCP HHO Time Hysteresis (1F)

HOPSHHO Margin for Average Ec/NoHHO Margin for Peak Ec/NoRelease Margin for Average Ec/NoRelease Margin for Peak Ec/NoCPICH Ec/No Averaging WindowEnable RRC Connection Release


Measurement Events for HSDPA Mobility• Triggering Events for Channel Type Switching

UE Tx power exceeds the absolute threshold-channel switching to DCH 0/0 kbps

6A

A primary CPICH goes below the absolute threshold -channel switching to DCH 0/0 kbps

1F

A primary CPICH enters the reporting range-channel switching to Cell_FACH

1A

DescriptionEvent

• 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.

Wei Yun

Note

inter-freq or inter-system HO


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.

Wei Yun

Note

for RT, no SHO allowed during RRC->RB state, only allowed after RB for NRT, no SHO allowed during RRC->HSDPA allocation (after the 1st RB reconfig for min bit rate)


• The RNC ignores the parameter value (and allows diversity handover of standalone signalling link) if measurement event 1A is received and the reported CPICH Ec/No of the entering cell meets the following conditions (that is, the threshold to perform HS-DSCH to Cell_FACH transition is exceeded):

(1) EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n)

(2) AveEcNoDownlink + ReleaseMarginAverageEcNo(n) < AveEcNoNcell(n)

EcNoDownlink :CPICH Ec/No of the serving cellEcNoNcell(n) : CPICH Ec/No of the entering cell AveEcNoDownlink : averaged CPICH Ec/No of the serving cellAveEcNoNcell(n) : averaged CPICH Ec/No of the entering cell

• The comparison is applied when a cell has entered the reporting range, and triggered event 1A, and RNC has not added the cell into the active set.

• In this case, the UE reverts to periodical reporting and continues reporting after the initial report by switching to the periodical measurement reporting mode.

• ReleaseMarginPeakEcNo(n) determines the maximum allowed difference between the CPICH Ec/No of the entering cell (n) and the CPICH Ec/No of the serving cell so that active set update is not executed.

• ReleaseMarginAverageEcNo(n) determines the maximum allowed difference between the averaged CPICH Ec/No of the entering cell(n) and the averaged CPICH Ec/No of the serving cell correspondingly.

• The HSDPA-specific HOPS parameters are used in the equation.

HSDPARRCdiversity (2/4)- Diversity handover of stand-alone signalling link - Exception


HSDPARRCdiversity (3/4)- Diversity handover of stand-alone signaling link

Ec/No

P CPICH 2

DCH AdditionWindow

P CPICH 1

Call StartHSDPARRCDiversity: Not Allowed

Addition Window (HSDPA FMCS) = 0dBAddition Time (HSDPA FMCS) = 1280msEcNo Filter coefficient (HSDPA FMCS) = 800msSHO of the HSDPA Capable UE (RNC) = disabledEnable RRC release (HSDPA HOPS) = enabledRelease Margin Average EcNo (HSDPA HOPS) = 2dBRelease Margin Peak EcNo (HSDPA HOPS) = 3.5 dBEcNo Averaging Window (HSDPA HOPS) = 8

ReleaseMarginAverageEcNoReleaseMarginPeakEcNo

Periodic MR (e1A)

DCH Addition Time

ASU

DCH DeletionWindow

DCH Deletion Time

MR (e1B)

ASU

2 Active Set

HSDPA

Allocation

Stand-alone SignallingLink

Wei Yun

Note

1st RB reconfig right before HSDPA allcation


HSDPARRCdiversity (4/4)- Diversity handover of stand-alone signaling link

Ec/No

P CPICH 2

DCH AdditionWindow

P CPICH 1

Call StartHSDPARRCDiversity: Not Allowed


Periodic MR (e1A)

DCH Addition Time

ASU

DCH DeletionWindow

DCH Deletion Time

MR (e1B)

ASU

Stand-alone SignallingLink

DCH Allocation

HSDPA Resumption Timer

HSDPA Allocation

* HSDPA enabled for both Serving & Target Cells

Wei Yun

Note

1st RB reconfig when having 2 AS, therefore cannot allocate HSDPA and go into DCH allocation only


EnableRRCrelease (1/4)- disabled

Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is disabled:

UE is transferred to the CELL_FACH state and the radio bearer is mapped tothe FACH with the RRC: Radio bearer reconfiguration procedure.


EnableRRCrelease (2/4)- disabled

time

Ec/No

HSDPA AdditionTime

MR(e1A)

HSDPA AdditionWindow

P CPICH 1

HSDPA allocation FACH cell updateAddition Window (HSDPA FMCS) = 0dBAddition Time (HSDPA FMCS) = 1280msEcNo Filter coefficient (HSDPA FMCS) = 800msSHO of the HSDPA Capable UE (RNC) = disabledEnable RRC release (HSDPA HOPS) = disabledRelease Margin Average EcNo (HSDPA HOPS) = 2dBRelease Margin Peak EcNo (HSDPA HOPS) = 3.5 dBEcNo Averaging Window (HSDPA HOPS) = 8

RB_Reconfiguration(FACH)


Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is enabled:

For users other than HS-DSCH allocated, EnableRRCRelease indicates whether the RRC connection release (excluding emergency calls) is allowed due to non-optimum fast closed loop power control.

For users with a HS-DSCH, If the RNC receives measurement event 1A and the EnableRRCRelease parameter is enabled, HS-DSCH MAC-d flow release is not allowed to be triggered directly.

When a cell has entered the reporting range and triggered event 1A and the RNC has not added the cell into the active set, the UE reverts to periodical reporting. This means that the UE continues reporting after the initial report by switching to periodical measurement reporting mode.

As the EnableRRCRelease parameter is enabled, the RNC’s decision on HSDSCH MAC-d flow release is based on CPICH Ec/No of the serving cell (EcNoDownlink), CPICH Ec/No of the neighbouringcell (EcNoNcell) and the ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo control parameters.

Based on the periodic measurement reporting mode and the control parameters, the UE is transferred to the CELL_FACH state and the radio bearer is mapped to the FACH with the RRC: Radio bearer reconfiguration procedure if the following conditions are effective:

(1) EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n)(2) AveEcNoDownlink + ReleaseMarginAverageEcNo(n) < AveEcNoNcell(n)

EnableRRCrelease (3/4) - enabled


EnableRRCrelease (4/4)- enabled

time

Ec/No

HSDPA AdditionTime

Periodic MR(e1A)

HSDPA AdditionWindow

P CPICH 1

HSDPA allocation FACH cell updateAddition Window (HSDPA FMCS) = 0dBAddition Time (HSDPA FMCS) = 1280msEcNo Filter coefficient (HSDPA FMCS) = 800msSHO of the HSDPA Capable UE (RNC) = disabledEnable RRC release (HSDPA HOPS) = enabledRelease Margin Average EcNo (HSDPA HOPS) = 2dBRelease Margin Peak EcNo (HSDPA HOPS) = 3.5 dBEcNo Averaging Window (HSDPA HOPS) = 8


RB_Reconfiguration(FACH)

Wei Yun

Note

different between disable and enable this parameter is: delaying the RB reconfig to FACH


HsdschGuardTimerHOHS-DSCH guard time after switching to DCH due to HOThe 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 sDefault value 5 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)• HSDPA resumption timer switches

the user from DCH to HS-DSCH, when UE enters HSDPA area

The conditions preventing HSDPA allocation in HSPDA coverage area to HSDPA capable UE are:

• More than one serving cell (Soft Handover)• Multi-RAB combination (not supported)

• Lack of HSDPA capacity in the cell

R99 coverage HS-DSCH coverage

Service NRT DCH

Switching to HS-DSCH when not in SHO area

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps (initial bitrate)

128kbps or 384kbps according to parameter settings

Download complete


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.


DCH to HS-DSCH switch (test case in NTN)• Resumption timer started

when Active set size =1.• Resumption timer value in

this case 4s.• Switching to HS-DSCH tried

after the timer expires.

Application throughput

0

500000

1000000

1500000

0 10 20 30 40 50s

bps

"MEASUREMENT_CONTROL"DCCH08:33.1RRCD

"RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:32.8RRCU

"MEASUREMENT_REPORT"DCCH08:32.8RRCU

"RADIO_BEARER_RECONFIGURATION"DCCH08:31.7RRCD

"MEASUREMENT_REPORT"DCCH08:30.7RRCU


"RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:30.5RRCU

"RADIO_BEARER_RECONFIGURATION"DCCH08:29.3RRCD


"ACTIVE_SET_UPDATE_COMPLETE"DCCH08:24.8RRCU

"ACTIVE_SET_UPDATE"DCCH08:24.8RRCD

MessageSubchannelTimeEventIdActive set size=1 after this Active Set Update (no SHO anymore). Resumption timer started.

RB reconfiguration to DCH0/0. 4s resumption timer applied before.

RB reconfiguration to HS-DSCH

~2.5 seconds gap according signaling. The data gap is about 6s

when measured with Ethereal.

DCH NRT HS-DSCH


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.

Wei Yun

Highlight

Documents

HSDPA Parameters Partner v1