happy bit

1 Nokia Siemens Networks HSUPA / JKuhr / September 2007For internal use

HSUPA (E-DCH) introduction & parametersJens Kuhr Network EngineeringCOO RA RD SA NE


OutlineHSUPA ChannelsHSUPA Scheduling mechanismHARQ ProcessHSUPA RAB-HandlingHSUPA Mobility aspectsHSUPA Admission ControlHSUPA Congestion ControlHSUPA OLPCUE categories + E-TFCI selection


Outline

HSUPA (High Speed Uplink Packet Access) is used to improve uplink data rates inWCDMA networks.

It is reusing the available infrastructure by using enhanced techniques (e.g.adaptive coding) thus allowing to make better use of the available ressources.

Provides higher peak rates and increases coverage for high datarates

Shorter round trip times (RTT) make the HSPA WCDMA network more interestingfor real time applications like online gaming

HSUPA uses an enhanced dedicated transport channel in uplink (E-DCH), unlikeHSDPA, where only one downlink channel is shared among the users.

HSUPA is specified for data rates of up to 5.76 Mbps


Comparison between HSUPA and HSDPA

Similarities with HSDPA:- NodeB controlled scheduling- HARQ process- Shorter TTI than classic DCH (10ms, 2ms (HSDPA 2ms TTI only))- Fast link adaptation techniques

Differences to HSDPA:- dedicated channel (E-DCH) instead of shared channel in HSDPA- no adaptive modulation- full mobility (soft handover possible)

In UMR and RAScurrently only

10ms TTIimplemented.

Like HSDPA, HSUPA is based on scheduling in the NodeB,link adaptation and HARQ process


HSUPA Principles

TTI = 2 / 10 ms1-4 CodeMulti-Code

transmission

FastPower Control

Hybrid ARQwith incr. redundancy Scheduling

BenefitHigher Uplink Peak rates: 2-5.76 Mbps

Higher Capacity: +50-100%Reduced Latency: ~50-75 ms


HSPA Scheduling

Node B w/ HSDPA3GPP Rel. 5

Fast pipe is shared among UEs

Sche

duling

A,B,C Node B w/ HSUPA

3GPP Rel. 6Dedicated pipe for every UE in ULPipe (codes and grants) changingwith timeE-DCH scheduling

E-DCH

-A

E-DCH

-B

E-DCH

-C

Node B Rel. 99

DCH -

A

DCH -

B

DCH -

C

Dedicated pipe for every UE


HSUPA Channels - Uplink


Channel mapping

E-DCH

E-DPCCHE-DPDCH

Transport channel

Physical channel

For HSUPA, the E-DCH is introduced as a new transport channelfor carrying user data on the uplink.

On physical layer, this translates into 2 new uplink channels.


E-DCH: Enhanced Dedicated Channel

Dedicated uplink transport channel

Dedicated to 1 UE

2ms or 10ms TTI

Controlled by NodeB scheduling process

Holds one or more dedicated physical data channels (E-DPDCH)


E-DPDCH: E-DCH Dedicated Physical Data Channel

Dedicated uplink physical channel

2ms or 10ms TTI

Controlled by NodeB scheduling process

The E-DPDCH is used by E-DCH for the transmission of user data andScheduling information (SI)

Up to 4 E-DPDCH per radio link for higher throughput

Supports soft handover


E-DPCCH: E-DCH Dedicated Physical Control Channel

Dedicated uplink physical channel.

Transmits control information about the E-DPDCH transmission: E-TFCI (Transport block format combination indicator) RSN (Retransmission sequence number) for the HARQ process Happy Bit

There is at most one E-DPCCH on each radio link.

Carries the Happy Bit With the Happy Bit the UE tells the NodeBscheduler every 2ms whether the

ressource allocation was sufficient totransmit all data or not.


E-DPDCH & E-DPCCH

E-DPDCH(user data, SI)

E-DPCCH(control data, e.g Happy Bit)


E-DCH serving cell E-DCH and HSDPA serving link is always assigned by RNC

to the same cell (Best Cell) based on UE measurements.

NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCH

Serving RLS

Non Serving RLS (1 RL)

same RG information(per RLS)

same HICH information(per RLS)

RG information per RL

HICH information per RLS

NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCHE-AGCHE-HICH

E-RGCH

Serving RLS







HSUPA Channels - Downlink


E-AGCH: E-DCH Absolute Grant Channel Common downlink physical channel Time-multiplexed shared channel with explicit UE addressing using E-

RNTI On the E-AGCH, the NodeB tells the UE an absolute power level

(alsolute grant, AG) for the E-DPDCH relative the DPCCH (precisevalue, thus also more information to be transmitted)

In soft handover state, the E-AGCH is transmitted by the serving E-DCHcell only

Uses SF256

E-AGCH (absolute pwr)

E-DPDCH(user data)

E-RGCH (up,down, hold)

E-DPDCH

(user data)

E-RGCH(down,

hold)


E-AGCH: primary & secondary absolute grant An UE can get two E-RNTIs allocated (primary & secondary E-RNTI) that it needs

to listen to on the E-AGCH.

The UE always follows the AG transmitted for the primary E-RNTI (primary AG). It can be commanded to follow the AG transmitted for the secondary E-RNTI as well.

This mechanism can be used to control a group of UEs together (which will thenall have the same secondary E-RNTI assigned)

E.g. group of always on UEs, that only occasionally send data They will then be controlled as a group by a limited secondary AG If one of that UE have needs to send more uplink data, it will then get an primary

grant assigned via the primary R-RNTI. As soon the primary grant is not needed anymore, the UE can be switched to secondary

grant again.


E-AGCH power settings in RNC

Example of command execution (hmi):

cre hsupa cellid=1 nodebid=1 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30

Indicates the Power offset relative to the pilot bits on the DL DPCCH

128(RC)

1.28(LMT)

RWLMT:dB

RC:0.01*dB

0..255(0..2.55)Mapping to-32..+31.75

by step of

0.25

Integerpo_agchagchPowerOffset

AGCHPWROFF

sbs3gRanAgchPwrOffset

E-AGCHPower Offset

DefaultR/W

UnitRangeTypeLMT-NameLongnameShortnameQ3-NameName


Scheduler in NodeB, O&M parameter description

Example of command execution (xml):


E-RGCH: E-DCH Relative Grant Channel Dedicated downlink physical channel Additional to the E-AGCH channel Used by the NodeB to transmit relative grants (RG) for the UL E-DPDCH channel Relative grants are UP, DOWN and HOLD commands In soft handover state, the E-RGCH can be transmitted by every cell in the AS

cells in the serving E-DCH link set can send UP, DOWN, HOLD other cells can send only DOWN and HOLD

For the Serving E-DCH RLS there is always one logical RG information but it is transmitted ineach cell belonging to the serving RLS to allow the UE a softer combining.

For Non Serving RLS(s) the RG information is per RL Requires much lower signaling overhead than E-AGCH Uses SF128


E-DPDCH(user data)


E-DPDCH

(user data)

E-RGCH(down,

hold)

Serving E-DCH radio link set:Cells belonging to the NodeB that transmits theServing E-DCH

Serving E-DCH RL


E-RGCH power settings in RNC




128 (RC)

1.28(LMT)

RWLMT: dB

RC:0.01*dB

0..255 (0..2.55)Mapping to-32..+31.75 bystep of 0.25

Integerpo_rgchrgchPowerOffset

RGCHPWROFF

sbs3gRanRgchPwrOffset

E-RGCH PowerOffset

DefaultR/W


Number of E-RGCH/E-HICH

-RW-1,..,4Integerno_rgch_hichnumberErgchEhich

NORGCHHICH

sbs3gRanNoRgchHich


DefaultR/W



E-RGCH power settings in NodeB



E-RGCH:Condition for sending RG DOWN commands A cell may send non-serving RG DOWN commands when:

Experienced total RTWP > Target RTWP signalled by CRNC && Non-serving E-DCH to total E-DCH power ratio > Target ratio

Non-serving E-DCH to total E-DCH power ratio is the ratio of power fromUEs for which this cell is a non-serving RL and the total E-DCH power.Target RTWP is calculated from HSUPA_scheduler_offsetRTWP

Congestion Level (N_ul+CCThreshold)

Congestion Level CC Hysteresis

Current Cell Load

Maximum Target RTWP

HSUPA Scheduler Offset

TIME


Condition for sending RG DOWN commandsRNC parameters


cre hsupa cellid=1 nodebid=1 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30cre cell cctl cellid=1 nodebid=1 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00 mmti_tcp=10.00 k=1ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false hsupa_oft=0.5

