HSPA Planning Training

8/10/2019 HSPA Planning Training

http://slidepdf.com/reader/full/hspa-planning-training 1/118



2 © Nokia Siemens Networks Presentation / Author / Date

Soc Classification level

Module 4 – HSDPA Parameters and RRM

Objectives

After this module the participant shall be able to:-

• Understand the functionality of HSDPA RRM in Nokia RAN

• Know the main RNC parameters controlling the HSDPA

functionality in Nokia RAN





Module Contents

• HSDPA resource handling

• Channel type switching

• HSDPA mobility handling

• HSDPA channel type selection

• HSDPA with additional RAB initiation

• HSDPA associated uplink DPCH scheduling

• HSDPA code multiplexing






http://slidepdf.com/reader/full/hspa-planning-training 6/1186 © Nokia Siemens Networks Presentation / Author / Date


Module Contents


• HSDPA Dynamic Resource Allocation

• HSDPA (Static) Resource Allocation

• Maximum bit rate of HS-DSCH MAC-d flow

• Code allocation of HS-SCCH physical channels








http://slidepdf.com/reader/full/hspa-planning-training 7/1187 © Nokia Siemens Networks Presentation / Author / Date


Module Contents


• HSDPA Dynamic Resource Allocation• Dynamic power allocation

• Dynamic NRT DCH scheduling

• Admission decision and overload control

• Prioritisation between HSDPA and NRT DCH power resources

• Dynamic allocation of HS-PDSCH codes








HSDPA Dynamic Resource Allocation

• Optional feature HSDPA Dynamic Resource Allocation contains the following

new and improved functionalities• Dynamic power allocation

• HSDPA power limitation not sent from RNC to BTS, always dynamic in BTS


• Prioritisation between NRT DCH and HSDPA traffic/power


• RNC applies HSDPA dynamic resource allocation if

• Parameter HSDPADynamicResourceAllocation is set to ‘Enabled’

• RNC receives capability indication from the BTS (Node B) with regards to dynamic

resource allocation





HSDPA power allocation methods

HSDPADynamicResource- Allocation

RNC sends the

PtxMaxHSDPA

to BTS

BTS allocates the

available DL power

dynamically to

HSDPA until PtxMaxHSDPA

Disabled

BTS allocates the

available DL power dynamically

toHSDPA until Cell max

DL power

Enabled

RNC schedules NRT DCH

according to HSDPApriority

RNC schedules NRT DCH

using dynamic NRT

scheduling

HSDPA (Static)

Resource Allocation

HSDPA dynamic

Resource Allocation





Module Contents



• Dynamic power allocation




• Dynamic allocation of HS-PDSCH codes• HSDPA (Static) Resource Allocation







Dynamic power allocation

• BTS allocates all unused DL power up to the max cell power

• All the power available after DCH traffic, HSUPA control channels and common channels

can be used for HSDPA

• PtxMax is the cellmaximum outputpower defined bythe managementparameter

PtxCellMax and theBTS capability(MaxDLPowerCapability )

PtxNC

PtxNRT

PtxHSDPA

PtxMax

PtxNonHSDPA





Module Contents






• Dynamic allocation of HS-PDSCH codes• HSDPA (Static) Resource Allocation







Dynamic NRT DCH scheduling

• RNC affects the HSDPA power allocation indirectly by scheduling NRT DCH bit

rates

• When there is at least one HS-DSCH MAC-d flow allocated in the cell,

PtxTargetPS is used for packet scheduling and handover control purposes

• PtxTargetPS is adjusted between PtxTargetPSMin and PtxTargetPSMax

• PtxTargetPSAdjustPeriod defines the adjustment period for the PtxTargetPS in

terms of Radio Resource Indication (RRI) reporting periods

• If PtxTargetPSMax and PtxTargetPSMin are set to the same value, RNC does

not adjust PtxTargetPS Dynamic NRT DCH scheduling disabled

PtxTargetPSMin PtxTargetPS PtxTargetPSMax





Dynamic NRT DCH scheduling

With no active HSDPA users:

1) NRT DCH scheduling to thePtxTarget+PtxOffset &RT DCH admission

to PtxTarget

With active HSDPA users:

2) NRT DCH scheduling to PtxTargetPS3) RT DCH admission to PtxTarget

HSDPA activeNo HSDPA users No HSDPA users

PtxTarget

+PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

1

2

3

PtxNonHSPA

PtxTotal





Dynamic NRT DCH scheduling – Adjustment

• Initial value of the PtxTargetPS is the lower from the following ones: PtxTarget or

PtxTargetPSMax

• Initial value is taken into use when the first HS-DSCH MAC-d flow is setup

• Usage ends when the last HS-DSCH MAC-d flow is deleted

• PtxTarget remains as a target for non-controllable load even if there are one or more

HS-DSCH MAC-d flows setup in the cell

• PtxTargetPS is adjusted based on received PtxTotal (Transmitted Carrier Power)

and PtxNonHSPA

• PtxNonHSPA = Transmitted carrier power of all codes not used for HS-PDSCH, HS-

SCCH, E-AGCH, E-RGCH or E-HICH transmission

• PtxTargetPS is adjusted only when there are NRT DCH users - in addition to the

HS-DSCH MAC-d flow(s) - in the cell.

• Adjustment of the PtxTargetPS is done in fixed steps, defined by the

PtxTargetPSStepUp and PtxTargetPSStepDown management parameters







Dynamic NRT DCH scheduling – Power congestion

1) Power congestion for HSDPA:

PtxTotal ≥ PtxHighHSDPAPwr

2) Power congestion for NRT DCH:

PtxNonHSPA ≥ (PtxTargetPS – 1 dB)

HSDPA active

PtxTarget

+PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

1

2

PtxNonHSPA

PtxTotalPtxHighHSDPAPwr





• Target (ideal) value for the PtxTargetPS is calculated for each adjustment period defined

by the management parameter PtxTargetPSAdjustPeriod

• Target (ideal) value for the PtxTargetPS is calculated as follows (in a linear fashion):

• Pmax is the cell maximum transmission power

• Ptx_nc is the total non-controllable transmitted DL power

• PSMax is the maximum allowed value for PtxTargetPS defined by the management parameter

PtxTargetPSMax

• PSMin is the minimum allowed value for PtxTargetPS defined by the management parameter

PtxTargetPSMin

• WeightRatio is the relative weight of DCH , i.e. WeightDCH / (WeightHSDPA + WeightDCH)

• WeightHSDPA is the summed weight of the HS-DSCH radio access bearers (MAC-d flows) and

WeightDCH is the summed weight of the NRT DCH radio access bearers

Dynamic NRT DCH scheduling – Ideal PtxTargetPS

PtxTargetPSTarget = MAX {MIN {P tx_nc + [(P max - P tx_nc ) x Weight Ratio], PSMax }, PSMin}

Current available power for NRT DCH + HSDPA





Dynamic NRT DCH scheduling – Example

• Pmax (cell maximum transmission power) = 20W (43 dBm)

• PtxTargetPSMax = 13W (41,14 dBm)• PtxTargetPSMin = 4W (36,02 dBm)

• Ptx_nc (total prevailing non-controllable DL load) = 5W

• 1 NRT DCH user (THP1, weight 0.9) + 1 HSDPA user (THP1, weight 1.0) + 1

HSDPA user (BG, weight 0.25)

WeightRatio = 0.9 / (1+0.25 + 0.9) = 0.42

• Target (ideal) NRT DCH scheduling target =

PtxTargetPSTarget = MAX{MIN{5W+[(20W-5W)x0.42],13W}, 4W} = 11.3W

Current available power for NRT DCH + HSDPA = 15 W





