HSPA Fundamentals For Technicals

HSPA Fundamental
for Technical
Personnel
TM5112EN01GLA00
nazilute.en.lmm
Legal notice
Intellectual Property Rights
All copyrights and intellectual property rights for Nokia Siemens Networks training documentation, product
documentation and slide presentation material, all of which are forthwith known as Nokia Siemens Networks training
material, are the exclusive property of Nokia Siemens Networks. Nokia Siemens Networks owns the rights to
copying, modification, translation, adaptation or derivatives including any improvements or developments. Nokia
Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license, sublicense, sell, transfer
and assign the Nokia Siemens Networks training material. Individuals can use the Nokia Siemens Networks training
material for their own personal self-development only, those same individuals cannot subsequently pass on that
same Intellectual Property to others without the prior written agreement of Nokia Siemens Networks. The Nokia
Siemens Networks training material cannot be used outside of an agreed Nokia Siemens Networks training session
for development of groups without the prior written agreement of Nokia Siemens Networks.
Indemnity
nazilute.en.lmm
The information in this document is subject to change without notice and describes only the product defined in the
introduction of this documentation. This document is intended for the use of Nokia Siemens Networks customers
only for the purposes of the agreement under which the document is submitted, and no part of it may be used,
reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens
Networks. The document has been prepared to be used by professional and properly trained personnel, and the
customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part
of the process of continuous development and improvement of the documentation.
The information or statements given in this document concerning the suitability, capacity, or performance of the
mentioned hardware or software products are given as is and all liability arising in connection with such hardware
or software products shall be defined conclusively in a separate agreement between Nokia Siemens Networks and
the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if
deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.
Nokia Siemens Networks will correct errors in the document as soon as possible. IN NO EVENT WILL NOKIA
SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCLUDING
BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARY
LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION,
BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT
This document and the product it describes are considered protected by copyrights and other intellectual property
rights according to the applicable laws.
Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation.
Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective owners, and they are
mentioned for identification purposes only.
TM5112EN01GLA00
2008 Nokia Siemens Networks GmbH

The reproduction, transmission or use of this document or its contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights created by patent grant or registration of utility model or design, are
reserved.
Technical modifications possible.
Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written
contract.
TM5112EN01GLA00
Nokia Siemens Networks 2009
HSPA System Overview in UMTS

Network
1
34 pages
Course
overview
HSDPA and HSUPA Features

49 pages
This workbook consists

of 7 chapters and 246
pages total.
HSPA Fundamental
for Technical
Personnel
HSDPA and HSUPA Physical Channel

51 pages
HSPA Protocols
23 pages
HSPA Mobility Management and

Handover control
5
25 pages
nazilute.en.lmm
HSPA Throughput and Congestion

Control
TM5112EN01GLA00
6
15 pages
NSN Products
49 pages
HSPA System Overview in UMTS Network
HSPA System Overview in

UMTS Network
Contents
nazilute.en.lmm/dizagilo.en.slo
Module Objectives.....................................................................................3
HSPA ...........................................................................................................4
3
3.1
3.2
UMTS Release 99 Environment............................................................... 6

UMTS Network - Network components...................................................... 6
UMTS - The Air Interface............................................................................8
4
4.1
4.2
4.3
HSDPA ......................................................................................................18
Higher Data Rate .......................................................................................19
Reduced Latency...................................................................................... 19
Increased Spectral Efficiency ....................................................................24
5
5.1
5.2
5.3
HSUPA ......................................................................................................26
Higher Data Rate .......................................................................................27
Reduced Latency...................................................................................... 27
Increased Cell Coverage and Throughput................................................ 27
6
6.1
Exercises..................................................................................................28
Solutions....................................................................................................32
TM5112EN01GLA00
1-1
1-2
TM5112EN01GLA00
Module Objectives
The aim of this module is to give theparticipant overview ofUMTS system and its
network. Air interface background is also provided. Issues in UMTS that are
solved in HSDPA and HSUPA are described.
After completing this module, the participant should be able to:
Describe UMTS network and Radio Access Network.
Explain aspects of UMTS Release 99 air interface.
Briefly introduce HSPA system andkey elements of HSPA.
TM5112EN01GLA00
1-3
HSPA
HSPA or HSxPA(High Speed Packet Access) is a generic term to refer to

improvements in the UMTS Radio Interface in the Releases 5 and 6 of the 3rd
Generation Partnership Project (3GPP) standards. HSPA comprises both the
improvements made in the UMTS downlink and uplink:
High Speed Downlink Packet Access - HSDPA
High Speed Uplink Packet Access - HSUPA
Both technologies offer distinctly increased data rates compared to UMTS Rel
99:
HSDPA offers data rates up to 14.4 Mbps in the downlink direction.
HSUPA offers data rates up to 5.76 Mbps in the uplink direction.
Additionally spectral efficiency is increased and latency is decreased. HSDPA and
HSUPA can be implemented in the standard 5 MHz carrier of UMTS networks
and can co-exist with the first generation of UMTS networks based on the 3GPP
Rel99 standard. HSPA affects mainly Radio Access Network (RAN) , therefore
no major changes in the Core Network (CN) are required.
UMTS Release 99
In UMTS Release 99 broad bandwidths of 5 MHz were reserved for UMTS.
Therefore high data rates are possible, particularly while having few participants
in a cell. Additionally a new multiplex method was introduced (Code Division
Multiple Access CDMA) which offers an increased flexibility in the exploitation of
the spectral resources.
UMTS Release 4
Release 4 aims to transmit all applications over a common core network independent whether they are real time or not. Therefore VoIP is introduced,
because the future core network will be IP-based.
UMTS Release 5
In the core network the main alteration is the implementation of IMS (IP
Multimedia Subsystem). The IMS represents and registers a user not only in the
mobile network but also in the Internet. Also the HLRis integrated in the IMS. In
the radio access network, HSDPA and QoS are introduced.
UMTS Release 6
Release 6 was completed in March 2005 introducing further enhancements to
UMTS including HSUPA (or E-DCH), MBMS (Multimedia Broadcast Multicast
Service) and Advanced Receivers.
1-4
TM5112EN01GLA00
The following Releases are issued by 3GPP (3rd Generation Partnership Project):
Fig. 1 UMTS releases and added features

TM5112EN01GLA00
1-5
UMTS Release 99
Environment
The evolution of UMTS affected mainly the air interface: WCDMA was introduced
as new multiplex method in Release 99. The core network is basically unchanged
from GSM. The followingsection deals with the changes in the network and on
the air interface made with UMTS.
3.1
UMTS Network - Network components
The core network in UMTS is based on the GSM cre network. However new
components are added in the Radio Access Network (RAN):
User Equipment UE
The UE replaces the MS and the SIM is replaced by the USIM, that means new
mobiles are required. By now all UEs are downward compatible to GSM.
Instead of the BTS a Node B is implemented. The Node B supports CDMA (Code
Division Multiple Access) on the UMTS frequency bands.
Radio Network Controller RNC
Similar to the BSC, an RNC is implemented as controller. In contrast to GSM a
direct Interface between RNCs exists to support handovers (Iur).
The RNC decides, like the BSC in the GPRS network, if the connection is circuit
or packet switched and transfers it to the MSC or to the SGSN.
1-6
TM5112EN01GLA00
Node B
Fig. 2 UMTS network components and interfaces

TM5112EN01GLA00
1-7
3.2
UMTS - The Air Interface
With UMTS a new multiplex method was introduced: WCDMA - Wideband Code
Division Multiple Access. Wideband refers to the used 5 MHz carrier of UMTS
whereas Code Division Multiple Access describes the used multiplex
method.UMTS covers several different air interface modes. Only FDD mode is
described here since it isthe de facto choice of UMTS implemented worldwide.
3.2.1
FDD Mode
In FDD mode, all participants are assigned a frequencycarrier of5 MHz in each
direction. The users are distinguished via codes. Theycantransmit and receive
simultaneously. The gap between the two frequency bands for UL and DL is
known as the duplex distance.
CDMA
In CDMA several signals are sent in the same frequency band and the same time
slot. Each signal is created by spreading a narrowband signal through the use of
a unique user code to a multiple of the original bandwidth. This process is called
spreading. The receiver correlates the sum of the received signal with the user
code and thereby reobtains the original narrowband signal,the process known as
despreading.
Fig. 3 Multiplex Methods
1-8
TM5112EN01GLA00
3.2.2
3.2.3
Spreading
The signal in UMTS is spread using codes. The binary, digital subscriber data
(1,0) is converted on the transmission side to bipolar data (-1, +1) before the
spreading process takes place. The spreading code also consists of bipolar data.
The value of a chip can be +1 or -1. The subscriber data is then multiplied by the
high chip rate spreading code. The result is the coded data, which is then
transmitted over the radio interface.
The receiver multiplies the received, code data sequence with the bipolar
spreading code to obtain a bipolar data sequence. The original subscriber data is
recovered by converting this data sequence to binary, digital data.
Fig. 4 Spreading
The smallest unit of digital information is generally called a bit (an abbreviation
derived form binary digit). To distinguish the smallest units in the original
subscriber information from the smallest units in the coded data, the smallest unit
in the coded data after spreading is called chip .
The smallest unit transmitted over the radio interface is called symbol . The
modulation methods differ in their ability to map a number of chips to symbols.
The simplest method can just map one bit per symbol.
TM5112EN01GLA00
1-9
To use the bandwidth of 5 MHz the user signal is spread to 3.84 Mchip/s. To
obtain a bandwidth being independent of theutilized bit rates in the cell, the chip
rate in the cell must be kept constant. Therefore the user signal is spread using
spreading codes. That means the length of the spreading code has to differ
dependent on the user data rate. The overall degree of spreading varies to
enable the final signal to fill the required channel bandwidth. As the input data
rate may vary from one application to the next, the degree of spreading needs to
be varied accordingly.
The spreading factor indicates the number of chips that spread a symbol each
time. The number of chips per data symbol is called the Spreading Factor (SF).
The spreading factor therefore states the relationship between the chip rate and
the data rate of the subscriber. The higher the bit rate of a signal, the less it is
spread and the less the processing gain. Processing Gain is the ratio of the
transmitted bandwidth to information bandwidth. One could say processing gain is
the amount of jamming or interference power that is reduced going through the
despreading process. Processing gain is the improvement in the signal-to-noise
ratio of a spread spectrum system. Higher spreading factors are more easily
correlated by the receiver and therefore a lower transmit power can be used for
the same symbol error rate.
The codes required to spread the signal must be orthogonalif they are to
enable multiple users and channels to operate without mutual interference. Codes
are orthogonal of each other if they are independent of each other that means
there is zero correlation between the different codes. In this way only the desired
1-10
TM5112EN01GLA00
Fig. 5 WCDMA: Transmission / Reception
recipient is able to correlate and decode the signal, all other signals appearing as
noise. This allows the physical radio frequency channel to be used by several
users simultaneously.
The codes used in W-CDMA are Orthogonal Variable Spreading Factor
(OVSF) codes. They are constructed from a tree, the OVSF code tree. The
creation of this OVSF code tree is rather simple: Out of one mother code evolves
two children codes. One of the children codes doubles the mother code. The
other children code takes the mother code and adds the inverted mother code.
Fig. 6 OVSF Code Tree
TM5112EN01GLA00
1-11
Every user gets a unique channelization code assigned depending on the

requested service. A code can be used in a channel if and only if no other code
on the path from the specific code to the root of the tree is used in the same
channel.
The different users and their applications can be distinguished by their unique
channelization code in the downlink direction per cell. Channelization codes are
used to separate channels from the same source.
Fig. 7 Channelization and Scrambling Codes
1-12
TM5112EN01GLA00
3.2.4
Scrambling
In addition to spreading, part of the process in the transmitter is the scrambling

operation. This is needed to separate terminals or base stations from each other.
Scrambling is used on top of spreading, so it does not change the signal
bandwidth but only makes the signal from different sources separable from each
other. In FDD so-called Gold codes are used to form scrambling codes (10ms
in length = 38400 chips).
Fig. 8 Usage of Channelization and Scrambling Code
TM5112EN01GLA00
1-13
Fig. 9 Scrambling Codes for FDD in the uplink direction
As it is not possible to retain exact synchronization in the uplink direction,

scrambling codes are used to ensure orthogonally of the signals in the uplink.
1-14
TM5112EN01GLA00
In the uplink direction another feature of scrambling code is used to address a

problem:
3.2.5
Usage of OVSF code tree
Depending on the current load situation every user is assigned the appropriate
spreading factor and unique channelization code within the cell according to the
requested service. The assigned channelization code determines the possible
data rate. As already mentioned a code can be used in a channel if and only if no
other code on the path from the specific code to the root of the tree is used in the
same channel. That means channelization codes are a limited resource within a
cell.
For example a 384 kbps Radio Bearer in the downlink is mapped to spreading
factor 8, but only 8 channelization codes with spreading factor 8 exist per cell.
Besides several channelization codes are needed for signaling purposes (e.g.
CPICH on 256,0 etc.). That means a maximum of 7 user data connections having
384 kbps in downlink direction are possible per cell.
Fig. 10 Utilization of OVSF code tree in the downlink direction
TM5112EN01GLA00
1-15
3.2.6
Timing Structure
In FDD, the air interface timing structure is as follows:a timeslotis defined as

the length of 2560 chips: this corresponds to a duration of 2/3 ms. A timeslot is
the shortest repetitive period.
A frameis defined by the duration of 10 ms andtherefore contains 15 timeslots.

In the FDD mode, a frame is the shortest possible transmission duration. Short
data packets for setting up a connection or packet-switched data packets are at
least one frame in duration. A frame is likewise the shortest period of time for
changing the transmission rate.
Fig. 11 Timing structure and usage in FDD mode
1-16
TM5112EN01GLA00
TM5112EN01GLA00
1-17
HSDPA
Technologically HSDPA is an upgrade to UMTS. Therefore HSDPA is already

called 3.5G in parallel to 2.5G, which meant a technological add on for GSM
networks in form of HSCSD or GPRS.
HSDPA is the abbreviation for "High Speed Downlink Packet Access". The name
describes an essential aspect of this new technology: the significantly increased
data throughput per user - up to 14.4 Mbps. HSDPA is applicable to
packet-switched data traffic.
The increased data throughput is not the only argument in favor of HSDPA,
further arguments will be introduced in the following sections.
HSDPA was introduced in Release 5. However it is not mandatory to implement
HSDPA in an UMTS network. HSDPA cells can coexist with non-HSPDA cells.
Interworking between HSDPA cells and non-HSDPA cells is possible.
Furthermore, HSDPA-capable mobiles can coexist with older mobiles in the same
HSDPA cell.
Why HSDPA? The three prevailing arguments for HSDPA are:
1-18
increased data rate

reduced latency
increased spectral efficiency
TM5112EN01GLA00
4.1
Higher Data Rate
HSDPA offers increased data rate per user compared to Rel 99. In the first
release 1.8 Mbps per user will be possible. Higher data rates up to 10.8 Mbps are
possible in newer releases. The maximumdata rate 14.4 Mbpsis only possible
under certain conditions, for example good channel conditions and sufficient
resources in the Node B which is rarely acheived.
4.2
Reduced Latency
HSDPA offers reduced latency compared to packet data connections via Rel99.
4.2.1
TCP Transmission Control Protocol
Most packet switched services use TCP for flow control. The protocol guarantees
reliable and in-order delivery of data from sender to receiver. TCP also
distinguishes data for multiple, concurrent applications (e.g. web server and
e-mail server) running on the same host. TCP supports many of the Internet's
most popular application protocols and resulting applications, including the World
Wide Web, e-mail and Secure Shell.
TCP combined with IP is the standard which is used in the Internet. In the
Internet protocol suite, TCP is the intermediate layer between the Internet
Protocol (IP) below it, and an application above it. Applications often need reliable
pipe-like connections to each other, whereas the Internet Protocol does not
provide such streams, but rather only unreliable packets. Therefore TCP is used
to provide a connection-oriented, reliable service between hosts.
TCP was mainly developed for wireline networks. Wireline networks usually offer
reliable, non-fluctuating quality. Therefore TCP works under the assumption, that
the channel quality remains constant and discontinuities in the data rate is
caused by congestion. Packet loss is dealt with as congestion. To avoid further
congestion and resulting retransmissions and drops in the data rate, TCP
regulates the data transport rate down to adapt to the conditions until better
conditions are assumed. Then TCP increases the data transport rate slowly up to
the maximum data rate.
TM5112EN01GLA00
1-19
4.2.2
TCP Slow Start and Congestion Avoidance

Mechanism
The transmission performance in the beginning of a data transmission and after a

congestion situation is characterized by the so called slow start phase.
During slow start, the initial size of the so called congestion window, used by the
sender for flow control, is usually one segment only.After eachacknowledgement
received by the sender, the size of the congestion window is doubled during slow
start phase, i.e., the amount of transmitted data starts exponentially. At a certain
point, when the congestion window becomes too large, congestion occurs and
data packets are discarded.
If the congestion window size reaches the slow start threshold again, TCP
changes from the slow start to the so called congestion avoidancephase. In
this phase, the congestion window is not increased exponentially but linearly:
Each time an acknowledgement is received, the congestion window is increased
by 1 step. But it cannot be increased more than the value suggested by the
receiver.
In case of congestion, the slow start threshold is reset to half of its actual value
and the congestion window is reset to 1 segment.
1-20
TM5112EN01GLA00
The initial slow start threshold, which is set to 65535 bytes, is reset to one half of
the receiver's window size. If now the congestion window is less or equal to this
reset slow start threshold, then TCP restarts with slow start.
Fig. 12 TCP Slow start and congestion avoidance

TM5112EN01GLA00
1-21
In mobile networks the air interface is characterized by fast-changing conditions,

for example, fast fading effects. Therefore drops in the data rate are rather
common. Because of the slow start/congestion avoidance characteristics in TCP,
drops caused by Fast Fading Effects induce time-consuming adjustment
mechanisms. The impact of the slow start/congestion avoidance on mobile data
connections is rather high and usually prevents the user from using the
theoretical possible data rate.
Latency delays in mobile networks are rather high. In UMTS the common latency
delay amounts between 200ms and 300ms, in GPRS even up to 700ms. HSDPA
offers distinct decreased latency delay times, the latency delay is approximately
100ms.
With HSDPA, thanks to HARQ (Hybrid Automatic Repeat Request) in the

UMTSNode Bat the MAC-hs level, a NACK requires less than 10 ms for
retransmission, which enables the recovery of erroneous frames before the TCP
timer expires and leaves the TCP throughput unaffected.
Fig. 13 Retransmission cycle in Rel99 and HSDPA
1-22
TM5112EN01GLA00
In wired networks error detection followed by retransmissions is usually used in

case of error. This method is typically implemented as an ARQ(Automatic
Repeat Request) system.
In mobile networks increased error rates are caused by fast changing conditions
on the air interface. A simple ARQ system would require a high number of
retransmissions resulting in a low data rate. Therefore as a preventive measure
the sender duplicates the user data. The receiver can use the redundant data to
reconstruct the original data. The need of retransmissions is consequently
reduced. This method is called Forward Error Correction (FEC).
Hybrid ARQ (HARQ) is defined as any combined ARQ and FEC method that
saves failed decoding attempts for future joint decoding. HARQ is not one method
but encompasses many named variants.
TM5112EN01GLA00
1-23
4.3
Increased Spectral Efficiency
In Release 99 every user is assigned a dedicated channel, partly independent of