Target Non-serving E-DCH to Total E-DCH Power ratio. This parameter can be updated only when HSUPA is not Active.

30RW%0,..,100Integerpr_edchtargetNonServEdchTotEdchPwrRat

TRGTNSEDCHPRAT

sbs3gRanTargNonServEdchPwrRat

Target Non-serving E-DCH to TotalE-DCHPower ratio

DefaultR/W

UnitRangeTypeLMT-NameLongname

ShortnameQ3-NameName

Offset value to calculate Maximum Target Received Total Wide Band Power

LMT:0.5RC: 5

RW**)

LMT: dBRC:0.1*dB

LMT: 0..10 step by0.1RC: 0..100

LMT:RealRC:Integer

hsupa_oftschedulerOffsetHsupa

SCHDOFFSHSUPA

sbs3gRanHsupaSchedOff

HSUPA_scheduler_offset

DefaultR/W

UnitRangeTypeLMT-Name

Longname



Condition for sending RG DOWN commandsNodeB parameters



E-HICH: E-DCH HARQ Indicator Channel Dedicated downlink physical channel Carries the HARQ ACK/ NACK messages for the UL E-DCH Is transmitted by all cells in the active set. UE continues to transmit on

E-DPDCH as long there is at least one ACK. HICH information is always send per RLS (Serving and Non Serving E-DCH RLS)

but it is transmitted in each cell belonging to the RLS to allow the UE a softercombining of the physical channels.

Uses SF128 Cells not belonging to the serving E-DCH link set transmit only ACKs

E-DPDCH(user data)

E-HICH (ACK,NACK)

E-DPDCH(user data)

E-HICH (ACK)

Serving E-DCH RLS

Only ACKs are send to save DL power. Cellsthat dont belong to the serving RLS expected to havea much larger NACK ratio due to worse channelconditions


E-HICH power settings




128 (RC)

1.28(LMT)

RWLMT: dB

RC:0.01*dB

0..255 (0..2.55)Mapping to-32..+31.75 bystep of 0.25

Integerpo_hichhichPowerOffset

HICHPWROFFsbs3gRanHichPwrOffset

E-HICH PowerOffset

DefaultR/W


LongnameShortnameQ3-NameName


-RW-1,..,4Integerno_rgch_hichnumberErgchEhich

NORGCHHICH

sbs3gRanNoRgchHich


DefaultR/W



Examples for AG, RG and HICH transmission

NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCH

Serving RLS






NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCHE-AGCHE-HICH

E-RGCH

Serving RLS






NodeB 1 NodeB 2

E-AGCHE-HICH

E-RGCH

Serving RLS

Non Serving RLS

Serving E-DCHCell




NodeB 1 NodeB 2

E-AGCHE-HICH

E-RGCHE-AGCHE-HICH

E-RGCH

Serving RLS

Non Serving RLS

Serving E-DCHCell




Example 1:2 radio links in servingRLS. RG & HICH iscombined.

Example 2:2 radio links in non-serving RLS. OnlyHICH is combined.RG is individual


Overwiev of all physical channels assigned to UEin HSUPA (NodeB with serving E-DCH RLS)


HSUPA Scheduling mechanism


Scheduler

The scheduler resides in the NodeB and manages the data transmissionof the Rel.6 UEs on the air interface.

The goal is, to assign as many resources as required to a single UE whilepreventing cell overload caused by many UEs transmitting too many data.

The scheduling algorithm is vendor specific, however the mechanism tocommunicate the scheduling results to the UE as well as certain inputparameters are defined by 3GPP.

Channels involved in the scheduling process Uplink

E-DPCCH (Happy Bit) E-DPDCH (Scheduling Information, SI)

Downlink E-AGCH (to send the AG) E-RGCH (to send RG: UP, DOWN, HOLD commands)


Scheduler Design Principles

Many HSDPA applications (e.g., web browsing, file download) requirehigh data rate in downlink, but only moderate data rate in uplink

Support of large number of UEs w/o need for channel type switching Minimized delay for uplink channel access Fast control of RTWP resource usage by Node B (scheduler) to avoid

overload on air interface Secondary Absolute Grant

Applications requiring a high uplink data rate should be served on demand Primary Absolute Grant


Performance Requirements

One common scheduling and one dedicated scheduling cycle per cell perTTI

Up to 3 cells with E-DCH scheduled on the same CHC Scheduling of 1 radio cell on a CHC

At least 32 HSUPA users / cell At least 32 users simultaneously transmitting on E-DPDCH / cell Maximum peak user throughput of at least 1.46Mbps One E-AGCH / cell One Secondary E-RNTI / cell

Scheduling of 3 radio cells on the same CHC At least 20 HSUPA users / cell At least 10 users simultaneously transmitting on E-DPDCH / cell Maximum peak user throughput of at least 1.46Mbps One E-AGCH / cell One Secondary E-RNTI / cell


Scheduler in NodeB

The scheduler in the NodeB controls the UL transmission on the E-DPDCH

Main input factors from the UE are: SI (Scheduling information) (periodically send on E-DPDCH or when triggered) Happy Bit (send on E-DPCCH) Transmitted bit rate by the UE

Main output factors to the UE are: Absolute allowed transmission power ratio E-DPDCH/DPCCH send on E-

AGCH Relative grants (UP, DOWN, HOLD) send on E-RGCH


Scheduler in NodeB, O&M parameters 1/2

The following NodeB O&M parameters influence the scheduler operation:

Target ratio of average non-serving E-DCH powers for scheduling of internalRelative Grants: (targetRatioOtherRlEdchPower)

For balancing of traffic load from UEs with different serving RLs between the cells of a Node B,a target ratio for the average non-serving E-DCH power of these UEs shall be provided.

Maximum Secondary Absolute Grant: (maxSecondAbsGrant) This value is an upper limit to the Secondary AG that may be assigned to all UEs in a radio cell. In UMR, all UEs start with secondary AG and are upgraded to primary AG upon demand (rise in

uplink traffic needs)

Maximum number of simultaneous UEs with Primary_Grant_Available ="True":(maxNumberPrimaryGrantUe)

This value is an upper limit to the number of UEs in a cell that may be simultaneously operatingwith a Primary AG.


Scheduler in NodeB, O&M parameters 2/2

The following NodeB O&M parameters influence the scheduler operation:

Time constant for UE inactivity detection: (ueInactivityTimer) inactivity indicates the number of idle subframes (2ms) after that a UE may be switched from state

Primary_Grant_Available = "True" to "False". If data transmission is less than what could be send with current secondary AG for the

timeframe of ueInactivityTimer, UE is reduced to secondary AG.

Scheduling priority weighting factors: (hsupaSchedulerWeight) The scheduler shall be provided one weighting factor per scheduling priority.



Specifies the weighting factors (alpha(k)) for each HSUPA scheduling priority level k 0...15.The attribute is applicable only if the LocalCellE is HSxPA-capable, otherwise it shall be ignored.There shall be one value per priority level and per radio cell.

1000R/W-Formula: x/1000Value range: 1 to 1000

hsupaSchedulerWeight

DefaultR/WUnitRangeName

HSUPA and HSDPA packet schedulers in the NodeB take the SchedulingPriority Indicator (SPI) into account. HSUPA and HSDPA packet schedulers weight different priority queues basedon SPI values. There is a weight value per SPI value in the NodeB(hsupaSchedulerWeight), which sets the magnitude how often queues ofdifferent SPI classes get scheduled in relation to other SPI classes.

0N/ABackground

115 (lowest)

151 (highest)Interactive

Scheduling Priority Indicator (SPI)Traffic handling priorityTraffic class


Scheduler in NodeB: Input parameters

Random Errors / Defects

OMC

LMT

TTITimer

HSUPA Scheduler

CHC

UE

HSDPAScheduler

RNC

O&M commands,Parameters

O&Mcom

mands,

Paramete

rs

RLfai

lure

Hap

pyB

it,S

ched

ulin

gIn

fo,

TBS

RTWP

CH

Cde

fect

NBAP log. O&M

NBAP UE-related procedures

UL congestion indication

Node B


NodeBScheduler Interface

FromFrame Protocol

Scheduler / CHCInternal

From E-DPCCHor E-DPDCH

Measurements



Scheduler Parameters

Input Data Output Data-Relative Grant (non-serving RLS)-Absolute Grant-Primary / Secondary Indicator

Congestion info from RNC-UE / MAC-d flow ID-Reference Congestion Limit-Indication of TNL Limitation

1

*

1

1

UE-related information

1

*

1

UE group related info

1

1..*

UE-specific-Relative Grant-Minimum SF

Neighbour cell specific-Internal Relative Grant

1

*

1

*



Scheduler Parameters

