04 Wcdma Hsupa RRM and Parameters PDF

Course Name N-0
WCDMA HSUPA
RRM and Parameters
www.huawei.com
Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved.
Confidential Information of Huawei. No Spreading Without Permission

Course Name N-1
Objectives
Upon completion of this course, you will be able to know:
HSUPA service mapping
HSUPA fast scheduling
HSUPA CE scheduling
HSUPA dynamic channel control configuration
HSUPA Mobility Management
Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved. Page1

Course Name N-2
Contents
1. HSUPA Service Mapping
2. HSUPA Fast Scheduling
3. HSUPA CE Scheduling
4. HSUPA Dynamic Channel Control Configuration
5. HSUPA Mobility Management

Course Name N-3
HSUPA Service Mapping
HSPA service mapping can be divided into:

Mapping of signaling
Mapping of service
RB Type Signaling & Traffic class Transport Channel
SRB Signaling DCH/CCH/HS-DSCH/E-DCH
Conversational
CS DCH
Streaming
Conversational
TRB DCH/HS-DSCH/E-DCH
Streaming
PS
Interactive
DCH/CCH/HS-DSCH/E-DCH
Background
The Radio Bearers (RB) available for transmission of RRC messages are defined as “SRB
(signalling radio bearers)”
During the setup of an RRC connection, the single SRB can be carried on the CCH,
DCH, HS-DSCH, or E-DCH
If it is CCH, the final corresponding physical channels are downlink SCCPCH and
uplink PRACH.
If it is DCH, the final corresponding physical channels are downlink and uplink
DPDCH.
If it is HS-DSCH, the final corresponding physical channel is HS-PDSCH.
If it is E-DCH, the final corresponding physical channel is E-DPDCH.

Course Name N-4
The Radio Bearers (RB) available for transmission of service are defined as “TRB (Traffic
radio bearers)”
The services in the CS domain have high transmission quality requirements and are
always mapped onto the DCHs.
The conversational services in the PS domain can be mapped onto the DCH, HS-
DSCH, or E-DCH
The streaming services in the PS domain can be mapped onto the DCH, HS-DSCH,
or E-DCH.
The interactive and background services in the PS domain can be mapped onto the
CCH, DCH, HS-DSCH, or E-DCH
If it is CCH, the final corresponding physical channels are downlink SCCPCH

and uplink PRACH.
If it is DCH, the final corresponding physical channels are downlink and uplink
DPDCH.
If it is HS-DSCH, the final corresponding physical channel is HS-PDSCH.
If it is E-DCH, the final corresponding physical channel is E-DPDCH.

Course Name N-5
Mapping of Signaling
Signaling mapping in RRC connection setup stage

Start
The selected Yes

channel = CCH
SRB is carried on
No FACH & RACH
SRB channel type False

RRC effect flag
True
HSDPA DCH
SRB channel type
HSPA
Downlink SRB on HS-DSCH Downlink SRB on HS-DSCH SRB is carried on
Uplink SRB on DCH Uplink SRB on E-DCH DCH
During the setup of an RRC connection, the single SRB can be carried on the CCH,
DCH, HS-DSCH, or E-DCH, as described below:
If the selected channel type is FACH, the SRB is carried on the CCH in both the
uplink and the downlink.
If the selected channel type is DCH, then
In the downlink, if Srb channel type RRC effect flag is set to TRUE and Srb
channel type is set to HSDPA or HSPA, the SRB is carried on the HS-DSCH;
otherwise, on the DCH.
In the uplink, if Srb channel type RRC effect flag is set to TRUE and Srb channel
type is set to HSPA, the SRB is carried on the E-DCH; otherwise, on the DCH.

Course Name N-6
Mapping of Signaling on HSUPA
Signaling mapping in TRB setup stage

Start
The selected Yes SRB is carried on

channel = CCH FACH & RACH
No
Yes
SRB channel type Uplink SRB Downlink SRB
= DCH on DCH on DCH
No No
Yes Downlink TRB Yes Downlink SRB
SRB channel type Uplink SRB
= HSDPA on DCH on HS-DSCH on HS-DSCH
No
Uplink SRB
Downlink TRB Yes Downlink SRB
on DCH
on HS-DSCH on HS-DSCH No
No Yes
Downlink SRB Uplink TRB Uplink SRB END
on DCH on E-DCH on E-DCH
The SRB mapping in TRB setup stage is different from the SRB in RRC connection
setup stage
During the setup of TRBs, the SRB can be carried on the CCH, DCH, HS-DSCH, or
E-DCH, as described below:
If the selected channel type is FACH, the SRB is carried on the CCH in both
the uplink and the downlink.
If the selected channel type is not FACH, then
In the downlink, if the channel types selected by all the TRBs are HS-
DSCH and Srb channel type is set to HSDPA or HSPA, the SRB is
carried on the HS-DSCH; otherwise, on the DCH.
In the uplink, if the channel types selected by all the TRBs are E-DCH
and Srb channel type is set to HSPA, the SRB is carried on the E-
DCH; otherwise, on the DCH.