the actual data rate. Resources are reserved for the user, but not completely
used. Therefore blocked but unused resources exist in a cell, the capacity of a
cell is not efficiently used.
HSDPA introduces shared channels. Resources are not assigned/reserved for
one user, but used among the users dependent on their demands. Node B
schedules the sharedchannels everyTransmission Time Interval (TTI) which is2
ms in HSDPA.A set of input parameters are considered by the Node B for
resource allocation. Input parameters are
feedback of the UEs about the channel quality (Channel Quality Indicator)
UE capabilities
priority class
status of buffer
available resources
outstanding retransmissions
Fig. 14 Increased spectral efficiency with HSDPA
1-24
TM5112EN01GLA00
TM5112EN01GLA00
1-25
HSUPA
Similarly to HSDPA in the downlink, HSUPA defines a new radio interface for the
uplink communication. HSUPA was introduced in Release 6. The first standard
was improved in December 2004, and the 3GPP Release 6 core specifications
defining the enhanced uplink were completed in May 2005. HSUPA is also known
as FDD Enhanced Uplinkor E-DCH.
As with HSDPA, the aim with HSUPA has been to increase capacity and
throughput for packet switched traffic while reducing delay. HSDPA is a
prerequisite for HSUPA support.
With HSDPA only providing improvements in downlink, HSUPA achieves the
following advantages compare to Release 99 in the uplink:
increased data rate

reduced latency
increased cell coverage and throughput
Fig. 15 HSUPA advantages
1-26
TM5112EN01GLA00
5.1
Higher Data Rate
HSUPA achieves higher uplink data rates by allowing spreading factor as low as
2 while using up to 4 channelization codes per user giving the maximum data
rate of 5.76 Mbps. In initial deployments of HSUPA, only up to1.44 Mbps is
possible.
5.2
Reduced Latency
With help of the new MAC-e and MAC-es introducedfor HSUPA, the scheduler
schedules radio resource and perform HARQ in the Node B in the uplink
direction.Thus thedelay and round trip timein HSUPA is greatly reduced just like
HSDPA.
5.3
Increased Cell Coverage and Throughput
Even though HSUPA allocates dedicated channels for every user, the spreading
factor is not fixed and can be switched between high data rate and minimal data
rate in each Transmission Time Interval (TTI) . The resulting user is called
"granted user" and "non-granted user", respectively.It is possible to base the
scheduler on radiocondition so thatthe scarce uplink radio resource is directed
toward users with higher throughput. Thus the overall cell throughput is
increased. In HSUPA, TTI can be either 2msor 10ms.
With fast retransmission, the required block error rate (BLER) required by the UE
is reduced. This demands less power control headroom and results in larger cell
coverage.
TM5112EN01GLA00
1-27
Exercises
Exercise 1
What is the base station and controller in UMTS?
1-28
TM5112EN01GLA00
Exercise 2
Explain the purpose of channelization code and scrambling code in DL.
TM5112EN01GLA00
1-29
Exercise 3
Why latency is reduced in HSDPA and HSUPA?
1-30
TM5112EN01GLA00
TM5112EN01GLA00
1-31
6.1
Solutions
Exercise 1 (Solution)
What is the base station and controller in UMTS?
Node B andRNC, respectively
1-32
TM5112EN01GLA00
Explain the purpose of channelization code and scrambling code in DL.
Channelization code is used to spread narrowband user information to
large bandwand. Differentchannels in the same cell are distinguished
by different channelization code.
Scrambling code is used to distinguish signals coming from different
cells.
TM5112EN01GLA00
1-33
Why latency is reduced in HSDPA and HSUPA?
Because acknowledgement and retransmission is between UE and
NodeB which is faster.
Shorter TTI means thereceiver does not have to wait long for a
complete data block to send acknowledge response. Smaller data
block because of small TTI also reduce the amount retransmit data.
1-34
TM5112EN01GLA00
HSDPA and HSUPA

Features
Contents
nazilute.en.lmm/loqutaqe.en.slo
2
2.1
2.2
2.3
2.4
2.5
Basic Principles of HSDPA ...................................................................... 4

Introduction of new high speed channels................................................... 4
Short TTI ..................................................................................................... 8
Usage of OVSF Code Tree with HSDPA..................................................10
UE Capabilities..........................................................................................12
Summary Rel 99 - HSDPA.......................................................................14
3
3.1
3.2
HSDPA Features Summary.................................................................... 16

HSDPA RelatedFeatures in RAS06......................................................... 16
HSDPA Related Features in UMR6.5 .......................................................18
AssociatedDCH.......................................................................................20
HS-PDSCH Codes ................................................................................... 22
Code Multiplexing................................................................................... 24
Dynamic HS-PDSCH Resource Allocation........................................... 25
UE Scheduling.........................................................................................26
Number of HSDPA Users ....................................................................... 29
10
Frequency Layer......................................................................................30
11
HSDPA with AMR .................................................................................... 32
12
12.1
12.2
12.3
Basic Principles of HSUPA .................................................................... 34

New HSUPA Channels and OVSF Code Usage ...................................... 34
HSUPA terminal categories.......................................................................37
Summary Rel' 99, HSDPA and HSUPA................................................... 38
13
HSUPA Features Summary.................................................................... 40
TM5112EN01GLA00
2-1
HSUPA Related Features in RAS06.........................................................40

HSUPA Related Features in UMR6.5 .......................................................41
14
E-DCHCodes and Spreading Factors ...................................................42
15
HSUPA with AMR .................................................................................... 42
16
HSPA+ ...................................................................................................... 44
17
17.1
Exercises..................................................................................................46
Solutions....................................................................................................48
13.1
13.2
2-2
TM5112EN01GLA00
Module Objectives
At the end of the module the participant will be able to:

Explain the basic principles of HSDPA and HSUPA.
Describe features contained in RAS06/UMR6.5 release.
Explain HSDPA codes, codemultiplexing, and dynamic resource allocation.
Explain different UE scheduling technique.
Describe HSPA with simultaneous AMR voice call.
TM5112EN01GLA00
2-3
Basic Principles of HSDPA
The followingsection illustrates the basic principles of HSDPA including new

channels, TTI (Transmission Time Interval), code usage, and UE capabilities.
2.1
Introduction of new high speed channels
With HSDPAone new transport channel and three new physical channels were
introduced in UMTS.
Transport Channels:
HS-DSCH (Transport Channel)
Physical Channels:
HS-PDSCH (High Speed Physical Downlink Shared Channel)

HS-SCCH (High Speed Shared Control Channel)
HS-DPCCH (High Speed Dedicated Physical Control Channel)
Fig. 1 HSDPA channels
2-4
TM5112EN01GLA00
2.1.1
HS-DSCH and HS-PDSCH
HSDPA introduces a new shared transport channel. The transport channel

carrying the user data with HSDPA operation is denoted as High Speed Downlink
Shared Channel (HS-DSCH). HS-DSCH enables user data rates up to 14.4
Mbps.
The High Speed Physical Downlink Shared Channel (HS-PDSCH) is a downlink
physical channel that carrying the HS-DSCH user data. The HS-DSCH can be
allocated to a maximum of 15 HS-PDSCH. In HSDPA a fixed spreading factor of
16 is specified for the HS-PDSCHs. The maximum number of HS-PDSCHs that
can be allocated per cell is 15.
Fig. 2 HSDPA: shared channels and multi code transmission
TM5112EN01GLA00
2-5
In HSDPA the newly introduced HS-DSCH is not only time multiplexed between
the users, but also code multiplexed. A code and time domain is introduced.
The individual HS-PDSCH channels are characterized by their channelization

code. Each Transmission Time Interval (TTI) , which consists of 3 timeslots in
HSDPA, the assignment of the channelization codes to the different users can be
changed.
Fig. 3 User in code and time domain
2-6
TM5112EN01GLA00
2.1.2
HS-SCCH
The High-Speed Shared Control Channel (HS-SCCH) is a downlink control

channel that informs mobile devices when HSDPA data is scheduled for them,
and how they can receive and decode it. It has a fixed spreading factor of 128.
For each HS-DSCH TTI, each HS-SCCH carries HS-DSCH related downlink
signaling for one UE.
Fig. 4 HS-SCCH and HS-DPCH
A UE can monitor up to 4 HS-SCCHs simultaneously.

A HS-SCCH set is a set of HS-SCCH which is used for HS-PDSCH allocation.
There is a maximum of four HS-SCCHs in a given HS-SCCH set. The HS-SCCH
set the UE is supposed to monitor is signaled by higher layers to the UE. Several
HS-SCCH sets can be configured in a cell.
Note:The number of HS-SCCHs per cells determines the maximum number of
simultaneous users per TTI.
2.1.3
HS-DPCCH
The High Speed Dedicated Physical Control Channel (HS-DPCCH) is an uplink

control channel used by the mobile to report the downlink channel quality, called
Channel Quality Index (CQI), and request for retransmissions. It uses fixed
spreading factor 256.
TM5112EN01GLA00
2-7
2.2
Short TTI
The introduction of a short Transmission Time Interval of 2ms in HSDPA is an

important contribution to reduce latency delays. TTI is defined as the inter-arrival
time of the transport block set, and is equal to the periodicity at which a transport
block set is transferred by the physical layer on the radio interface. In Rel 99
10ms, 20ms, 40ms and 80ms is possible as TTI time interval.
In HSDPA the TTI is shortened to 2ms corresponding to 3 timeslots of 2/3 ms.
Therefore every 2ms, the system can:
change the allocation of resources to the user

react to incorrect received data
react to changes concerning quality demands
Fig. 5 Quality cycle in HSDPA
2-8
TM5112EN01GLA00
Allocation of resources
Every TTI it is determined, what users are being served, and which HS-PDSCHs
they get allocated.
Retransmissions
In case of failure with HSDPA just the data of 2ms has to be retransmitted,
compared to 10ms/20ms/40ms/80ms in Rel99. Therefore the effective data rate
is increased.
Reaction to channel quality
The congestion avoidance algorithm in TCP is less affected by slow fading effects
due to faster adjustments to the channel quality on the air interface.
TM5112EN01GLA00
2-9
2.3
Usage of OVSF Code Tree with HSDPA
As already mentioned, channelization codes are a limited resource within a cell.

In one cell between 1 and 15 channelization codes can be reserved for
HS-PDSCHs. The used spreading factor is always 16. The reserved codes for
HSDPA can not be used for Rel 99 traffic, therefore the code usage has to be
closely monitored in HSDPA cells in order to avoid congestions within the OVSF
code tree.
In the downlink direction several signaling channels have to be considered
regarding the code tree usage:
- n HS-SCCHs - fixed spreading factor of 128, allocated in sequence
CPICH on 256,0
CCPCH on 256,1 (used by BCH/BCCH)
AICH spreading factor 256
PICH spreading factor 256
- n FACH spreading factor 256 - 4 (depending on implementation)
PCH spreading factor 256 - 4 (depending on implementation)
The PCH and one of the FACH may be multiplexed using the same
channelization code. In the following picture an example for an OVSF code tree
usage is shown:
2-10
TM5112EN01GLA00
1
1
1
1
1
1
1
Fig. 6 Usage of OVSF code tree with HSDPA (UMR example)

In the above example, four Rel 99 data connections with 384kbps in the direction
are still possible. Here C SF, n denotes channelization code n of spreading factor
SF.
TM5112EN01GLA00
2-11
2.4
UE Capabilities
In Release 5, twelve new UE categories have been specified, which differ in the
number of channelization codes, the minimum inter-TTI interval, and the support
of the 16 QAM modulation:
Codes
This is the maximum number of HS-DSCH multicodes that the UE can
simultaneously receive. It could be5, 10 or 15.
Minimum Inter TTI Interval
Minimum inter-TTI time defines the minimum time between the beginning of two
consecutive transmissions to this UE. If the inter-TTI time is one, this means that
the UE can receive HS-DSCH packets during consecutive TTIs, i.e. every 2 ms. If
the inter-TTI time is two, the scheduler would need to skip one TTI between
consecutive transmissions to this UE.
Transport Block Size
Transport block size is the maximum number of HS-DSCH transport block bits
that can be received within an HS-DSCH TTI.
Soft buffer size is the maximum number of soft channel bits over all the HARQ
processes. That means the buffer capacity for HARQ. This can impact the UE
receiver performance particularly in poor quality locations where the number of
retransmissions can be high.
Modulation
Supported modulations of UE can beQPSK only or both QPSK and 16QAM.
2-12
TM5112EN01GLA00
Soft Buffer Size
Fig. 7 UE Categories
TM5112EN01GLA00
2-13
2.5
Summary Rel 99 - HSDPA
The following table illustrates the main differences between HSDPA and Rel 99:
Fig. 8 Basic Principles of HSDPA in comparison to Rel 99
2-14
TM5112EN01GLA00
TM5112EN01GLA00
2-15
HSDPA Features Summary
This section gives the summary of the HSDPA support in Nokia Siemens
Networks products.Information up till RAS06 and UMR6.5 versions are provided
in this courses. Many of the features are covered in subsequent sections.
3.1
HSDPA RelatedFeatures in RAS06
HSDPA has been supported by Nokia Siemens Networks RNC 196/450 and
related Node B's sinceversion RAS05. The following tables list the features
related to HSDPA up toversion RAS06.
Fig. 9 RASHSDPA Feature (Part 1)
2-16
TM5112EN01GLA00

TM5112EN01GLA00
2-17
3.2
HSDPA Related Features in UMR6.5
HSDPA has been supported by Nokia Siemens Networks RNC RN750 and
related Node B's since version UMR5.0. The following tables list the features
related to HSDPA up to version UMR6.5.
Fig. 12 UMRHSDPA Feature (Part 1)
2-18
TM5112EN01GLA00
Fig. 13 UMRHSDPA Feature (Part 2)

TM5112EN01GLA00
2-19
AssociatedDCH
HSDPA only covers downlink data direction. Release 99 dedicated channel

(DCH) is still required for signaling and UL data. The maximum bit rate for
signaling is typically 3.4kbps in both UL and DL. Since DL DCH only contains
signaling, fixed spreading factor 256 is used in DL direction.On the other
hand,UL DCH contains both signaling and UL data.Typical UL data rates are
64kbps, 128kbps and 384kbps. Bit rate adaptation is possible by adjusting UL
spreading factor accordingto the actualutilization by the UE.
The feature 16 kbit/s Return Channel DCH Data Rate Support for HSDPA
(RAS06) further expand the range to include 16kbps as an option. So the
possible data rate becomes 16, 64, 128 or 384kbps.
The feature HSDPA RAB Handling Enhancements(UMR6.0) adds 32kbps UL
data rate. So thedata rates of 32, 64, 128 and 384kbps are possible in UL.
The advantage of allowed lower data rate is two folded:
The data rate can be reduced further in case of network overload or

congestion situation.The moredata rate reduction, the more interference
decrease.
Higher UL data rate via DCH is not foreseen because 384kbps already requires
spreading factor 4. HSUPA is a more viable option for higher uplink throughput.
2-20
TM5112EN01GLA00
Many HSDPAusers do not use muchbandwidth in the uplink. The uplink

data rate can be reduced. This frees upchannel element (CE) resource in
the Node B.
Fig. 14 16kbpsuplink DCH in RAS06

TM5112EN01GLA00
2-21
HS-PDSCH Codes
HS-PDSCH uses spreading factor 16 for spreading HSDPA traffic. So a

maximum 15 codes for HS-PDSCH are available.
On RAS, 5 codes are supported with basic HSDPA feature. The feature HSDPA
15 Codes further increase this number to 10 and 15.
With more codes:
Average cell throughput increased by between 30-50%.
On UMR, UMR5.0 can handle 15 codes and code multiplexing. Up to maximum

of 4 HS-SCCHmay be configured. However, only 5 codes can be assigned to a
UE. So UE incategory 7-10 only attains maximum 3.6 Mbps data rate. Full
support of UE category 7-10 is in UMR6.0.
2-22
TM5112EN01GLA00
With HSDPA 10 Mbps per User feature, user peak rates go up to 7.2 Mbps
with UEs supporting at least 10 codes (UE category 7-10) and up to
10.8Mbps with UEs supporting 15 codes (UE category 9-10).
There is significant resource gain if used with Shared HSDPA Scheduler
and HSDPA Dynamic Resource Allocationfeatures
When terminals support less codes than a cell, HSDPA Code Multiplexing
feature is needed to use the remaining capacity (i.e., 10 codes and two 5
code UEs each at 3.6 Mbps = 7.2Mbps).
Fig. 15 Higher number of HS-PDSCH codes

TM5112EN01GLA00
2-23
Code Multiplexing
Code multiplexing means multiple UE can receive HSDPA simultaneously. With

up to 15 HS-PDSCH codes possible, if UE only supports 5 codes and there is no
code multiplexing, 10 codes become idle when the network sends data to this
UE. So this feature is suggested when more than 5 codes are activated in a cell.
Since one HS-SCCH channel can signal data transmission for one UE, the
maximum number of UE involved incode multiplexing during one TTI from single
cell equals the number of HS-SCCH channels configured (max 3 in RAS06, max
4 in UMR).
The available HS-PDSCH codes and HS-PDSCH power of the cell are divided
between the UEs. The number of HS-PDSCH codes used depends on the
channel conditions experienced by UEs.If a cell supports more codes than the
UEs do, then more than one UE can be served during one TTI.
Fig. 16 Code multiplexing example with 3 HS-SCCH channelsand 15 HS-PDSCH channels
2-24
TM5112EN01GLA00
Dynamic HS-PDSCH
Resource Allocation
Because both Release 99 and HSDPA services share the same resource,varying
the amount ofresource assigned for HSDPA depending on the current Rel '99
traffic situation is highly preferred. HSDPA DynamicResource Allocation
feature in RAS covers:
Dynamic Power Allocation
The DL power used for HSDPA is controlled by Node B. All the power left after
DCH traffic, HSUPA control channels, and common channels is used for HSDPA.
This means that as long as there is HSDPA traffic in the cell, all the
availablepower amplifierpower in the Node B can be efficiently utilized.
Dynamic NRT DCH Scheduling
The RNC schedules the NRT DCH bit rates so that the DL power per user of
NRT DCH and HSDPA are equal.For example,if in a 20 W cell there happens to
be 8 W of RTand common channel load, then about 12 W is available for NRT
traffic. This 12 W is then divided so that in case of 2 NRT DCH users and 10
HSDPA users, about 2 W would be given to DCH side and 10 W to HSDPA side.
On operator's choice, the NRT DCH and HSDPAuser atdifferentTraffic Handling
Priority (THP) can be weighted differently toadjust the power resource allocated
for each user type.
Dynamic Allocation of HS-PDSCH Codes
The code allocation is dynamically following the power allocation. In practice this
means that once the NRT DCH bit rates have been decided, based on equal
power criterion, the code requirements for the DCH side have been fixed. All
other codes are then given to the HSDPA (operator may leave some margin to
allow fast voice call allocation). In case of new DCH connections (for which the
bit rate is again determined based on power criteria), the required amount of
HSDPA codes are given back to the DCH.
Direct Switch Between HS-DSCH and DCH
This feature also includes the direct switch from HS-DSCH to DCH other than
zero kbit/s and vice versa.
In UMR, the feature HSDPA Resource and Power Managementworks based