Configuration Data Input Data

Node B Configuration-Filter Coefficients-Constant Psi

E-DCH Cell Configuration-E-AGCH channelisation codes-Maximum Target RTWP-Reference RTWP-Target Non-serving E-DCH to Total E-DCH Power Ratio-Target Ratio of Avg. Pwrs. of Other E-DCH RLs (for Int. RG)-Maximum Secondary Absolute Grant-Max. No. of Simult. UEs with Primary_Grant_Available = "True"-Time Constant for UE Inactivity Detection-Scheduling Priority Weighting Factors-Rx Antennas-Scheduler Type-E-AGCH 3-Index-Step Threshold-E-AGCH 2-Index-Step Threshold-Time Constant for Assignment of Primary Absolute Grants-Init Value for Overhead Factor-Time constant for determination of TEBS status

11

10..*1

0..*

Node B / CHC internal signals-RTWP-E-DCH pwr (serving RLs)-E-DCH pwr (Other E-DCH RLs)-E-DCH pwr (non-serv. RLs)-Numbers of Other E-DCH RLs-BB Resource Status

Info from UE-Happy Bit-UPH-TEBS-HLBS

Congestion info from RNC-UE / MAC-Reference Congestion Limit-Indication of TNL Limitation

1

*

1

*

1

1

UE-related information

1

*

Node B internal info-HARQ process state-Duration of inactivity-Serving Grant-Primary Grant Available

1

*

UE group related info-Stored Secondary Grant

1

1..*


Scheduling Information

Periodically or if triggered the UE may transmit scheduling information (SI)on the E-DPDCH to the NodeB.

The information in the SI includes: Amount of data waiting to be transmitted in the buffer (TEBS) The priority of that data and the amount of the data with highest priority UPH: UE power headroom, the ratio of the maximum UE tx power and the

DPCCH power

The information from the SI is taken into account by the NodeB for thescheduling process

The SI contains a lot of information, is complex to encode and produces alarge overhead in signalling data A 2nd, more lean and faster mechanism via the Happy Bit is available in

addition.


Scheduling Information: RNC O&M Parameter

Periodicity for the UE to transmit scheduling information when Serving Grant is not assigned.

everyEDCHTTIRWms{everyEDCHTTI, ms4,ms10, ms20, ms50,ms100, ms200, ms500,ms1000}

pesc_ngperiodSchedInfoNoGrant

PERINOGRANT

sbs3gRanPeriodNoGrant

PeriodicityforScheduling Info nogrant

DefaultR/WUnitRangeLMT-Name

LongnameShortname

Q3-Name

Name

Periodicity for the UE to transmit scheduling information when Serving Grant is assigned.

everyEDCHTTIRWms{everyEDCHTTI, ms4,ms10, ms20, ms50,ms100, ms200, ms500,ms1000}

pesc_gperiodSchedInfoGrant

PERIGRANT

sbs3gRanPeriodGrant

PeriodicityforScheduling Info grant

DefaultR/WUnitRangeLMT-Name

LongnameShortname

Q3-Name

Name


cre edcinf edch_pref=rv0 etfci_idx=1 pesc_ng=every pesc_g=every maxrm_edch=15 edch_po=0


Happy Bit

The UE indicates every TTI on the E-DPCCH whether it is happy with the currentlyassigned E-DPDCH resources or not via the Happy Bit.

Happy Bit = 0 not happy Happy Bit = 1 happy

For every E-DCH transmission, the Happy Bit shall be set to "unhappy" if the threefollowing criteria are met: (TS25.321)

UE is transmitting as much scheduled data as allowed by the current Serving_Grant inE-TFC selection; and

UE has enough power available to transmit at higher data rate; and More than Happy Bit Delay Condition ms is required under the current conditions to

transmit the data in the UE buffer (TEBS).

Otherwise, the Happy Bit shall be set to "happy".

The NodeB scheduler takes that information into account when assigningresources for the next transmissions.

TEBS: Total E-DCH buffer status


Happy Bit RNC system internal parameter

Used when determining thesetting of the happy bit (asspecified in specified in 3GPPTS25.321).

10msms2ms, 10ms,20ms, 50ms,100ms, 200ms,500ms,1000ms

EnumeratedHappy bit delay condition

DescriptionDefaultUnitRangeTypeName

Happy bit delay condition is a system internal (hidden) parameter inUMR6.5.

Per UE category

It is a operator configurable parameter in RAS06(HappyBitDelayConditionEDCH).Default: 50ms


Scheduler Algorithm

Maximum PrimaryAbsolute Grant

Maximum SecondaryAbsolute Grant

Current SecondaryAbsolute Grant

Grant/Rate

UEs

Time

UE getsassigned

PAG

UE ismodifiedwith RGs



UE getsPAG

inactive

UE may usecurrent SAG

UE usingPAGs at thesame time is

limited

UE usingPAGs at thesame time is

limited

MaximumSAG isreached

UEsaddressedas a group

UEaddressedindividually UE on SAG

stopstransmission

UE on SAGmay start

transmissionarbitrarily


Scheduling illustration

Each Node B has fast control over the UE transmit power.The noise rise is controlled via fast Node B scheduling.

servingNode B

NB

NB

NB

UE sends rate requestto serving Node B

Serving Node B sendsAbsolute Grant

(limits the UEs sending power)

non servingNode Bs

A DOWN commandreceived by a non serving

Node B, has highestpriority !

Serving Node B sendsRelative Grant

UP DOWN HOLD

up - down - hold

hold

-do

wn

hold

Non serving Node Bs may onlysend Relative Grants to the UE

DOWN or HOLD

Non Serving NB

Non Serving NB


HARQ: Hybrid automatic repeat request


HARQ Process

There is one HARQ entity per UE. For the 10ms TTI, 4 HARQ processes are configured For the 2ms TTI, 8 HARQ processes are configured

HARQ messages (ACK/NACK) are send on the E-HICH to the UE

For retransmission, NodeB supports Chase Combining (CC) andIncremental Redundancy (IR)

HARQ messages are send by all NodeBs in the E-DCH active set: The NodeB with the serving E-DCH RLS send ACK and NACK msg. Other NodeBs only send ACK messages

For each RLS, one common HARQ information is send.

The UE continues to transmit as long there is at least one ACK messagereceived

NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCH

Serving RLS






NodeB 1 NodeB 2

Serving E-DCHCell

E-AGCHE-HICH

E-RGCHE-AGCHE-HICH

E-RGCH

Serving RLS






2ms TTI not yetsupported by NSNimplementations.


HARQ Process in soft handover

Serving NB

NB NB

NB

If one Node B receives the data packet correctly,further retransmissions from the UE can be stopped.Regardless what result the other involved Node Bshave received, the correctly received data packet willbe delivered to the higher layers. The UE needs toretransmit only when all involved Node Bs ask for it.

RNC

UE sends transportformat and data

packetAC

K

ACKACK, NACK

Non Serving Node Bssend back only ACK

The Node B thatcorrectly received thedata, forwards it to the

RNC (RLC)

RLC performsreordering of data

PDU

Non Serving NB

Non Serving NB

re-tx

UE sends retransmissiononly if no ACK message is

received


4 HARQ processes for the 10ms TTI The number of required HARQ processes results from the

- TTI size,- processing time in the NodeB,- propagation delay on the air-interface.

i-3 i-2 i-1 i

i-3 i-2 i-1 i

CPICH / P-CCPCH

E-DPDCH /E-DPCCH

i+1

1 2 3 0 1

i-3 i-2 i-1 i i+1

i-3 i-2 i-1 i i+1E-HICH

Tx (UE)

Rx (NB)

Processing timeat Node B

30ms = 115200 chips

2048 chips38400 chips

5 8 slots

i-3 i-2 i-1 i i+1

DL DPCH

Tx (NB)

For the 10ms TTI, 4 HARQ processes per UE are sufficient

Timing relation between uplink data transmissions and ACK/NACK sent on E-HICH for the 10ms TTI


HARQ Process: O&M Parameter I

rv0 indicates that the UE will only use E_DCH RV index 0.rvtable indicates that the UE will use an RSN based RV index as specified in 3GPP TS25.212Recommendation: rvtable

rv0Rec:rvtable

RW{rv0, rvtable}edch_prefedchHarqInfoPreference

EDCHHARQINFP

sbs3gRanEdchHarqInfoPref

HARQ Info forE-DCHPreference

DefaultR/WRangeLMT-NameLongnameShortnameQ3-NameName

edch_pref selects the HARQ method that will be used: rv0: Redundancy version 0, Chase Combining rvtable: Incremental redundancy

E-DCH MAC-d flow maximum number of retransmissions.