MAC-d flow(s) setup in the cell

NRT DCH user(s) in the cell

PtxTotal received

Yes

PtxTotal >=PtxHighHSDPAPwr

NoPtxTargetPS >

PtxTargetPSTarget

Yes

No decrease

Check increase

No

Decrease PtxTargetPS

Dynamic NRT DCH scheduling – PtxTargetPS decrease

• PtxTargetPS is decreased if

• PtxTotal > PtxHighHSDPAPwr= HSDPA power congestion

& PtxTargetPS > PtxTargetPSTarget

• Above target value

• Amount of decrease is determined

by the management parameter

PtxTargetPSStepDown, but limited

to

• PtxTargetPS ≥ PtxTargetPSTarget

PtxTargetPSTarget = target (ideal)value of the NRT DCH

scheduling target





Dynamic NRT DCH scheduling – PtxTargetPS increase

• PtxTargetPS is increased if

• PtxNonHSPA > PtxTargetPS - 1 dB

= Power congestion on DCH

& PtxTargetPS < PtxTargetPSTarget

• Below target value

• Amount of increase is determined by

the management parameterPtxTargetPSStepUp

PtxTargetPSTarget = target (ideal)value of the NRT DCH

scheduling target

MAC-d flow(s) setup in the cell

NRT DCH user(s) in the cell

PtxNonHSPA received

Yes

PtxNonHSPA >=

(PtxTargetPS - 1 dB)

Yes

No increaseCheck decrease

No

Increase PtxTargetPS

NoPtxTargetPS <

PtxTargetPSTarget





Dynamic NRT DCH scheduling – Summary

1) Power congestion for HSDPA:

PtxTotal ≥ PtxHighHSDPAPwr

Decrease PtxTargetPS downto

PtxTargetPSTarget

2) Power congestion for NRT DCH:PtxNonHSPA ≥ (PtxTargetPS – 1 dB)

Increase PtxTargetPS uptoPtxTargetPSTarget

HSDPA active

PtxTarget +PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

1

2

PtxNonHSPA

PtxTotalPtxHighHSDPAPwr

PtxTargetPSTarget

PtxTargetPSMax

PtxTargetPSMin

Dynamic Power Allocation and NRT Scheduling





Dynamic Power Allocation and NRT Scheduling

Parameters

• HSDPADynamicResourceAllocation

• Range:0 (Disabled), 1 (Enabled), Default:0,

Object:RNC• HSDPApriority

• Range:1 (HSDPA priority 1), 2 (HSDPA priority2), Default:1, Object:RNC

• PtxCellMax

• Range and step: 0..50 dBm, step 0.1 dBm,Default: 43 dBm, Object:WCEL

• MaxDLPowerCapability• Range and step: 0..50 dBm, step 0.1 dBm

Default value: -, Default value notes: Value setby the system, Object: WCEL

• PtxTargetPSMin

• Range:-10..50 dBm, step 0.1 dBm, Default:36dBm, Object:WCEL

• PtxTargetPSMax


• PtxTargetPSAdjustPeriod

• Range:1..255, step 1, Default:10O, bject:WCEL

• PtxTargetHSDPA• Range:-10 … 50 dBm, step 0.1 dBm,

Default:38.5 dBm, Object:WCEL

• PtxOffsetHSDPA

• Range:0 … 6 dB, step 0.1 dB, Default:0.8 dB,Object:WCEL

• PtxTargetPSStepUp

• Range:-0..5 dB, step 0.1 dB, Default:1 dB,Object:WCEL

• PtxTargetPSStepDown

• Range:-0..5 dB, step 0.1 dB, Default:1 dB

• PtxHighHSDPAPwr






Module Contents














DL TX power overload control

• DL TX power overload control is modified to co-operate with the dynamic HSDPApower allocation

• When there is at least one HS-DSCH MAC-d flow allocated in the cell, the targetfor non-controllable load is PtxTarget , and target for NRT DCH packet schedulingis PtxTargetPS

• DL overload control actions are targeted to NRT DCH(s) – not HS-DSCH MAC-dflows

• BTS adjusts power

no DL overload due to HSDPA Tx power• RNC detects DL overload from the non-HSDPA power measurement

• Overload control actions in downlink are started if the following condition is truewhen there are NRT DCH(s) allocated in the cell :

• Ptx_offset is defined by the management parameter PtxOffset

offset tx PS et t tx

HSPAnontx P P P _ _ arg _

_ _





DL TX power overload control

1) DL overload: PtxNonHSDPA ≥ PtxTargetPS + PtxOffset

Decrease NRT PS with (Enhanced) Overload Control

HSDPA active

PtxTarget +PtxOffset

PtxMax

PtxTargetPS

PtxNC

PtxNRT

PtxHSDPA

1

PtxNonHSPA

PtxTotal

PtxTargetPS+

PtxOffset





Module Contents












P i iti ti b t HSDPA d DCH





Prioritisation between HSDPA and DCH resources

• A particular traffic class (THP) can be excluded in determination of weight values by

setting the the traffic class (THP) specific weight value to 0

• Cell level weight is obtained by summing the weight value of each user up

• Weight of an individual user is an averaged weight of its NRT PS radio access bearers

• Weight of an individual user depends on the traffic class and traffic handling priority of its

NRT PS radio access bearers

• Whether user is included in the HSDPA traffic type or NRT DCH traffic type depends

on its allocated transport channel (DCH or HS-DSCH) in downlink

• RT traffic, e.g. AMR speech CS RAB, has always higher priority to NRT DCH and

HSDPA (HS-DSCH MAC-d flow) traffic

P i iti ti b t HSDPA d DCH





Prioritisation between HSDPA and DCH resources

• Weight of an individual user is an averaged weight of its NRT PS radio access

bearers

• Example1:• User1 with 1 AMR speech CS RAB + 1 PS RAB established (I/A THP2 HS-DSCH)

• WeightHSDPATHP2 = 90

• Weight value of the User1 = 90

• Example2:

• User2 with 2 PS RABs established (1 I/A THP1 DCH + 1 B/G DCH)

• WeightDCHTHP1 = 100, WeightDCHBG = 50

• Weight value of the User2 = (100 + 50)/2 = 75

• Cell level weight is obtained by summing the weight value of each user up

• Example3:

• User1: HSDPA weight = 90, User2: DCH weight = 75, User3: HSDPA weight = 100, User4: DCH

weight = 80, User5: DCH weight = 60

• WeightHSDPA

= User1+User3 = 190, WeightDCH

= User2+User4+User5 = 215,

• WeightRatio = 215 / (215 + 190) = 0.53

• Dynamic power allocation algorithm utilises WeightRatio

M d l C t t





Module Contents












HS PDSCH code set





HS-PDSCH code set

• RNC allocates HS-PDSCH codes from the set of codes defined by the managementparameters HSPDSCHCodeSet10 and HSPDSCHCodeSet15 for HSDPA 10 Codes and

HSDPA 15 Codes, respectively

Number of HS-PDSCH codes (full

set)

HSDPA15

Codes

HSDPA10

Codes

Staticcode

allocation

5 X X X6 - - -

7 - - -

8 X X -

9 - - -

10 X X -

11 - - -12 X - -

13 - - -

14 X - -

15 X - -

Default values forHS-PDSCH code

sets

Two UEs: 4 + 4

Two UEs: 5 + 5

Three UEs: 4 + 4 + 4

One UE: 14 practical max.

Maximum code allocation for HSDPA





Maximum code allocation for HSDPA

• Allocation of 15 is not possible when more than 2 HSDPA users active or 1 AMR

user in the cell 15 theoretical value

SF=1

SF=2

SF=4