on the power availablefor HSDPA, HSDPA power utilization,and available data
rate for HSDPA. NRT DCH power are adjusted so that the HSDPA could achieve
the power and data rate target. The feature Dynamic Code Allocation for
HSDPA adjusts the number of HSDPA codes according to DCH traffic.
Remaining two items are in basic HSDPA supported.
TM5112EN01GLA00
2-25
UE Scheduling
The packet scheduler has got a central function in HSDPA and is located in the
Node B in MAC-hs. The scheduler's main task is the assignment of resources to
the individual UEs on the HS-DSCH. The way of the implementation of the
scheduler is not specified in the 3GPP standard. Therefore the algorithms of the
scheduler are vendor specific.
Mainly three methods are distinguished:
Fair Scheduleror Round Robin Scheduler
The Round Robin Scheduler assigns the resources to the UEs sequentially.
Channel conditions are not taken into account. Therefore a high degree of
fairness is reached, whereas the capacity of the cell is not efficiently used. UEs
having bad channel conditions decrease the data rate of the system.
SNR-based Scheduler assigns the resources to the UE having the best channel
conditions or CQI. The system capacity is optimally used. The exploitation of the
fast fading channels produce an effect known as multi-user diversity, which
significantly contributes to the spectral efficiency of HSDPA. However UEs having
bad channel conditions may not get served at all.
Proportional Fair Scheduler
The Proportional Fair Scheduler is a compromise between the complete
exploitation of the system capacity and the fairness between the users. The user
having the best Relative Channel Qualitygets served: The Relative Channel
Quality is the ratio between the users instantaneously supported data rate to the
users average served throughput. When two UEs are in a cell having the same
CQI the UE which had been assigned less data in the previous period gets
served.
2-26
TM5112EN01GLA00
SNR-based Scheduler or Max-CIR Scheduler
Fig. 17 Different types of schedulers

Fig. 18 SNR Scheduling
TM5112EN01GLA00
2-27
The network operator has to evaluate the pro and cons of the different methods,
particularly the exploitation of the maximal system capacity in contrast to evenly
distributed resources between the users. The basic HSDPA support in RAS is
Round Robin while the one in UMR is Max-CIR. Proportional Fair Scheduler is
supported as optional on both systems.
2-28
TM5112EN01GLA00
Fig. 19 Input for user ranking
Number of HSDPA Users
The number of HSDPA users that can be handled on RAS depends on the
features activated as below:
Fig. 20 Type of scheduler and number of usersprovided byRAS feature
With scheduler working at WBTS level, only one scheduler works for all cells. The
number of concurrent users that are scheduled in the same TTI is limited. Shared
HSDPA Scheduler for Baseband Efficiencyhandles maximum 3 UE's per TTI
for the whole WBTS. However, the hardware required for shared scheduler is
only 1/3 of cell based scheduler.
UMRuses cellscheduler. The number of user depends on uplink DCH data rate
and the number of HSDPA cells handled by one CHC card. See NSN Products
chapter for more information.
TM5112EN01GLA00
2-29
10
Frequency Layer
When there are large amount of HSPA traffic, separating Rel '99 DCH and HSPA
traffic to different carrier frequencies (layers)of the same sector can be done.
Upon connection the network will check:
UE capability
The service UE is requesting
and redirect the UE to the correct layer. The feature is named Directed RRC
Connection Setup for HSDPA Layeron RAS and UE Differentiationon UMR.
The same principle also applies to HSUPA with three different types of layer:
Non-HSDPA
HSDPA only
HSDPA and HSUPA
On RAS there is an additional HSPA Layering for UEs in Common Channels

that redirect the UE when the UE makes transition from Cell_FACH to Cell_DCH
state.
Fig. 21 Directing UE to the correct frequency layer.
2-30
TM5112EN01GLA00
Separating into layers allows high HSPA cell capacity. 15 HS-PDSCH codes can
be used without sacrifice Rel '99 support such as voice or video calls.
With several carriers or layers belonging to the same type, load balancing
between carriers can be done. Also load overflow from one layer type to another
type might be possible. For example, if a DCH service is requested and
non-HSDPA layer is already congest, UE may setup in HSDPA layer and move
UE to HSDPA and move back to non-HSDPA when the situation of non-HSDPA
layer improves. In UMR, HSDPA Mobility Enhancementsis required for more
than one HSDPA-capable carriers.
TM5112EN01GLA00
2-31
11
HSDPA with AMR
Simultanous HS-DSCH and DCH is already in used in HSDPA. DCH is required

for signaling and UL traffic. It is possible that this DCH also handles AMR voice
call. It is enabled with HSDPA with Simultaneous AMR Voice Call(RAS) or
HSDPA RAB Handling Enhancements(UMR). Without this feature, the system
could revert back to Rel '99 CS+PS multi-call. UL data rate of packet switched is
fixed to 64kbps in this case for stable voice connection.
Fig. 22 Simultaneous HSDPA and AMR services
2-32
TM5112EN01GLA00
TM5112EN01GLA00
2-33
12
Basic Principles of HSUPA
The followingsection illustrates the basic principles of HSUPA including new

channels,code usage, and UE capabilities.
12.1
New HSUPA Channels and OVSF Code

Usage
HSUPA introduces a new transport channel:

E-DCH (Enhanced Dedicated Channel).
For physical channels, there are two new channels in the uplink direction:
E-DPDCH (E-DCH Dedicated Physical Data Channel), SF=256 - 2
E-DPCCH (E-DCH Dedicated Physical Control Channel), SF=256
In the downlink direction, the following physical channels are introduced:

E-AGCH (E-DCH Absolute Grant Channel), SF=256
E-RGCH (E-DCH Relative Grant Channel), SF=128
E-HICH (E-DCH HARQ Acknowledgement Indicator Channel), SF=128
The E-AGCH is time multiplexed and shared among HSUPA UE's. E-RNTI
(E-DCH Radio Network Temporary Identifier) is encoded into the E-AGCH to
identify the intended UE. For E-RGCH and E-HICH,one channelization
codeprovides 40 orthogonalsignatures. An HSUPA UE is addresseed using the
assigned channelization code and signature. E-RGCH and E-HICH of one UE
mustuse the same channelization code. Thus the 40 signatures is enough to
support 20 different UE's. It is possible for the network to manage several UE's
together by assigning the same signature.
2-34
TM5112EN01GLA00
The above channels are dedicatedto each HSUPA UE. For E-DPDCH, a
maximum of 4 E-DPDCH channels is possible in one UE although the actual
number of channels UE can handle depends on theE-DCH category of UE.
Fig. 23 Channels used by HSUPA UE

TM5112EN01GLA00
2-35
Fig. 24 Usage of OVSF code tree with HSUPA in UMR
Release 99 associated DCHcan be used in HSUPA for UL and DL signaling.

Alternatively, signaling may be carried in the same E-DPDCH and HS-PDSCH as
traffic. In this case E-DPDCH is used for UL signaling while HS-PDSCH is for DL
signaling.
2-36
TM5112EN01GLA00
The addition of HSUPA support consumes channelization code resource of the

cell. The below picture is an example of OVSF code tree utilization:
12.2
HSUPA terminal categories
As in HSDPA, the UEs differ in their capabilities to use HSUPA and are classified
in six UE categories. The UEs varies in their support of:
Maximum number of E-DCH codes transmitted.
Minimum spreading factor.
2 ms TTI.
Maximum transport block size.
Fig. 25 E-DCH UE Category
Note that a UE supporting HSUPA must support HSDPA. Also the UL DCH is
restricted to 64 kbpsfor simultaneous DCH and E-DCH configuration.
TM5112EN01GLA00
2-37
12.3
Summary Rel' 99, HSDPA and HSUPA
The following table gives the main differences between HSDPA, HSUPA, and Rel
99:
Fig. 26 Feature comparison
2-38
TM5112EN01GLA00
Fig. 27 Feature comparison

TM5112EN01GLA00
2-39
13
HSUPA Features Summary
Below are the summary of HSUPA featuressupported in Nokia Siemens

Networks products. Many of the functionalities in HSDPA, such as transport
network features, also apply to HSUPA. Only features previously not covered are
listed here.
HSUPA Related Features in RAS06
13.1
Fig. 28 RAS HSUPA Feature
2-40
TM5112EN01GLA00
13.2
HSUPA Related Features in UMR6.5
Fig. 29 UMRHSUPAFeature
TM5112EN01GLA00
2-41
14
E-DCHCodes and
Spreading Factors
The basic HSUPA support provides 2x SF4. The feature HSUPA 2.0 Mbps
enables 2x SF2 to be used. So the data rate increases from 1.44 Mbps to 2
Mbps. 2x SF2 is not supported in UMR6.5.
The TTI is always 10 ms in RAS06/UMR6.5.
15
HSUPA with AMR
In analogous to simultaneous HSDPA and AMR, the same applies to HSUPA and
AMR. The feature HSUPA With Simultaneous AMR Voice Callis required on
RAS.HSUPA with AMRis included in basic HSUPA support in UMR.
Fig. 30 Simultaneous HSDPA, HSUPAand AMR services
2-42
TM5112EN01GLA00
TM5112EN01GLA00
2-43
16
HSPA+
With HSDPA introducedin Release 5 and HSUPA in Release 6, there are further
improvements to HSPA in later releases. The resulting HSPA with those
improvements in Release 7 and 8is called HSPA+ , Evolved HSPA or HSPA
Evolution. Among additional features introduced are:
New modulation 64QAM for HSDPA. 64QAM modulates 6 bitsinto one
symbol, 50% increase of data rate comparing to 16QAM which modulates4
bits into eachsymbol.
New modulation16QAM for HSUPA. The modulation is also called 4PAM
(Pulse Amplitude Modulation) since each UL physical channel only occupies
either I or Q part of 16QAM constellation.This doubles uplink data rate.
Support of Multiple Input Multiple Output (MIMO). The MIMO in HSPA+
uses two antenna to send and receive, with different data stream being sent
in each pair.
Flat architecture where user packet switched data is transferred directly

between RNC and GGSN, bypassing SGSN.
HSPA+ will support the data rate up to 42Mbps in downlink and 22Mbps in uplink.
2-44
TM5112EN01GLA00
Optional all-IP access network where Node B and RNC are connectedvia
ethernet.
Fig. 31 HSPA+ Improvements

TM5112EN01GLA00
2-45
17
Exercises
Exercise 1
List three HSDPA features on RAS and/or UMR that are useful when a carrier is
shared between Rel 99 and HSDPA.
2-46
TM5112EN01GLA00
Exercise 2
List three HSDPA features on RAS and/or UMR that are useful when the HSDPA
traffic is so large that Rel 99 and HSDPA are handled in different carriers.
TM5112EN01GLA00
2-47
17.1
Solutions
List three HSDPA features on RAS and/or UMR that are useful when a carrier is
shared between Rel 99 and HSDPA.
On RAS:
HSDPA Dynamic Resource Allocation - to vary the number of
code and power depending on Rel 99 load.
16 kbit/s Return Channel DCH Data Rate Support for HSDPA more UL resource for Rel 99.
HSDPA with Simultaneous AMR Voice Call - No need to switch
the packet switched traffic Rel 99 so HSDPA benefit of efficient
resource usage is preserved.
HSDPA Resource and Power Management - to manage power
between Rel 99 and HSDPA.
Dynamic Code Allocation for HSDPA - to vary the number of code
and power depending on Rel 99 load.
HSDPA RAB Handling Enhancements - to support HSDPA
PS+AMR multi call.
2-48
TM5112EN01GLA00
On UMR:
List three HSDPA features on RAS and/or UMR that are useful when the HSDPA
traffic is so large that Rel 99 and HSDPA are handled in different carriers.
On RAS:
Directed RRC Connection Setup for HSDPA Layer - tomove UE in
correct carrier during call setup.
HSDPA 15 Codes - for larger HSDPA traffic.
HSDPA Code Multiplexing - sharing 15 codes to several HSDPA
UE.
On UMR:
UE Differentiation - to move UE in correct carrier.
HSDPA RAB Handling Enhancements -so thatPS+AMR multi call
is retained in HSDPA layer.
HSDPA Mobility Enhancements -support various types of
handoverbetween layers.
TM5112EN01GLA00
2-49
HSDPA and HSUPA

Physical Channel
Contents
nazilute.en.lmm/xacujahi.en.slo
2
2.1
2.2
2.3
New HSDPA Channels.............................................................................. 4

HS-PDSCH..................................................................................................5
HS-SCCH....................................................................................................6
HS-DPCCH..................................................................................................8
3
3.1
3.2
3.3
Adaptive Modulation and Coding ..........................................................10

Adaptive Modulation..................................................................................11
Adaptive Coding........................................................................................13
Channel Quality Identifier CQI.................................................................. 14
4
4.1
4.2
4.3
4.4
4.5
4.6
Hybrid Automatic Repeat Request........................................................ 16

HARQ Methods and Processes................................................................ 17
16QAM Constellation Rearrangement...................................................... 19
Redundancy Version Parameter............................................................... 20
Stop and Wait HARQ ................................................................................20
Soft Memory ..............................................................................................22
Retransmissions in HSDPA...................................................................... 23
HSDPA Process on Layer 1 and 2 .........................................................24
6
6.1
New HSUPA Channels............................................................................ 26

E-DPDCH Channelization Code Allocation and Modulation..................... 28
7
7.1
7.2
Fast Node B Scheduling.........................................................................32

Introduction of a Short TTI ........................................................................ 33
Introduction of HARQ ................................................................................33
Support of Macro Diversity.................................................................... 36
9
9.1
HSUPA Scheduling Mechanism.............................................................38

Node B Scheduling................................................................................... 39
TM5112EN01GLA00
3-1
Scheduling in UE .......................................................................................43
10
10.1
Exercises..................................................................................................44
Solutions....................................................................................................48
9.2
3-2
TM5112EN01GLA00
Module Objectives

List new channels used in HSDPA and HSUPA.
Explain the function of new physical channels.
Describe the procedures running within the physical channels.
TM5112EN01GLA00
3-3
New HSDPA Channels
The newly introduced channels in HSDPA fit into the lower layers: transport
channels and physical channels. The logical channels are not affected.
Fig. 1 New Physical Channels introduced forHSDPA
3-4
TM5112EN01GLA00
Fig. 2 Enhancement of channels in HSDPA, divided into transport channels and physical channels
To transmit user data the transport channel HS-DSCH(High Speed Downlink

Shared Channel) was introduced in HSDPA, which is mapped onto the physical
channel HS-PDSCH(High Speed Physical Downlink Shared Channel).
HARQ functionality and scheduling requires the introduction of two additional
physical channels for signaling purposes:
In uplink a signaling channel is required to provide feedback about received data
blocks, either ACK or NACK, for HARQ-processing: HS-DPCCH(High Speed
Dedicated Physical Control Channel).
Additionally a signaling channel is necessary in the downlink direction to inform
the UE about impending data transmissions in the upcoming TTI and their
transport block format: the so-called HS-SCCH(High Speed Shared Control
Channel).
2.1
HS-PDSCH
HS-PDSCH is the downlink physical channel carrying data. It requires a separate

dedicated channel for uplink data and signaling. Spreading factor of 16 is used
and multi code is possible. Up to 15 codes may be used. HS-PDSCH is shared
among all HSDPA users.
TM5112EN01GLA00
3-5
2.2
HS-SCCH
The downlink signaling consists of a downlink DPCH (Dedicated Physical

Channel) and a number of HS-SCCHs. A fixed spreading factor of 128 is
assigned. For each HS-DSCH TTI, each HS-SCCH carries HS-DSCH-related
downlink signaling for one UE.
The HS-SCCHs carries information regarding HARQ processes and used
transport format:
Transport Format and Resource related Information (TFRI)
Channelization Code-Set: information to the UE, which UE is assigned for the
succeeding TTI,and channelization codes of HS-PDSCHthe UEis supposed
to receive and decode.
Modulation Scheme: information to the UE, whether 16QAM or QPSK is
used.
Transport Block Size.
HARQ Process Identifier: identifythe data belongs to.
Redundancy and Constellation Version. The field contains the Redundancy
Version. parameter for incremental redundancy and the Constellation Version
parameter for 16QAM constellation.
New Data Indicator: information whether new data or a retransmission is
transmitted.
UE Identity: The H-RNTI of the UEis implicitly encoded.
Between the notification via HS-SCCH and the start of the corresponding
HS-DSCH TTI a fixed timing offset of 2*Tslot = 5120 chips is specified.
3-6
TM5112EN01GLA00
HARQ related Information
Fig. 3 HS-SCCH structure

Fig. 4 Timing relation between HS-SCCH and HS-PDSCH
TM5112EN01GLA00
3-7
2.3
HS-DPCCH
The High Speed Dedicated Physical Control Channel is configured in the uplink
direction and contains the following information:
HARQ Acknowledgement including the result of the Cyclic Redundancy
Check (CRC): ACK or NACK. HARQ acknowledgement field is DTXed when
there is no ACK/NACK information being sent.
Channel Quality Indicator (CQI): The transmission cycle and timing for the
Channel Quality Indicator is determined by UTRAN and signaled by higher
layer.
HS-DPCCH uses spreading factor SF=256.
Fig. 5 HS-DPCCH
3-8
TM5112EN01GLA00
Transmission of ACK/NACK commences 7.5 slots following the end of the

received HS-DSCH. This results in the following timing relations between the
HSDPA signaling channels and the HS-DSCH:
Fig. 6 Timing relations between the HSDPA channels
TM5112EN01GLA00
3-9
Adaptive Modulation and

Coding
In HSDPA link adaptionis used to adapt the signal to a certain UE to the radio
channel conditions. Link adaption therefore increases the spectral efficiency and
cell capacity. Italso enables higher data rates of the individual user.
In Rel 99 an adaption to the radio channel conditions was realized by the usage
of power control. Depending on the channel conditions and the requested Quality
of Service the power was regulated. Capacity in an UMTS cell is limited by
interference. To exploit the capacity of the system, it is necessary to keep the
used power of each transmitter as low as possible.
However the used power control algorithm in Rel 99 is rather slow. Additionally
large parts of the power spectrum are not used for transmission of user data.
HSDPA uses the unused power of the Rel 99 system. In order to do so, a
different approach to deal with changing channel conditions had to be found.
Fig. 7 Power in Rel 99 und HSDPA
In HSDPA the transmit power within a TTI is kept constant. Adaption to changing
radio conditions is realized by the selection of an appropriate modulation and
coding scheme. This principle is called Adaptive Modulation and Coding (AMC)
.It constitutes one of the main principles of HSDPA.
3-10
TM5112EN01GLA00
Adaptive modulation and coding (AMC) matches the modulation and coding
scheme to the instantaneous channel conditions for each user transmission. The
power of the transmitted signal is held constant over a subframe interval, and the
modulation and coding format is changed to match the quality of the received
signal or the channel conditions. In this scenario, users close to the base station
are typically assigned higher-order modulation schemes with higher code rates.
The modulation order and code rate will decrease as the distance from the base
station increases.
3.1
Adaptive Modulation
In Rel99 only QPSK (Quadrature Phase Shift Keying) is intended as modulation