Course Name N-7
Related Parameter
SRB channel type RRC effect flag

Parameter ID: SrbChlTypeRrcEffectFlag
This parameter specifies whether the parameter SRB channel

type is valid during the setup of an RRC connection
SRB channel type

Parameter ID: SrbChlType
Indicating the channel type of SRB
Srb channel type RRC effect flag
This parameter specifies whether the parameter Srb channel type is valid
during the setup of an RRC connection
TRUE: Srb channel type is valid during the setup of an RRC connection and
other processes
FALSE: Srb channel type is invalid during the setup of an RRC connection
but valid during other processes
Default value: False
Srb channel type
Indicating the channel type of SRB
DCH: Both uplink and downlink are beared on DCH.
HSDPA: Uplink is beared on DCH, downlink beared on HS-DSCH
HSPA: Uplink is beared on E-DCH, downlink beared on HS-DSCH
Default value: DCH

Course Name N-8
Mapping of Conversational Traffic on HSUPA
PS Conversational service
Voice over IP (VoIP)
Start
Yes
VoIP channel type Uplink TRB Downlink TRB
= DCH on DCH on DCH
No
Yes Uplink TRB Downlink TRB
VoIP channel type
= HSDPA on DCH on HS-DSCH
No Uplink TRB Downlink TRB

END
on E-DCH on HS-DSCH
The services in the CS domain have high transmission quality requirements and are
always mapped onto the DCHs.
The conversational services in the PS domain can be mapped onto the DCH, HS-
DSCH, or E-DCH. VoIP stands for Voice over IP, a PS conversational service. It uses
IP data packets to encapsulate voice data and transports them on the IP network to
implement the conversational services
In the downlink, if Voip channel type is set to HSDPA or HSPA, the PS

conversational service is carried on the HS-DSCH; otherwise, on the DCH.
In the uplink, if Voip channel type is set to HSPA, the PS conversational

service is carried on the E-DCH; otherwise, on the DCH.

Course Name N-9
Related Parameter
VoIP channel type

Parameter ID: VoipChlType
This parameter specifies the channel type of the VoIP

service
Voip channel type
This parameter specifies the channel type of the VoIP service
Value range: DCH, HSDPA, HSPA
DCH: The service is carried on the DCH in both the uplink and the downlink
HSDPA: The service is carried on the DCH in the uplink and the HS-DSCH in
the downlink
HSPA: The service is carried on the E-DCH in the uplink and the HS-DSCH in
the downlink
Default value: DCH

Course Name N-10
Mapping of Streaming Traffic on HSUPA
PS streaming service on HSUPA

Start
No
Cell support HSUPA
Yes
PS streaming on No
E-DCH is switched?
Yes
Requested service No Uplink TRB

rate >= Rate Th on DCH
Yes Uplink TRB

END
on E-DCH
The streaming services in the PS domain can be mapped onto the DCH, HS-DSCH,
or E-DCH.
If the maximum UL service rate is higher than or equal to UL streaming traffic

threshold on HSUPA, the cell supports HSUPA, and the
PS_STREAMING_ON_E_DCH_SWITCH is selected, then the service is carried on
the E-DCH. Otherwise, the service is carried on the DCH.

Course Name N-11
Related Parameter
PS Streaming on E-DCH switch

Parameter ID: PS_STREAMING_ON_E_DCH_SWITCH
UL streaming traffic threshold on HSUPA

Parameter ID: UlStrThsOnHsupa
The parameter specifies the rate decision threshold of UL

PS domain streaming service to be carried on the E-DCH
PS Streaming on E-DCH switch
If this parameter is checked, the cell supports HSUPA, and the maximum UL
service rate is higher than or equal to the streaming on HSUPA threshold, the
PS streaming service can be mapped onto the E-DCH.
Default value: not checked
UL streaming traffic threshold on HSUPA
The parameter specifies the rate decision threshold of UL PS domain

streaming service to be carried on the E-DCH.
Value range:D8, D16, D32, D64, D128, D144, D256, D384, which indicate
8kbit/s, 16kbit/s, 32kbit/s, 64kbit/s, 128kbit/s, 144kbit/s, 256kbit/s, 384kbit/s
Default value: D256

Course Name N-12
Mapping of Interactive & Background Traffic on

HSUPA
PS BE traffic on HSUPA
Start
No
Cell support HSUPA
Yes
Requested service No Uplink TRB

rate >= Rate Th on DCH
Yes Uplink TRB