15Rec: 5

RW

0,..,15maxrm_edchmaxNumberRetransmissionEdch

MAXRETREDCH

sbs3gRanMaxNoRetransEdch

Maximum Number ofretransmissions for E-DCH

DefaultR/W

RangeLMT-NameLongnameShortnameQ3-NameName

Recommendation: Set maxrm_edch to 5


HARQ Process: O&M Parameter II

The E-DCH HARQ Power Offset FDD is used to calculate the unquantised gain factor for an E-TFC (bed,j,uq) as defined in3GPP TS25.213.

0RWdB0,..,6edch_poedchHarqPowerOffsetFdd

EDCHHARQPWROFD

sbs3gRanEdchHarqPowOffFdd

E-DCHHARQ PowerOffset FDD

DefaultR/W

UnitRangeLMT-NameLongnameShortnameQ3-NameName



MAC-d flow specific power offset that is added on top of the transportblock specific power offset. A larger power offset means a lowerpropability of needing a retransmission and, thus, lower latency.

However, a higher power offset will likely result in a lower chosentransport block size, what will cause lower throughput.


HARQ Process: Impacts of parameter settings

The two parameters could be set in a way that:

- Delay tolerant services can have a lower power offset (edch_po)and higher retransmission propability,

- Streaming services can have a lower max. retransmission count(maxrm_edch) as they tolerate a few lost packets.


HSUPA RAB Handling


Supported HSUPA RAB Combinations

7.5.86464HS-DSCH

E-DCHPS + CSInteractive/Background +Conversational

ConversationalTransparent Data

Packet

7.5.412.212.2HS-DSCH

E-DCHPS + CSInteractive/Background +Conversational

NB-AMRPacket

7.5.1--HS-DSCH

E-DCHPSInteractive/Background-Packet

DLULDLUL21

21 3GPP Reference25.993

Max Rates for each RAB kbpsCS/PSTraffic ClassRABs

HSUPA establishment always requires the UE and the cell to be HSDPA capable

Single NRT call as well as multi call possible

In case of a multi call, only 64/64 kbps Rel.99 possible in addition to E-DCH

Only the RLC PDU size of 336 bits shall be supported for E-DCH


State Model (DCH_INACTIVITY is ON) with new E-DCH state

Cell_DCH

FACH_ACTIVE

Cell_PCH

DCH_ACTIVE

Single PS I/B AMR + PS I/B

AMR RAB Setup/RAB or IU Release

AMR RAB Setup

FACH_INACTIVEDCCH_ACTIVE

DCCH_INACTIVE

PS I/B Setup

PS I/B Setup

PS I/B Setup

In-/outward Mobility

T_HS-DSCH_FACH

T_FACH_PCH

UL or DLDTCH Activity

DCCHInactivity

DCCH Activity/Inactivity detection

T_HS-DSCH_FACH

T_DCH_FACH

T_FACH_PCH

AMR RAB Release

AMR RAB Setup/CS RAB or IU Release

CS IU Release

TVM 4A (RACH) orDL DTCH overflowor "Directed Retry"

HS-DSCH+

E-DCHCell_DCH

+HS-DSCH

In-/outwardMobility

HS-DSCH_E-DCH-ACTIVE

HS-DSCH-ACTIVE

In-/outwardMobility


UL BRA

TVM 4A orDL DTCH Activity

UL BRA

DCH_INACTIVE State

UL or DLDCCH Activity

DL DTCHActivity

CS RAB or IURelease

SBHO"Directed

Retry"

AMR RAB Setup/RAB or IURelease

PS I/B Setup

PS I/B Setup


State Model (DCH_INACTIVITY is OFF) with new E-DCHstate

Cell_DCH

FACH_ACTIVE

Cell_PCH

DCH_ACTIVE

Single PS I/BUDI + PS I/B or

AMR + PS I/B (DCH_INACTIVITY = FALSE)

AMR/UDI RABSetup/RAB or IU

Release

AMR/UDI RAB Setup

FACH_INACTIVE

PS I/B SetupPS I/B Setup

PS I/B Setup

PS I/B Setup

PS I/B Setup


T_HS-DSCH_FACH

T_FACH_PCH

DCCHInactivity

T_DCH_FACH

TVM 4A (RACH) orDL DTCH overflowor "Directed Retry"

HS-DSCH+

E-DCHCell_DCH

+HS-DSCH

In-/outwardMobility

HS-DSCH_E-DCH-ACTIVE

HS-DSCH_ACTIVE

In-/outwardMobility


UL BRAUL BRA

UL or DL DCCHActivity

DL DTCHActivity

CS RAB Setup/RAB or IU Release

SBHO"Directed

Retry"

AMR/UDI RAB Setup/RABor IU Release

CS RAB Setup

UL or DL DTCHActivity


Inactivity detection

When the UE is in HS-DSCH + E-DCH or HS-DSCH_E-DCH-ACTIVEstate (HSUPA mode), inactivity detection is based on the existing timerT_HS-DSCH_FACH.

Period of uplink and downlink inactivity before the PS I/B RAB is switched from HS-DSCH to FACH0 means that inactivity is not monitored and the connection is not switched to FACH

30RWs0,..,65535

Integer

thsdsch_fachhsDschFachSwitchTmr

HSDSCHFCHSWTMR

sbs3gRanHsDschFachSwitchTmr

Timer forthe switchfrom HS-DSCH toFACH

DefaultR/WUnitRangeTypeLMT-NameLongnameShortnameQ3-NameName

Example of command execution (hmi):cre rbc tfach_dchue=20 tbra_riue=1280 tbra_rdue=1280 tdch_fachr=65535 tfach_pchr=300 tpch_idler=7200 thsdsch_fach=30ulbra_ript=64K ulbra_rdpt=8K ul_fdpt=256 dl_upt=512 max_ccros=20 srbr=13.6 dch_inact=true ch_nonrab=comm ch_ibrab=dedcini_pib=64_64 t_strminact=0 flag_preempt=false ini_hsulpib=64 pc_csudi=false pc_psbe=false


HSUPA Mobility aspects


Overwiew

HSUPA supports soft handover One cell out of the active set acts as Serving E-DCH cell The serving E-DCH cell uses the E-AGCH and E-RGCH for scheduling

operation The other cells only use the E-RGCH and only send DOWN or HOLD Cells belonging to the same NodeB as the E-DCH serving cell, belong to

the Serving E-DCH radio link set


E-DPDCH(user data)


E-DPDCH

(user data)

E-RGCH(down,

hold)

Serving E-DCH RLS


E-DCH Active Set Size:E-DCH and DCH Active Set Size identical


E-DCH Active Set Size:E-DCH subset of DCH Active Set


Active set summary

For each UE, the E-DCH active set contains one Serving E-DCH RLS withone Serving E-DCH RL.

It is possible to have zero, one or more E-DCH RLs, which belong tothe Serving E-DCH RLS but which are not the Serving E-DCH RL. And,the E-DCH active set can contain zero, one, or more Non-Serving E-DCH RLs (which does not belong to the Serving E-DCH RLS).

For each UE, there is only one Absolute Grant transmitted by the ServingE-DCH Cell via the E-AGCH.

For each UE, there is one common Relative Grant (optional) transmittedper Serving E-DCH RLS, and, also one per Non-Serving E-DCH RL.


HSUPA mobility impact The main areas of E-DCH Mobility impacts are the followings:

UE Differentiation Algorithm E-DCH Serving Cell Selection E-DCH Inward Mobility (Intra freq. and Inter freq. HO case) E-DCH Serving Cell Change (Intra freq. and Inter freq. HO case) E-DCH Outward Mobility (Intra freq. and Inter freq. HO case) SHO handling for Non-Serving E-DCH RLs Inter System HO SRNS Relocation*

[Note]: Compressed Mode with E-DCH is not supported [Note]: E-DCH over Iur is not supported *[Note]: E-DCH Relocation is not supported


HSUPA Mobility aspectsUE differentiation algorithm


E-DCH UE differentiation algoritm UE Differentiation algorithm is applied during RRC Connection Setup and CTS

CtoD transition (due to NRT traffic overflow trigger).

UTRAN shall direct the E-DCH Capable UE with NRT RAB related RRCsignalling establishment to the freq. carrier which supports E-DCH.

The algorithm works only with Inter-Frequency Cells of the same sector (i.e. sameantenna flags set to TRUE)

E-DCH/HS-DSCH CapableUE Camps on RF1

E-DCH/HS-DSCH Capable UEshall be first attempted on RF3

If attempt on RF3 fails, furtherattempts on RF4 is performed

RF1 (Rel99)

RF2 (Rel99)