method. HSDPA introduces 16QAM(16 Quadrature Amplitude Modulation) as an
additional modulation method.
Both methods use phase modulation wherethe phase of a carrier wave is varied
in order to transmit the information contained in the signal. Having 2^n different
symbols, n bits per symbol can be coded. QPSK realizes a distinction of 4
symbols and can therefore transmit 2 bits per symbol (00,01,10,11). 16QAM
additionally uses amplitude modulation and enables therefore 16 symbols, by
which 4 bits can be transmitted simultaneously. Therefore the physical
transmission rate is doubled compared to QPSK while having the same symbol
rate.
Fig. 8 QPSK and 16QAM in comparison
TM5112EN01GLA00
3-11
HSDPA takes the different characteristics of 16QAM and QPSK into account and
uses the modulation suitable to the current channel conditions: 16QAM when they
are good and QPSK when they are bad.
However 16QAM requires distinct better channel conditions than QPSK. Because
of the fine mapping of the symbols the signal can be easily disrupted. Particularly
the amplitude of an electromagnetical wave experiences higher fluctuation than
the phase. The amplitude easily gets diminished by attenuation and can only be
correctly interpreted in good channel conditions. Therefore 16QAM is only
suitable in case of good channel conditions. 16QAM is also more complex to
implement as the process of modulation and demodulation is much more complex
than in QPSK. Therefore 16QAM is not implemented in all UEs, UEs belonging to
the category 11 and 12 will not be able to use 16QAM.
Fig. 9 Adaptive Modulation
3-12
TM5112EN01GLA00
3.2
Adaptive Coding
Coding Schemes
Rel 99 uses two different channel coding schemes:
Convolutional codingwith rate 1/3 and 1/2.
Turbo codingwith rate 1/3.
HSDPA only uses the 1/3 turbo encoder, which triples the original data in order to
transmit sufficient redundant information. However the effective coding rate in
HSDPA is the result of a combination of turbo coding and rate matching. Rate
matching means that bits on a Transport Channel are repeated or punctured.
First Rate Matching State
After channel codingusing the turbo code with rate 1/3 the number of transmitted
bits is matched to the available UE soft-buffering capability during the first rate
matching process. In the first rate matching process only Parity1 and Parity2 bits
are removed.
Second Rate Matching State
In the next step the number of bits is fitted to the number of physical channel bits
available in the HS-DSCH TTI. The number of available physical channel bits is
determined by the scheduler which assigns a Transport Format Resource
Combination (TFRC).
Fig. 10 Rate Matching in HSDPA
TM5112EN01GLA00
3-13
3.3
Channel Quality Identifier CQI
The Channel Quality Identifier (CQI) is a indicator notifying the quality of the used
radio link by the UE to the serving Node B. The CQI value can be 0 to 30. Each
CQI value corresponds to a certain transport block size, number of HS-PDSCHs,
and modulation format for a certain UE category, a so-called Transport Format
Resource Combination (TFRC)
The CQI is determined by the UE based on the P-CPICH. The CQI is a proposal
of the UE for a Transport Format Resource Combination (TFRC) for the following
TTI. The proposal is made under the assumption that the transport block error
probability (BLER) shall not exceed 10%. The TFRC includes:
Modulation
Transport block size
Number of channelization codes
TX power offset
Alternative methods are allowed by the 3GPP specification to determine the

transport format apart from evaluating the P-CPICH, e.g. selecting the transport
format based on the power of the associated DPCH.
The scheduler has to consider the UE capabilities when assigning a transport
format. Therefore the CQI tables are UE specific. In the following the CQI tables
for UE category 10 (having the highest possible data rate) and UE category 11
and 12 (which were already available in 2006) are shown.
3-14
TM5112EN01GLA00
The Scheduler in the Node B determines the actual transport format based on the
proposal from the UE in form of the received CQI.
Fig. 11 CQI Mapping Table UE category 10

Fig. 12 CQI Mapping Table UE category 11&12
TM5112EN01GLA00
3-15
Hybrid Automatic Repeat

Request
Forward Error Correction(FEC), also called channel coding, is a type of

digital signal processing that improves data reliability by introducing a known
structure into a data sequence prior to transmission or storage. FEC works by
adding check bits to the outgoing data stream. Adding more check bits reduces
the amount of available bandwidth, but also enables the receiver to correct for
more errors. The structure enables a receiving system to detect and possibly
correct errors caused by corruption from the channel and the receiver. This
coding technique enables the decoder to correct errors without requesting
retransmission of the original information. The probability of a successful data
transmission is increased, but because of the redundant data the data rate is
decreased.
HSDPA introduces Hybrid AQR (HARQ) . HARQ is defined as any combined
ARQ and FEC method that saves failed decoding attempts from previous
transmissions for future joint decoding with retransmissions.
3-16
TM5112EN01GLA00
Automatic Repeat Request (ARQ) protocols are protocols which are used for
error control. Basically the receiver checks the received data unit for possible
errors (usually the Cyclic Redundancy Check or CRC is used) and returns an
acknowledgment message, either to acknowledge a correct receipt of the data
(Acknowledgement or ACK) or to request a retransmission (Negative
Acknowledgement or NACK) in case of an erroneous received data unit. ARQ is
an error control method for data transmission in which the receiver detects
transmission errors in a message and automatically requests a retransmission
from the transmitter. Therefore ARQ ensures reliable transmission of data
Fig. 13 Redundancy versions in HARQ

4.1
HARQ Methods and Processes
HARQ encompasses a variety of methods. HSDPA implements two different

methods:
Chase combining
Incremental redundancy
4.1.1
Chase Combining
Chase combining is one of the simplest forms of HARQ. Chase combining

transmits in case of a retransmission exact the same data once again. The
decoder combines multiple received copies of the coded packet weighted by the
SNR prior to decoding. Always the same information and parity bits are sent to
be combined and every version of packet is self decodable. The set of parity bits
is always obtained by using the same puncturing scheme. This method provides
time diversity gain and is very simple to implement.
4.1.2
Incremental Redundancy
In Chase combining, always the same information and parity bits are sent.
Incremental redundancy (IR) may use different sets of parity bits (obtained by
different puncturing schemes) in consecutive packet transmissions. All these
groups of bits obtained from different transmissions have to be stored in the soft
TM5112EN01GLA00
3-17
buffer for combining. Hence, incremental redundancy provides more effective

transmission at the expense of increased soft buffer memory requirements.
The following picture demonstrates the main principle:
Fig. 14 Example for Incremental Redundancy
For simplicity, an IR buffer size of 10 bits/process and a single process are

assumed in this example:
The original data block containing 4 bits is turbo encoded at the 1/3 rate and
therefore tripled to 12 bits.
In the First Rate Matching the data block gets punctured to match to the IR
buffer size of 10 bits. We obtain 10 bits.
The Second rate-matching stage punctures the data again. The puncturing
pattern is determined by the redundancy version (RV) parameters set by
the scheduler (five grey bits in the above figure).
The five grey bits are transmitted.
The data arrives at the UE, is demodulated, padded with dummy bits, and
stuffed into the IR buffer. The data then is decoded. This block is checked
against the CRC (Cyclic Redundancy Check), and if found to be in error, is
stored, and a NACK requests retransmission.
The Node B sends the retransmission. It uses a different puncturing pattern
or redundancy version than on the first transmission (five white bits with a \
inside in the figure).
3-18
TM5112EN01GLA00
At the UE these bits are recombined with the original transmitted five bits.
Now for every data bit here are 2.5 bits available for decoding, which
increases the likelihood for success. If the block is after the CRC check still
in error, a NACK is sent to the Node B to request a retransmission.
To obtain the data for retransmission, yet another puncturing pattern or
tedundancy version is used (five white bits with a / inside in the figure).
The data is recombined with the previous transmissions and decoded. When
the data is correctly decoded, an ACK is sent and the transmission of the
next data unit can start.
Incremental redundancy is called HARQ Type II . If each transmission has to be
self-decodable, it is called is partial incremental redundancyor HARQ Type III
. In HSDPA both versions are employed.
Incremental redundancy reduces the effective coding rate in case of good
channel conditions, whereas in bad channel conditions more retransmissions are
necessary which induces a decreased data rate. Therefore under bad channel
conditions Chase combining is used, thus obtaining a diversity (time) gain.
In Rel 99 error protection was provided by the RLC layer in the RNC. Erroneous
data was dumped and not used for combining with retransmissions.
The HARQ functionality in HSDPA is located in the MAC-hs layer in the Node B
and UE and uses previously sent data for decoding. Therefore in HSDPA HARQ
provides a fast and effective error protection scheme.
4.2
16QAM Constellation Rearrangement
If 16QAM is used as modulation scheme, 16QAM constellation rearrangement is

deployed.
QPSK is much less prone to error than 16QAM. When using QPSK only a phase
estimate is necessary for the demodulation process. With 16QAM constellation,
the different bits mapped to the 16QAM symbols have different reliability, as a
more precise phase estimate is required and also the amplitude has to be
interpreted, and which may be easily affected by attenuation. Therefore two of the
four bits in a symbol have a higher probability of error than the other two bits.
This is compensated for with a method called constellation rearrangement. With
constellation rearrangement, the different retransmissions use slightly different
mapping of the bits to 16QAM symbols to improve the performance. The
rearrangement occurs during re-transmission and disperses the error probability
equally among all the bits in the average, after the re-transmission combining.
16QAM constellation rearrangement consists in the variation of the
bits-to-symbols-mapping, bits can be rearranged before retransmission in such a
manner that some less protected bits become more protected.
TM5112EN01GLA00
3-19
4.3
Redundancy Version Parameter
Incremental redundancy and 16QAM constellation rearrangement are controlled

by the so-called redundancy version (RV) Parameter. The UE gets the
redundancy parameter prior each transmission via HS-SCCH:
Transmission is self-decodable or non-self-decodable.
Used puncturing pattern.
Input parameter for 16QAM constellation rearrangement.
Chase combining is treated as a subcase of incremental redundancy, each
retransmission the same redundant version is sent.
After all HARQ is an implicit link adapation technique and therefore offers in
combination with AMC a powerful method to exploit the available resources.
4.4
Stop and Wait HARQ
The different HARQ methods can not only be distinguished by their way of
creating retransmissions, but also by their timing:
Continuous transmission of data without waiting for feedback -> complex in
implementation, requires buffering and labeling of the data.
Disruption of data transmission until feedback arrives -> simple in
implementation, but idle time of sender.
3-20
TM5112EN01GLA00
Fig. 15 16QAM constellation rearrangement
Stop and sait transmission is the simplest reliability technique. A stop and wait
protocol transmits a data block and then waits for a response. While it is waiting
the sender is said to be in the "idle" state and is unable to send further data. The
receiver receives each data block and sends an Acknowledgement (ACK) if it is
received correctly. Then the sender starts to transmit the next data block. In case
the data was not correctly received, a Negative Acknowledgement (NACK) is sent
and a retransmission is requested. The data units which couldnt be decoded are
stored as so-called soft bits or soft symbols and combined with the retransmitted
data to increase the likelihood of a successful transmission. Because of its
simpleness the demands of system and buffer capacity at the UE are rather low.
Following picture illustrates the principle:
Fig. 16 Stop and Wait ARQ
The advantage of the Stop-and-Wait (SAW) ARQ system lies within its simple
implementation. Buffer is only needed for the actual data block at the sender and
receiver and the data is already received in the correct sequence order. However
the available resources are not used efficiently as waiting times occurs which
decrease the data rate distinctly.
Therefore a N-channel SAW is implemented in HSDPA. The conventional SAW
ARQ process can transmit a next packet only when an ACK (positive
acknowledgement) for a previous packet is received. In order to better use the
waiting time between acknowledgments, multiple processes can run for the same
UE using separate TTIs. This is referred to as N-channel SAW and the multiple
processes are called HARQ processes. The processes are identified by their
TM5112EN01GLA00
3-21
HARQ process number to enable the UE on the receiving side to identify a

certain process to which a received packet belongs to. Moreover, the UE can
re-configure received packets in order and take necessary actions such as soft
combining of a corresponding packet, etc. While a channel is awaiting an
acknowledgment, the remaining N-1 channel continue to transmit and therefore a
consecutive transmission is possible, which increases the data rate.
Fig. 17 N channel HARQ in parallel
The identifier of the HARQ process is transmitted on the HS-SCCH. Three bits
are reserved for the HARQ process number. Theoretically maximal 8 HARQ
processes can be allocated per UE. The UE capabilities states the number of
maximal possible HARQ processes for the specific UE.
In HSDPA the HARQ processes are controlled by the scheduler.
4.5
Soft Memory
HARQ requires the UE to store temporarily the erroneous received data blocks
for soft combining. Soft bit is a received bit for which it is impossible to come to a
decision if it is a "0" or a "1". The required buffer at the UE is called Soft Buffer
In comparison to Rel 99 HSDPA requires more buffer capacity at the UEs. The
UEs differ in their buffer capacities, which determines the number of
simultaneously possible HARQ processes and the redundancy version. The
buffer capacity is listed in the UE categories.
3-22
TM5112EN01GLA00
4.6
Retransmissions in HSDPA
Following picture illustrates the ARQ loops in HSDPA:
Fig. 18 Retransmissions and ARQ loops in HSDPA
In general, an ARQ loop is more efficient at a lower layer due to lower RTT and
optimized PDU size. Buffering is required between ARQ loops in order to avoid
higher layer window stalling and unused lower layer capacity. Lower layer ARQ
must have limited persistency in order to avoid adverse reactions of higher layers,
e.g. retransmissions after timeout.
TM5112EN01GLA00
3-23
HSDPA Process on Layer

1 and 2
The scheduler in the Node B evaluates for different users the channel
conditions, the buffer status for each user, how much time has elapsed since
a particular user was last served, impending retransmissions and so forth. As
the implementation of the scheduler was not specified, the exact algorithm is
vendor-specific.
As soon as a specific TTI is assigned to a UE, the Node B identifies the
necessary HS-DSCH parameters: number of available codes, which
modulation method can be used, UE capabilities, etc. The UE category also
defines the capacity of the soft buffer and therefore which kind of HARQ
method can be used and the number of parallel HARQ processes.
Two slots before the corresponding HS-DSCH TTI the Node B starts to
transmit the HS-SCCH to inform the terminal of the necessary parameters.
The UE monitors the assigned HS-SCCH set. Once it has decoded Part 1
from an HS-SCCH intended for that terminal (containing channelization code
set and modulation scheme), it will start to decode the rest of that HS-SCCH
and will buffer the necessary codes form the HS-DSCH.
The HS-SCCH informs the UE in Part 2 of the HS-SCCH, to which HARQ
process the data belongs to, whether it is a new data transmission or not and
about the transport block size.
Upon decoding the potentially combined data, the UE sends an ACK/NACK
in the uplink direction depending on the outcome of the CRC check
conducted on the HS-DSCH data. The timing offset between the end of the
received HS-DSCH TTI and the start of the ACK/NACK transmission is fixed
to 7.5 slots.
3-24
TM5112EN01GLA00
To summarize the procedures on layer 1 and 2, the sequence of events is

illustrated:
Fig. 19 Sequence of events on layer 1 and 2

TM5112EN01GLA00
3-25
New HSUPA Channels
Unlike HSDPA, HSUPA remains based on a dedicated channel. The Enhanced

Dedicated Channel (E-DCH) is introduced as a new transport channel for user
data in the uplink direction. To support the E-DCH, two new physical channels in
the uplink directions have been specified:
E-DCH Dedicated Physical Data Channel (E-DPDCH)
E-DCH Dedicated Physical Control Channel (E-DPCCH)
The E-DCH Dedicated Physical Data Channel is used to carry uplink user data.
The E-DCH Dedicated Physical Control Channel transmits control information for
E-DPDCH including information to enable the Node B to decode the transmitted
user data (Scheduling and Transport Format Related Information). E-DPDCH and
E-DPCCH are transmitted simultaneously.
In the downlink direction two new physical channels are introduced to perform
scheduling tasks:
E-DCH Absolute Grant Channel (E-AGCH)
E-DCH Relative Grant Channel (E-RGCH)
Another physical channel is introduced in the downlink direction to support the
HARQ functionality:
E-DCH HARQ Acknowledgement Indicator Channel (E-HICH)
Similar to the HS-DPCCH in HSDPA in the uplink direction the E-HICH offers
feedback about the received data from the Node B to the UE in form of ACK
(Acknowledgement) or NACK (Negative Acknowledgement).
3-26
TM5112EN01GLA00
The E-AGCH and E-RGCH are used for the uplink Fast Scheduling mechanism.
Fig. 20 New Physical Channels introduced forHSUPA

TM5112EN01GLA00
3-27
6.1
E-DPDCH Channelization Code Allocation

and Modulation
In the UL the UE can use the whole code tree. Therefore in the uplink direction in
contrast to the downlink direction no shortage of channelization codes exists.
Like in HSDPA,multicode transmission is allowed in HSUPA. That means there

may be zero, one or up to four E-DPDCH on each radio link. The number of
allowed E-DPDCH is dependent on the configuration of a DPDCH:
Fig. 21 Channelization codes for E-DPDCH
The possible combinations E-DPDCH to E-DCH with their respective spreading

factor are:
3-28
TM5112EN01GLA00
Fig. 22 Combinations E-DCH E-DPDCH

TM5112EN01GLA00
3-29
In HSDPA 16QAM was implemented to increase the maximum possible data rata.
With HSUPA no new modulation was introduced with regard to radio link quality.
Binary Phase Shift Keying (BPSK) is used in the uplink direction, which maps one
bit per symbol.
This results in the following maximum data rates:
Fig. 23 Maximum possible data rate in HSUPA
3-30
TM5112EN01GLA00
TM5112EN01GLA00
3-31
Fast Node B Scheduling
Fast Node B scheduling refers to functionality that will be incorporated into the
Node B to enable management of the uplink noise rise caused by the different
UEs on a TTI level basis. The more efficient scheduling mechanism, allowing
better use to be made of the available spectrum and power budget, is the key
improvement in HSUPA. As in HSDPA the scheduler in HSUPA is also located in
the Node B. However instead of time slots and codes power is allocated to UEs
in form of E-DPDCH/DPCCH power ratio. In other terms, the uplink scheduling
mechanism is nothing more than a very fast power control mechanism.
Fig. 24 Fast Node B Scheduling
The two physical scheduling channels E-RGCH and E-AGCH are used to inform
the UE how to regulate its transmitting power level. In case of the E-RGCH, the
UE is instructed to either increase or decrease the transmit power level by one
step, or alternatively to keep the current transmit power level unchanged. In the
case of the E-AGCH, the Node B provides an absolute value for the power level
of the E-DCH at which the UE should transmit.
3-32
TM5112EN01GLA00
7.1
Introduction of a Short TTI
In order to accelerate packet scheduling and reduce latency a short TTI of 2 ms