END
on E-DCH
The interactive and background services in the PS domain can be mapped onto the
CCH, DCH, HS-DSCH, or E-DCH.
Low-rate PS services have relatively small amount of data. Therefore, such PS

services can be carried on the CCH to save radio resources.
If the maximum UL service rate is higher than or equal to UL BE traffic threshold on

HSUPA, then the service is carried on the E-DCH. Otherwise, the service is carried
on the DCH.

Course Name N-13
Related Parameter
UL BE traffic threshold on HSUPA

Parameter ID: UlBeTraffThsOnHsupa
The parameter specifies the rate decision threshold of UL

PS domain background or interactive service to be carried
on the E-DCH
UL BE traffic threshold on HSUPA
The parameter specifies the rate decision threshold of UL PS domain

background or interactive service to be carried on the E-DCH.
Value range:D8, D16, D32, D64, D128, D144, D256, D384, D608, D1450,
D2048, D2890, D5760, which indicate 8kbit/s, 16kbit/s, 32kbit/s, 64kbit/s,
128kbit/s, 144kbit/s, 256kbit/s, 384kbit/s, 608kbit/s, 1450kbit/s, 2048kbit/s,
2890kbit/s, 5760kbit/s
Default value:D608

Course Name N-14
Contents

Course Name N-15
HSUPA Scheduling Overview

1. Estimate RoT and Iub Bandwidth
RoT
available Uu load resource of a cell = Maximum Target Uplink
Load Factor - actual load
Iub bandwidth
available Iub bandwidth of a NodeB = bandwidth available for
HSUPA users within the NodeB range - total throughput of the
users
When the scheduling period (equal to one TTI) arrives, this estimation has to be
calculated.

Course Name N-16
Related Parameter
Maximum Target Uplink Load Factor
Parameter ID: MaxTargetUlLoadFactor
This parameter specifies the target uplink load factor for the
NodeB-controlled scheduler.
Target Non-serving E-DCH to Total E-DCH Power ratio

Parameter ID: NonServToTotalEdchPwrRatio
This parameter is used for deciding whether the NodeB sends

the RG DOWN command to a non-serving UE.
Maximum Target Uplink Load Factor
According to the parameter, the RNC calculates the maximum Received Total
Wideband Power (RTWP) and sends it to the NodeB through Iub signaling.
This parameter is set on the basis of the network planning. If this parameter is
set too small, the throughput of a cell will be small. If this parameter is set too
large, the interference becomes high and the coverage of the cell may be too
small.
Default value:75
Target Non-serving E-DCH to Total E-DCH Power ratio
The purpose of the participation of the RNC in cell arbitration is to know all the
requirements for the services in each cell. The parameter value set on the
basis of the network planning can enable a cell to have a larger portion of
high-priority users or services than the other cells.
This parameter is mainly used for load control
The default value: 0

Course Name N-17
User Selection in HSUPA

Scheduling
User selection based on SI & Happy bit
SI
The SI is at the end of the MAC-e PDU and is used to notify the
serving NodeB of the amount of system resources required by the
UE
Happy bit
The UE can use the Happy Bit to tell the serving Node B that the
resources allocated to the UE are not sufficient and that the UE is
capable of transmitting at higher rate.
Scheduling information
Highest priority Logical channel ID (HLID)
Total E-DCH Buffer Status (TEBS)
Highest priority Logical channel Buffer Status (HLBS)
UE Power Headroom (UPH)
Happy bit
Happy bit is in HS-DPCCH

Course Name N-18

Scheduling
Happy user
During the scheduling, the rate of happy user may be
decreased based on the following items
Effective data rate
Priority of UE
The algorithm queues all the happy users in descending order by Priorityn.
Priorityn = Reff/γSPI
Where
Priorityn is the priority value of user n

SPI is assigned by the RNC, which is used to provide different
scheduling opportunities according to the scheduling priority.SPI and
γSPI (SPI weight) are the same as those used for HSDPA.The smaller
the SPI, the larger the value of Priorityn. During the scheduling, the
rate of such a user is decreased before that of a user with a smaller
Priorityn.
Reff is the effective data rate

Course Name N-19

Scheduling
Unhappy user
Unhappy user queue
Unhappy user queue
Zero grant queue Non-zero grant queue
GBR=ON
GBR is not met GBR is met

GBR=ON
UE1 UE2 UE3 UE4 UE5 UE6 UE7 UE8 UE9 UE10 UE11 UE12
GBR=OFF
GBR=OFF
UE6 UE7 UE8 UE9 UE10 UE11 UE12
When queuing unhappy users, the algorithm considers the effective data rate, γSPI,
and GBR satisfaction degree.
Firstly, the algorithm arranges zero_grant users in descending order by Priorityn and
puts them to the end of the unhappy queue. Priorityn is calculated with the following
formula:
Priorityn = 1/(γSPI x Rreq)
Where