RF3 (E-DCH/HS-DSCH)

RF4 (E-DCH/HS-DSCH)

E-DCH/HS-DSCH CapableUE Camps on RF1

E-DCH/HS-DSCH Capable UEshall be first attempted on RF3

If attempt on RF3 fails, furtherattempts on RF4 is performed

RF1 (Rel99)

RF2 (Rel99)

RF3 (E-DCH/HS-DSCH)

RF4 (E-DCH/HS-DSCH)


E-DCH UE differentiation algoritm

To reserve the E-DCH/HS-DSCH Cell as much as possiblefor E-DCH/HS-DSCH capable UEs, HCS priorities for thedifferent layers should be set:

Non-E-DCH/HS-DSCH Cell (highest Priority) >>HS-DSCH Capable Cell >>E-DCH/HS-DSCH Capable Cell (lowest Priority)


Establishment Cause for UE Differentiation

The UE differentiation algorithm attempts to redirect a Rel6 UE to theappropriate frequency layer, if at RRC setup or CTS from FACH the

Establishment cause IE contains a cause value with corresponding bit inEstablishment Cause for UE Differentiation flag set to 1

Specifies Establishment Cause which will be considered in UE Differentiation procedure as HSDPA or HSUPA Capable.Establishment Cause for UE Differentiation flag is a bitmap of 32bits long. Each bit of this flag will correspond to an Establishment Cause.Bit 0 corresponds to originatingConversationalCall, bit 1 corresponds to originatingStreamingCall and so on. Following table shows how theeach bit of Establishment Cause for UE Differentiation flag is mapped to Establishment Cause and the default setting of this flag.

LMT: 16796(hex:0000419C)

LMT: 0,...,4294967295(hex:0,..,FFFFFFFF)

LMT: Integer(hex)RC: BitString[32]

ecuedifesatblCauseForUeDifferentiation

CAUSEUEDIFsbs3gRanEstCauseForUeDiffer

EstablishmentCause for UEDifferentiation

DefaultRangeTypeLMT-NamelongnameShortnameQ3-NameName

Originating

ConversationalC

all

Originating

Stream

ingC

all

Originating

InteractiveC

all

Originating

Background

Call

Originating

Subscribed

trafficC

all

Terminating

ConversationalC

all

Terminating

Stream

ingC

all

Terminating

InteractiveC

all

Terminating

Background

Call

Em

ergencyC

all

Inter-RA

Tcellre-selection

Inter-RA

Tcellchange

order

Registration

Detach

Originating

High

Priority

Signalling

Originating

LowP

riorityS

ignalling

Callre-establishm

ent

Terminating

High

Priority

Signalling

Terminating

LowP

riorityS

ignalling

Terminating

cause

unknown

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

(Spare

value)

Establishm

entCause

00111001100000100000000000000000DefaultSetting

00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

bit

A Rel6 UE,that

establishes aAMR speechcall will not

be redirectedto the HSPA

layer.


UE Differentiation SWP data

Enhanced UE differentiation algorithm is an optional feature which is notincluded in the standard feature set.

In order to enable it, the UE differentiation flag in the SWP data must beset to true

Flag set to 0 when operator has boughtthe feature

11 : off

0 : on

BooleanHSDPA UE differentiationfunction switch flag1 : off0 : on

DescriptionDefaultRangeTypeName


HSUPA Mobility aspectsE-DCH serving cell selectionE-DCH inward mobilityE-DCH serving cell changeE-DCH outward mobilitySHO of non serving radio linksBlind IFHOTiming re-initialized IFHOIntersystem HandoverSRNS relocation


E-DCH serving cell selection

The serving E-DCH Cell is selected based on best downlink quality cell: Considers a cell which provides the highest reliability for DL transmission of

AG to the UE A common DL best quality measure shall be beneficial generally for overall

performance of HSPA.

For the Serving E-DCH Cell: Select the Best Quality E-DCH/HS-DSCHCell for which the UE has reported the highest DL CPICH Ec/N0 or CPICHRSCP or smallest Pathloss value in the received RRC MeasurementReport 1A/1B/1C/1D.

For the Serving E-DCH RLS: Select the Node-B (RLS) where Serving E-DCH Cell is determined.

Event 1D triggers the change of the best cell


E-DCH inward mobility 1/2

E-DCH Inward Mobility is triggered, if the Measurement Report 1A/1B/1C/1D isreceived and the reported E-DCH/HS-DSCH Cell has the best quality. Also, thequality difference between the best Serving E-DCH Cell and others shall begreater than a predefined hysteresis (cre ifmrms hyst1d).

When E-DCH Inward Mobility is triggered, active set update (ASU) procedure (ifEvent 1A/1B/1C is received) is performed first, in preparation for the E-DCHInward Mobility procedure.

Rel99 E-DCH/HS-DSCHRel99 E-DCH/HS-DSCH

Serving E-DCH/HS-DSCH Cell


1A: this cell is newly added andit is Best Quality Cell

SRNC

SRNC

Serving E-DCH/HS-DSCH RL

RLs in DCH Active Set


E-DCH inward mobility 2/2

Supported Inward Mobility procedures:

From DCH/DCH to E-DCH/HS-DSCH

From DCH/HS-DSCH to E-DCH/HS-DSCH - Intra Node-B Case

From DCH/HS-DSCH to E-DCH/HS-DSCH - Inter Node-B Case


E-DCH serving cell change 1/2 E-DCH Serving Cell Change (SCC) is triggered if the quality of existing Serving

E-DCH/HS-DSCH Cell becomes worse than an other E-DCH/HS-DSCH Cellwithin the DCH Active Set.

When SCC is triggered, ASU procedure (if Event 1A/1B/1C is received) isperformed first, in preparation for the E-DCH SCC procedure.



1A: this cell is newly added andit is Best Quality Cell



SRNC

SRNCServing E-DCH/HS-DSCH RL



E-DCH serving cell change 2/2

Trigger 1: Measurement Report 1A/1B/1C/1D is received and the Quality ofthe current Serving E-DCH Cell is worse than other reported Cell (new best E-DCH Serving Cell).Also, the quality difference between the current Serving E-DCH and new bestE-DCH Cell is greater than a predefined hysteresis(cre ifmrms hyst1d).

Trigger 2: Measurement Report 1B/1C is received and the current Serving E-DCH Cell is removed, but another E-DCH Cell is available in the Active Setand the quality of this cell is the best.

Supported Serving Cell Change (SCC) procedures: SCC Intra Node-B Case SCC Inter Node-B Case


E-DCH outward mobility 1/3

E-DCH Outward Mobility is triggered if the UE leaves the E-DCH coverage or ifthe quality of the Non-E-DCH Cell is the best (among the Active Set cells).

When Outward Mobility is triggered, ASU procedure (if Event 1A/1B/1C isreceived) is performed first, in preparation for the E-DCH Outward Mobilityprocedure.




New link addedvia 1A

Quality of this link is worse thanNon-E-DCH Cell(s)

SRNC

SRNC

Serving E-DCH/HS-DSCH RL




Trigger 1: Event 1A/1B/1C/1D is received, and, the Quality of Non-E-DCHCell is better than all E-DCH Cell(s) within active set.Also, the quality difference between the current E-DCH Serving Cell and newbest Non-E-DCH cell is greater than a predefined hysteresis(cre ifmrms hyst1d).

Trigger 2: Event 2D (IFHO Triggers) is received and if IFHO with Inter-Frequency measurement (2A/2B) is triggered.[Note]: Blind IFHO does not invoke Outward Mobility.

Trigger 3: Event 2D/2D (Inter System 3A/3A Triggers)

Trigger 4: Upon reception of NBAP: RL Failure Indication to the currentServing E-DCH Cell.



Supported E-DCH Outward Mobility procedures:

From E-DCH/HS-DSCH to DCH/DCH

From E-DCH/HS-DSCH to DCH/HS-DSCH Intra Node-B Case

From E-DCH/HS-DSCH to DCH/HS-DSCH Inter Node-B Case


SHO of non-serving E-DCH RLs

RNC configures all potential E-DCH links constituting towards E-DCHActive Set. This is to realise the Soft/Softer HO gains for E-DCH configurations.

When Event 1A/1C is received, and if the UE context has beenconfigured with E-DCH, any newly to-be-added E-DCH RL shall beconfigured as part of E-DCH Active Set. Firstly, Rel6 NBAP: RL Setup/Addition Request message is applied to

perform SHO, and, to configure the E-DCH Link as part of E-DCH ActiveSet.

Secondly, Rel6 RRC: Active Set Update is applied to perform SHO, plus,the configuration of new E-DCH info.