SF=8

SF=16

SF=32

SF=64

SF=128

SF=256

15 HS-PDSCH codes

Up to three HS-SCCH codes

Codes for common

channels in the cell

Codes for associated DCHs and

non-HSDPA users

Maximum code allocation with HSUPA





Maximum code allocation with HSUPA

• Allocation of 15 is not possible when HSUPA is enabled in the cell

SF=1

SF=2

SF=4

SF=8

SF=16

SF=32

SF=64

SF=128

SF=256

14 HS-PDSCH codes

Up to three HS-

SCCH codes

Codes for common

channels in the cell Codes for associated DCHs and

non-HSDPA users

E-AGCH (256)

E-RGCH/E-HICH (128)

Dynamic code allocation procedure





Dynamic code allocation procedure

• Initial allocation of HS-PDSCH codes (SF=16) is executed in the cell setup phase

• The minimum number of HS-PDSCH codes is allocated initially

• RNC attempts to upgrade HS-PDSCH codes

• 1) In conjunction of the HS-DSCH MAC-d flow setup

• 2) Periodically

• RNC downgrades HS-PDSCH codes

• 1) Periodically• 2) In the case of DPCH code congestion

• RNC applies the timer HSPDSCHAdjustPeriod for periodical HS-PDSCH code

adjustment

• When the first HS-DSCH MAC-d flow is setup in the cell, RNC starts the timer

HS-PDSCH code upgrade - Periodical





HS-PDSCH code upgrade - Periodical

• RNC periodically upgrades HS-PDSCHcodes providing:

1. The number of currently allocated HS-

PDSCH codes is lower than themaximum allowed number of HS-PDSCH codes

2. BTS capability does not limit upgrade

3. Free SF=16 codes, which are adjacentto the currently allocated HS-PDSCHcodes, can be found in order to takethe next higher value from HS-PDSCH

code set into use4. Free SF=16 codes can be found sothat after upgrade number of freeSF=128 codes is greater than or equalto the value defined by themanagement parameterHSPDSCHMarginSF128 (def. 8)

• If the conditions for the periodical

upgrade are effective, the next greatervalue from the HS-PDSCH code set istaken into use.

CodeN HS-PDSCH codes allocated in the code set

HSPDSCHAdjustPeriod

expires

Keep the current number ofHS-PDSCH codes

Enough SF#128 codes

available after upgrade

No

Yes

Yes

Yes

Take the value CodeN+1 fromcode set into use

Cell/BTS capable of

CodeN+1 number of codes

CodeN < CodeMAX

Free SF#16 codes available

for CodeN+1

Yes

HS-PDSCH code downgrade - Periodical





HS-PDSCH code downgrade - Periodical

• RNC periodically downgrades HS-

PDSCH codes providing:

1. Timer for periodical adjustment ofthe HS-PDSCH codes(HSPDSCHAdjustPeriod ) expires

2. The number of currently allocatedHS-PDSCH codes is higher thanthe minimum allowed number of

HS-PDSCH codes

3. The number of currently availableSF128 codes is lower thanHSPDSCHMarginSF128 or thereis(are) no HS-DSCH MAC-d flow(s)setup in the cell.

• If the conditions determined above

are effective, the next lower valuefrom the HS-PDSCH code set istaken into use

CodeN HS-PDSCH codes allocated in the code set

HSPDSCHAdjustPeriod

expires

Yes

CodeN > Code

MIN

Available SF128 codes <HSPDSCHMarginSF128

Yes

Take the value CodeN-1

from

code set into use

Keep the current number of

HS-PDSCH codes

No

No

HS-DSCH MAC-d flow(s) exists YesNo

Code congestion





Code congestion

• RNC downgrades HS-PDSCH code(s) due to DPCH code congestion

• RNC does not downgrade HS-PDSCH codes lower than the minimum allowed

number of HS-PDSCH codes

• If RT request is congested due to lack of DPCH code(s), HS-PDSCH codes are

downgraded in order to admit RT request

• If NRT DCH scheduling is congested due to lack of DPCH code(s), HS-PDSCH

codes are downgraded in order to admit NRT DCH request

• # HS-PDSCH codes > DPCHOverHSPDSCHThreshold

• The number of HS-PDSCH codes after downgrade will be the highest possiblefrom the HS-PDSCH code set

Code congestion – HS-DSCH code downgrade





Code congestion HS DSCH code downgrade

• Periodical HS-DSCH code

downgrade if the number of

currently available SF128codes is lower than

HSPDSCHMarginSF128

• HS-DSCH code downgrade

due to NRT DCH code

congestion is allowed if

number of currently allocated

HS-PDSCH codes is greater

thanDPCHOverHSPDSCHThresh

old N u m b e r o f a l l o c a t e d S F 1 6 c o d e s

N u m b e r o f r e s e r v e d S

F 1 2 8 c o d e s

DPCHOverHSPDSCHThreshold

6

78

9

10

11

12

1314

15 Maximum in

code set

HSPDSCHMarginSF128

5

38

48

58

68

78

8898

108118

128

0

Code tree optimisation





Code tree optimisation

• After upgrade of the HS-PDSCH codes triggering condition of the code tree

optimisation procedure is checked

• Code change procedure tries to re-arrange the DPCH codes in order to make

room for HS-PDSCH code upgrade

• If there are DPCH codes in the shared code area, the following conditions andrules are checked each time a DPCH code is released:

1. Management parameter CodeTreeOptimisation is enabled in the cell

2. Number of currently allocated HS-PDSCH codes is lower than the maximum allowed

number of HS-PDSCH codes

3. DPCHs having only SRB DCH are not allowed to be re-arranged

4. All DPCH codes (SF8-SF256) can be accommodated in other than HS-PDSCH

code upgrade area, i.e. upgrade of the HS-PDSCH codes is possible

Dynamic Resource Allocation Parameters





Dynamic Resource Allocation Parameters

• WeightHSDPA

• Range:1..100, step 1, Object:RNC

• Default: WeightHSDPATHP1=100, WeightHSDPATHP2=75, WeightHSDPATHP3=50,WeightHSDPABG=25)

• WeightDCH

• Range:1..100, step 1, Object:RNC

• Default: WeightDCHTHP1=90, WeightDCHTHP2=65, WeightDCHTHP3=40, WeightDCHBG=15

• HSPDSCHCodeSet

• Bitmask (16 bits, bit 5 = 5 codes enabled etc.), Default: with 5 codes 32 (bit 5 = 1), with 10 codes

1312, with 15 codes 54560• HSPDSCHAdjustPeriod

• Range:1..60 s, step 1 s, Default:10 s, Object:RNC

• HSPDSCHMarginSF128

• Range and step: 0..128, step 1, Default value: 8, Object:WCEL

• DPCHOverHSPDSCHThreshold

• Range and step: 0..10, step 1 Default: 0, Object: WCEL• CodeTreeOptimisation

• Range and step: 0 (Optimisation not used), 1 (Optimisation used) Default: 1, Object: WCEL

Module Contents








• Code allocation of HS-PDSCH physical channels

• Allocation of the HSDPA power

• Selecting the priority of HSDPA



HSDPA (Static) Resource Allocation





( )

• HSDPA (static) resource allocation is applied if HSDPA dynamic resource

allocation is not enabled

• This feature consists of

• Static allocation of HS-PDSCH codes

• Static allocation of power resources for HSDPA in RNC

• BTS applies dynamic power allocation regardless of the resource allocation

method in RNC

Allocation of the HSDPA power





p

• The PtxMaxHSDPA parameter defines the maximum amount of HSDPA power

(HS-PDSCH and HS-SCCH total power)