Priorityn is the priority value of user n

SPI is assigned by the RNC, which is used to provide different
scheduling opportunities according to the scheduling priority.
Rreq is the requested service rate.
Then, for non-zero_grant users,
If the GBR switch (described in GBR Processing in the Scheduling Algorithm)
is set to ON, the algorithm queues the users according to the following
principles:
For the users whose requirements for the GBRs are not met, the
algorithm arranges them in descending order by Priorityn and puts
them before the zero_grant users. Priorityn is calculated with the
following formula:
Priorityn = Reff/(γSPI x RGBR)

Course Name N-20
For the users whose requirements for the GBRs are met, the algorithm
arranges them in descending order by Priorityn and puts them before
the users whose requirements for the GBRs are not met. Priorityn is
calculated with the following formula:
In this case, the users in an unhappy queue are arranged in descending order
by Priorityn: the users whose requirements for the GBRs are met, the users
whose requirements for the GBRs are not met, and zero_grant users. The rate
of a user is decreased before that of a following user but increased after that of
the following user.
If the GBR switch is OFF, the users are queued according to the following
principles:
For non-zero_grant users, the algorithm arranges them in descending

order by Priorityn:
In this case, the users in an unhappy queue are arranged in
descending order by Priorityn: non-zero_grant users and zero_grant
users. The rate of a user is decreased before that of a following user
but increased after that of the following user.

Course Name N-21
AG Up in Scheduling
Conditions for sending AG up
User is unhappy, and SI is received by NodeB successfully.
AGCH code resource is available for the user
The updated SG is satisfied with the requirement
When the user meets all of the following conditions, the NodeB schedules this user
through AG:
The user is unhappy and the SI sent from the user is received.
The AGCH code allocated to the user is idle and not used by other users.
The user meets the requirement: SGIndexreq - SGIndexcur > AG Threshold.
SGIndexreq and SGIndexcur are obtained from Rreq and Rcur.

Rcur is the current bit rate of the UE, which is calculated on the
basis of the E-TFCI carried on the E-DPCCH.
Rcur is equal to the MAC-e PDU size divided by the TTI length.
The MAC-e PDU size can be obtained according to the E-TFCI.
The AG threshold is adjusted dynamically according to the traffic volume at the
service source

Course Name N-22
RG Up in Scheduling
Conditions for sending RG up
The user is unhappy.
The user does not meet the conditions for sending AG UP.
The rate of the user is not decreased because of MBR

processing, Iub bandwidth limitation, and CE resource
limitation.
The user demodulates the data on the E-DPDCH correctly.
If all these conditions are met and both the Uu bandwidth and the Iub bandwidth allow
an increase in the user rate, the algorithm sends RG UP to the user.

Course Name N-23
Contents

Course Name N-24
HSUPA CE Scheduling Overview

HSUPA consumes more CEs after HARQ and soft
handover are introduced.
As the number of HSUPA users increases, the consumption
of CEs also increases, and the CE resource may become a
bottleneck.
To solve this problem, the CE scheduling algorithm is
introduced.

Course Name N-25
HSUPA CE Scheduling
When the CE scheduling period arrives, the algorithm
performs the following operations for CE scheduling:
Reclaiming the CEs of the serving RLS
Adding CEs for the serving RLS
Processing CEs based on equity
Processing CEs for users of non-serving RLs

Course Name N-26

The algorithm determines whether to reclaim the CEs based
on the CEavg of the serving RLS during the previous period.
If the number of CEs allocated to the serving RLS is larger
than CEinit and CEavg, the algorithm reclaims some CEs.
The algorithm determines whether to reclaim the CEs based on the CEavg of the
serving RLS during the previous period.
If the number of CEs allocated to the serving RLS is larger than CEinit and CEavg,
the algorithm reclaims some CEs. The number of CEs of the serving RLS decreases
to MAX(CEavg, CEinit). The reclaimed CEs take effect during the next period. The
algorithm notifies the MAC-e scheduler of SGmax.
CEinit: Initial number of CEs, which is calculated on the basis of the GBR
configured. If the user is not configured with the GBR, then CEinit is the
number of CEs occupied by an RLC PDU.
CEavg: Average number of CEs, which is calculated on the basis of the

average rate of the serving RLS.
SGmax: Maximum SG for the UEs, which is determinate by the CE

scheduling.

Course Name N-27
Adding CEs for the serving RLS