Blind IFHO

SRNC attempts to keep E-DCH/HS-DSCH configuration (i.e. E-DCHOutward Mobility is not performed), in case if Timing Maintained HardHandover is initiated (Blind IFHO reception of Event 2D).

Supported Blind IFHO procedures: E-DCH Inward Mobility

- From DCH/DCH or DCH/HS-DSCH to E-DCH/HSDCH E-DCH Serving Cell Change E-DCH Outward Mobility to DCH/HS-DSCH E-DCH Outward Mobility to DCH/DCH


Timing Re-initialized IFHO

If Timing Re-Initialised IFHO is invoked, SRNC performs E-DCHOutward Mobility to DCH/HS-DSCH, in preparation for Timing Re-Initialised IFHO with Inter-Frequency measurement(2A/2B) procedure.

Supported E-DCH Timing Re-initialised IFHO procedures: E-DCH Inward Mobility

- From DCH/DCH or DCH/HS-DSCH to E-DCH/HSDCH


Intersystem Handover

When UE is leaving the UMTS coverage with currently configured E-DCH/HS-DSCH, the reception of ISHO Event 2D/2D shall lead to E-DCH Outward Mobility to DCH/DCH, in preparation for the ISHOprocedure.


SRNS Relocation

For the case if SRNS Relocation Type of UE Involved without Iur isto be triggered, E-DCH Outward Mobility to DCH/HS-DSCH orDCH/DCH (depending on the Target RNC RRC Container supportversion) is first performed, in preparation to relocation procedure.

[Note]: For the case of SRNS Relocation Type of UE Not Involvedwith Iur or UE Involved with Iur, the UE state would have beenmoved to either DCH/DCH or DCH/HS-DSCH, prior to the relocationtrigger. This is due to the fact that E-DCH is not supported over Iur,and, the trigger for abovementioned relocation types is when theentire Active Set belongs to DRNC.


HSUPA Admission control


HSUPA Admission control

Admission control is triggered by procedures which set-up, add,delete or reconfigure a radio link.

A new radio bearer is admitted only, if the required resources areavailable in the cell and the QoS requirements of the alreadyexisting connections can be met after admission.

To maintain the satisfactory throughput on HSUPA, it must beprevented that too many HSUPA UEs are accepted in a cell.

For the new UL E-DCH channel, the existing AC algorithm hasbeen extended.


BLOCK BE to E-DCH Flag

Admission control sets in each HSUPA cell the BLOCK BE toE-DCH flag (true, false), based on the

number of serving E-DCH RLs (nth1, nth2) cell load utilization (cell_util_th)

The BLOCK BE to E-DCH flag is set to TRUE, if Number of serving E-DCH RLs >= Nth1 && Cell load Utilization > Cell_util_th Number of serving E-DCH RLs >= Nth2 (>= Nth1)


cre cell adc2 cellid=1 nodebid=1 nth1=10 nth2=32 cell_util_th=0.90 aul_hsupa=1.50


Cell load utilization calculation

The cell load utilization is defined as Cell Load Utilization = (Cell Load) / (Target Cell Load)

Cell Load: Cell Load calculated with measured and higher layer filtered RTWPTarget Cell Load: Cell Load calculated with Target RTWP(Cell Load = 1 Nul/RTWP and Target Cell Load = 1-Nul/Target RTWP)

Target RTWP: derived from theO&M Parameter HSDPA Scheduler Offset(hsupa_oft)

RTWP Congestion Level

(N_ul+CCThreshold)Congestion Level CC Hysteresis

Current Cell Load

Maximum Target RTWP


TIME


cre cell cctl cellid=1 nodebid=1ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90dl_cngh=0.15 mmti_rtwbp=10.00mmti_tcp=10.00 k=1 ebd=ena etpchr=enaperi_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0cc_emg=false hsupa_oft=0.5


BLOCK BE to E-DCH flag parameters

Cell load utilization threshold toapply Nth1 as Maximum number ofServing E-DCH RLs acceptable in aserving cell

LMT:0.9RC:90

LMT: 0,..,1step by 0.01RC: 0,..,100

LMT:RealRC:Integer

cell_util_th

cellUtilThres

CELLUTLTHR

sbs3gRanCellUtilThres

Cell_util_th

Maximum number of Serving E-DCH RLs acceptable in a servingcellNote : Nth2 >= Nth1

320,..,100Integernth2nth2NTH2sbs3gRanNth2

Nth2

Maximum number of Serving E-DCH RLs acceptable in a servingcell in case Cell load Utilization >Cell_util_thNote : Nth2 >= Nth1

100,..,100Integernth1nth1NTH1sbs3gRanNth1

Nth1

DescriptionDefault

RangeTypeLMT-Name

Longname

Shortname

Q3-Name

Name

cre cell adc2




Update of admission control UL scaling factor

UL load of the E-DCH channels can not be estimated as it is the case for DCH The actual load in UL created by an E-DPDCH is variable depending on the

decisions of the HSUPA scheduler

Because of this fact, the algorithm-internal UL scaling factor can not be updatedcorrectly in the conventional way if E-DPDCH traffic existing in the cell

UL AC Scaling factor update rule for UMR6.5:

IF the E-DCH/HS-DSCH cell has no Radio Link to any HSUPA UEs use conventional averaged UL scaling factor in AC ELSE use fixed HSUPA UL scaling factor (aul_hsupa) in AC


UL scaling factor HSUPA Parameter

HSUPA UL scaling factor used as fixed scaling factor in a cell, in case of HSUPA UEs which allocate Serving E-DCHRL exists in that cell

LMT:1.5RC: 150

LMT: 0,..,10 step by0.01RC: 0,..,1000

LMT:RealRC:Integer

aul_hsupascalingFactorHsupa

SCFACTHSUPA

sbs3gRanHsupaScalFact

aUL_HSUPA

DefaultRangeTypeLMT-NameLongname


cre cell adc2




Admission Control for HSDPA/HSUPA callNew Call Establishment Step1 : HSDPA / HSUPA blocking check

BLOCK BE to E-DCH and BLOCK BE to HS-DSCH flags must be setto FALSE

Step 2 : Load based HSDPA/HSUPA AC control

Only the load of non-scheduled dedicated channels are considered. The load is calculated in a conventional way using physical layer

characteristics of the bearers mapped on these channels (UL/DL) andthe scaling factor of AC (UL/DL):

UL and DL DPCH for SRB signalling UL DPCH for the HS-DPCCH (serving cell only)


Admission Control for HSDPA/HSUPA callHSUPA Soft Handover Load based HSDPA/HSUPA AC control: only the load of non-

scheduled dedicated channels is considered.

The load is calculated in a conventional way using physical layercharacteristics of the bearers mapped on these channels (UL/DL)and the scaling factor of AC (UL/DL):

UL and DL DPCH for SRB signalling

AC shall use admission control load threshold for handover bearersfor the UL/DL DPCH


Admission Control for HSDPA/HSUPA callInterfrequency Handover DCH to E-DCH and E-DCH to E-DCH

Step1 : HSDPA / HSUPA blocking check BLOCK BE to E-DCH and BLOCK BE to HS-DSCH flags must be set

to FALSE Step 2 : Load based HSDPA/HSUPA AC control

Only the load of non-scheduled dedicated channels are considered. The load is calculated in a conventional way using physical layer

characteristics of the bearers mapped on these channels (UL/DL) andthe scaling factor of AC (UL/DL):

UL and DL DPCH for SRB signalling UL DPCH for the HS-DPCCH (serving cell only)

E-DCH to DCH The conventional load based AC will be done for admission to DCH


Admission Control for HSDPA/HSUPA callInward Mobility

DCH/DCH to HS-DSCH/E-DCH Step1 : HSDPA / HSUPA blocking check

BLOCK BE to E-DCH and BLOCK BE to HS-DSCH flags must beset to FALSE

Step 2 : Load based HSDPA/HSUPA AC control UL and DL DPCH for SRB signalling UL DPCH for the HS-DPCCH

HS-DSCH/DCH to HS-DSCH/E-DCH Step1 : blocking check

BLOCK BE to E-DCH flags must be set to FALSE BLOCK BE to HS-DSCH flags must be set to FALSE if serving cell

changes Step 2 : Load based HSDPA/HSUPA AC control

UL and DL DPCH for SRB signalling UL DPCH for the HS-DPCCH


Admission Control for HSDPA/HSUPA callServing Cell Change

Step1 : HSDPA / HSUPA blocking check BLOCK BE to E-DCH and BLOCK BE to HS-DSCH flags must be set to

FALSE

Step 2 : Load based HSDPA/HSUPA AC control UL DPCH for the HS-DPCCH