• HSDPA power and number of HS-PDSCH codes are signalled to the BTS

• NBAP: Physical Shared Channel Reconfiguration procedure after cell setup in cells

that support HSDPA and have HSDPA enabled (parameter HSDPAenabled )

• HSDPA transmission power is limited by RNC so that

PtxMaxHSDPA < PtxMax - PtxTargetHSDPA

, where PtxMax = MIN(PtxCellMax , MaxDLPowerCapability) , PtxTargetHSDPA isthe PS scheduling target for PS NRT DCH

Module Contents










Code allocation of HS-SCCH physical channels





• RNC allocates 0…3 HS-SCCH

(SF=128) codes to the cell by

using the primary scrambling code• HSDPA needs at least one code

and more than one code is needed

if feature HSDPA Code

Multiplexing is chosen to be used

• HSDPAenabled and

MaxNbrOfHSSCCHCodes are celllevel RNP parameters

• Codes for HS-SCCH channels are

reserved in cell-setup phase and

so HS-SCCH code configuration

can not be changed on-line Do not allocateHS-SCCH codes

Allocate HS-

SCCHs depending

onMaxNbrOfHSSCC

HCodesparameter

BTS HSDPAcapable No

HSDPAEnabled in

the cell

Yes

No

Allocate one HS -SCCH code

END

Code-mux

activated in RNC

START

No

Yes

Yes

Code-mux

supported in BTSNo

Yes

Parameters





• PtxMaxHSDPA

• Range:0 … 50 dBm, step 0.1 dBm, Default:37.8 dBm, Object:WCEL

• PtxTargetHSDPA

• Range:-10 … 50 dBm, step 0.1 dBm, Default:38.5 dBm, Object:WCEL

• HSDPApriority

• Range:1 (HSDPA priority 1), 2 (HSDPA priority 2), Default:1, Object:RNC

• MaxBitRateNRTMACDFlow

• Range:64, 128, 256, 384,512, … , 14080; step 128 kbps, Default:9600 kbps *), Object:RNC • RNC supports the maximum user bit rate of the HS-DSCH MAC-d flow up to 6.72 Mbps, which

corresponds with the maximum air-interface bit rate 7.2 Mbps

• HSDPAPeakRateLimitRABMax

• Range:0 (No limitation), 1 (Limitation is active), Default:1, Object:RNC

• MaxNbrOfHSSCCHCodes

• Range:1..3, step 1, Default:1, Object:WCEL

Module Contents







• Direct DCH to HS-DSCH switch

• Direct HS-DSCH to DCH switch






Channel type switching





• Channel type switching is functionality where PS interactive/background radio

bearer mapping is changed from DCH to HS-DSCH or from HS-DSCH to DCH

• Switch to DCH is needed if use of HS-DSCH is not possible anymore

• Switch to HS-DSCH is needed when RB is mapped to DCH but conditions to use HS-

DSCH are fulfilled

• HSDPA is used every time when its use is possible

• Basic HSDPA functionality contains the following switches• Direct DCH to HS-DSCH switch


• In both switches above, DCH 0/0 is not used or it is ,at least, tried to be avoided

Module Contents














Direct DCH to HS-DSCH switch





• In direct DCH to HS-DSCH switch PS interactive/background radio bearer that is

mapped to DCH is reconfigured to HS-DSCH

Triggers for DCH to HS-DSCH switching





1. First HSDPA capable cell is added to the active set

• UE enters to HSDPA coverage

2. RAB configuration of the UE is changed so that it supports HS-DSCH

3. Initial HS-DSCH reservation did not succeed for temporary reason

• DCH was allocated although HS-DSCH was supported

4. HS-DSCH to DCH switch is done for IFHO/ISHO measurement, but IFHO or

ISHO was not performed due to unsatisfied measurement results

Conditions for starting DCH to HS-DSCH switch





1. UE has RAB combination that supports HSDPA (just I/B PS RAB or AMR+I/B

PS RAB)

• PS I/B RB is mapped to DCH

2. UE and at least one cell in active set are HSDPA capable

• If HSDPAMobility is disabled , active set size must be 1

3. CPICH Ec/No of HSDPA cell > CPICH Ec/No best AS cell –

HSDPAChaTypeSwitchWindow

• Candidate cell for HS-DSCH must be good enough compared to the best cells in

active set

4. No inactivity or low utilization detected on DCH (DL/UL)

5. No guard timers running to prevent HS-DSCH selection

• HsdschGuardTimerHO, HSDSCHGuardTimerLowThroughput,

HSDSCHCTSwitchGuardTimer, DCH to HS-DSCH switch retry prevention timer

Examples for starting DCH to HS-DSCH switch





• Change of RAB combination

• Release of video call

• Handover from cell without HSDPA

capability

• SHO with HSSPAMobility

• IFHO

• After HsdschGuardTimerHO

HSDPAnon-HSDPA

SWITCH

f1

f2

Measurements for the switch





• The quality of the candidate cell is validated by using periodical CPICH Ec/No

measurement

• RNC must have at least one measurement report containing CPICH Ec/No values forthe branches of the active set before the switch can be made

• Reporting period defined by the RNC level RNP parameter

HSDPACPICHCTSRepPer

• Otherwise this measurement has the same attributes and principles as periodicalCPICH Ec/No measurement in mobility case

• EcNoFilterCoefficient

• HSDPACPICHAveWindow

DCH to HS-DSCH switch execution





• It is checked that there are no other things preventing use of HS-DSCH

(for example maximum number of simultaneous HSDPA users)

• If new HSDPA user is not possible to be added to the cell then possible other cells inactive set are checked

• If a cell with free HSDPA capacity is found, then

• RNC and AAL2 resources are reserved for HS-DSCH

• Radio links, transport channel and radio bearer are reconfigured(DCH X/X DL:HS-DSCH, UL: DCH X)

• Radio bearer is mapped to HS-DSCH

• RNC and AAL2 resources for DCH are released

• HS-DSCH specific measurements are configured to the UE

Module Contents














Direct HS-DSCH to DCH switch





• In direct HS-DSCH to DCH switch PS interactive/background radio bearer that is

mapped to HS-DSCH is reconfigured to DCH

• Use of DCH 0/0 is tried to be avoided

• This functionality does not bring any new reasons/triggers for HS-DSCH to DCH

switch

• See ‘HSDPA channel type selection’

• DCH is tried to be reserved in the next scheduling period with the initial bit rates

defined by the RNP parameters InitialBitRateUL and InitialBitRateDL

• If the initial bit rates can not be allocated, then zero bit rates are used instead (DCH

0/0)

Parameters





• HSDPAChaTypeSwitchWindow

• Range and step: 0..4 dB, step 0.5 dB, Defaultvalue: 0 dB, Object:RNC

• HsdschGuardTimerHO• Range and step: 0..30 s, step 1 s Default value:

5 s, Object:RNC

• HSDSCHGuardTimerLowThroughput

• Range and step: 0..240 s, step 1 s Default value:30 s, Object:RNC

• HSDSCHCTSwitchGuardTimer

• Range and step: 0..30 s, step 1 s Default value:5 s, Object:RNC

• HSDPACPICHCTSRepPer

• Range and step: 0 (500 ms), 1 (1000 ms), 2(2000 ms), 3 (3000 ms), 4 (4000 ms), 5 (6000ms) Default value: 2, Object:RNC

• HSDPACPICHAveWindow

• Range and step: 1..10, step 1 Default value: 3,Object:RNC

• EcNoFilterCoefficient

• Range and step: 0 (Filtering period of 200 ms ),1 (Filtering period approximates 300 ms), 2