was introduced corresponding to 3 TS in WCDMA. However the support of the
short TTI of 2ms is not mandatory for the UE. The ability, which minimum TTI is
supported, is a UE capability and is part of the definition of the UE Categories. It
is configured during call setup whether a 2ms or a 10ms is to be used for the
E-DCH.
7.2
Introduction of HARQ
Similar to HSDPA an N-channel parallel HARQ with stop and wait protocol is
applied in HSUPA. In contrast to HSDPA, which is an asynchronous system,
HSUPA is based on synchronous downlink ACK/NACKs. Retransmissions of a
MAC-e PDU follows its previous HARQ (re)transmission after N TTI = 1 RTT.
Fig. 25 Synchronous HARQ in HSUPA
TM5112EN01GLA00
3-33
The number of the parallel HARQ processes depends on the TTI:

8 processes for the 2 ms TTI
4 processes for the 10ms TTI
The number is chosen to enable an uninterrupted E-DCH transmission.
As in HSDPA the turbo coding with rate 1/3 is used. Incremental redundancy and
Chase combining are supported and performed via rate matching.
The ACK/NACK information is transmitted on downlink from each cell in the

E-DCH active set, radio links belonging to the same radio link set sent the same
information. When the UE receives any ACK from Node B it quits the
retransmission process.
Fig. 26 HARQ process in HSUPA
3-34
TM5112EN01GLA00
TM5112EN01GLA00
3-35
Support of Macro Diversity
In HSUPA macro diversity is supported. The following terms are applied:

Active Set
Active set is defined as the set of Node Bs the UE is simultaneously connected
to.
Serving E-DCH cell
The serving E-DCH cell and the HS-DSCH serving cell shall be identical. That
means the serving E-DCH cell is the best server in the downlink direction. In
HSUPA only the serving E-DCH cell is allowed to transmit absolute grants to
submit absolute values for the power level to the UE.
Serving Radio Link Set
The serving radio link set consists of the serving E-DCH cell and the other cells
of the active set belonging to the same Node B. The serving radio link set may
transmit one relative grant to order the adjustment of the power level one step up
or down or to be kept constant.
Non-serving radio links are the radio links belonging to a Node B which does not
provide the serving E-DCH cell. These cells are only allowed to transmit relative
grants.
3-36
TM5112EN01GLA00
Non-Serving Radio Link
Fig. 27 Active Set in HSUPA

That means intra-Node B softer handover and inter-Node B soft handover is

supported in HSUPA. macro diversity is performed by the MAC-es entity in the
SRNC.
TM5112EN01GLA00
3-37
HSUPA Scheduling
Mechanism
The following entities are involved in the scheduling process and the
E-TFC-selection:
HARQ entity.
E-TFC selection function.
Serving grant update function.
Multiplexing and Transmission Sequence Number (TSN) setting.
Fig. 28 MAC-es/e insideUE
3-38
TM5112EN01GLA00
9.1
Node B Scheduling
The serving grant update functionsupplies the serving grant. Serving grant
indicates the maximum E-DPDCH to DPCCH power ratio that the UE is allowed
to use for scheduled data in the following transmission. The value in the
appropriate state variable will be provided to the E-TFC selection function to help
in selecting the best format for the upcoming transmission. The serving grant
update function is executed every TTI.
Fig. 29 Serving Grant function in HSUPA
TM5112EN01GLA00
3-39
The UE shall check, whether it received an absolute grant from its serving cell
(Serving cell = Best server in downlink direction). The absolute grants are
transmitted via E-AGCH and are linked to its corresponding TTI by the timing
relation. Absolute grants are the absolute limitation of the maximum amount of UL
resources the UE may use, that means the maximum power ratio the UE is
allowed to use.
In case an absolute grant is received, the serving grant value is set to the
absolute grant value.
The absolute grant is conveyed in form of E-DCH traffic to pilot ratio

(E-DPDCH/DPCCH) that the UE is allowed to use in the next transmission.
Fig. 30 Mapping of Absolute Grant Value
3-40
TM5112EN01GLA00
In case no absolute grant is received, the UE evaluates the relative grants

transmitted on the E-RGCH. Relative grants are distinguished whether they are
transmitted by the serving radio link (Radio link belonging to the Node B
maintaining the serving cell) or the non-serving radio link (Radio Links belonging
to other Node Bs).
Relative grants from the serving radio link can have the values:
UP
DOWN
HOLD
When receiving a relative grant from a serving radio link, the UE determines the
serving grant according to a specified scheduling grant table , which means it
moves one step down or two or three steps up the table values based on the
current serving grant.
Fig. 31 Scheduling Grant Table
TM5112EN01GLA00
3-41
ETPR (E-DPDCH Transmit Power Ratio) holds the E-DPDCH to DPCCH power
ratio used as reference for relative grant commands. This variable is set to the
E-DPDCH to DPCCH power ratio used for the E-TFC selected for the previous
TTI on this HARQ process.
Relative grants form non-serving radio links can only have the value HOLD or
DOWN in order to avoid overload situations in the corresponding cell. When a
DOWN is sent, the serving grant of the non-serving radio links is determined.
The UE takes the lowest value of the serving radio links and non-serving radio
links and transfers the value to the E-TFC selection function.
The absolute and relative grants are provided by the Node B as part of the
scheduling function located in the Node B. The Node B allocates the E-DCH
resources by means of absolute and relative grants and takes into account
HARQ state.
Load Situation: noise, interference from other cells, DCH users, E-DCH
users.
Happy Bit: transmitted from UE to Node B via E-DPCCH to indicate, whether
it wants and has the ability to allocate more power or is satisfied (unhappy
happy).
Other information.
Fig. 32 Scheduling in Node B
3-42
TM5112EN01GLA00
9.2
Scheduling in UE
The E-TFC (E-DCH Transport Format Combination)selection and HARQ process

in the UE is executed as follows:
Fig. 33 E-TFC Selection in HSUPA
The HARQ entity informs the E-TFC selection entity that no retransmission is
impending and new data could be sent. In case the E-TFC selection entity signals
need for a new transmission, the HARQ entity obtains the transmission
information from the E-TFC Selection unity. The serving grant update function
provided the E-TFC selection function with the maximum E-DPDCH to DPCCH
power ratio that the UE is allowed to allocate for the upcoming transmission for
scheduled data.
Further the HARQ entity obtains the MAC-e PDU from the multiplexing and TSN
setting entity and finally triggers the new transmission.
The used redundancy version in the HARQ process is based on the
Retransmission Sequence Number, which is incremented in each
retransmission up to a maximum of three. The used channel coding is the turbo
coder with Rate 1/3. Incremental redundancy or Chase combining is performed
via rate matching. The puncturing pattern is determined by the retransmission
sequence number.
TM5112EN01GLA00
3-43
10
Exercises
Exercise 1
List new channels introduced for HSDPA and a short description about their
usage.
3-44
TM5112EN01GLA00
Exercise 2
HSDPA Physical Channel Procedures
Understand how in data transmission in HSDPA works.
None
Which of the following is correct about HSDPA? Multiple correct answers are
possible.
16QAM is supported by every UE.
CQI table is different depending on UE category.
Different puncturing pattern is indicated by redundancy version parameter.
Stop and wait HARQ technique with N channels is used.
HARQ is between UE and RNC.
TM5112EN01GLA00
3-45
Exercise 3
List new channels introduced for HSUPA and a short description about their
usage.
3-46
TM5112EN01GLA00
Exercise 4
HSUPA Physical Channel Procedures
None
possible.
10ms TTI is supported by every UE.
Happy bit is sent by UE to the network.
Soft handover is supported by HSUPA.
Every cell in the active set can send Absolute Grant.
TM5112EN01GLA00
3-47
10.1
Solutions
List new channels introduced for HSDPA and a short description about their
usage.
HS-PDSCHfortraffic.
HS-SCCH to specify the UE, the codes of HS-PDSCH,and
information to decode HS-PDSCH.
HS-DPCCH for acknowledgement and channel quality.
3-48
TM5112EN01GLA00
HSDPA Physical Channel Procedures
None
possible.
16QAM is supported by every UE.
CQI table is different depending on UE category.
Different puncturing pattern is indicated by redundancy version parameter.
Stop and wait HARQ technique with N channels is used.
HARQ is between UE and RNC.
TM5112EN01GLA00
3-49
List new channels introduced for HSUPA and a short description about their
usage.
E-DPDCH for traffic.

E-DPCCH for information how to decode E-DPDCH, happy bit.
E-AGCH to signal new E-DPDCH power used compared to
DPCCH.
E-RGCH to adjust E-DPDCH power.
E-HICH to acknowledge.
3-50
TM5112EN01GLA00
HSUPA Physical Channel Procedures
None
possible.
10ms TTI is supported by every UE.
Happy bit is sent by UE to the network.
Soft handover is supported by HSUPA.
Every cell in the active set can send Absolute Grant.
TM5112EN01GLA00
3-51
HSPA Protocols
HSPA Protocols
Contents
nazilute.en.lmm/tugamidu.en.slo
2
2.1
2.2
2.3
2.4
Protocol Stack........................................................................................... 4
Radio Interface Protocol Architecture Rel99 .............................................. 4
Network Layer - Layer 3 ..............................................................................6
Data Link Layer - Layer 2 ........................................................................... 7
Physical layer - layer 1 ................................................................................9
3
3.1
3.2
3.3
Protocol Stack Enhancements with HSDPA ........................................ 10

Physical layer - layer 1 ..............................................................................11
Introduction and function of MAC-hs ........................................................ 12
UE identifiers - Introduction of H-RNTI..................................................... 16
Protocol Stack Enhancements with HSUPA ........................................ 18
5
5.1
Exercises..................................................................................................20
Solutions....................................................................................................22
TM5112EN01GLA00
4-1
HSPA Protocols
4-2
TM5112EN01GLA00
HSPA Protocols
Module Objectives

List the protocols used in HSDPA and HSUPA (layer1, 2 and 3).
Describe function of each layer.
TM5112EN01GLA00
4-3
HSPA Protocols
Protocol Stack
Several enhancements in the protocol stack were made to adapt UMTS to

HSDPA. In the first part of the following chapter a short introduction to the
protocol stack on the radio interface with Rel99 is given. The second part
illustrates the enhancements made with HSDPA.
2.1
Radio Interface Protocol Architecture

Rel99
The protocol architecture in UTRAN is split into horizontal layers and vertical
planes. The layers and planes are independent of each other. This modularity of
the model allows to alter parts within the protocol stack without adapting the
complete protocol stack.
Control Plane: The control plane consists of all application protocols that are
used for radio network controlling. The control plane is used for all control
signaling, which is UMTS-specific.
User Plane: The user plane supports the data streams for user data.
The radio interface consists of three protocol layers:
Physical Layer (Layer 1)
Data Link Layer (Layer 2)
Network Layer (Layer 3)
4-4
TM5112EN01GLA00
On the Radio Interface two vertical planes can be distinguished:
HSPA Protocols
Fig. 1 User Plane and Control Plane

TM5112EN01GLA00
4-5
HSPA Protocols
2.2
Network Layer - Layer 3
The Network Layer (Layer 3) consists of the Radio Resource Control (RRC)
Layer.
RRC is responsible for the Control Plane Signaling of Layer 3 between UEs and
UTRAN. It manages and controls the resources on the radio interface, e.g.
connection establishment, control of radio bearer and mobility management. All
messages of higher layers are encapsulated in RRC messages for transmission
on the air interface. RRC has got control interfaces to the lower layers to
configure characteristics of the lower layer protocol entities including parameters
for the physical, transport and logical channels. The same control interfaces are
used by the RRC layer e.g. to command the lower layers to perform certain types
of measurements and by the lower layers to report measurement results and
errors to the RRC.
Broadcast of information related to the non-access stratum (Core Network)
and to the access stratum (cell specific),
Establishment, maintenance and release of an RRC connection between the
UE and UTRAN (including the allocation/de-allocation of a Radio Network
Temporary Identifier RNTI for the UE),
RRC connection mobility functions (hard and soft handovers, cell and URA
updates),
Paging,
Assignment, reconfiguration and release of radio resources (i.e. codes) for
the RRC connection,
Control of requested Quality of Service QoS,
UE measurement reporting,
Outer loop power control,
Control of ciphering.
4-6
TM5112EN01GLA00
The RRC functions are:
HSPA Protocols
2.3
Data Link Layer - Layer 2
The data link layer is split into the following sub layers:
MAC - Medium Access Control
RLC - Radio Link Control (user and control plane)
PDCP - Packet Data Convergence Protocol (user plane only)
Packet Data Convergence Protocol (PDCP) is used only in the user plane for
packet switched services. It shall perform the following functions:
Header compression and decompression of IP data streams (e.g. TCP/IP
and RTP/UDP/IP headers) at the transmitting and receiving entity,
respectively: the header compression method is specific to the particular
network layer, transport layer or upper layer protocol combinations e.g.
TCP/IP for non real-time applications and RTP/UDP/IP for real-time
applications.
Transfer of user data: transmission of user data means that PDCP receives
IP packets from the application and forwards them to the RLC layer and vice
versa.
The Radio Link Control (RLC) offers data transfer to the higher layer, so-called
radio bearer services. RLC-services are called signaling radio bearer in the
control plane and radio bearer in the user plane. RLC operates in three different
modes (transparent, unacknowledged and acknowledged mode), which offers
different functions to the higher layers dependent on the demands of the higher
layers. In acknowledged mode the HARQ-functionality is located in the RLC with
Rel99.
TM5112EN01GLA00
4-7
HSPA Protocols
Medium Access Control (MAC) coordinates access to the physical layer.

Mapping between logical channels and transport channels. Logical channels
are channels which are classified by the type of information they transmit
(Control and Transport channels). They are located between RLC and MAC.
Transport channels are described by how and with what characteristics data
is transferred over the radio interface and is located between MAC and the
physical layer. Physical channels carry the payload data and govern the
physical characteristics of the signal.
Selection of the appropriate transport format for each transport channel
depending on instantaneous source rate: given the transport format
combination set (TFCS, a list of one or several transport formats) assigned
by RRC, MAC selects the appropriate transport format within the assigned
transport format set for each active transport channel depending on source
rate. A transport format consists of a transport block size (TBS), a
transmission time interval TTI (10, 20, 40 or 80 ms), a channel coding (rate
1/1, 1/2 or 1/3) and a size of the cyclic redundancy check CRC (0, 8, 12, 16
or 24 bits).
Priority handling between UEs on common and shared transport channels in
order to utilize the spectrum resources efficiently for bursty transfer.
Identification of UEs on common and shared transport channels: when a
particular UE is addressed on a common DL channel, or when a UE is using
a common UL channel, there is a need for inband identification of the UE.
Traffic volume monitoring: measurement of traffic volume on logical channels
and reporting to RRC (based on the reported traffic volume information, RRC
performs transport channel switching decisions).
Dynamic transport channel type switching: execution of the switching
between common and dedicated transport channels based on a switching
decision derived by RRC.
Ciphering for the RLC transparent mode (e.g. CS traffic like speech).
The Medium Access Sub layer is comprised of the following MAC entities:
MAC-b: This entity handles the Broadcast Channel (BCH).
MAC-c/sh: This entity handles the Paging Channel (PCH), the Forward
Access Channel (FACH), the Random Access Channel (RACH).
MAC-d: This entity is responsible for handling of dedicated logical channels
and transport channels.
4-8
TM5112EN01GLA00
The functions of MAC include:
HSPA Protocols
2.4
Physical layer - layer 1
The physical layer offers transport of data units as service to the higher layer.
The transport is realized by the physical channels.
TM5112EN01GLA00
4-9
HSPA Protocols
Protocol Stack
Enhancements with HSDPA
HSDPA affects mainly the physical layer (Layer 1) and the data link layer (Layer
2).
The following modifications and enhancements in the protocol architecture are
made:
Enhancements on the physical layer.

Introduction of a new MAC-entity: MAC-hs.
Introduction of HS-DSCH Frame Protocol to provide Flow Control between
Node B and RNC.
Fig. 2 Changes in the user plane for HSDPA
The UTRAN protocol model consists of different layers, which are logically
independent of each other. Therefore changes can be made within one layer
without affecting other layers. For HSDPA no changes in the core network are
necessary except the support of the corresponding Radio Access Bearers. As
HSDPA mainly concerns the data link layer and physical layer, interworking of
HSDPA and non-HSDPA cells is possible.
4-10
TM5112EN01GLA00
HSPA Protocols
3.1
Physical layer - layer 1
Particularly the physical layer was affected by the introduction of HSDPA:
Fig. 3 Introduction of HSDPA - changes on the physical layer
TM5112EN01GLA00
4-11
HSPA Protocols
3.2
Introduction and function of MAC-hs
To support HSDPA, MAC-hs was introduced. The MAC-hs layer in UTRAN is

responsible for:
Scheduling
Scheduling/Priority Handling includes the allocation of resources to the users. The
scheduling is dependent on the priority class of the data, the used algorithm in
the scheduler and other input data like channel quality and impending
retransmissions.
Error correction via H-ARQ
The HARQ entity provides error detection and correction. Erroneous data is
requested for retransmission and in contrast to Rel99 the received data of the
erroneous transmission is not dumped but kept for combining with the newly
transmitted data.
Flow control
Selection of an appropriate transport format

A transport format and resource combination is selected suitable to the current
channel conditions.
4-12
TM5112EN01GLA00
Flow control ensures a controlled data flow between the MAC-hs entity in the
Node B and the MAC-d / MAC-c/sh entity in the RNC. Flow control takes the
capacity on the air interface and the buffer in the Node B into consideration.
HSPA Protocols
Fig. 4 MAC-hs functions in UTRAN

TM5112EN01GLA00
4-13
HSPA Protocols
On the UE side the MAC-hs layer also handles the HARQ-functionality. This
includes the generation of the feedback to the Node B concerning the correct or
erroneous reception of the data (Acknowledgement or Negative
Acknowledgement). Also a reordering function is implemented as a sequential
reception of data packets cannot be ensured because of possible
retransmissions.
Fig. 5 MAC-hs functions in UE
4-14
TM5112EN01GLA00
HSPA Protocols
In contrast to the other MAC sublayers the MAC-hs is already terminated in the
Node B. Therefore a number of important functions get relocated from the
RNC to the Node B. This induces a significant gain of time in combination with a
short TTI of 2ms.
The relocation of the MAC-hs entity in the Node B was mandatory in order to
profit from the time-savings by the dynamic allocation of resources and advanced
error correction.
To support MAC-hs in the Node B more processing power has to be installed in
the Node B.
Fig. 6 Protocol termination of radio interface protocols (control Plane) in HSDPA
TM5112EN01GLA00
4-15
HSPA Protocols
3.3
UE identifiers - Introduction of H-RNTI
S-RNTI : The S-RNTI is allocated by the serving RNC. The SRNC uses the
S-RNTI to address the UE. The D-RNC uses the SRNTI to identify the UE to
the SRNC. The S-RNTI uniquely addresses the UE in the SRNC.
D-RNTI : The D-RNTI is allocated by a DRNC, but the D-RNTI is never used
on the air interface Uu. Instead the SRNC uses the D-RNTI to identify the UE
to the DRNC. The D-RNTI uniquely identifies the UE in the DRNC.
C-RNTI : The C-RNTI is allocated by a controlling RNC when the UE
accesses a new cell of this CRNC. The C-RNTI is unique in the cell. The
corresponding CRNC shall be able to translate the C-RNTI into S-RNTI (if
CRNC=SRNC) or into D-RNTI (if CRNC=DRNC). The C-RNTI is used by UE
to identify itself to the CRNC, and is used by the CRNC to address the UE.
U-RNTI : The U-RNTI (UTRAN - RNTI) consists of the Serving-RNC-Identifier
and S-RNTI (U-RNTI = RNC-ID + S-RNTI). The U-RNTI is a unique identifier
of the RRC connection within PLMN and is used on the radio interface.
H-RNTI: H-RNTI is used as a UE identifier for the HS-DSCH and allocated
by the CRNC. It is unique within one cell controlled by the allocating CRNC
and is reallocated when a cell change is performed.
4-16
TM5112EN01GLA00
A Radio Network Temporary Identifier (RNTI) is used to identify a UE when a