If the CEavg of the serving RLS during the previous period
is larger than or equal to the number of CEs allocated to the
users, the algorithm selects the users based on the queuing
result and CE resource, and increases the number of CEs
of these users by one step
For the users whose Reff is smaller than the GBR, the algorithm queues the users
based on Priority = Reff/(γSPI x GBR).
For the users whose Reff is larger than or equal to the GBR and whose GBR is not
configured, the algorithm queues the users based on Priority = Reff/γSPI.
The smaller the Priority value of a user is, the earlier the number of CEs of this user is
increased. The users are queued in ascending order by Priority. The number of CEs
of the users whose GBR is not reached is increased before that of the users whose
GBR is reached or not configured.
After adding CEs, the algorithm notifies the MAC-e scheduler of the new CEs and the
maximum SG index that corresponds to only one CE. During the addition, the
algorithm can preempt the CEs of the non-serving RLs until the number of these CEs
decreases to the minimum number, that is, the number of CEs required for correct E-
DPCCH demodulation and decoding.

Course Name N-28
Processing CEs based on equity

If the number of the idle CEs on the RL is less than the
minimum and the number of idle CEs on a bearing board is
smaller than the difference between the number of CEs
corresponding to SF4 and that corresponding to 2xSF4, the
algorithm performs equity-based processing for the users of
the serving RLS on the board

Course Name N-29
Processing CEs for users of non-serving

RLs
When there are idle CEs on a bearing board, the algorithm
performs CE processing for users of non-serving RLs on the
board.
The principle for CE allocation is that the algorithm allocates
enough CEs when there are sufficient idle CEs to enable
more users to obtain soft handover gain.
When there are idle CEs on a bearing board, the algorithm performs CE processing for users of non-
serving RLs on the board. The principle for CE allocation is that the algorithm allocates enough CEs
when there are sufficient idle CEs to enable more users to obtain soft handover gain. Based on the
CEavg of non-serving RLs during the previous period, the algorithm increases the number of CEs to
CEup by one step, as listed in Table 4-1. The users are queued based on Priority, as calculated below:
Priority = CEneed/γSPI
CEneed = NRL x (CEnew - CEassign)
NRL: the number of RLs on the current UL board. The users are queued in ascending order by
Priority. The smaller the value of Priority is, the earlier the user is processed.
CEnew = Min[CEup, CE(E-DCH MBR), CE(Maximum Set of E-DPDCHs)]
CE(E-DCH MBR): the number of CEs corresponding to the E-DCH MBR
CE(Maximum Set of E-DPDCHs): the number of CEs corresponding to the Maximum Set of E-DPDCHs
CEassign: the number of CEs allocated to this user
If the idle CEs can meet the requirements for CEneed, the algorithm allocates new CEs to the user and
notifies the MAC-e scheduler of the new CEs and the maximum SG index that corresponds to only one
CE. If no new CE is available, the algorithm allocates CEs based on the minimum number.

Course Name N-30
Contents

Course Name N-31
HSUPA DCCC
HSUPA DCCC
One 1.44M HSUPA UE will consume 22 CE. In order to
improve the uplink CE efficiency, HSUPA DCCC has to be
used
HSUPA DCCC is to change the uplink service rate, but UE can

not report the traffic volume to RNC in 3GPP.
MAC-D throughput measurement can be used for HSUPA

DCCC.
In each measurement period (E-DCH Throu Meas Period for E-DCH service, DCH
Throu Meas Period for DCH service), the MAC-d takes statistics of the data volume
properly received by this RB. The result is then divided by the measurement period to
obtain the throughput value.

Course Name N-32
HSUPA DCCC
HSUPA DCCC strategy
Up and down
Up only
Parameter ID MML Command Parameter description
Value range:
HsupaDcccStg SET DCCC RATE_UP_AND_DOWN_ON_EDCH,
RATE_UP_ONLY_ON_EDCH

Course Name N-33
HSUPA DCCC
HSUPA DCCC principle
For throughput-based rate reallocation on the E-DCH, both events 4a and 4b apply,
that is, both rate upsizing and downsizing are applicable for both uplink and downlink.
For throughput-based rate reallocation on the DCH, only event 4b applies, that is,
only rate downsizing is applicable.

Course Name N-34
HSUPA DCCC
HSUPA DCCC principle
Service rate range
… …
R1 R2 Ri RN-1 RN

HSUPA_DCCC_SWITCH SET CORRMALGOSWITCH HSUPA DCCC algorithm switcher
HsupaRateAdjustSet SET EDCHRATEADJUSTSET HSUPA Rate Adjustment Set Rate

E-DCH Throughput Measurement
E2FThrouMeasPeriod SET UESTATETRANS
Period
HsupaInitialRate SET FRC HSUPA BE traffic Initial bit rate
A specified group of adjustment rate and the associated throughput threshold has to
be configured:
{(R1, TR1), ... (Ri, TRi), ... (RN, TRN)}
where:
For E-DCH services,
The first figure in each pair of parentheses is the HSUPA adjustment rate
which is set through the HSUPA UpLink rate adjust set parameter.
The second figure is the associated throughput threshold of this HSUPA