(Filtering period approximates 400 ms), 3(Filtering period approximates 600 ms), 4(Filtering period approximates 800 ms), 5(Filtering period approximates 1100 ms), 6(Filtering period approximates 1600 ms) Defaultvalue: 3, Object:FMCS

• InitialBitRateUL

• Range and step: 8 (8 kbps), 16 (16 kbps), 32 (32

kbps), 64 (64 kbps), 128 (128 kbps), 256 (256kbps), 384 (384 kbps) Default value: 64,Object:WCEL

• InitialBitRateDL

• Range and step: 8 (8 kbps), 16 (16 kbps), 32 (32kbps), 64 (64 kbps), 128 (128 kbps), 256 (256kbps), 384 (384 kbps) Default value: 64 ,Object:WCEL

Module Contents








• HSDPA mobility handling with the Serving HS-DSCH Cell Change

• Measurement control and handover path parameters

• HSDPA cell reselection

• Directed RRC connection setup for HSDPA layer• HSPA layering for UEs in common channels





HSDPA mobility handling





• In Nokia RAN, there are two methods available to handle the HSDPA mobility

1. HSDPA mobility handling with the serving HS-DSCH cell change

2. HSDPA cell reselection and HSDPA mobility handling with DCH switching (HSDPAcell reselection)

• Operators can set the preferred method with the management parameter

HSDPAMobility• = 0 (Disabled), use HSDPA cell reselection

• = 1 (Enabled), use serving HS-DSCH cell change

Module Contents







• HSDPA mobility handling• HSDPA mobility handling with the Serving HS-DSCH Cell Change

• Measurement reporting

• Measurement setup

• Initial serving cell selection

• Serving HS-DSCH Cell Change algorithm



• Directed RRC connection setup for HSDPA layer

• HSPA layering for UEs in common channels





Serving HS-DSCH Cell Change





1. Intra Node-B serving HS-DSCH cell change

2. Inter Node-B serving HS-DSCH cell change

3. HS-DSCH to DCH switch (needed if the UE is moving to a cellwithout HSDPA support or inter-RNC case with SHO)

Full intra-frequency mobility for HSDPA users and enablesHSDPA also in SHO region

HSDPA capable cell

HSDPA not supported

12

3

HSDPA Handover UL/DL DCH = soft/softer HO ; DL HS-DSCH = serving cell change

Serving HS-DSCH Cell Change





HS-SCCH

HS-PDSCH

DPCH

DPCHServingHS-DSCH cell

Soft/softer handover is not supported

for HS-SCCH/HS-PDSCH.

HS-DPCCH

• Transmission of the HS-SCCH and the HS-PDSCH to one UE belongs to only

one of the radio links assigned to the UE

• No soft/softer handover support

• Synchronized change of the serving HS-DSCH cell allows implementation of

HSDPA with full mobility and coverage, including HSDPA coverage for UEs with

an active set size larger than one for its dedicated channels

Module Contents









• Measurement reporting• Measurement setup

• Initial serving cell selection

• Serving HS-DSCH Cell Change algorithm

• Measurement control and handover path parameters• HSDPA cell reselection







Measurement reporting and Serving HS-DSCH CellChange





Event Description Actions on HSDPA

1A A primary CPICH enters the reporting

range.

Start HSDPA specific measurements

1B A primary CPICH (Serving HS-DSCH cell)

leaves the reporting range.

Trigger for serving HS-DSCH cell change

1C A non-active primary CPICH becomes

better than an active (Serving HS-DSCH

cell) one


6F/6G UE Rx-Tx time difference for a RL

included in the active set becomes larger

than an absolute threshold


1F A primary CPICH goes below the absolute

threshold.

Trigger for releasing the HS-DSCH MAC-d flow (after 1F for

all AS cells) + for AMR multi-RAB inter-frequency/-RAT

measurements

6A UE Tx power exceeds the absolute

threshold.

Trigger for releasing the HS-DSCH MAC-d flow + for AMR

multi-RAB inter-frequency/-RAT measurements

Uplink quality deterioration report (in RNC) Trigger for releasing the HS-DSCH MAC-d flow

DL transmitted code power > limit Trigger for releasing the HS-DSCH MAC-d flow + for AMR

multi-RAB inter-frequency/-RAT measurements

Module Contents

















HSDPA specific parameters for handovers





• HSDPAFMCS/I/Gidentifier

• Identifies parameter set for inter-/intra-frequency and inter-system measurements of a user having HS-DSCH allocated.

• RTWithHSDPAFmcs/i/gIdentifier, RTWithHSDPAHopsIdentifier • When AMR speech CS RAB is established simultaneously (possible when parameter

AMRWithHSDSCH is enabled) with an NRT PS RAB having HS-DSCH transport channel

• HSDPAHOPSidentifier

• Identifies parameter set for intra-frequency HOs of a user having HS-DSCH allocated.

• HsdschGuardTimerHO

• Defines time when HS-DSCH allocation is not allowed for a UE, after successful channel type switchingto DCH due to any HO reasons.

• Default, 5s.

• The HSDPA coverage can be maximised by defining separate measurement control

and handover path parameters for UE that supports HSDPA

• These HSDPA-specific parameter sets are sent with the RRC: MEASUREMENTCONTROL when a HS-DSCH transport channel is being allocated.

Module Contents










• HSDPA cell reselection and DCH switching







HSDPA cell reselection and DCH switching





• Setting the parameter HSDPAMobility to Disabled activates


• Mobility handling with DCH switching• HSDPA cell reselection applies transition to the CELL_FACH state

• When UE enters soft handover coverage area

• Triggered by the measurement event 1A

• HSDPA mobility handling with DCH switching applies DCH X/X allocation

• Based on the measurement events 1F and 6A• To initial bitrates with Direct HS-DSCH to DCH switch

• UL DCH quality deterioration report can be used to control HSDPA mobility

• In the case of an AMR multi-service, DL Transmitted Code Power measurementis used as a trigger to initiate inter-frequency measurements

• HS-DSCH MAC-d flow is released before transition to the CELL_FACH state orallocation of initial bitrates with Direct HS-DSCH to DCH switch

Measurement reporting and HSDPA cell reselectionand DCH switching





Event

Description Actions on HSDPA

1A A primary CPICH enters the

reporting range.

Trigger HS-DSCH release and transition to the

CELL_FACH state

1F A primary CPICH goes below

the absolute threshold.

Trigger for releasing the HS-DSCH MAC-d flow

and allocation of DCH X/X (0/0 or initial

bitrates with Direct HS-DSCH to DCH switch)

+ for AMR multi-RAB inter-frequency/-RAT

measurements

6A UE Tx power exceeds the

absolute threshold.

Uplink quality deteriorationreport (in RNC)

DL transmitted code power >

limit

For AMR multi-RAB Trigger for releasing the HS-

DSCH MAC-d flow and allocation of DCH X/X

(0/0 or initial bitrates with Direct HS-DSCH to

DCH switch) and starting inter-frequency/-RAT

measurements

HSDPA cell reselection

T ll ( ll i h





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

HSDPA cell reselection details

HSDPA S i C ll Ch i C ll FACH f t i d l i i t





• 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

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/0DCH Initial bit rateDCH Final bit rate)

HSDPA cell reselection Parameters

Addition Window (HSDPA FMCS) = 0dBAddition Time (HSDPA FMCS) = 1280ms

EcNo Filter coefficient (HSDPA FMCS) = 800ms

Enable RRC release (HSDPA HOPS) = enabled

Release Margin Average EcNo (HSDPA HOPS) = 2dB





time

Ec /No

CPICH 2

HSDPA A ddit ion Time

MeasurementReports (1A)

HSDPA

Addi t ionWindow

CPICH 1