Congestion Control


Congestion handling

Event Triggered common measurements are used forcongestion detection

Two staged congestion resolution handling Stage1 : BRA, CTS Stage2 : BRA, CTS, Call Dropping

HSDPA DL/HSUPA UL UEs will be considered only in Stage 2

UEs selection criteria for congestion handling In DL or DL/UL Congestion: Downlink spreading factor (HSDPA DL/DCH

UL UEs and HSDPA DL/HSUPA UL UEs, the SF of their associated DPCHchannel will be used)

UL Congestion: Minimum UL Channelisation Code Length


DL congestion handling

Stage1 Following UEs are handled in Stage1 beginning with the one having

the lowest SF: For CTS: Single PS BE UEs (excluding HSDPA DL/HSUPA UL and

HSDPA DL/DCH UL UEs) For BRA: Multi-call PS BE UEs (except UEs with minimum rate, HSDPA

DL /DCH UL multi-call and ,HSDPA DL/HSUPA UL multi-call)

Stage2 Firstly, pre-emptable RLs are ordered in ascending order of priority

class and ascending order of DL SF Secondly, all non-pre-emptable RLs are ordered in ascending order of

DL SF CTS , BRA or Call Dropping are applied in every congestion handling

period For single-call HSDPA DL/DCH UL, single-call HSDPA DL/HSUPA

UL bearers CTS is applied


UL congestion handling

Stage1 Following UEs are handled in Stage1 beginning with the one having

the lowest Min. UL Channelisation Code length: For CTS : Single PS BE UEs (excluding HSDPA DL/HSUPA UL , including

HSDPA DL/DCH UL UEs) For BRA : Multi-call PS BE UEs (except UEs with minimum rate, HSDPA

DL/HSUPA UL multi-call)

Stage2 Firstly, pre-emptable RLs are ordered in ascending order of priority

class and ascending order of Min. UL Channelisation Code length. Secondly, all non-pre-emptable RLs are ordered in ascending order of

Min. UL Channelisation Code length. CTS , BRA or call dropping are applied in every congestion handling

period For single-call HSDPA DL/DCH UL, single-call HSDPA DL/HSUPA UL

bearers CTS is applied


Congestion Control Interactions with Scheduler

It must be assured that HSUPA Traffic will not cause congestion in a cell Maximum Target RTWP value for scheduler is defined according to

Congestion Control Thresholds in a cell Maximum Target RTWP is derived from the O&M Parameter HSUPA

Scheduler Offset (hsupa_oft)

RTWP Congestion Level (N_ul+CCThreshold)

Congestion Level CC Hysteresis

Current Cell Load

Maximum Target RTWP


TIME


Scheduler offset parameter


cre cell cctl cellid=1 nodebid=1 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00 mmti_tcp=10.00 k=1ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false hsupa_oft=0.5

Offset value to calculate Maximum Target Received Total Wide Band Power

LMT:0.5RC: 5

RW**)

LMT: dBRC:0.1*dB

LMT: 0..10 step by0.1RC: 0..100

LMT:RealRC:Integer

hsupa_oftschedulerOffsetHsupa

SCHDOFFSHSUPA

sbs3gRanHsupaSchedOff

HSUPA_scheduler_offset

DefaultR/W


Longname



Outer loop power control


HSUPA OLPC

Outer loop power control is located in the RNC and operates with blockerrors (CRC indication) as input to achieve a certain desired block errorrate (BLER).

In HSUPA only case, MAC level retransmissions are performed by aHARQ protocol between the UE and the Node B

The BLER seen by the OPLC in the RNC will be much lower than the BLER seen bythe HARQ process in the NodeB

OLPC Handling: without HARQ with HARQ


HSUPA OLPC

Because of this fact, for HSUPA it is more reliable to have an OLPCalgorithm which considers the number of retransmission information.

For each TTI in which E-DPDCH transport block is received or HARQfailure indication is signalled from NodeB, OLPC will update the SIR targetof DPCCH as following:

NHR_th = min[NHR_th, Max_number_of_retransmissions_for_HSUPA]

No change in SIR targetNumber of HARQ Retransmissions = {13,14,15}

STEP_DOWN

[Number of HARQ Retransmissions NHR_th ANDNumber of HARQ Retransmissions {13,14,15} ]ORHARQ Failure Indication Received

SIR target of DPCCHE-DPDCH


Update of SIRtarget

HSUPA=step_sizeHSUPA. (step_hsupa)

In HSDPA/HSUPA only case, the SIR target will be signalled to the closedloop power control (CLPC) in the Node B if the following condition issatisfied:

Update_threshold_for HSUPA is a new O&M parameter (upthr_hsupa)

DOWNstepBLER

BLERSIR

tSIRinchangNoSIRUPstepSIR

SIR

tt

ttHSUPAtOLPC

tOLPC

HSUPAetOLPC

tOLPC

_...1

targe___..............._.............................

:

arge

argetarge

targe

targ

targe_

HSUPAforThresholdUpdateSIRSIR ettCLPCettOLPC ___arg_arg_


OLPC parameters for HSUPA

NHR to decide bad E-DPDCH quality. It isrecommended to set this parametersmaller than Max number ofretransmissions for HSUPA for aneffective functioning OLPC. The values13,14 and 15 are not recommended to set,because in 3GPP these values arereserved.Should not be changed to valuesgreater than 0 in order to avoidthroughput degradation.

0-0..15nhr_thnhrThreshold

NHRTHRsbs3gRanNhrThres

NHR_th

Threshold value for updating the SIR targetin NodeB for HSDPA DL/HSUPA UL onlycase

LMT:0.1RC: 1

LMT:dBRC:0.1*dB

LMT: 0.0,..,25.5step by 0.1RC: 0,..,255

upthr_hsupa

updateThresHsupa

UPDTHRHSUPA

sbs3gRanUpdateThresHsupa

Updatethresholdfor HSUPA

Step size of the outer loop power controlfor HSDPA DL/HSUPA UL only case

LMT:0.3RC: 3

LMT:dBRC:0.1*dB

LMT: 0.0,..,25.5step by 0.1RC: 0,..,255

step_hsupa

stepSizeHsupa

STEPSHSUPA

sbs3gRanHsupaStepSize

Step sizeHSUPA

DescriptionDefault

UnitRangeLMT-Name

Longname

Shortname

Q3-Name

Name


cre olpc thr_upd=0.1 step_size=0.3 lowthr_sirerr=-3 upthr_sirerr=3 mmfc_sirerr=0 ofs_thr2e=1.0 ofs_thr2f=2.0 hyst_tme=80hyst_tmf=80 step_hsupa=0.3 upthr_hsupa=0.1 nhr_th=0


OLPC parameters for HSUPA: NHR_th

When NHR_th is set to a value >0, lab tests have shown negative impact on ULthroughput.

Due to the nature of power control (assign the least needed resources to maintaina given QoS), the OLPC will adapt the SIR target in a way, that the majority of theE-DPDCH transmissions will be done with NHR_th-times retransmissions (e.g. 1retransmission for NHR_th=1).

With 1 retransmission made for nearly each transmission (NHR_th=1), theexpected throughput is halved with respect to an environment, where no or onlylittle retransmission are done.

For the moment, the recommendation is to leave NHR_th at 0 inorder to have maximum throughput and minimum latency.


UE categories


HSUPA UE categories

Like in HSDPA, also in HSUPA different UE categories are defined 6 HSUPA UE categories exist They mainly differ in the number of supported E-DPDCHs and SFs as well

as in the supported TTI sizes Category 6 offers the highest throughput, category 1 the lowest.

NOTE: When 4 codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4

114842000010 ms and2 ms TTI

SF24Category 6

-2000010 ms TTIonly

SF22Category 5

57722000010 ms and2 ms TTI

SF22Category 4

-1448410 ms TTIonly

SF42Category 3

27981448410 ms and2 ms TTI

SF42Category 2

-711010 ms TTIonly

SF41Category 1

Maximum number of bits of an E-DCH transport blocktransmitted within a 2 ms E-DCH TTI

Maximum number ofbits of an E-DCHtransport block

transmitted within a10 ms E-DCH TTI

Support for10 and 2 ms

TTI EDCH

Minimum

spreading factor

Maximumnumber ofE-DCHcodestransmitted

E-DCHcategory

TS 35.306

Cat. 1+3 are fullysupported inUMR6.5 and

RAS06. Othersonly with 10ms TTI

and SF4


User plane architecture for a single MAC-d flow

DCCH / DTCHDATAHeader

MAC-d

MAC-e

DATA

DATA

DATA DATA

RLC PDU:

L1

RLC

MAC-d FlowMAC-es