adjustment rate.
TRi = Ri x threshold rate ratio
The threshold rate ratio is set through the percent of ratio for nKbps parameter.
The RN is the highest rate in the set defined by the HSUPA UpLink rate adjust set
parameter.

Course Name N-35
HSUPA DCCC
Increase service rate principle
Suppose Ri is current configured rate
If average throughput > [Ri * Threshold Rate Ratio], for a

defined number of consecutive times
Upsize the service rate to Ri+1 if allowed
If the AvgThroughput is higher than the 4a threshold for Ttrig_4a consecutive times
(Period Amount to trigger 4A on EDCH) and the Tpend_4a timer whose length is
defined through Period Amount after trigger 4A on EDCH is not started, event 4a is
reported and the Tpend_4a timer is started.
In the aspect of DCCC for HSUPA,
The 4a threshold is the throughput threshold associated with the current HSUPA
adjustment rate, that is, TRt.
TRt = Rt x threshold rate ratiot

Course Name N-36
HSUPA DCCC
Increase service rate parameters
EDCH Period Number to Trigger for Event 4A
EDCH Pending Period Number after Trigger for Event 4A
EDCH Period Number to

EDCHTIMETOTRIGGER4A ADD TYPRABDCCCMC Trigger for Event 4A
Value range: 0~1023
EDCH Pending Period
Number after Trigger for
EDCHPENDINGTIME4A ADD TYPRABDCCCMC
Event 4A
Value range: 0~1023

Course Name N-37
HSUPA DCCC
Decrease service rate principle
Suppose Rt is current configured rate
If average throughput < [Rt-1* Threshold Rate Ratio], for a

defined number of consecutive times
The 4b event is triggered , and downsize to a proper rate, Ri, if

measured average throughput is between Ri-1 and Ri
If the AvgThroughput is lower than the 4b threshold for Ttrig_4b consecutive times
(Period Amount to trigger 4B on EDCH or Period Amount to trigger 4B on DCH)
and the Tpend_4b timer whose length is defined through Period Amount after
trigger 4B on EDCH or Period Amount after trigger 4B on DCH is not started,
event 4b is reported and the Tpend_4b timer is started.
In the aspect of DCCC for HSUPA, The 4b threshold is the throughput threshold
associated with the previous rate, that is, TRt–1.
TRt–1 = Rt–1 x threshold rate ratiot–1
If the current HSUPA adjustment rate is the minimum rate, the 4b rate threshold is the
threshold rate of E-DCH to FACH state transition (E-DCH to FACH 4b Threshold).
In the aspect of DCCC for DCH services, the 4b threshold is calculated as follows:
TRt-1 = Rt-1 x threshold rate ratiot-1
where:
Rt-1 is the previous rate in the rate adjustment set.
Threshold rate ratiot-1 is defined by the parameter percent of ratio for nKbps
(n = 8, 16, 32, 64, 128, 144, 256, 384).

Course Name N-38
HSUPA DCCC
Decrease service rate principle
Time to trigger for 4B
Pending time to trigger for 4B
EDCH Period Number to

EDCHTIMETOTRIGGER4B ADD TYPRABDCCCMC Trigger for Event 4B
Value range: 0~1023
EDCH Pending Period
Number after Trigger for
EDCHPENDINGTIME4B ADD TYPRABDCCCMC
Event 4B
Value range: 0~1023

Course Name N-39
Contents
3. HSUPA Scheduling
4. HSUPA Dynamic Channel Configuration Control

Course Name N-40
HSUPA Mobility Overview

HSUPA handover

Course Name N-41

E-DCH active set
All cells can receive UE uplink information
Only HSUPA serving cell can send AG to the UE
The other cells in serving RLS, can send RG, including UP,
DOWN and Hold, which should be same as HSUPA serving
cell. For HICH, it’s the same as RGCH.
The cells, which are in E-DCH active set, but not in the serving
RLS, can only send DOWN and HOLD in RGCH. For HICH,
only ACK and DTX can be sent

Course Name N-42

The criteria to be in E-DCH active set
The cell should support HSUPA
All the cells in E-DCH active set should have the same SRNC
The cell should have enough resource for supporting HSUPA
HSUPA serving cell

HSUPA serving cell should be same as HSDPA serving cell

Course Name N-43
Contents
5.1 Intra-frequency HSUPA handover
5.2 Inter-frequency HSUPA handover
5.3 Inter-RAT HSUPA handover
5.4 HSUPA SRNS Relocation
5.6 HSUPA direct retry