HSDPA CELL_FACH

Release Margin Average EcNo (HSDPA HOPS) = 2dB

Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB

EcNo Averaging Window (HSDPA HOPS) = 8

ReleaseMarginAverageE

cNo

ReleaseMarginPeakEcNo

Reconfigurationto Cell_FACH

HSDPA

Discouraging SHO during Connection Establishment

HSDPARRCdiversity





• Where,

MeasNew is the Ec/No measurement result of the cell entering the reporting range

MeasCell is the Ec/No measurement result of the serving cell

MeasAveNew is the averaged Ec/No measurement result of the cell entering the reporting rangeMeasAveCell is the averaged Ec/No measurement result of the serving cell

ReleaseMarginPeakEcNo and ReleaseMarginAveEcNo are parameters defined in the HSDPA

HOPS

o) ginPeakEcN ReleaseMar Meas Meas Cell New (

• This parameter defines which set of thresholds are applied for soft handover during

connection establishment while a UE has a standalone SRB

• If the measurement event 1A is triggered and the reported CPICH Ec/No of the enteredcell fulfils either one of the equations below, active set update is allowed despite the value

of the parameter HSDPARRCdiversity

)ginAveEcNoReleaseMar MeasAve(MeasAve Cell New



Directed RRC connection setup for HSDPA layer

• This feature is meant for multi layer networks where high speed downlink packet





• This feature is meant for multi layer networks where high speed downlink packetaccess (HSDPA) is supported in some layer(s) (carrier frequency)

• The primary target of this feature is to• Direct the HSDPA capable UEs to the layer that supports HSDPA

• If several HSDPA capable layers exist the HSDPA load balancing between these layers isutilized.

• Remove non-HSDPA UE from HSDPA layer(s)

• Feature works inside BTS between cells of same sector• Same Sector ID, PtxPrimaryCPICH, CPICHtoRefRABoffset, PLMN code (MCC +

MNC )

f1, Rel’99f1, Rel’99

f2, HSDPA + Rel’99f2, HSDPA + Rel’99

Rel’99 and Rel-4 UE

andRel-6 or newer non-HSDPA capable UE

Rel-5 UE

andRel-6 or newer HSDPAcapable UE

Signalling and sector

• Directed RRC connection set up for





• Directed RRC connection set up for

HSDPA layer

• When UE initiates the RRC connection

setup, it indicates

• 3GPP release it supports (access

stratum release indicator IE )

• Rel-4, Rel-5, Rel-6, … • Rel-6 UE indicates if it supports HSDPA

and HSUPA (UE capability indication

IE )

• The service UE is going to use

(Establishment cause IE )



Basic functionality

• Basic functionality is selected when the DirectedRRCForHSDPALayerEnhanc





Basic functionality is selected when the DirectedRRCForHSDPALayerEnhanc

management parameter is set to ‘Disabled’

• 3GPP release 5 or newer UEs are directed from non-HSDPA supporting cell to

the cell, which supports HSDPA

• 3GPP release 99 or release 4 UEs are directed from HSDPA supporting cell to

the cell, which does not support HSDPA

• Load of target cell is not taken into account

• With basic functionality the Directed RRC connection setup for HSDPA layer

cannot be used simultaneously in the cell with Directed RRC connection setup

feature

Enhanced functionality

• Enhanced functionality is selected when the





Enhanced functionality is selected when the

DirectedRRCForHSDPALayerEnhanc management parameter is set to ‘Enabled’

• Enhancement of Directed RRC connection setup for HSDPA layer

• The service indicated by UE in RRC connection request is taken into account

• The services are defined with DRRCForHSDPALayerServices parameter

• More than 2 layers are supported

• Target cell load checking and HSDPA load balancing

• Simultaneous use of Directed RRC Connection Setup and Directed RRC Connection

Setup for HSDPA layer is supported

• UE capability indication IE (coming in RRC Connection Request message) is used in

decision making for Rel-6 and onwards UEs

• Separate only DCH, HSDPA and HSUPA capable Rel-6 UEs

Decision to change the layer

• Non HSDPA UEs (R99 or R4, R6 without HSDPA) are directed away from HSDPA





( ) ycapable cell

• If load of the target cell is not too big

• HSDPA UEs (R5 or R6 with HSDPA) are directed away from non-HSDPA capable cell

• If establishment cause indicated by the UE is activated with DRRCForHSDPALayerServices parameter

• If maximum number of HS-DSCH users is not reached in target cell

• If several target layer candidates exists the HSDPA load balancing is applied

• HSDPA UEs (R5 or R6 with HSDPA) are directed to another HSDPA capable cell

• For load balancing reasons

• If establishment cause indicated by the UE is activated with DRRCForHSDPALayerServices parameter

• HSUPA capable UE (R6 with HSDPA/HSUPA)

• As for HSDPA capable UE

• HSUPA capable UE is directed to HSUPA capable cell if possible

• HSUPA capable UE is not directed away from HSUPA capable cell

Directed RRC connection setup in non-HSPA layer

Decision making

UE reporting Rel-6

HSDPA & HSUPA capability





1. UE HSPA capability = cell HSPAcapability (f1)

A Yes -> current layer (f1)

B&C No -> f2 & f3

2. Establishment cause =DRRCForHSDPALayerServices

B&C No -> current layer (f1)

B&C Yes -> f2 & f3

3. UE HSPA capability = target cellHSPA capability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPAthroughput

B -> f2 or f3

f1, R´99

f2, HSDPA

f3, HSDPA&HSUPA

A

B

UE reporting Rel5 or

Rel-6 & HSDPA capability

Any other UE

C

Directed RRC connection setup in HSDPA/HSPAlayer

Decision making





1. UE HSDPA capability = cell HSDPA

capability (f2/f3)

A No -> f1

B&C No -> f2 & f3

2. Establishment cause =

DRRCForHSDPALayerServices

B&C No -> current layer (f2/f3)

B&C Yes -> f2 & f3

3. UE HSUPA capability = cell HSUPAcapability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPA throughput (for

interactive and background

Establishment cause)

B -> f2 or f3f1, R´99

f2, HSDPA

f3, HSDPA&HSUPA

A

B

UE reporting Rel5 or

Rel-6 & HSDPA capability

Any other UE

UE reporting Rel-6

HSDPA & HSUPA capability

C

HSDPA load balancing

• HSDPA load balancing is used when there are two or more layers that support





g y pp

HSDPA

• HSDPALayerLoadShareThreshold defines threshold for number of HSDPA UEsrequired to trigger load balancing

• If #UEs > HSDPALayerLoadShareThreshold in a cell in sector

• HSDPA UEs are directed to different HSDPA layers to balance available power per

HSDPA user• CellWeightForHSDPALayering parameter can be used to direct more HSDPA UEs to

selected layer

• If # UEs < HSDPALayerLoadShareThreshold in all cells in sector

• HSDPA UEs are directed to same HSDPA layer

• The cell which CellWeightForHSDPALayering has biggest value is chosen

HSDPA load balancing (under threshold)

Number of HS-DSCH users in the cell in the decision making moment





Cell which has

1. highest cell weight

(CellWeightForHSDPALayering )

2. number of HS-DSCH users is

highest

shall be selected.

Cell

f1

g

Max

0

HSDPALayerLoadShareThreshold

Cell

f2

Cell

f3

HSDPA load balancing (over threshold)

Number of HS-DSCH users in the cell in the decision making moment





Cell which has

1. highest cell weight

(CellWeightForHSDPALayering )

2. number of HS-DSCH

users is highest

shall be selected.

Cell

f1

Max

0

HSDPALayerLoadShareThreshold

Cell

f2

Cell

f3

Cell which has highest

HSDPA power per

user available shall be

selected

HSDPA load balancing (HSDPA power per user)

Operator parameterPmax





1

*

DPAusers NumberOfHS

yering ForHSDPALaCellWeight PtxNonHSPA P PerUser HSDPApower Max

(Range 0.01 … 1)

Number of HSDPA usersactive in the cell

A cell with highest available HSDPA power per user shall be selected.

HSPA

power

Non

HSPA

power

Cell

PtxNonHSPA

max

0

Interworking with Directed RRC connection setupfeature

(Both parameters DirectedRRCEnabled and DirectedRRCForHSDPAEnabled are enabled.)





• The decision of directed RRC connection setup for HSDPA layer is done first:

Decision = Change layer: Directed RRC connection setup for HSDPA layer is done

Decision = Do not change layer: The decision of directed RRC connection setup is done

• If several candidates exist (more than 2 layers) for Directed RRC connection setup UE is

tried to keep in most suitable layer from capability point of view.

• Non-HSDPA capable UE -> non-HSDPA capable cell

• HSDPA capable UE -> HSDPA or HSDPA&HSUPA capable cell

• HSDPA&HSUPA capable UE -> HSDPA&HSUPA capable cell is preferred and HSDPAcapable is next preferred.

• HSDPA/HSPA capable UEs in Directed RRC connection setup

• are not transferred away from HSDPA/HSPA layer if they are requesting interactive or

background service.

• can be transferred away from HSDPA/HSPA layer if they are requesting other than interactive

or background service.

Parameters

• DirectedRRCForHSDPALayerEnabled

• Range and step: 0 (Disabled) 1 (Enabled) Default value: 0 Object:WCEL





• Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:WCEL

• DirectedRRCForHSDPALayerEnhanc

• Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:WCEL• DRRCForHSDPALayerServices

• Range and step:

• Bit 0: Conversational Call , Bit 1: Streaming Call , Bit 2: Interactive Call , Bit 3: Background Call , Bit 4: Subscribed trafficCall , Bit 5: Emergency Call , Bit 6: Inter-RAT cell re-selection , Bit 7: Inter-RAT cell change order , Bit 8: Registration , Bit9: High Priority Signalling , Bit 10: Low Priority Signalling , Bit 11: Call re-establishment , Bit 12: Terminating – causeunknown , Bit 13: MBMS reception , Bit 14: MBMS ptp RB request , Bit 15: Other

• Default value: 204 (11001100)

• In default the Directed RRC connection setup for HSDPA layer is done only for Interactive and Background calls, Inter-RAT cell re-selections and Inter-RAT cell change order.

• Object:RNC

• HSDPALayerLoadShareThreshold

• Range and step: 0..48, step 1, Default value: 3, Object:RNC

• CellWeightForHSDPALayering

• Range and step: 0.01..1, step 0.01, Default value: 1, Object:WCEL

• DirectedRRCEnabled• Range and step: 0 (Disabled), 1 (Enabled), Default value: 1, Object:WCEL

Module Contents







• HSDPA mobility handling• HSDPA mobility handling with the Serving HS-DSCH Cell Change









HSPA layering for UEs in common channels

• HSPA layering for UEs in common channels is triggered in transition from

CELL FACH t CELL DCH t t





CELL_FACH to CELL_DCH state

• Complements directed RRC connection setup for HSDPA feature

• The primary target of this feature is to

• Direct the HSDPA UEs to the cell that supports HSDPA

• If several HSDPA capable layers exist the HSDPA load balancing between these layers is

utilized

• Remove non-HSDPA UEs from HSDPA layer(s)

• Feature works inside BTS between cell of same sector

• Same Sector ID, PtxPrimaryCPICH, CPICHtoRefRABoffset, PLMN code (MCC +

MNC )



Decision to change the layer

• Non HSDPA UEs (R99 or R4, R6 without HSDPA) are directed away from HSDPA

capable cell





capable cell

• If load of the target cell is not too big

• HSDPA UEs (R5 or R6 with HSDPA) are directed away from non-HSDPA capable cell

• If operation is allowed for RAB type (CS/PS) defined with ServicesToHSDPALayer parameter

• If maximum number of HS-DSCH users is not reached in target cell

• If several candidates exists the HSDPA load balancing is applied

• HSDPA UEs (R5 or R6 with HSDPA) are directed to another HSDPA capable cell

• For load balancing reasons

• UE is requesting interactive or background service

• HSUPA capable UE (R6 with HSDPA/HSUPA)

• As for HSDPA capable UE

• HSUPA capable UE is directed to HSUPA capable cell if possible

• HSUPA capable UE is not directed away from HSUPA capable cell



Parameters

• HSDPALayeringCommonChEnabled

R d t 0 (Di bl d) 1 (E bl d) D f lt l 0 Obj t WCEL





• Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:WCEL

• ServicesToHSDPALayer

• Range and step: 0 (Any type of service is requested), 1 (NRT PS RAB is requested),

Default value: 0, Object:RNC

Module Contents


Ch l t it hi











HSDPA channel type selection

• The HSDPA channel type selection feature determines the optimal downlink

transport channel for the user (FACH DCH or HS-DSCH)





transport channel for the user (FACH, DCH or HS DSCH)

• The UE-specific packet scheduler (PS) performs the channel selection• Triggered by capacity request (UL/DL)

Selection between DCH and HS-DSCH

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





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

2. UE capability supports HS-DSCH3. The cell supports HSDPA and HS-DSCH is enabled in the cell

4. Multi-RAB combination of the UE is supported with HS-DSCH• The only allowed combination is 1 AMR voice CS RAB + 1 Interactive/Background class service PS RAB. This multi-RAB is

supported if operator has enabled the parameter AMRWithHSDSCH .

5. The number of simultaneous HS-DSCH allocations in the BTS/cell is below the maximum number• 16/BTS, 16/cell, 16/cell group, 48/cell group or 48/cell

6. HsdschGuardTimerHO and HsdschGuardTimerLowThroughput guard timers are not running for that UE

• Both guard timers are operator-configurable parameters7. UE is not performing inter-frequency or inter-system measurements

8. Active set size = 1 (if HSDPAMobility is disabled)

9. UE does not have DCHs scheduled with bit rates higher than 0kbps ??

10. HS-DSCH physical layer category is supported

11. When HSDPA Dynamic Resource Allocation is disabled and 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 <=PtxtargetHSDPA

B) Ptxtotal <=PtxtargetHSDPA