RRC connection exists. Especially when data packets are transferred via
common or shared channel, the UE needs to be addressed. Every UTRAN entity
like RNCs and Node Bs will provide their special identifier for the UE. There are
five types of RNTIs:
HSPA Protocols
Fig. 7 RNTI in UTRAN

TM5112EN01GLA00
4-17
HSPA Protocols
Protocol Stack
Enhancements with HSUPA
The following enhancements take place on the protocol stack in order to support
HSUPA:
Changes on the Physical Layer

Introduction of E-DCH FP to ensure Flow Control
Introduction of MAC-e in Node B and UE
Introduction of MAC-es in RNC and UE
Fig. 8 Protocol Stack HSUPA
The MAC-es/e sublayer was introduced to handle the E-DCH specific functions.
On the UE side the MAC-e/es entity provides the HARQ functionality,
multiplexing of multiple MAC-D PDUS into MAC-es and MAC-e PDUs and setting
of the Transmissions Sequence Number (TSN). Furthermore the MAC-e/es entity
is responsible for the selection of the E-TFC (Transport Format Combination)
according to the scheduling information.
The MAC-e in the Node B controls access to the E-DCH and is connected to
MAC-es located in the s-RNC. That means MAC-e in the Node B performs the
E-DCH Scheduling and the HARQ-functionality. Additionally the MAC-e
demultiplexes the MAC-e PDUs to their corresponding MAC-d flows into MAC-es
4-18
TM5112EN01GLA00
HSPA Protocols
PDUs and forwards them to the SRNC. Note that the soft combining for the
possible multiple Radio Links of a Node B takes place in the Node B.
The MAC-es entity in the SRNC performs reordering functions and Macro
Diversity Selection in case of soft handover with multiple Node Bs. Then it
disassembles the MAC-es-PDUs to MAC-d PDUs and forwards them to MAC-d.
Higher Layers only have to be adopted in order to support E-DCH (e.g. RRC to
configure E-DCH and Core Network to support the corresponding Radio Access
Bearer). New UE identifier is also added: E-RNTI.
TM5112EN01GLA00
4-19
HSPA Protocols
Exercises
Exercise 1
Fill in the missing HSDPA protocols in the figure.
4-20
TM5112EN01GLA00
HSPA Protocols
Exercise 2
Fill in the missing HSUPA protocols in the following figure.
TM5112EN01GLA00
4-21
HSPA Protocols
5.1
Solutions
Fill in the missing HSDPA protocols in the figure.
See chapter text.
4-22
TM5112EN01GLA00
HSPA Protocols
Fill in the missing HSUPA protocols in the following figure.
See chapter text.
TM5112EN01GLA00
4-23
HSPA Mobility Management and Handover control
HSPA Mobility
Management and
Handover control
Contents
nazilute.en.lmm/yahupota.en.slo
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
Cell Change in HSDPA ............................................................................. 4

Overview......................................................................................................4
Best Server, Active Set and Monitored Set ................................................ 5
Events ..........................................................................................................6
Measurement Control..................................................................................7
Measurement Report .................................................................................10
Channel Reconfiguration Procedures....................................................... 11
Reconfigurations........................................................................................11
Cell Change - Examples........................................................................... 16
In- and outward Mobility with HSDPA.......................................................21
Mobility in HSUPA ...................................................................................24
TM5112EN01GLA00
5-1
5-2
TM5112EN01GLA00
Module Objectives

UnderstandHSDPA cell change,HSDPA inward and outward mobility.
UnderstandHSUPA handover,HSUPA inward and outward mobility.
TM5112EN01GLA00
5-3
Cell Change in HSDPA
2.1
Overview
In HSDPA the downlink is only served by one cell. The cell where the HS-DSCH
is currently established is called the serving HS-DSCH cell. The quality of the
serving HS-DSCH cell constantly varies due to the mobility of the UE. If the
quality is degraded or the serving HS-DSCH cell is deleted, the serving RNC
(SRNC) needs to move the serving function to another cell where the quality is
good. This process is called cell change .
Note that although the HS-DSCH is only served by one cell, the associated DCH
can be served by multiple cells. Therefore soft handover is possible with
associated DCH. For HS-DSCH, only hard handover is possible.
Fig. 1 Cellsserving HSDPA UE
5-4
TM5112EN01GLA00
2.2
Best Server, Active Set and Monitored Set
In order to monitor the quality of the radio link and to perform mobility procedures
the SRNC needs information about the channel quality. UTRAN may control a
measurement in the UE either by broadcast of SYSTEM INFORMATION and/or
by transmitting a MEASUREMENT CONTROL message.
Cells that the UE is monitoring are grouped in the UE into three mutually
exclusive categories:
Active Set
Active set is defined as the set of cells the UE is simultaneously connected to
(i.e., thecells currently assigning a downlink DPCH to the UE constitute the
active set). Usually the number of simultaneously active set links is restricted to
three.
Monitored Set
Cells, which are not included in the active set, but are included in the
CELL_INFO_LIST and are therefore explicitly indicated to be measured by
UTRAN belong to the monitored set.
Detected Set
Cells detected by the UE, which are neither in the CELL_INFO_LIST nor in the
active set belong to the detected set. Reporting of measurements of the detected
set is only applicable to intra-frequency measurements made by UEs in
CELL_DCH state.
Further the following terms are applied:
Best Server
Best server is the server having the best value of the measured value (RSCP,
Ec/Io, Path loss). The Best server is used for the HS-DSCH.
Candidate Set
The candidate sets includes possible candidates for handovers, that are presently
not used in the soft handover connection.
TM5112EN01GLA00
5-5
2.3
Events
Events in UMTS are the occurrence of a given report criteria predefined by the
UTRAN and are the basis of decision making of the SRNC regarding mobility
management. The measurements can either be event triggered or periodic.
The following events are defined based on the measurements of Ec/Io, RSCP,
ISCP and path loss (extract of 3GPP 25.311):
Fig. 2 Extract of events
In Release 5, only network controlled serving HS-DSCH cell change is supported.

The decision to perform a cell change is based on UE measurement reports and
other information available in the network. In HSDPA, the existing event 1d is
used for cell change decisions. The cell in the active set with the strongest
measurement (Ec/No or RSCP) is used as serving HS-DSCH cell. When UE
detects that another cell becomes better than the current serving HS-DSCH cell.
UE sends event 1d measurent reports to the UTRAN. UTRAN then triggers
serving HS-DSCH cell change. Handovers in HSDPA are hard handovers, as
only one cell is served in downlink direction.
5-6
TM5112EN01GLA00
2.4
Measurement Control
The RRC Measurement Control message in the downlink direction contains the
following:
Servers to be monitored
Measured quantities for the active set
Measured quantities for the monitored set
Threshold values to use
Size of reporting range
The following figures show the Measurement Control message regarding
intra-frequency measurements. The first part contains the configuration of the
servers the UE is supposed to monitor. In the example two servers are shown,
the original message contains 12 servers.
Fig. 3 Measurement Control message for intra-frequency measurement (Part 1)
In the second part, the values to be measured in the active and monitored set are
defined. In the example for both sets the Ec/No is reported.
TM5112EN01GLA00
5-7
In the third part the report criteria are given:

Validity of the trigger conditions (active set or monitored set, in case of
monitored set a maximum number can be defined. As the top 8 usually gets
measured, five is a sensible figure).
Reporting Range.
Hysteresis and Time-to-Trigger.
Weighting factor.
5-8
TM5112EN01GLA00
Fig. 4 Measurement Control message for intra-frequency measurement (Part 2)
Fig. 5 Measurement Control message for intra-frequency measurement (Part 3) - event 1a, 1b and
1c
Fig. 6 Measurement Control message for intra-frequency measurement (Part 3) - event 1d
TM5112EN01GLA00
5-9
2.5
Measurement Report
Based on the measurement control messages and the performed measurements

done by the UE the occurrence of certain events can be detected and reported to
the UTRAN in form of measurement reports.
In intra-frequency reports, the measured values, the events and the

corresponding servers are specified.In this example Ec/No in the measurement
report can be converted to actual value by the relation: Ec/No = -24.5dB + value *
0.5 dB.
Fig. 7 Measurement Report for intra-frequency reporting event 1a
5-10
TM5112EN01GLA00
2.6
Channel Reconfiguration Procedures
To perform a cell change in HSDPA a channel reconfigurationhas to take

place. Channel reconfiguration means a change of the channel mapping; in RLC /
MAC / physical layer the mapping logical channel -> transport channel -> physical
channel is readjusted.
2.7
Reconfigurations
The RLC and MAC-protocol are responsible for the mapping of the channels:
MAC assigns the logical channels to the transport channels. This is done in
the SRNC.
The physical layer maps the transport channels to the physical channels. The
mapping takes place in the Node B. The HSDPA specific channels are
managed in the MAC-hs sub layer in the Node B.
When performing a cell change a physical channel reconfigurationis sufficient

if the MAC-hs entity is not changed, that means if an intra-Node B cell change is
executed. The mapping of the logical channel to the transport channel is not
affected if the HS-DSCH transport channel and radio bearer parameters do not
change.
Fig. 8 Physical Channel Reconfiguration in Node B
TM5112EN01GLA00
5-11
The Physical Channel Reconfiguration message from Node B to the RNC

contains
The new scrambling code (in this case 97)

Channelization code (here 16,7)
Reason for the reconfiguration (here Code Change)
Activation time as Connected Frame Number (here 224)
Fig. 9 Physical Channel Reconfiguration Message
When the transport channel parameters change, the procedure transport channel
reconfiguration is performed. In case of cell change to another Node B
(inter-Node B Cell Change), the MAC-hs entity has to be reset and a new Iub
bearer needs to be established. Therefore a transport channel reconfiguration
needs to be executed.
5-12
TM5112EN01GLA00
Fig. 10 Transport Channel Reconfiguration in SRNC

The Transport Channel Reconfiguration message from the RNC to the Node B
includes the new channel mapping.
TM5112EN01GLA00
5-13
Fig. 11 Transport Channel Reconfiguration Message (Part 1)
Fig. 12 Transport Channel Reconfiguration Message (Part 2)
5-14
TM5112EN01GLA00
TM5112EN01GLA00
5-15
2.8
Cell Change - Examples
In the following chapter three examples of Cell Change procedures are illustrated:
Intra Node B Cell Change without change of Active Set: Physical Channel
Reconfiguration
Inter Node B Cell Change without change of Active Set: Transport Channel
Reconfiguration
Inter Node B Cell Change with change of Active Set: Active Set Update and
Transport Channel Reconfiguration
2.8.1
Cell Change: Physical Channel Reconfiguration
In this example it is assumed that two radio links are contained in the active set.
Both of them are HSDPA capable and the cell change takes place between the
two of them. Also those two radio links belong to the same Node B.
1.
2.
3.
4.
5.
5-16
As in this case both the source and target HS-DSCH cells are controlled by
the same Node B, only one Node B has to be informed. The SRNC requests
the serving HS-DSCH Node B to perform a synchronized radio link
reconfiguration using the RADIO LINK RECONFIGURATION PREPARE
message. The reconfiguration comprises a transfer of the HS-DSCH
resources from the source HS-DSCH radio link to the target HS-DSCH radio
link. The message includes also necessary information to set up the
HS-DSCH resources in the target HS-DSCH cell.
The serving HS-DSCH Node B sends a RADIO LINK RECONFIGURATION
READY message.
The SRNC transmits a RADIO LINK RECONFIGURATINON COMMIT
message to the serving HS-DSCH Node B including the activation time. At
the indicated activation time, the serving HS-DSCH Node B stops HS-DSCH
transmission to the UE in the source HS-DSCH cell and starts HS-DSCH
transmission to the UE in the target HS-DSCH cell.
The SRNC transmits a PHYSCAL CHANNEL RECONFIGURATION message
to the UE. The message includes activation time, MAC-hs reset indicator,
serving HS-DSCH radio link indicator, HS-SCCH set info and HS-DSCH UE
identity.
At the indicated activation time the UE resets MAC-hs, stops receiving
HS-DSCH in the source HS-DSCH cell and starts HS-DSCH reception in the
target HS-DSCH cell. The UE sends a PHYSICAL CHANNEL
RECONFIGURATION COMPLETE message to the SRNC.
TM5112EN01GLA00
A synchronized cell change is shown, therefore the reconfiguration is not

executed as soon as possible ("Activation Time" = Now) but at a given activation
time. This activation time is specified in form of a CFN (Connected Frame
Number).
Fig. 13 Physical Channel Reconfiguration

TM5112EN01GLA00
5-17
2.8.2
Example for a Transport Channel Reconfiguration
In the following an example for an inter-Node B cell change is illustrated. It is

assumed that the active set contains two radio links which both support HSDPA.
The cell change is executed between the two radio links already belonging to the
Active Set. As the MAC-hs entity needs to be reset, a transport channel
reconfigurationprocedure is required.
Fig. 14 Cell Change: Transport Channel Reconfiguration
The message RADIO LINK RECONFIGURATION PREPARE gives the Node B

all the necessary information to add, modify or delete the HS-DSCHs. The
message RADIO LINK RECONFIGURATION READY informs the UTRAN about
the actual configuration.
1.
2.
3.
5-18
Based on measurement reports the SRNC decides there is a need for a

serving HS-DSCH cell change and prepares a RADIO LINK
RECONFIGURATION PREPARE message to the target Node B in order to
add resources for the target HS-DSCH radio link.
Additionally it requests the source Node B to perform a synchronized radio
link reconfiguration using the RADIO LINK RECONFIGURATION PREPARE
message, removing its HS-DSCH resources.
The source HS-DSCH Node B returns a RADIO LINK RECONFIGURATION
READY message including an indicator that MAC-hs will reset as a result of
the reconfiguration.
TM5112EN01GLA00
4.
5.
6.
7.
8.
9.
The target HS-DSCH Node B also returns a RADIO LINK

RECONFIGURATION READY message.
The HS-DSCH transport bearer to the target HS-DSCH Node B is
established.
The RNC transmits a RADIO LINK RECONFIGURATION COMMIT to the
source and target HS-DSCH Node B including the activation time. At the
indicated activation time the source HS-DSCH Node B stops and the target
HS-DSCH Node B starts transmitting on the HS-DSCH to the UE.
The SRNC also transmits a TRANSPORT CHANNEL RECONFIGURATION
message to the UE. The message includes activation time, MAC-hs reset
indicator, serving HS-DSCH radio link indicator, HS-SCCH set info and
HS-DSCH UE identity.
At the indicated activation time the UE resets MAC-hs, stops receiving
HS-DSCH in the source HS-DSCH cell and starts HS-DSCH reception in the
target HS-DSCH cell. The UE returns a TRANSPORT CHANNEL
RECONFIGURATION COMPLETE message to the SRNC.
The HS-DSCH transport bearer to the source HS-DSCH Node B is released.
The inter-Node B and Intra-Node B cell change differ in the number of Node Bs
involved (in intra-Node B cell change, only one Node B has to be informed about
the radio link reconfiguration). Also in an intra-Node B cell change the transport
channel parameters do not change, therefore no Transport Bearer set up is
required.
TM5112EN01GLA00
5-19
2.8.3
Example for a combined Active Set Update and Cell

Change
This example is a special case, as first a active set update has to take place
because of a Measurement report containing the event 1a, an then a cell change
is performed to the newly added radio link.
1.
2.
3.
4.
5.
The SRNC recognizes the need for an addition of a radio link. It allocates
radio resources for the new radio link and requests the target Node B to
establish a new radio link by transmitting a RADIO LINK SETUP REQUEST
message including the necessary parameters for DPCH establishment.
The target Node B allocates resources, starts physical layer reception on the
DPCH on the new radio link and responds with RADIO LINK SETUP
RESPONSE message.
The DCH transport bearer is established.
The SRNC sends an ACTIVE SET UPDATE message to the UE. The
message includes an identification of the radio link to add.
The UE adds the new radio link to its active set and returns an ACTIVE SET
UPDATE COMPLETE message to the SRNC.
Now the already known procedure of the transport channel reconfiguration takes
place.
Fig. 15 Active Set Update and Cell Change
5-20
TM5112EN01GLA00
2.9
In- and outward Mobility with HSDPA
Inward mobilityis triggered if the UE enters an area where HSDPA is supported

and the HSDPA cell is the best server. Outward mobilityoccurs if the UE leaves
the area where HSDPA is supported. In both cases channel type switching
between DCH and HS-DSCH takes place.
Fig. 16 HSDPA mobility
TM5112EN01GLA00
5-21
2.9.1
Example Inward Mobility HSDPA
Inward mobility occurs if a Radio Link is added to the active set and the added
cell is HSDPA capable and the best server.
Fig. 17 Channel Type Switching DCH HS-DSCH: Inward Mobility
After the active set update, the SRNC sends a RADIO LINK
RECONFIGURATION PREPARE message to the Source Node B in order to
modify the UL DTCH (if necessary) and delete the DL DTCH.
The SRNC transmits also A RADIO LINK RECONFIGURATION PREPARE
message to the target Node B to establish the HS-DSCH, delete the DL
DTCH and modify the UL DTCH if necessary.
When the Iub bearers have also been modified or set up according to the
new configuration, RADIO LINK RECONFIGURATION COMMIT is sent to
the Node B
Finally TRANSPORT CHANNEL RECONFIGURATION is sent to the UE.
5-22
TM5112EN01GLA00
TM5112EN01GLA00
5-23
Mobility in HSUPA
With HSUPA macrodiversity is used. The UE uses soft handover for associated
DCH and for E-DCH. Active set updates are performed using the already existing
triggers and procedures (events 1A, 1B, 1C). Active set of E-DCH can be the
same or subset of associated DCH subset. The following cells in E-DCH active
set are distinguished:
Serving E-DCH Cell
Serving E-DCH cell is the best server in the downlink direction. It transmits both
E-AGCH and E-RGCH to HSUPA UE. A UE can have only one serving E-DCH
cell. The serving E-DCH cell and the serving HS-DSCH cellmust beidentical,
although RRC signaling is independent for both.
Serving E-DCH Radio Link Set
Non-serving E-DCH Radio Link