Course Name N-44
Intra-frequency HSUPA Handover

Scenario1
The UE moves from one HSUPA cell to another HSUPA cell.
Events 1A, 1B, 1C, and 1D are triggered
Non-HSUPA cells do not exist either before or after the active

set is updated
The RNC updates the active set according to the reported

events. If the best cell changes, the HSUPA serving cell is
updated to keep consistent with the best cell.

Course Name N-45

Scenario1

Course Name N-46

Scenario2
The UE moves from an HSUPA cell to a DCH cell
Events 1A and 1C are triggered, and the cells to be added are

non-HSUPA cells

events. If the target cell supports only DCH, the services are
reconfigured for DCH

Course Name N-47

Scenario2

Course Name N-48

Scenario 3
The UE moves from a DCH cell to an HSUPA cell
Events 1B and 1C are triggered, and the cells to be removed or

replaced are non-HSUPA cells
All cells after the active set is updated are HSUPA cells

events. If all the cells in the updated active set are HSUPA
cells, whether services are redirected to E-DCH depends on
the channel mapping policy

Course Name N-49

Scenario 3

Course Name N-50

Scenario 4
The UE moves from a DCH cell to an HSUPA cell
Triggering conditions for intra-frequency hard handover are

met
Event 1D is triggered
The RNC performs intra-frequency hard handover through the

physical channel reconfiguration message and decides
whether to reconfigure services from DCH to E-DCH according
to the channel mapping policy after the handover

Course Name N-51

Scenario 4

Course Name N-52

Scenario 5
The UE moves from an HSUPA cell to a DCH cell
Triggering conditions for intra-frequency hard handover are

met
Event 1D is triggered
The RB reconfiguration is implemented, and services on E-

DCH are reconfigured for DCH

Course Name N-53

Scenario 5

Course Name N-54

Related parameter
To guarantee the success of HSUPA SHO, The

bandwidth on EDCH will be reduced to HSUPA
HSUPABESHORATETHD SET DCCC
SHO THD RATE before soft handover, if current
bit rate is higher than this threshold rate

Course Name N-55
Contents

Course Name N-56
Inter-frequency HSUPA Handover

Scenario 1
The UE moves from one HSUPA cell to another HSUPA cell
Event 2B is triggered
The HSUPA admission request is made for the target cell. After
the request is accepted, the handover is performed through the
physical channel reconfiguration message. If the request is
denied, the RB reconfiguration is implemented, and services
on E-DCH are reconfigured for DCH

Course Name N-57

Scenario 1

Course Name N-58

Scenario 2
The UE moves from an HSUPA cell to a non-HSUPA cell
The DCH admission request is made for the target cell. After
the request is accepted, the RB reconfiguration is implemented,
and services on E-DCH are reconfigured for DCH

Course Name N-59

Scenario 2

Course Name N-60

Scenario 3
The UE moves from a non-HSUPA cell to an HSUPA cell
The inter-frequency handover on DCH is performed, and then

the HSUPA admission request is made for the target cell by the
RNC. After the request is accepted, the RB reconfiguration is
implemented, and services on DCH are reconfigured for E-
DCH

Course Name N-61

Scenario 3

Course Name N-62
Contents

Course Name N-63
Inter-RAT HSUPA Handover

Inter-RAT handover can be triggered on the basis of
coverage and service
The introduction of HSUPA does not affect the triggering
conditions and decisions of both coverage- and service-
based inter-RAT handover algorithms

Course Name N-64
Contents

Course Name N-65
HSUPA SRNS Relocation

RAN6.1 does not support soft handover over Iur on E-DCH.
The services on E-DCH will be reconfigured for DCH when
a new cell controlled by a different RNC is to be added to
the active set

Course Name N-66


Course Name N-67


Course Name N-68
Contents

Course Name N-69
HSUPA to HSUPA Direct Retry

Suppose that two HSUPA cells cover the same physical
area and is defined as neighboring cells.
Directed retry is triggered in the following cases:

The access to an HSUPA cell is rejected when the service is
set up.
The access to an HSUPA cell is rejected when the channel

transition from FACH to E-DCH is triggered by the increase of
the traffic volume.
The access to an HSUPA cell is rejected when the channel

transition from DCH to E-DCH is triggered.

Course Name N-70
HSUPA to HSUPA Direct Retry

Two frequency cover same sector
F1 F1 F1
HSUPA HSUPA HSUPA
F2 F2
HSUPA

Course Name N-71
Non-HSUPA to HSUPA Direct Retry

Suppose that an R99 cell and an HSUPA cell cover the
same physical area.

In the R99 cell, the UE initiates a service that should be set up
on the E-DCH according to the service mapping rules
The traffic volume of the UE increases when the UE stays in