Release of DL HS-DSCH MAC-d flow and UL DCH / E-DCH

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 (Packet





UE moved to Cell FACH

(

scheduler) / UL NRT E-DCH can be released (HSUPA)

Or

• MAC-d flow has low throughput and UL NRT DCH can be released (Packet

scheduler) / UL NRT E-DCH can be released (HSUPA)

• 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

AMR call + NRT DCH 0/0

Parameters

• HSDSCHQoSclasses

• Range and step: Bit 0: Background , Bit 1: Interactive THP=3 , Bit 2: Interactive THP=2 , Bit 3:





Interactive THP=1, Default value: 15, Object:RNC

• AMRWithHSDSCH• Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:RNC

• HsdschGuardTimerHO

• Range and step: 0..30 s, step 1 s, Default value: 5 s, Object:RNC

• HsdschGuardTimerLowThroughput

• Range and step: 0..240 s, step 1 s, Default value: 30 s, Object:RNC

• MACdflowthroughputAveWin

• Range and step: 0..10 s, step 0.5 s Default value: 3 s, Object:RNC

• MACdflowutilRelThr

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

• MACdflowthroughputRelThr

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

Module Contents








• HSDPA mobility handling• HSDPA channel type selection




HSDPA with additional RAB initiation

• The multi-RAB combination ‘AMR + Interactive/Background PS RAB’ is

supported simultaneously with the HS-DSCH transport channel





pp y p

• Operator chooses the usage of this combination by enabling the

AMRWithHSDSCH parameter (optional feature)

Sector inf o

AMR call (UL&DL)

PS: HS-DSCH (DL)

PS: DCH (UL)

HSDPA in DL, DCH (return channel) in UL

AMRspeech call in UL&DL

Sector inf o

AMR call (UL&DL)

PS: HS-DSCH (DL)

PS: DCH (UL)

HSDPA in DL, DCH (return channel) in UL

AMRspeech call in UL&DL

HSDPA suspension

• HSDPA is suspended for the duration of the AMR multi-call, if the parameter

AMRWithHSDSCH is set to disabled





• For other multi-call combinations, the suspension is always applied

• With direct HS-DSCH to DCH switch it is possible that DCH with initial bit rate is

reserved directly after suspension

bit

rate HS-DSCH

time

DCH

After HSDPA issuspended, DCH packetscheduling procedurescan be applied -> if still

enough data in buffer,DCH is allocated

bit

rate HS-DSCH

time

DCH



Non-supported

RAB combination

for HSDPA setup ->

HSDPA is suspended

bit

rate HS-DSCH

time

DCH



bit

rate HS-DSCH

time

DCH



Non-supported

RAB combination

for HSDPA setup ->

HSDPA is suspended

Module Contents







Channel type switching

• HSDPA mobility handling• HSDPA channel type selection




HSDPA associated uplink DPCH channel

• When the radio bearer is mapped onto HS-DSCH transport channel in downlink,

either E-DCH or DCH is allocated in uplink as a return channel





• Supported data rates for UL DCH return channel are 16, 64, 128 and 384 kbit/s

• 16 kbps UL DCH return channel is an optional feature, which can be activated by the

operator with the management parameter HSDPA16KBPSReturnChannel

• Minimum allowed bit rate with HSDPAminAllowedBitrateUL parameter

• Not limited by BitRateSetPSNRT

PS: HS-DSCH (DL)

PS: DCH (UL)

PS: HS-DSCH (DL)

PS: DCH (UL)

HSDPA associated uplink DPCH scheduling

• If the HS-DSCH allocation is triggered by uplink, normal NRT DCH schedulingrules are applied

f ff ff C





• If the traffic volume measurement indicates High traffic volume, the RNC attempts to

allocate a return channel with the highest possible bit rate• TrafVolThresholdULHigh parameter

• If the traffic volume measurement indicates Low traffic volume, the RNC attempts toallocate a return channel with configured initial bit rate

• HSDPAinitialBitrateUL parameter

• If the HS-DSCH allocation is triggered by downlink, the RNC attempts to allocate

the uplink with the HSDPAinitialBitrateUL parameter• In the case of direct DCH to HS-DSCH switch, the HSDPA UL DCH bit rate can

be same as existing DCH UL bit rate

• If even initial bit rate or higher can not be allocated, HS-DSCH allocation is notpossible

DL/UL DCH is scheduled to the UE



Example use case 1: HSDPA UL DCH with initial bitrate 64 kbps

• The initial bit rate (HSDPAinitialBitrateUL) is set to 64 kbps. The minimum bit rate

is set to 16 kbps (HSDPAminAllowedBitrateUL)





64

kbps

384

128

t

0

Capacity

Request

(Traf.vol

measurement

low)

Initial bitrate

64 kbps

Decrease of the

retried NRT DCH

bitrate

Priority based

scheduling/

RT-over-NRT

Minimum bitrate

16 kbps

Capacity

Request

(Traf.vol

measurement

high)

Capacity

Request

(Traf.vol

measurement

high)

t1

t2

t3

t5

16

t4

Example use case 2: Initial bit rate 128 kbps





Parameters

• HSDPA16KBPSReturnChannel

• Range and step: 0 (Disabled), 1 (Enabled), Default value: 0, Object:RNC

• HSDPAminAllowedBitrateUL





• Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps), Default value: 3 , Object:RNC