Non-serving E-DCH radio links (RL) are the cells in the E-DCH active set that are
not handled by the same Node B as serving E-DCH cell. Each non-serving
E-DCH RL can only transmit E-RGCH.The relative grant sent in E-RGCH can
only be HOLD or DOWN.
Similar to HSDPA, to change the serving E-DCH cell an E-DCH serving cell
change is triggered. Also the E-DCH serving cell change is a hard handover.
5-24
TM5112EN01GLA00
Serving E-DCH radio link set (RLS) refers to the cells within E-DCH active set
that are handled by the same Node B as serving E-DCH cell. Cells other than
serving E-DCH cell can only transmit E-RGCH. The content of E-RGCH from
serving E-DCH radio link set must be identical. The relative grant sent in
E-RGCH can be UP, HOLD or DOWN.
In- and outward mobility are performed via channel type switchingor state
transition from DCH to E-DCH and vice versa. In case of decreased / increased
traffic amount transition to / from Cell_FACH is possible.
Fig. 18 In- and Outward Mobility in HSUPA
TM5112EN01GLA00
5-25
HSPA Throughput and Congestion Control
HSPA Throughput and

Congestion Control
Contents
nazilute.en.lmm/qujetelu.en.slo
What input parameters affect the maximum data rate in

HSDPA?......................................................................................................4
HSDPA Throughput...................................................................................6
What input parameters affect the maximum data rate in

HSUPA?......................................................................................................8
HSUPA Throughput.................................................................................10
HSPA Congestion....................................................................................10
7
7.1
Exercises..................................................................................................12
Solutions....................................................................................................14
TM5112EN01GLA00
6-1
6-2
TM5112EN01GLA00
Module Objectives

Describe HSPA throughput in any condition (fixed, mobile etc).
Know how system does in congestion situation.
TM5112EN01GLA00
6-3
What input parameters

affect the maximum data
rate in HSDPA?
The following input parameters influence the maximal possible date rate in
HSDPA:
Number of assigned codes : A HS-PDSCH has got a fixed spreading factor

of 16. Therefore per HS-PDSCH 240 kSymbols/s can be transmitted (3.84
MSymbols/s / 16). When using 15 HS-PDSCH per TTI, a maximum of 3.6
MSymbols/s can be reached. The number of assigned channelization codes
depends on the scheduler, the UE capability, the reserved codes and load
situation within a cell.
Modulation: Using QPSK 2 bit per symbol can be transmitted resulting in a
maximum data rate of 7.2 Mbps in case of 15 used HS-PDSCHs (3.6
Msymbols/s * 2). 16QAM transmits 4 bit per symbol, therefore when using 15
codes 14.4 Mbps could be transmitted (3.6 MSymbols/s * 4). 14.4 Mbps is
usually cited as maximum data rate of HSDPA. However this is the
modulation rate, that means protocol overhead, CRC bits and redundant bits
for Forward Error Correction are included.
Coding rate: In HSDPA Turbo Coder with coding rate 1/3 is implemented.
However the effective coding rate in HSDPA is the result of Channel Coding
and Rate matching. The effective coding rate can be much higher than 1/3.
For example a UE category 10 has 27952 bits as maximum Transport Block
size. This corresponds to the highest data rate of 13.976 Mbps when using
16QAM, and 15 HS-PDSCHs and an effective code rate of 0.9714 ((27952
bit TBS + 24 bit CRC per 2ms) / 14400000 bit/s). This data rate is only
theoretical, since it requires ideal channel conditions that can only be
achieved in a laboratory environment.
Channel conditions I : The UE evaluates the CPICH and notifies the
channel conditions in the form of a transport format proposal to the Node B,
the so-called Channel Quality Identifier. The Mapping of the CQI to transport
format is UE specific.
6-4
TM5112EN01GLA00
UE category: The maximal data rate per UE-category varies between 0.9
and 14.4 Mbps. The data rate results out of the number of HS-DSCH
multicodes, the maximal transport block size and the Minimum
Inter-TTI-Interval.
Terminal performance: Basic detector performancesuch assensitivity and
interference suppression capability, this can vary from one mobile model to
another.
Channel conditions II : Besides AMC link adaption in HSDPA is performed

in the selection of the corresponding HARQ method. Channel conditions also
influence the quality of the received data packets and therefore the number
of required retransmissions.
Scheduler algorithm: Implementation of scheduler algorithm, e.g. Round
Robin, C/I or Proportional Fair.
Fig. 1 HSDPA UE categories
TM5112EN01GLA00
6-5
HSDPA Throughput
The following charts give the average user throughput versus HSDPA code
power for different types of users and channel conditions:
I or is own cell interference observed by the UE,
I oc isother cell interference observed by the UE.
As the UE moves closer to the Node B, UE receives higher received power from
own cell and lower power from interference. So the ratio I or / I oc typically increases
as the distance between UE and Node B decreases. At cell edge in macro cell,
the ratio could be as low as -3 dB.
Reference: WCDMA for UMTS: Radio Access for Third Generation Mobile
Communications, 2nd Edition by Harri Holma, Antti Toskala.
Fig. 2 Average pedestrian user throughput at different power resource and radio condition
6-6
TM5112EN01GLA00
Fig. 3 Averagevehicular user throughput at different power resource and radio condition
From the charts, pedestrian user with very good radio quality I or / I oc = 15 dB can
achieve about 600 kbps throughput at 1 W. Increasing power to 5 or 10 W does
not improve throughput as much. For a Node B with 20 W, assume that 7 W is
consumed by common channels and the cell is intended for HSPA-only service.
The remaining 13 W can be divided for 15 codes to get about8 Mbps throughput.
User with very bad radio quality I or / I oc = -2 dB has throughput only about 70 kbps
at 1 W. About 1 Mbps is possible with this user with 15 codes. Note that using a
few code with very large power, for example 3 codes withapprox. 4 W each
results in lower throughput. Few code with large power is still useful when the UE
Category can onlyhandle5 or 10 codes.
In summary,it is expected to increase cell throughput in HSDPA. For macro cells,
about 1.3 - 2.2 Mbps throughput in HSDPA from about 850 kbps in Rel '99. For
micro cells where the interference from neighborcell is low, cell throughput can be
improved from 1.4 Mbps in Rel '99 to 3.5 - 5 Mbps in HSDPA.
TM5112EN01GLA00
6-7
What input parameters

affect the maximum data
rate in HSUPA?
Analogous to HSDPA, many factors affect the maximum throughput performance

of HSUPA:
UE category: A total 6 UE category with category 6 supports up to 5.76
Mbps.
Receiverperformance: Basic detector performance for UL signal in Node B.
Number of assigned codes and spreading factor : The smallest spreading
factor and the maximum number of codes that the cell assign to UE.Cell
may allow SF4 but disallow SF2, for example.
Channel conditions: Higher interference situation cause the network to

reduce UE grant.
UE transmitter power : This is the UE power class. Higher transmitter power
allow larger coverage.
Scheduler algorithm: How the scheduler send grant commands among the
HSUPA users that are actively transmitting.
6-8
TM5112EN01GLA00
Coding rate: This depends on ACK/NACK feedback and the selection of

amount of data to transmit within one TTI.
Fig. 4 E-DCH UE Category

TM5112EN01GLA00
6-9
HSUPA Throughput
With HSUPA, the uplink is expected to have increased cell throughput from about
800 kbps in Rel '99 to about 1.3 Mbps in macro cell, about 40% improvement.
For micro cell with reduced interference, the improvement is more dramatic.Up to
100% improvement from 1.1 Mbps to 2.2 Mbps can be expected.
HSPA Congestion
In the network, traffic with conversationalclass such as voice and video calls
are treated as higher priority. Streamingand interactive has lower and lower
priority while backgroundclass has the lowest. Thus HSPA, used to carry
interactive/background traffic, is usually treated as lower priority than voice or
video call and only uses the remaining resource available. The same cannot be
said between HSPA and Rel '99 of the same interactive/background traffic class.
The system may actually prefer HSPA to Rel '99 for those traffic. The resource
we concern are:
Channelization Code: Only downlink channelization code has to be

considered because they share the same code tree. This is another limitation
in the downlink.
Radio Interference: The uplink interferenceis the limitation of uplink traffic
capacity.
Channel Element: The computation resource in Node B. This varies
depending on implementationand usually concerns uplink direction.
In the case when downlink resource is scarce, the code and power intended for
HSDPA is reduced andmade available forRel '99 use to ease congestion. When
the powerremaining for HSDPA is small, the cell may only able to serve HSDPA
mobile with very good radio condition. In other words, the coverage for HSDPA in
the cell is greatly reduced.
In case of high uplink interference, the associated UL DCHin HSDPA is
reconfigured to a lower data rate, i.e., by changing the spreading factor. For
HSUPA, the grant for HSUPA users can be decreased to force HSUPA UE's to
transmit at lower power.The UL spreading factorcan also bechanged
whenchannel element resource becomes a limitation.
6-10
TM5112EN01GLA00
Node B Transmit Power : This is often thebottleneck ofthe downlink.
Fig. 5 HSUPA congestion notification via E-RGCH

TM5112EN01GLA00
6-11
Exercises
Exercise 1
Which HS-DSCH and E-DCH category offers the highest data rate?
6-12
TM5112EN01GLA00
Exercise 2
Listfive factors affecting HSDPA transfer data rate.
Also listfive factors affecting HSUPA transfer data rate.
TM5112EN01GLA00
6-13
7.1
Solutions
Which HS-DSCH and E-DCH category offers the highest data rate?
For HS-DSCH: category 10.

For E-DCH: category 6.
6-14
TM5112EN01GLA00
Listfive factors affecting HSDPA transfer data rate.
Also listfive factors affecting HSUPA transfer data rate.
Factors for HSDPA transfer rate:
HS-DSCH category of UE
Number of HS-PDSCH codes configured in the cell
Amountofpower available for HSDPA users
Number of HSDPA usersin the cell sharing the code and power
UE radio condition
Factors for HSUPA transfer rate:
E-DCH category of UE
Minimum SF of E-DCH allowed by the cell
Maximum number of E-DCH codes for one UE allowed by the cell
Amount of interference in the network
UE radio condition
TM5112EN01GLA00
6-15
NSN Products
NSN Products
Contents
nazilute.en.lmm/
2
2.1
HSPA Implementation on RAS ................................................................ 4

HSPA Implementation on RAS ................................................................... 4
3
3.1
HSPA Feature Activation in RAS ...........................................................16

Feature Activation on RAS ........................................................................16
4
4.1
HSPA Implementation on UMR ..............................................................24

HSPA Implementation on UMR ................................................................ 24
5
5.1
HSPA Feature Activation in UMR .......................................................... 34

Feature Activation on UMR .......................................................................34
6
6.1
Exercises..................................................................................................46
Solutions....................................................................................................48
TM5112EN01GLA00
7-1
nazilute.en.lmm/hupawoxa.en.slo
NSN Products
7-2
TM5112EN01GLA00
NSN Products
Module Objectives

Know how HSPAis implemented in Nokia Siemens Networks products.
Explain the requirements on a WBTS/NodeB for HSPA.
Explain channel element and WBTS/NodeB dimensioning.
Explain HSPA and Iub interface.
Describe how to activate the features in the network elements (RNC and
WBTS/Node B).
Know how to activate HSDPA and HSUPA.
nazilute.en.lmm/hupawoxa.en.slo
TM5112EN01GLA00
7-3
NSN Products
HSPA Implementation on
RAS
2.1
HSPA Implementation on RAS
nazilute.en.lmm/dilinehe.en.slo
This section describe HSPA implementation on Nokia Siemens Networks RNC

196 or RNC 450 based systems. The corresponding Node B models are Ultrasite,
Metrosite,Flexi and Pico WCDMA BTS.
Fig. 1 Different types of RNC in RAS product line
7-4
TM5112EN01GLA00
NSN Products
Fig. 2 Different types ofNode Bin RAS product line

2.1.1
RNC
In RNC, no additional hardwares are required in order to provide HSPA support.

However the DMPG s processing resource inside DMCU must be reserved for the
HSDPA pool. Each DMPG can support 6 BTS. Between 1 and 4 DMPGs can be
allocated from each DMCU to HSDPA. The maximum number of DMPGs in the
RNC configuration allocated to HSDPA can be 48.
TM5112EN01GLA00
7-5
NSN Products
Fig. 3 DMPG Pooling
7-6
TM5112EN01GLA00
NSN Products
2.1.2
WBTS
The HSPA capacity depends of the features activated in the network. In the
WBTS, HSDPA modulation can be QPSK onlyor both QPSK, 16-QAM. There
can be 5, 10, or 15 codes for HSDPA. Shared scheduler or cell specific scheduler
may be used to handle user traffic. There could be 16 or48 users per WBTS if
shared scheduler is used.Alternatively, 16 or48 users percell is possiblefor cell
specific scheduler. With 16-QAM and 15 codes, data rate of 10.8 Mbit/s is
possible.
In RAS06, HSUPA must be used together with HSDPA. There isa maximum of
24 HSUPA users per WBTS and maximum19 grantedusers per cell. 2xSF4 is
supported with 2xSF2 is available as "HSUPA 2.0Mbps" feature.
Fig. 4 HSDPA Features (yellowindicates new inRAS06)
TM5112EN01GLA00
7-7
NSN Products
Fig. 5 HSDPA Features (yellowindicates new inRAS06)
7-8
TM5112EN01GLA00
NSN Products
2.1.3
Channel Elements
In the WBTS, HSDPA and HSUPA features consume channel capacity resources.
For UltraSite WCDMA BTS, WSPC is required.One WSPC provides 64 channel
elements.
For Flexi WCDMABTS, the System Module handles the baseband processing
including HSPA.System Module FSMB provides up to 240 channel elements. It
may be expanded by the Extension Module for the total of 480 CE.
The following factor must be taken into account for CE requirement:
Common Control Channels
Rel. 99 service: number of users for each service
HSDPA: number of codes, type of scheduler, number of users, and UL data
rate
HSUPA: number of users
Fig. 6 WBTS Channel Capacity
TM5112EN01GLA00
7-9
NSN Products
Fig. 7 Channel Element requirements
7-10
TM5112EN01GLA00
NSN Products
2.1.3.1
WBTS Dimensioning Examples
Below are examples of CE usage for Ultrasite and Flexi WBTS respectively. 48
users per cell are assumed with HSDPA and HSUPA support.
Fig. 8 Ultrasite WBTS dimensioning example (48 users/cell HSDPA+HSUPA)
TM5112EN01GLA00
7-11
NSN Products
Fig. 9 FlexiWBTS dimensioning example (48 users/cell HSDPA+HSUPA)
7-12
TM5112EN01GLA00
NSN Products
2.1.4
HSPA and Iub Interface
The feature Path Selectionallows defining dedicated VCCs for selected types of
traffic. This feature makes it possible to separate, for example, RT-DCH,
NRT-DCH and HSPA traffic to dedicated paths. The paths can have different
service categories and traffic parameters according to the required QoS targets.
OPEX and CAPEX savings are gained in RAN transport NW. This feature makes
it possible to direct different traffic types to separate transmission paths and use
cost-optimized transport media and service categories according to the specific
QoS requirements.
Path selection divides the traffic into 4 path types. The Stringentpath definition
is designed to be used for RT-DCH VCCs, Bi-Levelfor NRT-DCH VCCs and
Tolerantfor HSDPA and HSUPA VCCs
For each path a dedicated VCC can be configured. Alternative configurations
could use 2 or 3 VCCs
4 VCC configuration - dedicated VCCs for HSDPA traffic, HSUPA traffic,

NRT-DCH traffic and RT-DCH traffic
3 VCC configuration - dedicated VCCs for HSPA traffic, NRT-DCH traffic and
RT-DCH traffic
3 VCC configuration - dedicated VCCs for HSDPA traffic, HSUPA traffic and
DCH traffic
2 VCC configuration - a dedicated VCC for HSPA traffic, and a dedicated
VCC for DCH traffic
2 VCC configuration without HSPA - a dedicated VCC for RT-DCH traffic and
a VCC for NRT-DCH traffic
TM5112EN01GLA00
7-13
NSN Products
The following transport features may provide further benefits when used together
with Path Selection:
UBR+ for Iub User Plane for the statistical multiplexing gains.
Transport Bearer Tuning for configurable activity factor for DCHs.
Dynamic Scheduling for HSDPA with Path Selection for reduced packet loss
and delay on the Iub.
Dynamic Scheduling for NRT-DCH with Path Selection for reduced packet
loss and delay on the Iub.
Hybrid BTS Backhaul for using Ethernet for the tolerant path.
7-14
TM5112EN01GLA00
Fig. 10 Path Selection feature
NSN Products
nazilute.en.lmm/mekebadu.en.slo
TM5112EN01GLA00
7-15
NSN Products
HSPA Feature Activation in

RAS
3.1
Feature Activation on RAS
The procedure to activate features on RAS can vary from version to version. The
information provided here is for RAS06. It is given as example for the work
involved if HSPA is to be implemented in the network.
3.1.1
Licence Based Feature Management
Some features are parameter based, activating such features only require
modification to the radio network parameter of RNC. Several features need
licences in order to activate. Licences are either capacitylicence or on/off
licence.
Capacity licence defines the allowed capacity that the feature can use or
provide. It permits incrementing or decrementing capacity in steps.
Licences can be time limited, i.e., they have a predefined expiry date stated in
the licence file. Continuation licences for both types can be ordered and should
be installed before the existing licence expires.
3.1.2
Working with Licence
A LICENCEsubdirectory needs to exist in the rootdirectory of the RNC

harddisk. It is transferred to this directory by ftp in binary mode. It is managed by
MML command group ZW7 . The LICENCE subdirectory is automatically emptied
after licence installation.
The feature states can be defined in the command:
OFF means that the feature is inactive.
ON means that the feature is active.
CONFIGmeans that the feature is active but not yet used. Feature
configuration is permitted.Certain features require to first be installed in
CONFIG state
7-16
TM5112EN01GLA00
On/off licence allows the feature to run without capacity limitations.
NSN Products
Fig. 11 RAS HSPA Sales Item in RAS06(Part 1)

Fig. 12 RAS HSPA Sales Item in RAS06(Part 2)
TM5112EN01GLA00
7-17
NSN Products
3.1.3
Activating HSDPA
After related HSDPA RAS features are activated, DMPG resource pool inside
DMCU of RNC must be configured for HSDPA. Two pools are defined: DCH
DMPG for Release 99 traffic and HS DMPG for HSDPA. The command group
used is ZWP . The current setting can be interrogated via ZWPI and modified via
ZWPM.
Restarting DMPG for the changes to be effective. Alternately DMPG state may be
changed to blocked, test and then back to working.
Fig. 13 Example of DMPG pool configuration
7-18
TM5112EN01GLA00
NSN Products
Support of HSDPA traffic in the network can be activated using the following
parameters:
HSDPAenabled
HSDSCHQoSclasses
Set HSDPAenabled to 1 (Enabled) when all relevant parameters in the cell
belowhas beenset.
Fig. 14 HSDPA activation parameters
TM5112EN01GLA00
7-19
NSN Products
Additionally, FMC (Frequence Measurement Control) and HOP (Handover Path)