CELL_FACH state in the R99 cell, and the service fulfills the
criteria of service mapping to HSUPA.

Course Name N-72

Suppose that an R99 cell and an HSUPA cell cover the
same physical area.

The associated timer expires.
For a service that should be set up on the E-DCH according to the
service mapping rules, it might be set up on the DCH of the R99
cell because, for example, the admission request is rejected early.
Under such a circumstance, the system starts a timer for the
inconsistency between the channel that is suitable for the service
and the channel that carries the service.

Course Name N-73

Related parameters
SET Only this switch is on, can do DRD if

HSUPA_DRD_SWITCH
CORRMALGOSWITCH HSUPA need retry
When the DCH is handed over to the
HS-DSCH/E-DCH, a timer for retry
HRETRYTIMERLEN SET COIFTIMER
needs to start. You can set the timer
length in this parameter

Course Name N-74
HSUPA to Non-HSUPA Direct Retry

When the non-HSUPA cell and HSUPA cell are the inter-
frequency co-coverage cells, the direct retry includes the
following:
When a subscriber asks to establish the CS service in the HSUPA cell
F1/F3 F1/F3 F1/F3 F1/F3
Non-HSUPA Non-HSUPA Non-HSUPA Non-HSUPA
F2 F2
F2
HSUPA HSUPA HSUPA
CS service CS service

Course Name N-75
Summary
HSUPA mobility management
HSUPA handover
HSUPA to HSUPA handover
HSUP to non-HSUPA handover
Non-HSUPA to HSUPA handover
HSUPA to GRPS handover
HSUPA direct retry

HSUPA to HSUPA
Non-HSUPA to HSUPA
HSUPA to non-HSUPA

Course Name N-76
Thank you
www.huawei.com

04 Wcdma Hsupa RRM and Parameters PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

04 Wcdma Hsupa RRM and Parameters PDF

Uploaded by

Copyright:

Available Formats

Course Name N-0

Copyright © 2008 Huawei Technologies Co., Ltd. All rights reserved.

Confidential Information of Huawei. No Spreading Without Permission

HSUPA fast scheduling

HSUPA dynamic channel control configuration

HSUPA Mobility Management

Confidential Information of Huawei. No Spreading Without Permission

2. HSUPA Fast Scheduling

4. HSUPA Dynamic Channel Control Configuration

5. HSUPA Mobility Management

Confidential Information of Huawei. No Spreading Without Permission

HSUPA Service Mapping

HSPA service mapping can be divided into:

SRB Signaling DCH/CCH/HS-DSCH/E-DCH

If it is HS-DSCH, the final corresponding physical channel is HS-PDSCH.

If it is E-DCH, the final corresponding physical channel is E-DPDCH.

Confidential Information of Huawei. No Spreading Without Permission

If it is CCH, the final corresponding physical channels are downlink SCCPCH

Confidential Information of Huawei. No Spreading Without Permission

Signaling mapping in RRC connection setup stage

The selected Yes

SRB channel type False

If the selected channel type is DCH, then

Confidential Information of Huawei. No Spreading Without Permission

Mapping of Signaling on HSUPA

Signaling mapping in TRB setup stage

The selected Yes SRB is carried on

If the selected channel type is not FACH, then

Confidential Information of Huawei. No Spreading Without Permission

SRB channel type RRC effect flag

This parameter specifies whether the parameter SRB channel

SRB channel type

Indicating the channel type of SRB

Srb channel type RRC effect flag

Default value: False

Srb channel type

Indicating the channel type of SRB

DCH: Both uplink and downlink are beared on DCH.

HSDPA: Uplink is beared on DCH, downlink beared on HS-DSCH

HSPA: Uplink is beared on E-DCH, downlink beared on HS-DSCH

Default value: DCH

Confidential Information of Huawei. No Spreading Without Permission

Mapping of Conversational Traffic on HSUPA

No Uplink TRB Downlink TRB

In the downlink, if Voip channel type is set to HSDPA or HSPA, the PS

In the uplink, if Voip channel type is set to HSPA, the PS conversational

Confidential Information of Huawei. No Spreading Without Permission

VoIP channel type

This parameter specifies the channel type of the VoIP

Voip channel type

This parameter specifies the channel type of the VoIP service

Value range: DCH, HSDPA, HSPA

Default value: DCH

Confidential Information of Huawei. No Spreading Without Permission

Mapping of Streaming Traffic on HSUPA

PS streaming service on HSUPA

Requested service No Uplink TRB

Yes Uplink TRB

If the maximum UL service rate is higher than or equal to UL streaming traffic

Confidential Information of Huawei. No Spreading Without Permission

PS Streaming on E-DCH switch

UL streaming traffic threshold on HSUPA

The parameter specifies the rate decision threshold of UL