• BitRateSetPSNRT

• Range and step: 0 (Predefined bit rate set is not in use = All supported bit rates are in use), 1 (Predefined bitrate set is in use), Default value: 0, Object:RNC

• TrafVolThresholdULHigh

• Range and step: 0 (8 bytes), 1 (16 bytes), 2 (32 bytes), 3 (64 bytes), 4 (128 bytes), 5 (256 bytes), 6 (512bytes), 7 (1024 bytes. 1 KB), 8 (2048 bytes. 2 KB), 9 (3072 bytes. 3 KB), 10 (4096 bytes. 4 KB), 11 (6144bytes. 6 KB), 12 (8192 bytes. 8KB), 13 (12288 bytes. 12 KB), 14 (16384 bytes. 16 KB), 15 (24576 bytes. 24

KB), Default value: 7, Object:RNC

• TrafVolThresholdULLow

• Range and step: 8 (8 bytes), 16 (16 bytes), 32 (32 bytes), 64 (64 bytes), 128 (128 bytes), 256 (256 bytes), 512(512 bytes), 1024 (1 KB) Default value: 128, Object:RNC

• HSDPAinitialBitrateUL

• Range and step: 1 (16 kbps), 3 (64 kbps), 4 (128 kbps), 6 (384 kbps), Default value: 3, Object:RNC

• DynUsageHSDPAReturnChannel

• Range and step: 0 (Off), 1 (On), Default value: 0, Object:RNC



HSDPA Code Multiplexing

• Optional feature HSDPA Code Multiplexing enables simultaneous transmission of

(max) three HSDPA users within a single cell during a single Transmission Time

Interval (TTI)





Interval (TTI)

• HSDPA Code Multiplexing is activated in RNC by giving to cell level RNP parameter

MaxNbrOfHSSCCHCodes value that is bigger than 1

• Each multiplexed HSDPA user needs own HS-SCCH code

• This feature can not be used without HSDPA 10 Codes or HSDPA 15 Codes

feature• Nokia RAN uses at least 3 HS-PDSCH codes per one multiplexed HSDPA user

Two multiplexed users needs 6 HS-PDSCH codes and that is not supported by basic

HSDPA functionality

48 simultaneous HSDPA users per cell

• This feature makes it possible to have 48 simultaneous HSDPA users in one cell

• Maximum number of HSDPA users depends on also configuration of BTS





• Depending on activated features and BTS configuration the maximum is

• 16 per cell

• 16 per cell group

• 48 per cell group

• 48 per cell

• A cell group builds up from those cells that are controlled by same MAC-HSscheduler in BTS

• HSDPA 48 Users per Cell is activated with the RNC level RNP parameter

HSDPA48UsersEnabled

• Sensible Iub and BTS baseband dimensioning requires that also feature 16 kbit/s

Return Channel DCH Data Rate Support for HSDPA is in use

Parameters

• MaxNbrOfHSSCCHCodes

• Range and step: 1..3, step 1, Default value: 1, Object:WCEL





• HSDPA48UsersEnabled

• Range and step: 0 (Not in use), 1 (In use) Default value: 0, Object:RNC

Module 4 –

Summary

Summary

Radio resource management for HSDPA consists many





functions:• HSDPA resource handling






ANNEX –

RAS05.1 RAS06

• Removed features and parameters

• Resumption timer

RAS06 BTS 0 dB f t i





• RAS06 BTS uses 0 dB power safety margin

Date post:	02-Jun-2018
Category:	Documents
Upload:	lhgoul
View:	215 times
Download:	0 times

HSPA Planning Training

Documents