used for HSDPA traffic must bespecified inthe parameters in WCEL object:
HSDPAFmcsIdentifier (intrafrequency handover)
HSDPAFmciIdentifier(interfrequency handover)
HSDPAFmcgIdentifier (intersystem handover)
RTWithHSDPAFmcsIdentifier (HSDPA with AMR intrafrequency handover)
RTWithHSDPAFmciIdentifier (HSDPA with AMR interfrequency handover)
RTWithHSDPAFmcgIdentifier (HSDPA with AMR intersystem handover)
and the following parameters in ADJSobject:
HSDPAHopsIdentifier(intrafrequency handover)
RTWithHSDPAHopsIdentifier(HSDPA with AMR intrafrequency handover)
Theparameters related toRadio Resource Management (RRM) must be set:
PtxTargetHSDPA(Target for transmitted non-HSDPA power)
PtxMaxHSDPA(Maximum allowed HSDPA power)
DirectedRRCEnabled(Directed RRC connection setup enabled)
Fig. 15 Frequency Measurement Control settings in WCEL Handover Control tab
7-20
TM5112EN01GLA00
PtxOffsetHSDPA(Offset for transmitted non-HSDPA power)
NSN Products
Fig. 16 Handover Path settings in ADJS

TM5112EN01GLA00
7-21
NSN Products
3.1.4
Activating HSUPA
HSUPA can beused for interactive and background traffic classes in RAS06 and
can be activated using the parameters:
HSUPAEnabled
EDCHQOSClasses
HSUPA can only be used in combination with HSDPA and so the corresponding
HSDPA parameters should be checked: HSDPAenabled, HSDSCHQoSclasses.
Furthermore, the parameter HSPAFmcsIdentifierand
RTWithHSPAFmcsIdentifier in the WCEL should be specified to Frequency
Measurement Control (FMC) object intended for HSDPA+HSUPA users.
Once HSUPA has been enabled, the RNC configures
E-AGCH (E-DCH Absolute Grant Channel)
E-RGCH (E-DCH Relative Grant Channel)
E-HICH (E-DCH HARQ Acknowledgement Indicator Channel)
RNC allocates spreading codes and transmit power for each of these channels.
The Node B reserves the minimum hardware channel requirement.
Fig. 17 HSUPA activation parameters
7-22
TM5112EN01GLA00
NSN Products
nazilute.en.lmm/bumavino.en.slo
TM5112EN01GLA00
7-23
NSN Products
HSPA Implementation on
UMR
4.1
HSPA Implementation on UMR
This section describe HSPA implementation on Nokia Siemens Networks eRNC

196 or RNCplus based systems.
4.1.1
RNC Hardware
To support HSDPA, HSDST and HSPRLC cards must be equipped in the RNC.
Furthermore, upgraded CHC96 cards are required in the Node B.
To supportHSUPA, HDHT cards must be equipped at the RNC. No additional

changes to the NodeB is required.
Fig. 18 D-LSF example for eCS (STM-1) model unit
7-24
TM5112EN01GLA00
NSN Products
Fig. 19 H-TRKF example for eCS (STM-1) model unit

TM5112EN01GLA00
7-25
NSN Products
4.1.1.1
HSDST
The HSDST card provides the functions listed below:

U-Plane protocol handling with regard to:
MAC-d
HS-DSCH Frame Protocol
Internal Frame Protocol
Traffic monitoring:
Monitoring the number of transmitting MAC-d PDUs.
The HSDST card is inserted in the C-LSM module and works in single mode.
Each HSDSToffersthroughputcapacity of 160Mbit/s. The RNC is always
equipped with 2 HSDST cards supporting redundant load-sharing configuration.
Fig. 20 HSDST creation
7-26
TM5112EN01GLA00
NSN Products
4.1.1.2
HSPRLC
TheHSPRLC card, located in B-PRM module, handles the following

functionalities:
Handles the IP/UDP/GTP-U protocol (the Iu side), and RLC/PDCP and
internal Frame Protocol (Iub side).
Handles both HSDPA and Rel. 99 traffic.
Performs QoS control
Each HSPRLC occupies two slots in B-PRM. Thus one B-PRM can
accommodate 4 HSPRLC cards. A HSPRLC card has throughput of 20Mbit/s of
packet switched traffic. A mix of HSPRLC and older PRLC, occupying one slot
with throughput 3Mbit/s, is possible in the same RNC.
Fig. 21 HSPRLC creation
TM5112EN01GLA00
7-27
NSN Products
4.1.1.3
HDHT
The is no hardware difference between the new HDHT card and the existing DHT
card in DHTM module. HSUPA traffic is supported by changing some DHT
boards to HDHT boards via firmware download.
The HDHT handles the functions of E-DCH Frame Protocol and MAC-d/MAC-es.
HDHT is used when Rel. 6 capable UE initiates a PS call. Each HDHT board
adds 6Mbit/s Rel. 6 throughput and requires at least one HSPRLC for maximum
HSUPA traffic. However, converting a DHT to HDHT costs 150 Erlang of Rel. 99
traffic capacity.
7-28
TM5112EN01GLA00
NSN Products
4.1.2
Node B Hardware
Node B requires HSPA-capable Channel Card. Existing CHC96 can be

upgradedwithnewfirmware to support HSDPA and HSUPA. The firmware is
included in any HSPA capable load. Each CHC96 provides 96 Channel
Elements (CE) and 144 AMR equivalent (AMReq)of throughput. Older CHC48
which provides 48 CE and 72 AMReq does not support HSPA.
In UMR6.5, the maximum of 3 HSPA capablefrequencies per Node Bare
possible. Each of these cells can be a combined HSDPA andHSUPA cell or an
HSDPA only cell. All HSDPA traffic belonging to a cell must not besplitted
todifferentCHC cards. One CHC can handle 1 HSPA-capable cells in single-cell
modeor up to3HSPA-capable cells in multi-cell mode.
One CHC can process up to 15 HS-PDSCH channelization codes for 16-QAM or
30 codes for QPSK. The next figure givesa summary of number of codeswhen
there isone HSPA carrierwith variable number of cells and HSPA-capable CHC
cards, assumed that all cells have the same number of HS-PDSCH codes.
Fig. 22 HSDPA codes possible, assumed equal number in all cells
The CHCcan be operated in single or multi-cell mode for HSUPA cells serving
up to 32 (1 radio cell) or up to 20 (3 radio cells) E-DCH users per CHC.
TM5112EN01GLA00
7-29
NSN Products
To findthe maximum number of HSDPA users, the number of CE and AMR

equivalent in are relevant. The number of CE and AMReq consumed by
aHSDPA user depends only on theuplink DCH. One HSDPA user with
64kbit/suplink consumes 1 CE and 4 AMReq.One HSDPA user with 128kbit/s
UL consumes 1 CE and8 AMReq.And one HSDPA user with 384kbit/s UL
consumes 1 CE and16 AMReq. Uplink 32kbit/sdata rateis also possible with
"HSDPA RAB Handling Enhancement" feature in UMR6.0. Based on this
information, the maximum number of possible HSDPA UE can be found as in the
next Table.
Fig. 23 Number of HSDPA users per cell
7-30
TM5112EN01GLA00
NSN Products
For HSUPA, each user is allocated 2 CE. Different types of user have to be
distinguished for AMReq usage:
Non-grant user : Users who are located in the HSUPA cell but have recently
not received grants from HSUPA Scheduler are called "non-grant users".
These users are allowed to transmit o the E-DCH at minimum rate only,
thusrequiring only 2 AMReq.
Grant user : This term defines an HSUPA user who is located in the HSUPA
cell and has received a grant from the HSUPA Scheduler. "Grant users"
therefore transmit on the E-DPDCH with the allowed power and resulting
minimum spreading factor (SF). In addition, "grant users" transmit on the
DPCCH, E-DPCCH, HS-DPCCH and DPDCH.
Fig. 24 Consumed CHC UL resource per user
TM5112EN01GLA00
7-31
NSN Products
4.1.3
HSPA and Iub Interface
The introduction of HSUPA causes drastic increase in UL traffic in Iub interface.

To prevent degradation of services and cell loss of inband control messages, the
separation of Rel 99 traffic and HSPA traffic, as well as further separation of
HSDPA and HSUPA is strongly recommended. UMR6.0 allows traffic to be
separated in VP level while UMR6.5 allows traffic to be separated in VC.
Trafficseparationfeature also allows UBR/UBR+ connections to intermediate
transport network for the transport of HSPA traffic rather than relying on CBR for
those traffic.
An example of Iub configurationwith VC separation is shown (Fig. 26) . ATM

traffic for HSDPA and HSUPA are configured as UBR+ to guarantee the
throughput of the inband signaling. Thus excessive HSDPA traffic will not cause
degradation of HSUPA due to HSUPA acknowledgement in DL being dropped or
vice versa. Rel 99 still relies on CBR as required by speech and video calls.
Other Iub configurations are possible.
Fig. 25 Feature evolution
7-32
TM5112EN01GLA00
NSN Products
Fig. 26 Iub VP/VC configuration example

TM5112EN01GLA00
7-33
NSN Products
HSPA Feature Activation in

UMR
5.1
Feature Activation on UMR
Features in eRNC or RNCplus must beenabled by Nokia Siemens Networks

service personnel. It isnot visible to the enduser. Aftera feature is enabled,
operator may activate it via appropriate parameters in RNC database. Thedetail
offeature activationonUMR can vary from version to version. The information for
UMR6.5 is given as example here to show the work involved if HSPA is to be
implemented in the network.
5.1.1
License Management in Node B
Many aspects of Node Bare based on capacity licenses according to "pay as you
grow" scheme. These includes:
number of cellsfor DRIC.

maximum transmit powerfor ngCAT.
HSDPA throughput of Node B.
Licenses are managed as license pool in Radio Commander and loaded into
Node B as needed. Licenses may be installed in the card right from the factory.
5.1.2
HSDPA License
The HSDPA data throughput license specifies the peak data rate of HSDPA
traffic allowed for a particular Node B. If the requested peak data exceeds the
licensed value, Node B rejects the activation of HSDPA cells with an error "Not
enough user plane processing resources". Data throughput licenses are stored in
the Core Controller (CC) and require a Node B restart to activate.
1 license equals peak data throughput of 2.4Mbit/s. In UMR6.5, there is no
restrictions for HSPA cell configurations. Eachcell in the Node B can be set
independently to HSPA mode, regardless of the Node B type.The HSDPA
throughput licenses are distributed to all HSDPA capable cells in the Node B.A
maximum of six HSDPA data throughput licenses can be applied to a particular
cell, thus allowing a maximum capacity of 14.4 Mbit/s per cell. Stated in the other
way, operating HSDPA with 5 codes and 16QAM modulation will consume 2
HSDPA data throughput licenses.For HSDPA operation with5 codes and QPSK
modulation, 1 license willbe utilized.
7-34
TM5112EN01GLA00
nazilute.en.lmm/lenonaki.en.slo
number of channel elements.
NSN Products
HSDPA can be managed centrally by Licensing Application from Radio

Commander.
Fig. 27 Starting the Licensing Application
TM5112EN01GLA00
7-35
NSN Products
Fig. 28 Increasing HSDPA throughput
7-36
TM5112EN01GLA00
NSN Products
5.1.3
HSUPA License
HSUPA capacity license is stored in RNC and can be updated by service

personnel. The license is in terms of number of HSUPA capable cells. Each time
an HSUPA object, representing HSUPA cell, is created or deleted. The internal
counter is updated. The creation of an HSUPA object is rejected if the number of
HSUPA objectshas already reached the license limit.
Fig. 29 Displaying HSUPAlicense usage
TM5112EN01GLA00
7-37
NSN Products
5.1.4
Activating HSDPA
Before any HSDPA specific data can be added, it is necessary to activate this
optional feature. This task can only be done by aNokia Siemens
Networksservice technician.
The introduction of HSDPA requires new parameters to configure the systems
mobility part with respect to the following:
HSDPA RAB Handling
HSDPA Mobility Handling
HSDPA Code and Power Allocation
HSDPA Admission Control
The first two parts are RNC wide object, while the latter two must be configured
cell by cell.
5.1.4.1
HSDPA RAB Handling
For each UE category, one HSDPA Radio Resource Management

(HSRARESMNGMT)object has to be created. This object represents the HSDPA
measurement information:
Fig. 30 Radio Bearer modification
7-38
TM5112EN01GLA00
Appropriate timer for channel type switching between HS-DSCH and FACH must
be set in Radio Access Bearer Control (RABC) object.
NSN Products
Fig. 31 HSDPA Radio Resource Management

TM5112EN01GLA00
7-39
NSN Products
5.1.4.2
HSDPA Mobility Handling
The following 2 parameters of the IntraFrequencyHandoverControl

(INTRAFREQHOC) are relevant for HSDPA. Event 1D (change of best cell) is
used totrigger serving HS-DSCH cell change. Hysterhesis and time-to-trigger
parameters are usedin order to avoid frequent changes of the serving HS-DSCH
cell or channel-type switching between HS-DSCH and DCH.
Fig. 32 Intra Frequency Handover Control
7-40
TM5112EN01GLA00
NSN Products
5.1.4.3
HSDPA Code and Power Allocation
The new parameter HSDLPKTACH High Speed Downlink Packet Access

Channelhas to be added as a Cell Subobject to theUTRAN cellobject.
Fig. 33 High Speed Downlink Packet Access Channel for a UTRAN cell
TM5112EN01GLA00
7-41
NSN Products
5.1.4.4
HSDPA Admission Control
HSDPA admission control requires thetreatment ofnew HSDPA related issues:

Restriction Control for PS Bearers . It is configured in Admission Control
(ADMC) object.
Within an HSDPA enabled network, it is expected that PS radio bearers will be
established on HS-PDSCH instead of making use of the DCH.
However, the following situations lead to the preferred choice to set up a PS
bearer on the DCH:
HSDPA is not supported by the UE
The requested multicall/bearer combination is not supported by HSDPA
standards
The Node B is out of resources on the CHC, but a retry on DCH state might
be possible
The rate restriction can be adjusted to apply if there are at least X HSDPA-UEs
within the HSDPA cell. If there are less than X HSDPA-UEs in the HSDPA cell,
the rates/SF will not be restricted by this functionality. This maximizes the
throughput for legacy UEs, especially in case of low HSDPA load.
Fig. 34 HSDPA ADMC parameters
7-42
TM5112EN01GLA00
The number of HSDPA-UEs within the HSDPA-enabled cell are measured.

Admission control restricts the admission of PS interactive/background bearers on
the HS-PDSCH when a specified threshold is reached.
NSN Products
5.1.5
Activating HSUPA
To enable HSUPA, a system wide object EDCHINFand per UTRAN cell

HSULPKTACHmust be created.
5.1.5.1
EDCH Information
The EDCH info settings are used to specify the RNC wide HSUPA parameters. It
is used to set some retransmission values and timers for all cells in general.
For retransmission it can be specified how many MAC-e retransmissions should
be attempted, before an RLC retransmission is necessary. The power offset of
the respective signaling channel as well as the redundancy version of the
retransmission are set here.
The scheduling info timers are important for the Node B to judge the necessity to
increase or decrease resources for individual UEs. Between the scheduling info
transmissions there is only little information update possible relative to current
settings for grant UEs and none for non Grant UEs.
Fig. 35 HSUPA Settings
TM5112EN01GLA00
7-43
NSN Products
5.1.5.2
HS UL Packet Access Channel
Instance number of managed object HSULPKTACH (HS UL Packet Access

Channel). Only one instance of this MOC can be created per UTRAN cell. Here
all cell specific HSUPA setting regarding codes and power offsets can be created
or modified.
Fig. 36 Create HSULPKTACH
7-44
TM5112EN01GLA00
NSN Products
nazilute.en.lmm/qadaxagu.und.slo
TM5112EN01GLA00
7-45
NSN Products
Exercises
Exercise 1
Which hardwares have to be considered for HSDPA and HSUPA support in RNC
and WBTS in RAS?
7-46
TM5112EN01GLA00
NSN Products
Exercise 2
andNode Bin UMR?
TM5112EN01GLA00
7-47
NSN Products
6.1
Solutions
and WBTS in RAS?
RNC: DMPG inside DMCU.

WBTS: WSPC for Ultrasiteor FSMA/FSMBfor Flexi.
7-48
TM5112EN01GLA00
NSN Products
andNode Bin UMR?
RNC: HSDST, HSPRLC, HDHT.
Node B: CHC96 or hsCHC.
TM5112EN01GLA00
7-49

HSPA Fundamentals For Technicals

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

HSPA Fundamentals For Technicals

Uploaded by

Copyright:

Available Formats

HSPA Fundamental

2008 Nokia Siemens Networks GmbH

HSPA System Overview in UMTS

HSDPA and HSUPA Features

This workbook consists

HSDPA and HSUPA Physical Channel

HSPA Mobility Management and

HSPA Throughput and Congestion

HSPA System Overview in UMTS Network

HSPA System Overview in

UMTS Release 99 Environment............................................................... 6

HSPA System Overview in UMTS Network

HSPA System Overview in UMTS Network

HSPA System Overview in UMTS Network

HSPA or HSxPA(High Speed Packet Access) is a generic term to refer to

HSPA System Overview in UMTS Network

Fig. 1 UMTS releases and added features

HSPA System Overview in UMTS Network

UMTS Network - Network components

HSPA System Overview in UMTS Network

Fig. 2 UMTS network components and interfaces

HSPA System Overview in UMTS Network

UMTS - The Air Interface

Fig. 3 Multiplex Methods

HSPA System Overview in UMTS Network

HSPA System Overview in UMTS Network

Fig. 5 WCDMA: Transmission / Reception

HSPA System Overview in UMTS Network

Fig. 6 OVSF Code Tree

HSPA System Overview in UMTS Network

Every user gets a unique channelization code assigned depending on the

Fig. 7 Channelization and Scrambling Codes

HSPA System Overview in UMTS Network

In addition to spreading, part of the process in the transmitter is the scrambling

Fig. 8 Usage of Channelization and Scrambling Code

HSPA System Overview in UMTS Network

Fig. 9 Scrambling Codes for FDD in the uplink direction

As it is not possible to retain exact synchronization in the uplink direction,

In the uplink direction another feature of scrambling code is used to address a

HSPA System Overview in UMTS Network

Usage of OVSF code tree

Fig. 10 Utilization of OVSF code tree in the downlink direction

HSPA System Overview in UMTS Network

In FDD, the air interface timing structure is as follows:a timeslotis defined as

A frameis defined by the duration of 10 ms andtherefore contains 15 timeslots.

Fig. 11 Timing structure and usage in FDD mode

HSPA System Overview in UMTS Network

HSPA System Overview in UMTS Network

Technologically HSDPA is an upgrade to UMTS. Therefore HSDPA is already

increased data rate

HSPA System Overview in UMTS Network

Higher Data Rate

TCP Transmission Control Protocol

HSPA System Overview in UMTS Network

TCP Slow Start and Congestion Avoidance

The transmission performance in the beginning of a data transmission and after a

HSPA System Overview in UMTS Network

Fig. 12 TCP Slow start and congestion avoidance

HSPA System Overview in UMTS Network

In mobile networks the air interface is characterized by fast-changing conditions,

With HSDPA, thanks to HARQ (Hybrid Automatic Repeat Request) in the

Fig. 13 Retransmission cycle in Rel99 and HSDPA

HSPA System Overview in UMTS Network