Reordering

Disassembly

MAC-d PDU:

TSN

MAC-e header

Padding(Opt)DDI1 N1 DATA1DDI0

Transport block:

DDI NIub FP:

HARQ

MAC-es PDU:

E-DPDCH

MAC-e PDU: SI


Transport block strukture

Padding

(optional)

SI(opt.)18 bit

Payload320 bit

Header16

Payload320 bit

Header16

Payload320 bit

Header16

TSN6bit

N6bit

DDI6bit

Transport block of E-DPDCH, MAC-e

MAC-es

RLC PDU (w/ header)

Example:

Transport block size: 2058 bit (E-TFCI: 71) (as the result of the E-TCF selection process) Bits available for RLC PDUs: 2058 bit (6+6+6) bit = 2040 bit

Number of 336 bit RLC PDU per TB: 2040 / 336 = 6.07 6 PDUs

Max. RLC throughput: 6 PDU * 320 bit/PDU *100 = 0.192 Mbps

The size of the MAC-e/es PDU (and so the number of RLC PDUs per TTI) is determinedby the E-TFC selection process in the UE.

DDI: Data Description IndicatorN: Number of MAC-es PDU, fixed to 1 in UMR and RASTSN: Transmission sequence numberSI: Scheduling information, per TTI or also only periodic


Example: HSUPA UE 3 throughput @ 10ms TTI

A category 3 UE has a max. TB size of 14484 bit@10ms TTI

With a PDU size of 336 bit, max. 43 RLC PDUs can be transmitted per TTI (14484 bit 18 bit) / 336 bit = 43.1 ( 43 PDUs, rest of the TB is padding)

Payload of one RLC PDU: 320 bit (336 bit 16 bit header)

Max. throughput: 43 PDU * 320 bit/PDU * 100 = 1.376 Mbps

NOTE: When 4 codes are transmitted in parallel, two codes shall be transmitted with SF2 and two with SF4

114842000010 ms and2 ms TTI

SF24Category 6

-2000010 ms TTI onlySF22Category 5

57722000010 ms and2 ms TTI

SF22Category 4


27981448410 ms and2 ms TTI

SF42Category 2


Maximum number of bits of an E-DCHtransport block transmitted within a 2 ms E-

DCH TTI

Maximum number ofbits of an E-DCHtransport block

transmitted within a 10ms E-DCH TTI

Support for 10and 2 ms TTI

EDCH

Minimumspreading factor

Maximum numberof E-DCH codestransmitted

E-DCH category


Transport Block Size Selection (TS25.321)

3GPP has standardized different E-TFC Transport Block Size tables that shall beused by the UE for the TB size selection on the E-DCH

The UE selects one E-TFCI out of that table according to its capabilties (e.g. maxTB size of the UE), the grant assigned by the scheduler and the amount of datato be transfered.

For the different TTIs (2ms, 10ms), different TB Size tables are defined

In the current implementation, only the tables for the 10ms TTI are applicable

Via O&M parameter it can be chosen, which table the UE shall use.

E-TFC: E-DCH Transport Format CombinationE-TFCI: E-DCH Transport Format Combination Indicator


10ms TTI E-DCH Transport Block Size Table 0E-TFCI TB Size

(bits)E-TFCI TB Size


(bits)E-TFCI

TB Size(bits)

E-TFCI

TB Size(bits)

0 18 30 389 60 1316 90 4452 120 150511 120 31 405 61 1371 91 4636 121 156752 124 32 422 62 1428 92 4828 122 163253 130 33 440 63 1487 93 5029 123 170014 135 34 458 64 1549 94 5237 124 177065 141 35 477 65 1613 95 5454 125 184406 147 36 497 66 1680 96 5680 126 192047 153 37 517 67 1749 97 5915 127 200008 159 38 539 68 1822 98 61619 166 39 561 69 1897 99 641610 172 40 584 70 1976 100 668211 180 41 608 71 2058 101 695912 187 42 634 72 2143 102 724713 195 43 660 73 2232 103 754714 203 44 687 74 2325 104 786015 211 45 716 75 2421 105 818616 220 46 745 76 2521 106 852517 229 47 776 77 2626 107 887818 239 48 809 78 2735 108 924619 249 49 842 79 2848 109 962920 259 50 877 80 2966 110 1002821 270 51 913 81 3089 111 1044422 281 52 951 82 3217 112 1087723 293 53 991 83 3350 113 1132824 305 54 1032 84 3489 114 1179725 317 55 1074 85 3634 115 1228626 331 56 1119 86 3784 116 1279527 344 57 1165 87 3941 117 1332528 359 58 1214 88 4105 118 1387729 374 59 1264 89 4275 119 14453

In UMR6.5, the parameteretfci_idxis used to select the table.UMR6.5 default: Table1

In RAS06, always Table 1 is used.


10ms TTI E-DCH Transport Block Size Table 1E-TFCI TB Size



(bits)

0 18 41 5076 82 118501 186 42 5094 83 121322 204 43 5412 84 121863 354 44 5430 85 124684 372 45 5748 86 125225 522 46 5766 87 128046 540 47 6084 88 128587 690 48 6102 89 131408 708 49 6420 90 131949 858 50 6438 91 13476

10 876 51 6756 92 1353011 1026 52 6774 93 1381212 1044 53 7092 94 1386613 1194 54 7110 95 1414814 1212 55 7428 96 1420215 1362 56 7464 97 1448416 1380 57 7764 98 1455617 1530 58 7800 99 1482018 1548 59 8100 100 1489219 1698 60 8136 101 1515620 1716 61 8436 102 1522821 1866 62 8472 103 1549222 1884 63 8772 104 1556423 2034 64 8808 105 1582824 2052 65 9108 106 1590025 2370 66 9144 107 1616426 2388 67 9444 108 1623627 2706 68 9480 109 1650028 2724 69 9780 110 1657229 3042 70 9816 111 1717230 3060 71 10116 112 1724431 3378 72 10152 113 1784432 3396 73 10452 114 1791633 3732 74 10488 115 1851634 3750 75 10788 116 1860635 4068 76 10824 117 1918836 4086 77 11124 118 1927837 4404 78 11178 119 1986038 4422 79 11460 120 1995039 4740 80 1151440 4758 81 11796

In UMR6.5, the parameteretfci_idxis used to select the table.UMR6.5 default: Table1

In RAS06, always Table 1 isused.


Transport Block Size Table: O&M Parameter

Indicates which standardised E-TFCS Transport Block Size Table shall be used. The related tables are specified in 3GPPTS25.321.

1RW-0,..,1Integeretfci_idxetfciTableIndex

ETFCITBIDXsbs3gRanEtfciTableIdx

E-TFCITableIndex

DefaultR/W


Longname





Overview: New Objects and Parametersrelated to HSUPA in UMR6.5


New HMI objects & parameters (office data)

ver=00000_06/13/07size=0005449055# New Header field containing the number of HSUPA licenses. Not relevant for HSUPA operation but only for consistency check purposes.hsupa_license=1026

# New HDHT HW Card for HSUPA operation.cre eqp hdht10100 cp00

# Existing OLPC object is extended by 3 parameters for HSUPA power control.cre olpc thr_upd=0.1 step_size=0.3 lowthr_sirerr=-3 upthr_sirerr=3 mmfc_sirerr=0 ofs_thr2e=1.0ofs_thr2f=2.0 hyst_tme=80 hyst_tmf=80 step_hsupa=0.3 upthr_hsupa=0.1 nhr_th=0

# New object for HSUPA admission control. One instance per HSUPA cell.cre cell adc2 cellid=1 nodebid=0 nth1=10 nth2=32 cell_util_th=0.90 aul_hsupa=1.50

# Existing congestion control object extended by one paramater for HSUPA congestion controlcre cell cctl cellid=1 nodebid=0 ul_cngt=10.0 ul_cngh=2.0 dl_cngt=0.90 dl_cngh=0.15 mmti_rtwbp=10.00mmti_tcp=10.00 k=1 ebd=ena etpchr=ena peri_cngh=0.5 mmfc_rtwp=0 mmfc_tcrp=0 cc_emg=false hsupa_oft=0.5

# New object for E-DCH channel configuration. One instance per RNC.cre edcinf edch_pref=rv0 etfci_idx=1 pesc_ng=every pesc_g=every maxrm_edch=15 edch_po=0

# New object for HSUPA channel power and HARQ process handling. One instance per HSUPA cell.cre hsupa cellid=1 nodebid=0 no_rgch_hich=4 po_agch=1.25 po_hich=1.25 po_rgch=1.25 pr_edch=30

happy bit

Documents

Transcript of happy bit