Wcdma

9300 W-CDMA UA06 HSxPA Radio Principles
TMO18043 Issue 1
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2009
All rights reserved Alcatel-Lucent 2009 Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent 2009 UA06 HSxPA Radio Principles - Page 1
Empty page
Switch to notes view!
2
This page is left blank intentionally
Terms of Use and Legal Notices

1. Safety Warning Switch to notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the equipment alone. The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent. All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark. Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent. Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly prohibited. User obtains no rights in the information or in any product, process, technology or trademark which it includes or describes, and is expressly prohibited from modifying the information or creating derivative works without the express written All Rights Reserved Alcatel-Lucent 2009 3 consent of Alcatel-Lucent.
All rights reserved Alcatel-Lucent 2009
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages. Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an endorsement, nor a recommendation. This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely accurate. Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment and its operation, or contact your nearest Alcatel-Lucent representative for more information. The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties, including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of dealing, usage or trade practice. Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including, but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these Terms of Use and Legal Notices shall remain in full force and effect.
Blank Page
4
Course Outline
1. This Description AboutHSDPACourse
Course outline 1. HSDPA Introduction Technical support Key Concepts 2. HSDPA Course objectives
4. Topic/Section is Positioned Here 5. Topic/Section is Positioned Here 6. Topic/Section is Positioned Here
3. HSDPA Channels
4. H-ARQ for Fast Retransmission 1. Topic/Section is Positioned Here

Xxx Xxx Xxx
5. HSDPA Scheduling Mechanism
6. Adaptative Modulation and Coding 7. Topic/Section is Positioned Here with 16-QAM 7. HSDPA protocols 8. HSDPA Scenarios 9. HSDPA A-L implementation 1. HSUPA Fundamentals 2. HSUPA Channels 3. HSUPA Scheduling 4. HSUPA HARQ 5. HSUPA Protocols 6. HSUPA Scenarios 7. HSUPA A-L implementation
2. Topic/Section is Positioned Here

2. HSUPA Description 3. Topic/Section is Positioned Here
5
Course Outline [cont.]

6
Course Objectives
Welcome to UA06 HSxPA Radio Principles
Upon completion of this course, you should be able to: describe the evolution of 3G system with HSDPA / HSUPA describe UTRAN functions and state protocols related to HSUPA/HSDPA
7
Course Objectives [cont.]

8
About this Student Guide

Conventions used in Switch to notes view! this guide
Note
Provides you with additional information about the topic being discussed. Although this information is not required knowledge, you might find it useful or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment damage or personal injury.
Where you can get further information

If you want further information you can refer to the following: Technical Practices for the specific product Technical support page on the Alcatel website: http://www.alcatel-lucent.com
About this Student Guide [cont.]

10
Self-assessment of Objectives
Contract number : Course title :
Client (Company, Center) : Language : Switch Number of trainees : Surname, First name :
At the end of each section you will be asked to fill this questionnaire Please, return this sheet to the trainer at the end of the training to notes view!
Dates from : Location : to :
Did you meet the following objectives ? Tick the corresponding box Please, return this sheet to the trainer at the end of the training
Yes (or globally yes) No (or globally no)
Instructional objectives 1 To be able to XXX
Comments
2
11
9300 W-CDMA UA06 HSxPA Radio Principles All Rights Reserved Alcatel-Lucent 2009
Self-assessment of Objectives [cont.]

Instructional objectives Yes (or Globally yes) No (or globally no) Comments
12
Other comments
Thank you for your answers to this questionnaire
Do not delete this graphic elements in here:
Section 1 HSDPA Description

Module 1 HSDPA Introduction
9300 W-CDMA UA06 HSxPA Radio Principles TMO18043 Edition 1
All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 1
1 Objectives
This section will enable you to Describe HSDPA introduction technological context List HSDPA main concepts and benefits List HSDPA target applications and services Compare HSDPA approach with existing technologies Describe HSDPA future evolutions
What is HSDPA?
HSDPA Key Points Radio Resource Allocation User Throughput Management HSDPA Main Concepts & Benefits Theoretical Peak User Data Rates HSDPA Market Applications HSDPA Solution Key Values
HSDPA Solution Main Facts
1 2
HSDPA Description 9300 W-CDMA UA06 HSxPA Radio Principles
1.1 What is HSDPA?
1 3
1.1 What is HSDPA?
1.1 HSDPA Key Points
Radio Access Technology
Downlink Only
High Throughputs
Low Latency
Shared Channels
PS Dedicated
1 4
HSDPA (High Speed Downlink Packet Access) is a UMTS packet air interface (add-on solution on top of 3GPP R4 architecture) that allows higher downlink peak data rates than UMTS. In addition, HSDPA provides lower latency with reduced Round Trip Delays enabling great interactive applications like multi-user gaming. HSDPA introduces a new common high speed downlink channel shared by several users. It also introduces enablers for the high speed transmission at the physical layer (see next slide). The various system evolutions triggered by HSDPA implementation are restricted to the access network and there is no modification to the core network and traffic classes.
1.1 What is HSDPA?
1.2 What HSDPA has been designed for?

HSDPA standardized by 3GPP R5 to:
increase the Downlink data throughput manage Non-Real Time applications (interactive and background class) provide instantaneous high data rates in the PS domain (e.g. Internet browsing, video on demand) HSDPA could be deployed in both Frequency Division Duplex (FDD) and Time Division Duplex (TDD) modes (both high and low chip rates)
DL
UL
In the following material we will only refer to HSDPA in FDD mode

1 5
HSDPA Description 9300 W-CDMA UA06 HSxPA Radio Principles All Rights Reserved Alcatel-Lucent 2009
HSDPA is based on techniques such as Adaptive Modulation and Hybrid ARQ to achieve high data throughput, high peak rates and reduce delay. It relies on a new type of transport channel, the HS-DSCH, which is terminated in the Node B. HS-DSCH is applicable only on PS domain RABs. [refer to 3GPP TS 25.308] It can significantly increase user data rates but only for best effort services such as Internet access or file download. In a first step, HSDPA is not intended as a solution for real-time services that require guaranteed QoS and also places heavy demands on terminals initial deployments are expected to be confined to 3G data cards on laptops.
1.1 What is HSDPA?
1.3 A new shared channel: HS-DSCH

with DCH with HS-DSCH
A shared channel is much more efficient than a dedicated channel to carry bursty packet traffic
1 6
Why is a shared channel more efficient to carry packet bursty traffic than a dedicated channel? With a bursty traffic, the demand for high data rate is sporadic. Indeed once the UE will demand for a high data rate to download a file for example, and between 2 such a demands, it wont need it anymore. So with the use of a dedicated channel, the channel with its resources are dedicated to this UE. Consequently between 2 demands like web browsing, the resources are lost. On the contrary, a shared channel is able to allocate most of its resources to one UE when it asks for, and the rest of the time, shares those resources with other UE in order to maximize the use of the channel. To summarize: dedicated channels are more adapted to symmetrical and constant traffic because they are able to ensure a certain level of Quality of Service (QoS), they are NOT efficient at all for PS nonreal time traffic. HSDPA is then based on the use of a shared channel: the High Speed Downlink Shared Channel (HS-DSCH). The High Speed Downlink Shared Channel is a downlink transport channel shared by several UE. In the Evolium solution the HS-DSCH is associated with a Dedicated Channel DCH for the RRC and NAS signalling.To know more about those channels refer to the section HSDPA Channel in the chapter key concepts for HSDPA. The HS-DSCH is transmitted over the entire cell or over only part of the cell using beam-forming antennas (i.e. smart antennas). [refer to 3GPP TS 25.211] Note: No Soft Handover/ No fast Closed Loop Power Control as the link adaptation is now performed by the adaptation of the Modulation with the Coding Rate. What are the disadvantages of a shared channel? Not adapted to real-time application (such as a voice call, video games) as it is should be much more complex to ensure a certain QoS
1.2 HSDPA Solution Main Facts
1 7
2.1 Theoretical Peak User Data Rates
14.4M
2M 0.31 M 0.38 M
2.4M
3.1M
3.6M
1 8
HSDPA provides impressive enhancements over W-CDMA R4 for the downlink. It offers peak data rates of up to 10 Mbps, resulting in a better end-user experience for downlink data applications. The HSDPA-capable UE are classified in categories depending on their receiving capabilities (processing, modulation, number of codes,...). A single user can receive up to 15 multi-codes resulting in a potential peak data rate of 10.8 Mbps. However, the maximum specified peak data rate with HSDPA is 14.4 Mbps (Layer1 throughput) when higher order modulation is used with no coding (effective code rate of one) and with 15 multi-codes. Achieving this rate in a real system remains very unlikely as it would require an unloaded system serving a single user extremely close to the NodeB. Nevertheless, the ability to offer higher peak rates for an increasingly performance-demanding end user at a substantially lower cost will create a significant competitive advantage for HSDPA operators. Supporting rich multimedia applications and content and more compelling devices at lower user costs will enable early adopters to differentiate themselves with advanced services, resulting in higher traffic per user and increased subscriber growth
UE Category 10
UE Category 6
1xRTT
W-CDMA
1xEV-DO
1xEV-DV
EGPRS
HSDPA
HSDPA
2.2 HSDPA Market Applications

Business Market Consumer Market
Virtual Office Corporate VPN Remote Applications / Tools Web Browsing Massive Downloads ...
Multiplayer Gaming Video Streaming & TV Advertising / News Broadcast Music & Video Downloads Web Surfing ...
Working Anywhere!
1 9
Having Fun!
HSDPA will change wireless communications by delivering broadband in wireless access. This is the next big technological advancement needed to increase usage. It will boost usage in business sectors by providing a virtual office environment anywhere and it will also trigger usage by the consumer market by leveraging the end-user experience of fixed broadband. The first trend will be for the business market by extending Wireless LAN applications to everywhere providing a virtual office to sales force, and all nomadic jobs. Indeed, HSDPA allows for broadband to be truly ubiquitous for the very first time without the inconvenience of looking for hotspots or wireless access points. One of the most dramatic changes the telecom sector has faced in recent years has been the diminishing time lag between the corporate sector and the consumer market in their uptake for new technology. As far as the consumer market is concerned, HSDPA will blend the boundary between their fixed broadband access and their mobile services: HSDPA will provide the seamless access to all applications already used at home for entertainment like music and video downloads, multiplayer gaming, and TV. HSDPA has a great opportunity to enter the triple play market by addressing residential access with a bundle offer for TV, Internet Access, and Voice and Mobile services.
2.3 Typical Data Rates
Peak user bit rate with first handsets 1.8 Mbps for Line of Sight (LoS)
(Categories 11&12: QPSK only, 5 codes max.)
Example of user bit rate performance with different mobility scenarios with the best UE categories.
10.8 Mbps for LoS
7 Mbps Pedestrian at 3km/h
3 Mbps at 30km/h
1 10
2.4 Factors of HSDPA Performances
User Equipment Capabilities
Infrastructure Performances
HSDPA Throughput
Radio Conditions Traffic Load in the cell
1 11
The theoretical 14.4 Mbps of cell Throughput shared among users can be achieved only under several criteria: The UE must be capable to support highest modulation and coding schemes. The UE must experience very good channel conditions (e.g. very high SINR) The load of the cell should allow the Node-B to provide all resources to HSDPA users. The radio Resource Management or the type of scheduling algorithm of the infrastructures can also impact the performances for a sake of fairness or of priority among users.
2.5 HSDPA Solution Key Values
Software Upgrade Only

PA H S D DY REA
45W/60W MCPA Ready for HSDPA Applications
Strong partnership with leading device manufacturers Major contribution to 3GPP HSDPA working group
1 12
A key attribute of Nortel W-CDMA infrastructure is its flexibility for future upgrades. New features, some of which were in the earliest stages of standardization at the time of the system specification, have been taken into account in the Radio Access Network architecture and system design. This proactive approach enables Nortel to implement HSDPA with simple upgrades to its current RAN platforms. Being able to integrate HSDPA and R4 traffic into the same carrier is essential. With the Nortel solution this is achieved without changing the base station RF elements. Nortel high power MCPA is already sized for indoor and outdoor HSDPA high demanding power applications. Consequently HSDPA can boost user and system performance using the initial 5 MHz frequency layer. This does not prevent from choosing to allocate HSDPA services on a dedicated carrier, this option being also completely supported by the current Nortel base station RF elements. The Nortel HSDPA Solution is also fully backwards compatible with 3GPP R4, allowing HSDPA to be introduced into networks gradually. Both R4 and HSDPA capable terminals can share the same radio carriers.
1.3 HSDPA deployment and evolution
1 13
3.1 Deployment and evolution of HSDPA

HSDPA should cover Dense Urban and Indoor environments
Global Satellite
Suburban
Urban
Indoor
MSS
EDGE
UTRA/FDD
HSDPA
1 14
HSDPA is particularly efficient in Line of Sight environment such as Micro-cells. In those environments, HSDPA have more possibilities to use high combination with 16-QAM which results in very high throughput.
* source: DoCoMo Engineering
Indoor Users 70%
Outdoor Users 30%
Studies show that Broadband Mobile users are generally connecting inside buildings as shown on the figure above. Then we can expect an efficient usage of HSDPA for those users.
Indoor coverage + HSDPA = a Winning combination
3.2 Configurations of Deployment inside UMTS
Dedicated Configuration
HSDPA on dedicated carrier
R99 only cell HSDPA cell R99/HSDPA cell
HSDPA on shared carrier
Mixed Configuration
HSDPA on two carriers
1 15
Support of HSDPA on dedicated cells Several carrier configurations exist for the support of HSDPA. Operators are given the possibility to dedicate cells to HSDPA. This will for example lead to the configuration illustrated in the following figure, with 2 cells per sector, one supporting DCH traffic and the other supporting HSDPA traffic. The carrier dedicated to HSDPA will support: In Downlink, the HS-DSCH channels as well as the associated DCH and the common channels In Uplink, the DCH and signalling HS-DPCCH channels Operators can thus benefit from an early HSDPA deployment configuration offering: Full HSDPA capacity (full carrier power and set of codes) and high throughputs, in order to have appealing services for the capture of new subscribers A secured transition to HSDPA with a stepwise approach, limiting the impact of this new technology introduction on the existing DCH services and QoS. This corresponds to the Alcatel recommended configuration for the launch of HSDPA services. It is also very well suited for Laptop applications (data cards). Support of mixed DCH bearers and HSDPA bearers in the same cell Another HSDPA carrier configuration available with EVOLIUM Release R5 provides the ability to mix DCH and HSDPA traffic in the same cell. In this case, DCH and HSDPA traffic will share the cells resources in terms of power and codes. Alcatel recommends going for this configuration as soon as the optimization of HSDPA has been performed successfully on the dedicated carrier, not to harm the current QoS of DCH services. Then, this mixed configuration will enable operators to take full benefit of HSDPA handsets capable of multicall support. Indeed, the mixed carrier configuration offers the ability to have a voice call on DCH simultaneously with a Packet call on HSDPA. There is a third configuration with 2 layers: one freq. dedicated to DCH/another one mixed: HSDPA and DCH, that also enables multi-calls.
3.3 Evolutions of HSDPA
3G Long Term Evolutions ( 3GPP R7 / R8) - OFDM: Up to 100 Mbps - MIMO
HSDPA (3GPP R5) - Up to 14.4 Mbps (DL)
HSDPA Enhancements (3GPP R6) - HSUPA (E-DCH): Up to 2 Mbps (UL) - Smart Antennas: Up to 20 Mbps (DL) - Higher Cell capacity - Enhanced QoS
2005
1 16
2006
2007
Beyond
HSDPA (3GPP R5): (Frozen in June 2002) HS-DSCH AMC (QPSK/16-QAM) H-ARQ MAC-hs
HSDPA (3GPP R7/R8): New multiplexing technique : Orthogonal Frequency Division Multiplexing (OFDM) Higher frequency bandwidth Higher carrier frequency Extended modulation technique: 64-QAM Spatial Multiplexing using Multiple Input Multiple Output (MIMO) systems
HSDPA (3GPP R6): (Frozen in March 2005) CQI enhancement for FDD mode Fractional dedicated physical channel . HSUPA (with Enhanced-DCH in UL) Smart antennas Some key aspects of the E-DCH are: Dedicated channel operating in the cell_DCH state Fast node B based scheduling Capable of operating with/without HSDPA in DL Significant latency reduction enhancement due to fast Node B scheduling, fast HARQ and shorter TTI.
refer to [3GPP TR 25.899] for more information about those improvement
1 Self-Assessment on the Objectives

Please be reminded to fill in the form Self-Assessment on the Objectives for this module The form can be found in the first part of this course documentation
1 17

Module 2 HSDPA Key Concepts
2 Objectives
After this section, you will be able to List HSDPA key features
HSDPA Key Features
HSDPA Technical Overview
HSDPA Main Concepts & Benefits Radio Resource Allocation User Throughput Management Code and Time Multiplexing Scheduling Principle Adaptive Modulation and Coding Fast Retransmission Combining: Hybrid-ARQ NodeB Role
1 19
2.1 HSDPA Key Features
1 20
1.1 HSDPA Main Concepts & Benefits

HSDPA
No Fast Power Control (100% of available power used) No Variable Spreading (SF = 16) No Soft Handover (for DL user data channel) Time & Code Multiplexing of User Data (Shared Channel) Adaptive Modulation & Coding (Rate Adaptation) Fast Retransmission / Scheduling Layer in NodeB Short Radio Framing (2ms) Higher User Data Rates Lower Service Response Time Higher Packet Data Capacity Better Services Availability
- resource allocation - fast retransmission
HSD PA
Better End-User Perceived Quality End1 21

HSDPA introduces a completely new strategy to handle downlink high data rate packet services and two of the most fundamental features of W-CDMA (fast power control and spreading factor variability) are disabled. In addition, the new downlink channel used to carry the PS data does not support Soft Handover. Basically, HSDPA introduces a new common High Speed Downlink Shared Channel (HS-DSCH) shared by several users. In addition, it introduces enablers for the high speed transmission at the physical layer like the use of a shorter TTI (2 ms), the use of Adaptive Modulation and Coding, and the use of fast retransmission based on hybrid ARQ (HARQ) techniques. These key mechanisms are located within the UMTS BTS. HSDPA considerably improves the 3G end-user data experience by enhancing downlink performance. HSDPA significantly reduces the time it takes a mobile user to retrieve broadband content from the network. A reduced delay is important for many applications such as interactive gaming. HSDPA notably allows a more efficient implementation of interactive and background traffic classes as standardized by 3GPP. HSDPA high data rates also improve the use of streaming applications, while lower roundtrip delays will benefit Web browsing applications. In addition, HSDPA improved capacity opens the door for new and data-intensive applications that cannot be fully supported with R4 because of bandwidth limitations.
1.2 Radio Resource Allocation

SR MT 99
Dedicated Channel Dedicated Channel Dedicated Channel
HS
A DP
Shared Channel
1 22
The WCDMA system normally carries user data over dedicated transport channels, or DCHs, which brings maximum system performance with continuous user data. The DCHs are code multiplexed onto one RF carrier. In the future, user applications are likely to involve the transport of large volumes of data that will be bursty in nature and require high bit rates. HSDPA introduces a new transport channel type, High Speed Downlink Shared Channel (HS-DSCH) that makes efficient use of valuable radio frequency resources and takes into account packet data services burstiness. This new transport channel shares multiple access codes, transmission power and use of infrastructure hardware between several users. The radio network resources can be used efficiently to serve a large number of users who are accessing bursty data. To illustrate this, when one user has sent a data packet over the network, another user gets access to the resources and so forth. In other words, several users can be time multiplexed so that during silent periods, the resources are available to other users.
1.3 User Throughput Management

SR MT 99
Same Throughput
Unused
Power Control
Unused Power Data Power
Data
HS
A DP
Rate Adaptation
100% 100% Power
1 23
There is no more fast Power Control with HSDPA and the High Speed Downlink Shared Channel is transmitted at a constant power while the modulation, the coding and the number of codes are changed to adapt to the variations of radio conditions. Where R4 dedicated downlink PS data channels offer a constant data rate using power adaptability, HSDPA shared channel opposes PS data rate variability.
2.2 HSDPA Technical Overview
1 24
2.1 Code and Time Multiplexing

UE 1 UE 2 UE 4
Codes
Code #4 Code #3 Code #2 Code #1
F e S x. l iab Mu r Va ime oT n
2ms
UE 3
UMTS/FDD (R99)
Time
Codes
Code #5 Code #4 Code #3 Code #2 Code #1
1 25
6 =1 s F d S I=2m ux. e Fix d TT e M ixe Cod F e& Tim
HSDPA (R5)
Time
How are UE multiplexed in HSDPA? Time multiplexing between UE Code multiplexing between UE, and one or several codes per UE. What is a radio resource in HSDPA? An HSDPA radio resource is defined for one UE: over a shared channel (HS-DSCH) during a TTI fixed to 2ms by a certain number of Codes (up to 15 channelization codes with a fixed Spreading factor SF=16) by a certain amount of transmitted power
2.2 Scheduling Principle

Quality measurement reports Priorities between UEs Time since last transmission
Different algorithms to perform the resource allocation based on:

Codes
Code #5 Code #4 Code #3 Code #2 Code #1
2ms
Time
HS-DSCH/HS-PDSCHs
RNC
1 26
Node B
What happen if we dont use scheduling? Without Scheduling, if radio resources are equally shared between UE in order not to waste them, it may happen that one UE is allocated some resources when it experiences bad radio conditions. We know that in that case, the data will be corrupted at reception or even lost. It will be required to retransmit the same data once again. Then it results in a loss of resources (as the same resources could have been allocated to other UE in better radio conditions) and in loss of time (as other UE are still waiting for resources and for this one the network will have to retransmit the same radio frame).
2.2 Scheduling Principle [cont.]

The UE are scheduled according to specific criteria such as radio conditions
Fading (Channel variation)
UE1 UE2 UE3
Time
UE 1 2ms
UE 2 2ms
UE 1 2ms
UE 3 2ms
Fast Scheduling: granularity of 2ms (HS-DSCH TTI)

1 27
TTI= Transmission Time Interval How to schedule the UE? Based on Channel Quality Measurements (CQI) performed by the UE and some other parameters (like priorities between users, duration since the last transmission), the scheduler (based in the Node-B) decides which TTI, which data rate with which codes and which power to allocate to each UE. To perform this scheduling at the speed of the channel variation, it has been shown that the channel is sufficiently constant for a bit rate lower than 5ms, which is why 3GPP decided to fix the scheduling resolution (TTI) to 2ms. Why UE 3 is scheduled on the last TTI? It may have not been scheduled since a long time and this scheduler has implemented some fairness in time between users.
2.3 Adaptive Modulation and Coding

Radio Link Quality
Quality Feedback
Ok, for this UE: at the next TTI, I choose the 16-QAM modulation and a coding rate of 3/4
Quadrature Phase Shift Keying 4 states 2 bits per symbol QPSK 16-QAM
16 Quadrature Amplitude Modulation 16 states 4 bits per symbol
The user rate is adapted to the quality of the radio link at each TTI by the selection of a modulation and a coding rate
1 28
R99 versus R5 regarding modulation and coding rate Adapting the coding rate is already performed in R99. In R5, coding rate is adapted much faster, every TTI (=2ms) and 3GPP offers also the possibility to change the modulation to 16-QAM when achieving very good channel conditions.
Link adaptation in R99 different than the one in R5 Traditionally, WCDMA has used fast power control as link adaptation, but HSDPA holds the transmission power constant over the TTI and uses Adaptive Modulation and Coding (AMC) as an alternative link adaptation method to power control and variable SF in order to improve the spectral efficiency. HSDPA provides a higher dynamic Link Adaptation by adapting the data rate and the power depending on the radio conditions faster than with WCDMA in R99. A good Link Adaptation allows to work under good conditions everywhere: at cell edge (with low data rate and/or high power) and at cell center (with high data rates and/or low power).
2.3 Adaptive Modulation and Coding [cont.]
Throughput [Kbps]
2500 2000 1500 1000 500 0
Bad el nn cha itions nd co
16-QAM + coding rate 3/4
QPSK + coding rate 1/2

d Goo nel an ons ch iti d con
Radio link quality (SNR) [dB]
16-QAM : Highest Throughput in good channel conditions QPSK : Robustness in case of bad radio conditions
1 29
SNR= Signal to Noise Ratio CR = Coding Rate How the AMC maximizes the spectral efficiency over scheduling resource allocation? The Adaptive Modulation and Coding (AMC) optimizes the spectral efficiency by maximising the user bit rate during its transmission time: indeed it changes the modulation and the coding rate to increase the bit rate in the limit of a certain quality of the link (BLER threshold). How AMC is working? The AMC enables to select the most suitable combination of parameters (modulation/Nb. codes/coding rate). For example, it selects 16-QAM, CR=3/4 over 10 codes when SNR>y dB, and QPSK, CR=1/2 over 5 codes when SNR<y dB.
2.4 Fast Retransmission Combining: Hybrid-ARQ

Hybrid-Automatic Repeat reQuest (H-ARQ) reduces the delay and increases the efficiency of retransmission data.
Packet transmission
RLC NACK
RLC Re-Transm ission
On a DCH channel
Node-B UE
Serving RNC
RLC ACK
Serving RNC
1 30
& TER CIENT F AS F F I EE ORRLC ACK M

Packet transmission
H-ARQ NACK
H-ARQ Re-Tx
Combining Rx packets
On the HS-DSCH channel
H-ARQ ACK
Node-B
UE
What is the goal of H-ARQ? The H-ARQ mechanism has been introduced to reduce the delay and increase the efficiency of retransmitting data by allowing lower layer retransmission (at MAC layer).
2.5 NodeB Role

RNC
Capacity Request Control FP
Capacity Allocation Control FP
Data FP
Flow Control
Dynamically fills the Queues of each UE
Queue IDs
Scheduler
Fills the TTIs with one or more users based on their priority and feedback information
HARQ Processes
Retransmissions handling, TFRC selection, AMC
Feedback Reception
Radio Transmission
1 31
The main architectural shift with respect to R4 is the introduction of MAC entity, the Mac-hs layer, located in the NodeB, near the physical channel, which allows s high reactivity in the resource allocation according to the RF conditions changes. This Mac-hs layer manages the scheduling of users and the retransmissions of packets. This architectural evolution gives a new importance to the role of the NodeB in the UTRAN. It then necessarily goes together with the introduction of some new functions managed by the NodeB among which: Flow Control: new control frames are exchanged in the user plane between NodeB and RNC to manage the data frames sent by the RNC; Scheduler: it determines for each TTI which users are going to be served and how many data bits they are going to receive; Hybrid Automatic Repeat Query: This ARQ schema is for error recovery at the physical layer (which exists independently of the ARQ scheme at the RLC layer). This fast retransmission scheme is of paramount importance for TCP as generally TCP has not performed well in a wireless environment; Adaptive Modulation and Coding: new channel coding stages and radio modulations schemes are introduced to provide data throughput flexibility; Feedback demodulation and decoding in UL.

1 32

Module 3 HSDPA Channels
3 Objectives
After this section, you will be able to Describe HSDPA channel operation
HSDPA New Channel Structure
Channel Features
HSDPA Channels HSDPA Physical Layer Structure Channel mapping in 3GPP/HSDPA (Downlink) Channel mapping in 3GPP/HSDPA (Uplink) Structure of HS-DSCH-associated Channels HS-DSCH specific Characteristics OVSF Code Tree Reservation Power Management Principles (first Tx)
Power Management
1 34
3.1 HSDPA New Channel Structure
1 35
1.1 HSDPA Channels

What are the channels related to HSDPA?
Control in DL (HS-SCCH) Resource allocation information (TTI, codes,)
Data in UL/DL (DTCH/DCH) DL in option UE Signaling (DCCH/DCH) RRC/RLC Signaling
Data in DL (HS-DSCH maps onto 1 up to 15 HS-PDSCHs) Useful Data only
Channel quality feedback (HS-DPCCH) [UL] Channel Quality Indicator (CQI) -HS-DPCCH ACK/NACK - HS-DPCCH
1 36
[3GPP TS 25.211] The HS-SCCH (High Speed-Shared Control CHannel) is a fixed rate (SF=128) downlink physical channel used to carry downlink signalling related to HS-DSCH transmission (e.g. Transport Block size, Modulation, number of codes). All relevant Layer 1 information is transmitted in the associated HS-SCCH i.e. the HS-PDSCH does not carry any Layer 1 information. If the UE did detect consistent control information intended for this UE in the immediately preceding subframe, it is sufficient to only monitor the same HS-SCCH used in the immediately preceding subframe. [3GPP TS 25.214] If the UE did not detect consistent control information intended for this UE on any of the HS-SCCHs in the HS-SCCH set in the immediately preceding subframe, the UE shall monitor all HS-SCCHs in the HSSCCH set. The maximum size of the HS-SCCH set is 4. [3GPP TS 25.321] The Transport Block size [bits] for HS-DSCH (High Speed-Donwlink Shared CHannel) is derived from the TFRI (Transport Format Resource Indicator) value signalled on the HS-SCCH and from the modulation and the number of codes also signalled on the HS-SCCH. (See table of mapping in TS 25.321) [see next slide for information about HS-DPCCH, HS-PDSCH, associated DCH]
1.2 HSDPA Physical Layer Structure
(DL) HS-PDSCH (High Speed Physical Downlink Shared CHannel)

Data information with fixed SF=16 (up to 15 per UE) Supports QPSK modulation and 16-QAM in option
(DL) HS-SCCH (High Speed Shared Control CHannel)

Control information for only one UE with fixed SF=128
(allocated channelization codes, UE identity, Transport Block size, H-ARQ process )
3GPP specifies a max. of 4 HS-SCCH/cell, then up to 4 UEs/TTI
(UL) HS-DPCCH (High Speed Dedicated Physical Control CH.)

Control information (ACK/NACK and CQI) with fixed SF=256
(UL/DL) Associated DPDCH/DPCCH (associated DCH)

Control information (RRC/RLC level) Data information (in UL at least)
1 37
The UE shall transmit the ACK/NACK information received from MAC-hs in the corresponding HS-DPCCH (High Speed-Dedicated Physical Control CHannel) sub-frame.[3GPP TS 25.211] The HS-DPCCH (SF=256) carries uplink feedback signalling related to downlink HS-DSCH transmission. The HS-DSCH-related feedback signalling consists of Hybrid-ARQ Acknowledgement (HARQ-ACK) and Channel-Quality Indication (CQI). There is at most one HS-DPCCH on each radio link. The HS-DPCCH can only exist together with an uplink DPCCH. [3GPP TS 25.211] The High Speed Physical Downlink Shared Channel (HS- PDSCH) is used to carry the High Speed Downlink Shared Channel (HS-DSCH). A HS-PDSCH corresponds to one channelization code of fixed spreading factor SF=16 from the set of channelization codes reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates to UE being assigned multiple channelisation codes in the same HS-PDSCH subframe, depending on its UE capability. An HS-PDSCH may use QPSK or 16QAM modulation symbols. An associated uplink DCH mapped on a DPCH is necessary to carry data of the UE as HS-PDSCH is just carrying data in DL. [see previous slide for information about HS-SCCH, HS-DSCH]
1.3 Channel mapping in 3GPP/HSDPA (Downlink)
Logical Channels
DTCH
CTCH
DCCH
CCCH
PCCH
BCCH
Transport Channels
DCH HS-DSCH
HS A DP
FACH
PCH
BCH
Physical Channels
DPDCH + DPCCH HS-PDSCHs + HS-SCCHs
HS A DP
DPDCH and DPCCH multiplexed by time
S-CCPCH
P-CCPCH
Not associated with transport channels
AICH
PICH
CPICH
P-SCH
S-SCH
1 38
HS-DSCH definition: refer to [3GPP TS 25.301] The HS-DSCH is a resource that exists in downlink only. It has only impact on the physical and transport channel levels, so there is no definition of shared channel in the logical channels provided by MAC. The HS-DSCH is a transport channel for which a common pool of radio resources is shared dynamically between several UEs. The HS-DSCH is mapped to one or several physical channels such that a specified part of the downlink resources is employed. For the HS-DSCH no macrodiversity is applied, i.e. a specific HS-DSCH is transmitted in a single cell only.The HS-DSCH is defined as an extension to DCH transmission. Physical channel signalling is used for indicating to a UE when it has been scheduled and then the necessary signalling information for the UE to decode the HS-PDSCH. In every HS-DSCH TTI, one or several HS-PDSCHs can be used in the downlink. Therefore, the HS-DSCH supports code multiplexing. MAC multiplexing of different UEs shall not be applied within an HS-DSCH TTI, i.e. within one HS-DSCH TTI an HS-PDSCH is assigned to a single UE. However, MAC multiplexing is allowed on a TTI by TTI basis, i.e. one HS-PDSCH may be allocated to different UEs at each TTI. Resource allocation and UE identification on HS-DSCH: For each HS-DSCH TTI, each HS-SCCH carries HS-DSCH related downlink signalling for one UE, along with a UE identity (via a UE specific CRC) that identifies the UE for which this information is necessary in order to decode the scheduled HS-PDSCH.
Note: In Evolium R5, DCCH is not mapped on HS-DSCH
1.4 Channel mapping in 3GPP/HSDPA (Uplink)
Logical Channels
DTCH
DCCH
CCCH
Transport Channels
DCH1
DCH2
RACH
CCTrCH
Physical Channels
DPDCH + DPCCH HS-DPCCH
H PA SD
DPDCH and DPCCH multiplexed by modulation
PRACH
Note: In Evolium R5, DCCH is not mapped on HS-DSCH
1 39
1.5 Structure of HS-DSCH-associated Channels

Tslot=2560 chips, Mx10x2k bits (k=4)
HS-PDSCH Structure
(Downlink Data Channel)
Slot #0
Data (N bits) Slot #1 Slot #2
M=2 for QPSK M=4 for 16-QAM
One HS-PDSCH subframe (TTI=2ms =3 time slots) Transport block size Hybrid-ARQ process number H-ARQ related info. Redundancy version New-data indicator TTI=2ms Part-2 CRC UE Identity via UE specific CRC
Part-1
HS-SCCH Structure
(Downlink Control Channel)
Channelization codes to despread Modulation scheme (QPSK or 16-QAM)
HS-DPCCH Structure
(Uplink Control Channel)
Subframe #0
ACK/NACK
Downlink CQI
Subframe #i One radio frame (10 ms)
Subframe #4
1 40
Frame structure for HS-PDSCH (SF=16, turbo coding) A HS-PDSCH corresponds to one channelization code of fixed spreading factor SF=16 from the set of channelization codes reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates to UE being assigned multiple channelization codes in the same HS-PDSCH sub-frame, depending on its UE capability. An HS-PDSCH may use QPSK or 16QAM modulation symbols, but n HS-PDSCH codes transmitted in parallel for a UE shall use the same modulation. M is the number of bits per modulation symbols i.e. M=2 for QPSK and M=4 for 16QAM. For FDD, following information is carried on the HS-SCCH (SF=128, convolution coding r=1/2), refer to [3GPP TS 25.858] Transport-format and Resource related Information (TFRI): Channelization-code set: 7 bits, Modulation scheme: 1 bit, Transport-block size: 6 bits Hybrid-ARQ-related Information (HARQ information): Hybrid-ARQ process number: 3 bits (thus corresponding to a maximum of 8 HARQ processes at UE), Redundancy version: 3 bits, New-data indicator: 1 bit (0 for the first MAC-hs PDU transmitted by a HARQ process), UE ID: 10 bits implicitly encoded in the CRC Frame structure for Uplink HS-DPCCH (SF=256, 15 kbps channel bit rate), refer to [3GPP TS 25.211] The HS-DPCCH carries uplink feedback signalling related to downlink HS-DSCH transmission. The HS-DSCH-related feedback signalling consists of Hybrid-ARQ Acknowledgement (HARQ-ACK) and Channel-Quality Indication (CQI). Each sub frame of length 2 ms (3*2560 chips) consists of 3 slots, each of length 2560 chips. The HARQ-ACK (positive or negative) is carried in the first slot of the HS-DPCCH sub-frame. The CQI is carried in the second and third slot of a HS-DPCCH sub-frame. There is at most one HS-DPCCH on each radio link. The HS-DPCCH can only exist together with an uplink DPCCH.
3.2 Channel Features
1 41
2.1 HS-DSCH specific Characteristics

Fixed TTI, 2 Modulations, lower Coding Rates, Multi-Code Transmission, Code Multiplexing
Ex.: QPSK Coding rate=1/4 Ex.:16-QAM Coding rate=3/4
Codes
UE 1 User 5 User 3 User 5 UE 3 UE 5 UE 2 UE 4
15 codes
(SF=16)
User 1 User 4 User 4 User 2
HS-PSDCH #5
User 1
User 2 TTI=2ms
User 1
User 3
User 3
Time
1 42
The HS-DSCH has specific characteristics in many ways compared with existing Release99 channels: The Transmission Time Interval (TTI) or interleaving period has been defined to be 2 ms (3 slots) to achieve short round-trip delay for the operation between the terminal and Node B for retransmissions. The HS-DSCH 2-ms TTI is short compared to the 10-, 20-, 40- or 80-ms TTI sizes supported in Release99. Adding higher order modulation scheme, 16 QAM, as well as lower encoding redundancy has increased the instantaneous peak data rate. In the code domain perspective, the SF is fixed; it is always 16, and multi-code transmission (up to 15 codes/UE) as well as parallel transmission (up to 4 UE/TTI) of different users can take place. The maximum number of codes that can be allocated is 15, but depending on the terminal (UE) capability, individual terminals may receive a maximum of 5, 10 or 15 codes. Channel Coding [25.858] HS-DSCH channel coding uses the existing rate 1/3 Turbo code and the existing Turbo code internal interleaver, as outlined in 3G TS 25.212. Other code rates are generated from the basic rate 1/3 Turbo code by applying rate matching by means of puncturing or repetition. [Holma] turbo coding is the only coding scheme used. However, by varying the transport block size, the modulation scheme and the number of multi-codes and turbo code rates other than 1/3 become available. In this manner, the effective code rate can vary from to ; i.e. the number of bits per code can vary by changing the coding gain.
2.2 OVSF Code Tree Reservation

SF4 SF8 SF16 SF32 SF64 HS-SCCH SF128 HS-PDSCH
HSDPA
SF4 SF8 SF16 SF32 SF64 SF128 SF256

1 43
HS-PDSCH
cmCH HS-SCCH
HSDPA + DCH
The configuration of the OVSF code tree can provide up to 15 SF16 codes allocated to HS-PDSCH and up to 4 SF128 codes for HS-SCCH. All R99 common channels (P-CPICH, P-CCPCH, S-CCPCH) are allocated at the top of the tree, with a minimal equivalent occupancy of SF32. Immediately below the HS-SCCH SF128 codes are allocated. These codes are allocated at cell setup and cannot be used or preempted for other services. The HS-PDSCH SF16 codes are allocated and reserved by the RNC at the bottom of the tree. All the remaining codes are therefore contiguous and left for further DCH allocations. This includes associated DCH as well as any other calls mapped on DCH (e.g. speech calls, streaming, etc). Note that the maximum configuration (15 HS-PDSCH codes and 4 HS-SCCH codes) leaves no room in the OVSF tree for DCH (due to common channels occupancy) so it is not even possible to allocate associated SRB for HSDPA calls.
3.3 Power Management
1 44
3.3 Power Management
3.1 Power Management Principles (first Tx)
Cell Power PMAX
HS-DSCH
PHSDPA
HS-SCCH DCH margin DCH
CmCH
1 45
HSDPA power management is based on the principle that HSDPA channels can use all the remaining power left by dedicated and common channels. In order to compensate the DCH power fluctuation mainly due to power control, a margin is considered. The total available power for HSDPA corresponds to the difference between the maximum available power in the cell and the power for R99 channels plus margin. UE is scheduled only if there remains enough power to transmit at least the HS-SCCH. Otherwise the NodeB try to schedule another UE in the TTI. If all UEs require power for HS-SSCCH higher than what is available at NodeB level, none of them is scheduled.

1 46

Module 4 H-ARQ for Fast Retransmission
4 Objectives
After this section, you will be able to Describe H-ARQ process
Hybrid Automatic Repeat Query Principles HARQ Processes Redundancy Version
1 48
4.1 Hybrid Automatic Repeat Query Principles
1 49
1.1 Fast Retransmission with Hybrid-ARQ
Packet transmission
RLC NACK
RLC Re-Transm ission
R4/R5 on a DCH channel

UE
Serving RNC
RLC ACK
The erroneous block is deleted!
Packet transmission
H-ARQ NACK
H-ARQ Re-Tx
Combining Rx packets
R5 on the HS-DSCH channel
RLC ACK
H-ARQ ACK
Serving RNC
Node-B
UE
The erroneous block is stored for recombination!
1 50
What is the goal of H-ARQ? The H-ARQ mechanism has been introduced to reduce the delay and increase the efficiency of retransmitting data. What are the advantages of H-ARQ implemented in R5 vs. R99? In previous releases of UMTS (R99), with H-ARQ type I, when the UE received a false block, it threw it away and waited for a retransmission of the block from the RNC hoping it could decode this one. Hybrid ARQ Type II/III is added in R5, whose aim is to recombine a retransmission with previous transmissions in order to increase the probability to decode it. Time diversity is added: because of the fast fading effect, transmitting twice a block at 2 distinct times with a power P and add the received soft bits is much better than transmitting it only once with a power 2*P since the probability not to be in a fading hole at least is increased. What are the drawbacks of H-ARQ? The disadvantage of H-ARQ is that the UE needs to store the false blocks and add the new soft bits received to the previous ones he couldnt decode correctly, which requires additional memory and processing. How it works?
1. 2.
The Node B transmits one packet in 1 HS-DSCH TTI. The UE sends a ACK/NACK indicating if the packet was correctly received or not. In case of NACK, the UE stores the received data in a buffer. If the Node B has received a NACK, it will retransmit the same transport block (at the earliest 12 ms after the previous transmission) and the UE will combine the packet with the previous transmission(s) (which increases the probability to decode correctly the transport block). If the Node B has received a ACK, it will transmit a new block.
3.
4.
1.2 H-ARQ in HSDPA: How it works?
1st H-ARQ Process

at T0
HS-DSCH block #1
NACK / CQI HS-DPCCH
ACKNOWLEDGMENT
HS-DSCH block #1
HS-PDSCHs
FIRST TRANSMISSION
block #1
Soft buffer
1 51
1.2 H-ARQ in HSDPA: How it works? [cont.]
2nd H-ARQ Process

at T0 + 2ms
HS-DSCH block #2
ACK / CQI HS-DPCCH
ACKNOWLEDGMENT
HS-DSCH block #2
HS-PDSCHs
FIRST TRANSMISSION
block #1
block #2
Soft buffer
1 52
Re-Ordering
3rd H-ARQ Process

at T0 + 4ms
HS-DSCH block #3
ACK / CQI HS-DPCCH
ACKNOWLEDGMENT
HS-DSCH block #3
HS-PDSCHs
FIRST TRANSMISSION
block #3 block #1 block #2
Soft buffer
1 53
Re-Ordering
1st H-ARQ Process

ACK / CQI HS-DSCH block #1 HS-DPCCH
at T0 + 12ms
ACKNOWLEDGMENT
2nd decode attempt success after combining
FIRST Re-TRANSMISSION
HS-DSCH block #1
HS-PDSCHs
block #3 block #1 block #1 block #3 #2 block #2 #1
Soft buffer
1 54
Re-Ordering
H-ARQ Combination mechanism may require new Mobile equipment with a larger memory to store MAC-hs PDU until a decoding success.
4.2 HARQ Processes
1 55
4.2 HARQ Processes
2.1 Multiple HARQ Processes

CK /NA ACK
HARQ HARQ HARQ HARQ Soft Bits Combining
UE Category Category 1 Category 2
HARQ Processes 2 2 3 3 6 6 6 6 6 6 3 6
HSDSCH
ACK/NACK
Category 3 HARQ HARQ Category 4 Category 5 Category 6 Category 7 Category 8 HARQ HARQ Soft Bits Combining Category 9 Category 10 Category 11 Category 12
Retransmission Management
HARQ HARQ HARQ HARQ HARQ HARQ HARQ HARQ
ACK /NA
Soft Bits Combining

CK
1 56
The retransmission mechanism selected for HSDPA is Hybrid Automatic Repeat Query (HARQ) with Stop and Wait protocol (SAW). HARQ allows the UE to rapidly request retransmission of erroneous transport blocks until they are successfully received. HARQ functionality is implemented at the MAC-hs layer, which is terminated at the NodeB, as opposed to the RLC (Radio Link Control), which is terminated at the S-RNC. Therefore the retransmission delay of HSDPA is much lower than for R4, significantly reducing the delay jittering for TCP/IP and delay sensitive applications. The HARQ consists in:
Re-transmitting by the NodeB the Data Blocks not received or received with error by the UE. Combining by the UE the transmission and the re-transmission in order to increase the probability to
decode correctly the information. This is a form of soft combining. There is a HARQ process assigned per transport block for all the retransmissions. 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 Multiple Stop And Wait mechanism. While one channel is waiting an acknowledgment, the remaining channels continue to transmit. The number of processes per UE is limited and depends on UE category. The number of processes per UE category is defined by 3GPP specifications. Once this number is reached, the UE is not be eligible by the scheduler for new transmissions unless one of them is reset (ACK reception, max number of retransmissions reached).
4.2 HARQ Processes
2.2 Parallel H-ARQ Processes

Example: 2 UEs, several process each, different Inter-TTI intervals
HS-DPCCH UE1 (Uplink Control)
N N A A A A A
(2.5 TTI) between the reception of the packet and when the node B receives the ACK/NACK
UE1 packet1 2 ms UE1 packet2 UE1 packet3 UE1 packet4 UE1 packet5 UE1 packet6 UE1 packet1 UE1 packet2 UE1 packet7 UE1 packet8 UE1 packet9
HS-PDSCH UE1 (Downlink Data)
Minimum of 12 ms before the same process can be used for the transmission of a packet with new data or the retransmission of this packet HS-PDSCH UE2 (Downlink Data)
UE2 packet1
Inter-TTI interval
= 1 for UE1 = 3 for UE2

UE2 packet1
UE2 packet2
HS-DPCCH UE2 (Uplink Control)

UE #1 process #1 UE #2 process #1 UE #1 process #2 UE #2 process #2 UE #1 process #3 UE #1 process #4
N UE #1 process #5 UE #1 process #6
1 57
ACK/NACK delay and data processing (UE, Node B) allow to work with several H-ARQ processes during unused TTI. Up to a maximum of 8 simultaneous H-ARQ processes can be supported by the UE. Time between 2 different H-ARQ processes (inter-TTI interval) depends on the UE category.
4.2 HARQ Processes
2.3 Stop And Wait Principles

HARQ
Wait for Transmission
UE is Scheduled
Update RV Parameters
TB TB
HARQ HARQ
Transmit Data HSDSCH Wait for ACK/NACK Reception

ACK ACK/NACK/DTX? NACK DTX
Insert DTX Indication
Reset & Free HARQ Process
Nret = Nret + 1
ACK/NACK
YES
Nret > Nret_max
NO
1 58
Once a UE is scheduled, a HARQ process is assigned that may correspond to either a new Transport Block transmission or a TB retransmission. The RV parameters are computed accordingly and data is transmitted. The HARQ process is then waiting for feedback information (ACK/NACK/DTX): In case of ACK reception, the HARQ process is reset and corresponding MAC-d PDUs are removed from memory. This HARQ process can now be used for a new transmission. In case of NACK reception, the number of retransmissions must be incremented. If the maximum number of retransmissions is not reached, the HARQ process is inserted in the NACK list of HARQ processes asking for retransmission. In case of DTX indication, the same actions as for NACK reception are performed, except that a parameter must be updated to notify DTX detection (this changes the RV parameter update). After a NACK reception or a DTX indication, the HARQ processes are just waiting for being re-scheduled for a new retransmission. Note: DTX indication is used when there is no ACK/NACK reception.
4.3 Redundancy Version
1 59
3.1 HARQ Types

HARQ Blocks Decoding
New Block NO
Deliver to Upper Layer
Combine
RVBlocks
Error?
YES
Update RV Database
DATA
DATA
DATA
DATA
DATA
Chase Combining
NACK
NACK
NACK
NACK
ACK
Incremental Redundancy Combining
DATA
DATA1
DATA2
DATA3
DATA4
NACK
1 60
NACK
NACK
NACK
ACK
Different HARQ types are supported:

Chase Combining is the basic combining scheme. It consists in the NodeB simply retransmitting the
exact same set of coded symbols of the original packet.

Partial Incremental Redundancy: different redundancy information can be sent during re-transmissions.
For all redundancy versions the systematic bit must be transmitted (only RV parameters with s=1 are taken in account)
Full Incremental Redundancy corresponds to sequences where both systematic and non-systematic bits
can be punctured.
3.2 Two H-ARQ Combining Techniques

Chase Combining
Turbo coding Rate 1/3 1st rate matching 2nd rate matching RV=6 UE buffer size
Incremental Redundancy
Original useful data bits Turbo coding Rate 1/3
Node B side
UE buffer size
1st rate matching 2nd rate matching RV=0
1st transmission 2nd transmission 3rd transmission UE side Eff. coding rate (RCC) = # data bits / (#data bits + # parity bits) RIR < RCC Better protection of the data bits higher probability to decode correctly
RV=6
RV=2
RV=6
RV=5
RV=6
Parity bits (protection)
1 61
HOW are those data blocks combined to be able to recover a correct blocks from several corrupted copies? 1st step Rate Matching: 3GPP TS 25.212] The first rate matching stage matches the number of input bits to the virtual buffer. Note that, if the number of input bits does not exceed the virtual buffering capability, the first ratematching stage is transparent. The 1st rate matching performs segmentation at the maximum UE buffer size when required. The second rate matching stage matches the number of bits after first rate matching stage to the number of physical channel bits available in the HS-PDSCH set in the TTI. The 2nd rate matching follows transport format indications to achieve the effective coding rate expected during the TTI. 2nd step retransmission according to combining methods: Chase Combining (CC) Retransmit the same block with exactly the same bits at each retransmission The UE buffer size is fixed for each transport block retransmission Incremental Redundancy (IR) Retransmit the same block with different redundancy information at each retransmission, thanks to different rate matching version. The use of different Redundancy Versions (RV) increases the performances of the channel since the total effective coding rate is decreased (more protection bits) at each retransmission The UE buffer size increases for each transport block retransmission. IR requires a larger memory and processing in the UE than the Chase Combining case. The ARQ combining scheme is based on Incremental redundancy. Chase Combining is considered to be a particular case of Incremental Redundancy.
3.3 Answer the Questions
According to the previous slide:

What is the coding rate (Rbuffer) after the 1st rate matching for both combining mechanisms? What is the coding rate (RCC(#k)) of each block applying the Chase Combining mechanism? What is the coding rate (RIR(#k)) of each block applying the Incremental Redundancy combining mechanism? Compare the effective coding rates (RIR(UE) and RCC(UE)) at UE side between CC and IR techniques after retransmissions.
1 62
3.4 H-ARQ Combining Performances
coding rate 3/4, Pedestrian A, 3 km/h, H-ARQ = ON, N_max = 5
High error rate
10% BLER
0.1
2dB gain (N=3)
BLER
Re
0.01
Low error rate

0.001
Bad link quality

-10 -5
i ng od tal ec n r d e me y c tte r Be h Inc ndan t wi Redu Good link ~2dB gain quality (N=3)
0 Ior/Ioc [dB] 5 10
-t
n ra
sm
ns sio is
N = 1, CC N = 2, CC N = 3, CC N = 1, IR N = 2, IR N = 3, IR
1 63
What does this figure represent? Error rate is function of the quality of the radio link BLER= Block Error Rate Ior/Ioc is representative of the radio conditions of the cell, in dB: N represents the index of transmission N=1 first transmission; N=2 second transmission (=first re-transmission) IR = Incremental Redundancy is an H-ARQ combining technique CC = Chase Combining is another H-ARQ combining technique What happen without H-ARQ? Without H-ARQ, to reach an error rate of 5%, an Ior/Ioc of 8 dB is required, meaning a good link quality. If the channel quality induces a BLER=0.1=10%, it means 10% chance to receive an erroneous block (at N=1). If this block is effectively in error, at the first retransmission (N=2), the chance to get the same block in error is now at the power of 2, i.e. BLER=10%x10%=0.01=1%, for the second retransmission (N=3), the block has been received in error for the second time, your chance to receive again the block in error for the third time is BLER=0.1%. What are the advantages of H-ARQ? You can notice that for the same number of re-transmission, both H-ARQ combining techniques achieve better performances than without (much less errors for the same quality of the link). What are the performances of the H-ARQ combining techniques? We can notice that for a single retransmission (N=2), there is not much differences between Chase Combining and Incremental Redundancy. For the second re-transmission (N=3), IR achieves better performances than CC with a gain of 2dB.
3.5 Redundancy Version Parameters

RV Coding
16QAM XRV 0 1 2 3 4 5 6 7 s 1 0 1 0 1 1 1 1 r 0 0 1 1 0 0 0 1 b 0 0 1 1 1 2 3 0 QPSK XRV 0 1 2 3 4 5 6 7 s 1 0 1 0 1 0 1 0 r 0 0 1 1 2 2 3 3
HARQ Types
Chase Combining Partial Incremental Redundancy Full Incremental Redundancy
RV Update
New Tx?
NO YES
XRV=TRV[0] k=0
MIR RV Update Table

k QPSK XRV 16QAM XRV 0 0 6 1 2 2 2 5 1 3 6 5 4 1 0 5 3 3 6 4 4
Kmax
7 7 7
DTX?
NO
YES
XRV=XRV
TRV[k]
k=k+1 XRV= TRV[k mod Kmax]

1 64
The IR and modulation parameters necessary for the channel coding and modulation steps are the r, s and b values. The r and s parameters (Redundancy Version or RV parameters) are used in the second rate matching stage, while the b parameter is used in the constellation rearrangement step:
-
s is used to indicate whether the systematic bits (s=1) or the non-systematic bits (s=0) are prioritized in transmissions. - r (range 0 to rmax-1) changes the initialization Rate Matching parameter value in order to modify the puncturing or repetition pattern.
- b can take 4 values (0,...,3) and determines which operations are produced on the 4 bits of each symbol in 16QAM. This parameter is not used in QPSK and constitutes the 16QAM constellation rotation. These three parameters are indicated to the UE by the Xrv value sent on the HS-SCCH. The Xrv update follows a predefined order stored in a table Trv. A configurable parameter (CC/PIR/MIR) indicates the possibility to chose between Chase Combining, Partial Incremental Redundancy or a mix between Partial and Full Incremental redundancy. It implies that three different tables must be stored. Each HARQ type is characterized by its update table Trv.
3.6 Dynamic RV Table Selection
0 0 6
1 2 2
2 4 5
3 6 0
First RTx?
PIR
QPSK XRV 16QAM XRV
YES
k 0 0 6 1 5 1 2 1 3 3 3 4 7
FIR Dynamic RV Table Selection CC+CoRe

maximum number of bits per HARQ number of RM2 punctured bits number of systematic bits total number of radio bits
QPSK XRV 16QAM XRV
k 16QAM XRV
0 6
1 5
2 0
3 4
0 0
CC
QPSK XRV
1 65
The aim this feature is to optimize RV choice by dynamically selecting the most efficient HARQ type (and its corresponding RV table) according to several parameters: UE category, number of HARQ processes and applied AMC for first transmission. In case this mode is activated for different HARQ types (each one being associated to a restricted redundancy version set) that can be selected are: Chase Combining (CC), CC + Constellation rearrangement (CC+CoRe), Partial Incremental Redundancy (PIR), and Full Incremental Redundancy (FIR). The principle is that Incremental Redundancy is only selected when required, i.e. only when punctured bits by the second Rate Matching stage and total number of soft bits per HARQ process the UE can handle are higher than the number of transmitted bits. Otherwise Chase Combining is efficient enough. In case of IR, it is only necessary to puncture systematic bits (FIR) in case it is not possible to transmit all parity bits punctured by the second RM stage in the first retransmission. Note. As the RV of the 1st transmission is identical whatever the HARQ type is, the HARQ Type only needs to be determined when 1st retransmission occurs.

1 66

Module 5 HSDPA Scheduling Mechanism
5 Objectives
After this section, you will be able to Describe NodeB Scheduler structure
CQI Measurements Fast Scheduling
1 68
5.1 CQI Measurements
1 69
1.1 CQI Reporting
P - CP HS - D PCC H
ICH
Cat.6 CQI
0 1 ... 22
Cat.6 D
0 0 ... 0 -1 -2 -3 -4 -5 -6 -7 -8
PHS-DSCH = PP-CPICH + +
23
2ms
Target BLER 10%
24 25 26 27 28 29 30
1 70
The procedure to allocate power to the HSDPA traffic channel described in the standard is mainly based on terminal measurements and reporting. In this procedure the UE first estimates the Signal to Interference Ratio, from this SIR estimate it determines the power of the HS-DSCH and then determines the corresponding CQI. CQI determination is then performed by the UE with a HS-DSCH BLER target of 10%. HS-DSCH power estimates are based on the UE measurement of the power of the Primary Common Pilot CHannel (P-CPICH) (see formula in the above slide). is the Measurement Power Offset, provided by the RNC to the NodeB via NBAP signaling and to the UE via RRC signaling. This is a fixed offset relatively to the power of the pilot. is the reference power offset which depends on the CQI processed based on value reported by the UE and on the category of the UE (CQI mapping tables). The power HS-DSCH is equally distributed around the physical channels HS-PDSCH.
1.2 Channel Quality Feedback

The Channel Quality Indicator (CQI) is reported to the Node-B on the UL control channel (HS-DPCCH)
Reported CQI (estimated by the UE)
SCHEDULER (every TTI)

[TFRC selection]
Transport Block Size H-ARQ parameters (RV) Number of channelization codes Allocated power HS-PDSCH Modulation Type
Channel Quality Feedback (CQI)
available codes available power UE capabilities ACK/NACK
CQI ?
CQI 1 CQI 2 CQI 30
User data and Signalling

1 71
A CQI mapping table example is shown below for UE category 10.
CQI value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Transport Block Size 137 173 233 317 377 461 650 792 931 1262 1483 1742 2279 2583 3319
Number of HS-PDSCH 1 1 1 1 1 1 2 2 2 3 3 3 4 4 5
Modulation Type QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK
CQI value 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
Transport Block Size 3565 4189 4664 5287 5887 6554 7168 9719 11418 14411 17237 21754 23370 24222 25558
Number of HS-PDSCH 5 5 5 5 5 5 5 7 8 10 12 15 15 15 15
Modulation Type 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM 16-QAM
5.2 Fast Scheduling
1 72
5.2 Fast Scheduling
2.1 Scheduler Type
UE Capabilities
Available Power & Codes
ACK/NACK/CQI
Previously Transmitted PDUs
Retransmissions First QId0 New Transmissions QId1 QIdN
Round Robin
Fair
CQI
Proportional Fair
Alcatel-Lucent
C1
UE #0 power codes number of bits

1 73
UE #1 power codes number of bits

UE #N power codes number of bits
The aim of the scheduler is to dynamically share available DL bandwidth among users in order to optimize overall throughput and fulfill UTRAN and UE criteria. The scheduler first receives as input, every TTI, the number of codes available and the remaining power for HS-PDSCH and HS-SCCH. The received ACK/NACK and CQI, UE capabilities and configuration parameters (provided by RNC) then can select the sub-flows of the users to schedule in order to optimally uses available resources. The main concepts of the scheduler are:
Retransmissions are of higher priority then the new transmission and should be scheduled first. The Queue ID (Qid) is chosen according the radio condition (based on CQI) and the Scheduling Priority
Indicator (SPI or CmCH-PI).

The transport blocks should be optimized according to the transmitted CQI and the available resources
(codes, power and CPU) In UA5.0 the MAC-hs scheduler has been enhanced in order to support of various MAC-hs scheduler type and manage SPI. Five scheduler types are available:
Alcatel-Lucent scheduler: mobiles are chosen according to the number of transmitted bits and the CQI
reported;
Classical Proportional Fair scheduler: mobiles are chosen according to reported a high CQI versus their
averaged CQI to take benefit from instantaneous good radio conditions vs. average conditions;
Pure Fair scheduler: Throughput provided per UE must be equal; Max C/I scheduler chooses mobiles with the best CQI; Round Robin scheduler serves mobiles one after the other one.
5.2 Fast Scheduling
2.2 NodeB Scheduler

Flow Control
(UEX, SPIY)
QId0 available codes available power UE capabilities ACK/NACK/CQI Compressed Mode information UE HSDPA synchronisation state
QId1
QIdK
QIdN
HARQ
COST COST = f(C1, C2) C1 = f(Scheduler Type) C2 = f(SPI, UE Category)
NodeB Scheduler
1 74
MAC-hs scheduling consists of choosing the MAC-D flow (QId) to serve. The selection of a Qid to be scheduled is based on a single cost function which inputs are:
C1 takes into account the Radio criteria (CQI) and the function depends on the scheduler type. C2 takes in account the priority of the QID and mainly depends on the base credit assigned to this SPI
priority and the average CQI. C2 is only used by Alcatel-Lucent and Classical Proportion Fair schedulers. The resulting cost is a function of these two costs, and is different according to the scheduler type. Indeed, for Nortel Proportional Fair scheduler, the resulting cost should be equal to *C1+*C2, while for the classical Proportional Fair, the resulting cost is rather equal to *C1*C2 (, , being hard coded). The QId with the smallest cost is scheduled first. Costs are updated after the QId has been served.
5.2 Fast Scheduling
2.3 UE, QId and SPI

UE0 cmCH-PI 6 cmCH-PI 4 UEN cmCH-PI 4 CID n QI1 SP4 cmCH-PI 6 PDU flow0 QI2 SP6
RNC
PDU flow0
NodeB
QI0 SP4
QI0 SP6
1 75
Each UE can be configured with one or more MAC-d flows according to the number of PS services established and mapping rules on RNC side. Each MAC-d flow is associated to a CID for data Frame Protocol. One MAC-d flow is constituted of one or more logical subflows. If these subflows are assigned the same priority, they are multiplexed at RNC side and this is transparent to NodeB and they are seen as a single flow. If these subflows are assigned a different priority, they are discriminated by the SPI/CmCH-PI parameter and are seen as different flows. These resulting flows then constitute the priority queues for a UE and are assigned a Queue ID. Up to 8 queues can be defined per UE and are referred in the whole document as the QId. For one UE, two QIds from the same MAC-d flow then necessarily have two different priorities, while two QIds of two different MAC-d flows may have the same priority. A QId is then unambiguously defined by its MAC-d flow CID and its priority (SPI). In the scheduler the QId of all UEs are classified according to their SPI/CmCH-PI. This enables allocating some bandwidth according to the priority. Up to 16 SPI can be defined in the scheduler.
PDU flow0
CID m
CID l
5.2 Fast Scheduling
2.4 SPI Management
TC SPI ARP THP
CQIAV C2 QIdN QIdM WEIGHT TBSAV TBSAV WEIGHT CQIAV TC SPI ARP THP
THROUGHPUTN THROUGHPUTM
1 76
SPI management only applies to Nortel and Proportional Fair schedulers and is not supported by the other schedulers. The second cost function C2 is based on the priority of the QId, and mainly on the based credits allocated to this SPI priority, and on the average CQI in order to share the HSDPA radio capacity of the cell between users so that the throughput of each QId is be proportional: to the weight of the SPI, to the transport block size of the averaged CQI reported by the UE. The base credits assigned per SPI priority provide the relative weight given per priority. The absolute value is not meaningful, only the ratio between priorities is important. Ratio on throughputs may be subject to a certain tolerance (around 10%) and are not fully respected in case there is no resource limitation for some UEs (to avoid wasting resources by artificially restraining some UEs while other UEs suffer very bad radio conditions). Note: SPI is determine based on the combination of the UMTS Traffic Class, the Allocation/Retention Priority and the Traffic Handling Priority.

1 77

Module 6 Adaptative Modulation and Coding with 16-QAM
6 Objectives
After this section, you will be able to Describe AMC schemes
Adaptative Modulation and Coding UE Categorization
1 79
6.1 Adaptative Modulation and Coding
1 80
1.1 AMC Principles
UE Category
Reported CQI
800 700 600
AMC Illustration QPSK QPSK QPSK 16QAM 16QAM
Throughput (kbps)
AMC
500 400 300 200 100
2ms
Coding Rate
Modulation Scheme
Number of OVSF Codes
-20
-15
-10
-5
Ior/Ioc (dB)
Maximum Throughput
1 81
Adaptive Modulation and Coding (AMC) is a fundamental feature of HSDPA. It consists in continuously optimizing the user data throughput based on the channel quality reported by the UE (CQI feedback. This optimization is performed using adaptive modification of the coding rate, the modulation scheme, the number of OVSF codes employed and the transmit power. Different combinations of modulation and channel coding rate (based on the Transport Format and Resource Combinations or TFRC) can be used to provide different peak data rates. Essentially, when targeting a given level of reliability, users experiencing more favorable channel conditions (e.g. closer to the NodeB) will be allocated higher data rates. The above figure shows an illustration of the user throughput evolution for one single OVSF code in function of the channel quality as a result of AMC.
1.2 Modulation Schemes

16QAM
Q
QPSK
1011 1001 0001 0011 10 1010 1000 0000 0010 I I 1110 1100 0100 0110 11 01 Q 00
1111
1101
0101
0111
2 bits per symbol 480kbps per OVSF 960 bits per TTI
4 bits per symbol 960kbps per OVSF 1920 bits per TTI
1 82
In order to achieve very high data rates, HSDPA adds a higher order modulation (16QAM) to the existing QPSK modulation used for R4 channels. As the 16QAM requires 2 times more bits to define one radio modulation symbol, the resulting number of bits per TTI is multiplied by a factor 2, same thing for the total maximum throughput at the physical layer. QPSK is mandatory for HSDPA capable UE, 16QAM is optional.
1.3 AMC implementation with 16-QAM
The modulation and coding rate are adapted to the quality of the link 16-QAM is fully efficient in Line of Sight environment
User data and Signalling
CQI ?
Channel Quality Feedback (CQI)
1 83
Why not always use the 16-QAM modulation? The curve above is deriving the Cell Throughput as a function of channel quality [C/(I+N)] are rather explicit. We see that the combination [16-QAM_15codes_21754bits] allows to achieve the highest throughput (>12Mbps in LoS environment). However with the same Modulation and Coding Scheme combination, we notice that the performance are really low when the quality of the link is getting worse. In this situation, it is rather better to use a lower coding rate and a more robust modulation technique in order to achieve a better throughput at the end. Then the goal of the AMC is to dynamically adapt this combination (Modulation+Coding Scheme) to maximize the throughput.
1.4 Support of 16-QAM

Peak data rate achieved using 16-QAM with the highest coding rate and 15 codes in parallel
(expecting favourable channels conditions)
M=2 for QPSK M=4 for 16-QAM
QPSK
16-QAM
Signal Constellations for QPSK and 16-QAM modulations
Throughput PEAK =
1 84
NBCODES RateTURBO M W 15 1 4 3.84 10 6 = = 14.4 Mbps SF 16

M: number of bits per symbol W: UMTS chip rate (3.84 Mchip/s) SF: spreading factor
6.2 UE Categorization
1 85
2.1 UE Categories
HS-DSCH Category Category 1 Category 2 Category 3 Category 4 Category 5 Category 6 Category 7 Category 8 Category 9 Category 10 Category 11 Category 12 HS-PDSCH Max Number 5 5 5 5 5 5 10 10 15 15 5 5 Inter-TTI Min Interval 3 3 2 2 1 1 1 1 1 1 2 1 Modulation QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK & 16-QAM QPSK only QPSK only Max Peak Rate 1.2 Mbps 1.2 Mbps 1.8 Mbps 1.8 Mbps 3.6 Mbps 3.6 Mbps 7.3 Mbps 7.3 Mbps 10.2 Mbps 14.4 Mbps 0.9 Mbps 1.8 Mbps
QPSK mandatory for HSDPA capable UE 16-QAM optional

1 86
Twelve categories have been specified by Release 5 for HSDPA UEs according to the value of several parameters among which are the following: Maximum number of HS-DSCH codes that the UE can simultaneously receive (5, 10 or 15). Minimum inter-TTI interval, which defines the minimum time between the beginning of two consecutive transmissions to this UE. If the inter-TTI interval is one, this means that the UE can receive HS-DSCH packets during consecutive TTIs, i.e. every 2 ms. If the inter-TTI interval is two, the scheduler needs to skip one TTI between consecutive transmissions to this UE. Supported modulations (QPSK only or both QPSK and 16QAM), Maximum peak data rates at the physical layer (number of HS-DSCH codes x number of bits per HSDSCH / Inter-TTI interval). These twelve categories provide a much more coherent set of capabilities as compared to R99 which gives UE manufacturers freedom to use completely atypical combinations.
2.2 UE Capabilities and Max Bit Rates

Category 6 UE CQI Mapping Table
CQI Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 ... 29 30 1 1 1 1 1 1 2 2 2 3 3 3 4 4 5 5 ... 5 5 HS-PDSCH Number RLC Throughput out of range 0 kbps 0 kbps 0 kbps 0 kbps 144 kbps 144 kbps 144 kbps 288 kbps 288 kbps 432 kbps 576 kbps 720 kbps 864 kbps 1008 kbps 1296 kbps 1440 kbps ... 3024 kbps 3024 kbps QPSK QPSK QPSK QPSK QPSK QPSK QPSK
softCQI 20 Soft CQI vs C/I - Pedestrian_a 1 RX 25
Modulation
QPSK QPSK QPSK QPSK QPSK QPSK QPSK QPSK 16-QAM ... 16-QAM 16-QAM
15
10 -10
-8
-6
-4
-2
0 C/I (dB)
10
Target BLER 10%

1 87
The maximum achievable data rate depends on the UE category but also on the instantaneous radio conditions it is exposed to. Each UE category has therefore a reference table specifying the supported combinations between the reported CQI values, the number of codes and the radio modulation (QPSK or 16-QAM). Instantaneous radio channel conditions are known at the UTRAN level thanks to the periodical decoding of the Channel Quality Indicator sent by the UE to the NodeB onto the HS-DPCCH. The UE first estimates the Carrier over Interference ratio (C/I). From this estimate the UE then determines a CQI (with a maximum HS-DSCH BLER target of 10%) and then it sends this indication back to the NodeB. The NodeB takes this input into consideration in order to adapt the throughput to the UE. Note: a UE reporting a CQI value of 0 is not scheduled by the NodeB.

1 88

Module 7 HSDPA protocols
7 Objectives
After this section, you will be able to Describe new MAC architecture and data flows List the HSDPA coding chains main steps
HSDPA Distributed Architecture TFRC Selection and channel coding
1 90
7.1 HSDPA Distributed Architecture
1 91
1.1 HSDPA Protocol Stack

HS-PDSCH
Data Transfer (PS I/B)
HS-SCCH
Downlink Transfer Information (UEid, OVSF,...)
Introduction of MAC-hs
RNC Iub
DPCH
Upper Layer Signaling
HS-DPCCH
Feedback Information (CQI, ACK/NACK)
New Transport Channel HS-DSCH

RLC MAC-d
New Frame Protocol HS-DSCH

RLC MAC-d
MAC-hs
PHY
MAC-hs Uu
PHY
HS-DSCH FP L2 L1
Flow control
Iub
HS-DSCH FP L2 L1
Flow control
Iur
HS-DSCH FP L2 L1
UE
1 92
NodeB
C-RNC
S-RNC
HSDPA is an increment on UTRAN procedures, and it is fully compatible with R4 layer 1 and layer 2. It is based on the introduction of a new MAC entity (MAC-hs) in the NodeB, that is in charge of scheduling / repeating the data on a new physical channel (HS-DSCH) shared between all users. This has a minor impact on network architecture, there is no impact on RLC protocol and HSDPA is compatible with all transport options (AAL2 and IP). On NodeB side, MAC-hs layer provides the following functionalities: Fast repetition layer handled by HARQ processes. Adaptive Modulation and Coding. New transport channel High Speed Downlink Shared Channel (HS-DSCH) Flow control procedure to manage NodeB buffering. Some L1 new functionalities are introduced compared to R4: 3 new physical channels: High Speed Physical Downlink Shared CHannel (HS-PDSCH) to send DL data, High Speed Shared Control CHannel (HS-SCCH) to send DL control information relative to HSPDSCH, and High Speed Dedicated Physical Control CHannel (HS-DPCCH) to receive UL control information. New channel coding chain for High Speed Downlink Shared CHannel (HS-DSCH) transport channel and HS-SCCH physical channel.
1.2 HSDPA Layer2/Layer1 Flows

RRC (RNC) RRC (RNC) RLC (RNC) RLC (RNC)
MAC Control
PCCH BCCH CCCH
CTCH
MAC Control
MAC Control
DCCH DTCH DTCH
MAC-hs MAC-hs (NodeB) (NodeB) MAC-c/sh MAC-c/sh (C-RNC) (C-RNC)
MAC-d (S-RNC)
Associated Downlink Signaling
HS-DSCH
Associated Uplink Signaling
PCH
FACH
RACH
DCH
DCH
R5 L1: HSDPA (NodeB) R5 L1: HSDPA (NodeB)

HS-SCCH HS-PDSCH HS-DPCCH
R4 L1: Channel Coding / /Multiplexing (NodeB) R4 L1: Channel Coding Multiplexing (NodeB)
S-CCPCH S-CCPCH PRACH DPCH DPDCH/DPCCH
1 93
In terms of flow multiplexing, the 3GPP specifications allow 3 types of multiplexing: Multiplexing at the logical channel level, meaning that several logical flows from a given user may be multiplexed over the same MAC-d entity. Multiplexing at the MAC-c/sh level, meaning that several MAC-d flows, either from the same or from different users, may be multiplexed over the same MAC-hs entity. Multiplexing at the MAC-hs level, which receives all the MAC-d flows and sub-flows. In UA04.2 only one single DTCH is supported over HSDPA (as the DCCH is supported over the associated DCH, and this version of HSDPA does not support multiple PS RAB for a single user).
7.2 TFRC Selection and channel coding
1 94
2.1 MAC-hs Architecture (UTRAN side)

to MAC-d MAC-d flows MAC-hs
TFRC Fields Value 2677 bits 4 QPSK 8103 bits 4 21.5 mW 5.4 mW 2 ms
Example:
Transport Block Size # codes Modulation Min. HARQ buffer size # MAC-d PDUs Total Tx Power Power per code
Flow Control
Scheduler
HARQ TFRC Selection
TTI
Associated Downlink Signaling

1 95
HS-DSCH
Associated Uplink Signaling

HSDPA induces an improvement of both the global throughput and the peak data rates per user and reduces the DL packet transmission delay mainly due to the introduction of a fast repetition layer at the NodeB characterized by: a new MAC entity (the MAC-hs) located in the NodeB. It manages the scheduling of users and the retransmissions of packets. a new transport channel, the HS-DSCH, whose transmission is based on shorter sub-frames: 2ms (TTI). a retransmission protocol, the HARQ (Hybrid Automatic Repeat Query) that handles fast repetitions of erroneous blocks (with possibly a change of the rate matching parameters that increases the global coding rate). a mechanism that adapts data format to radio conditions, the Adaptive Modulation and Coding (AMC), with the possibility of choosing between two modulations (QPSK and 16QAM).
Refer to Appendix for more details about MAC-hs PDU construction
2.2 HS-DSCH Coding Chain

CRC attachment Bit Scrambling Code Block Segmentation Turbo Coding HARQ Entity Physical Channel Segmentation HS-DSCH Interleaving Constellation Rearrangement (16QAM) Physical Channel Mapping R99 Modified Functionality R99 Functionality
New Functionality
1 96
Some coding steps are identical to the R4 functionalities applied to DCH: CRC attachment: 24 bits CRC length, Code Block segmentation, Channel coding: Turbo Code 1/3, Physical channel segmentation, HS-DSCH interleaving: R99 second interleaving (for 16QAM it is applied twice), Physical channel mapping. One step has been strongly modified: the HARQ functionality. It is a two-stage Rate Matching: The first stage corresponds to the R4 rate matching, except that it matches the input bits to a virtual buffer size instead of matching them to the number of physical channel bits (thats the purpose of the second stage). The second stage keeps the same structure than the R4 rate matching but the computation of the initial parameters is different and systematic bits may be punctured. The initial parameters are determined by the RV parameters. Two brand new functions are introduced: Bit scrambling Constellation rearrangement only applied in case of 16QAM.
2.3 HS-SCCH Coding Chain

OVSF Code Set Modulation Scheme MUX TBS HARQ
s, r, b RV Coding MUX CRC NDI
CC 1/3 Rate Matching
UEId CC 1/3 Puncturing
UE Masking MUX CC 1/3 Rate Matching
UE Masking
Slot #0: Code Set, Modulation
Slot #1: TBS, HARQ TSUBFRAME = 2ms
Slot#2: RV, NDI
1 97
The HS-SCCH is coded in two parts: the first part corresponds to the first slot and indicates the Transport Format and Resource Indicator (TFRI) i.e. the HS-PDSCH codes the UE must demodulate, and the modulation used (0:QPSK, 1:16QAM) the second part corresponds to the two last slots and indicates the transport block size (TBS), the RV parameters, the HARQ process index and the New Data Indicator (value updated for each new Transport Block transmission). Input bits of the first part are also injected for CRC computation. On the two parts, the UEId (H-RNTI provided by the RNC) is applied as a mask. The coding chain is given in the above figure.

1 98

Module 8 HSDPA Scenarios
8 Objectives
After this section, you will be able to Describe main procedures associated with HSDPA call establishment and mobility. Call Setup Mobility Iub Flow Control
1 100
8.1 Call Setup
1 101
8.1 Call Setup
1.1 Call Establishment

How is HSDPA triggered by the network?
3. DCH ? HS-DSCH ? Channel Type Selection 1. Request for service (e.g. Web Browsing)
RNC Node B Core Network
UE
4. HS-DSCH Establishment
2. RAB Assignment Request
1 102
8.1.1 Call Establishment
Channel Type Selection

HS-DSCH or DCH ? RAB assignment request from CN
RAB Traffic Class
Service = PS?
Traffic Class =
Streaming/ I/B
UE Capabilities
HSDPA UE?
HS-DSCH selection
Cell Capability
Primary Cell = HSDPA Cell?
1 103
With the introduction of HSDPA in the UTRAN, a new type of transport channel can be allocated to serve the RAB requested from the CN. Thus, the channel type selection algorithm allows selecting either DCH or HS-DSCH depending on the RAB characteristics received from the CN. At reception of a RAB assignment Request, the SRNC selects the transport channel type between DCH and HS-DSCH according to the following constraints: RAB traffic class Only PS RABs with traffic class interactive and background are transported on HS-DSCH. In UA06 Alcatel-Lucent support also the Streaming traffic class over HSDPA UE capability to support HS-DSCH HS-DSCH can be selected only if UE supports it, as indicated by the UE capability Support of HSPDSCH, and if UE supports the combination of already established DL DCH and HS-DSCH, as indicated by the UE capability DL capabilities with simultaneous HS-DSCH configuration Cell capability to support HS-DSCH HS-DSCH can be selected only if one cell of the active set supports HSDPA or if one collocated cell (on another carrier) supports HSDPA. Channel type selection is performed prior to radio admission control. Then depending on the channel type selection, either DCH RAC or HSDPA RAC is triggered.
8.1 Call Setup
1.2 Initial Connection Establishment

UE NodeB
RRC / RACH / RRC Connection Request
RNC
Establishment Cause AS Indicator
SGSN
NBAP / RL Setup Request NBAP / RL Setup Response SRB Definition (DCCH) U-RNTI Target RRC State (Cell_DCH) RRC / FACH / RRC Connection Setup RRC / RACH / RRC Connection Setup Complete HSDPA Capability UE Category
RRC / DCCH / Initial Direct Transfer (Service Request) RANAP / Service Request
RRC / DCCH / Measurement Control
1 104
Most of the steps of this first phase are common to all type of calls. There are few elements specific to HSDPA. RRC Connection Request embeds the Establishment Cause and the AS Indicator that may be used for Traffic Segmentation. RRC Connection Setup states the properties of the SRB to be used and includes a first Adio NEtwork Temporary Identifyer. RRC connection Setup Complete indicates to RNC UE capabilities.
8.1 Call Setup
1.3 RAB Assignment Phase

UE
NodeB
RNC
SGSN
RANAP / RAB Assignment Request
NBAP / RL Reconfiguration Prepare NBAP / RL Reconfiguration Ready NBAP / RL Reconfiguration Commit
Measurement Power Offset Scheduler & HARQ properties MAC-d PDU size HS-DPCCH properties
HS-SCCH Codes Number of HARQ
RRC / DCCH / Radio Bearer Setup RRC / DCCH / Radio Bearer Setup Complete
HS-SCCH Codes HARQ number and properties H-RNTI Measurement Power Offset HS-DPCCH properties
RANAP / RAB Assignment Response

1 105
In this second phase only the NBAP Radio Link Reconfiguration procedure and RRC Radio Bearer Reconfiguration are modified because of HSDPA.
8.2 Mobility
1 106
8.2 Mobility
2.1 Intra-Frequency Mobility

Core Network Primary cell change
RNC
RNC
NodeB
HS-DSCH Transition HS-DSCH Mobility HS-DSCH Mobility
NodeB Primary Cell
R4 cell
HSDPA cell
HSDPA cell
HSDPA cell
DCH only HS-DSCH+DCH
DCH Fallback
1 107
HS-DSCH Mobility
HS-DSCH Mobility
As defined by 3GPP HS-DSCH is established in only one cell so is never in soft handover. In Alcatel-Lucent implementation HS-DSCH is established in the primary cell because it is the best candidate (good radio conditions and not changing too often). Each time the primary cell changes the HS-DSCH RL is deleted on the former primary right after the RRC Measurement Control procedure has been performed, and it is re-established under the new primary, using a synchronous reconfiguration. If the new primary cell does not support HSDPA then the RB is reconfigured to DCH (iRM CAC is performed). If the new primary cell supports HSDPA while the former did not, and given that the UE supports HSDPA, then the RB is reconfigured to HS-DSCH (HSDPA CAC is performed).
8.2.1 Intra-Frequency Mobility
HS-DSCH Primary Cell Change

RNC Primary cell change RL Reconfiguration Prepare RL Reconfiguration Ready RL Reconfiguration Prepare RL Reconfiguration Ready RL Reconfiguration Commit (Activation CFN) RL Reconfiguration Commit (Activation CFN) RB Reconfiguration (Activation CFN) Measurement Control (new neighbouring list) Activation CFN RB Reconfiguration Complete source Node B target Node B UE
1 108
As defined by 3GPP HS-DSCH is established in only one cell so is never in soft handover. In Alcatel-Lucent implementation HS-DSCH is established in the primary cell because it is the best candidate (good radio conditions and not changing too often). Each time the primary cell changes, the HS-DSCH RL is deleted on the former primary and it is reestablished under the new primary, using a synchronous reconfiguration. During the reconfiguration data transfer on HS-DSCH is suspended by the RNC. If it is not possible to re-establish HS-DSCH on the new primary (CAC failure) then the radio bearer may fall back to DCH. If the new primary cell does not support HSDPA then the RB is reconfigured to DCH (iRM CAC is performed). In case of CAC failure for the DCH then the PS RAB is released. If the new primary cell supports HSDPA while the former did not and given the UE supports HSDPA, then the RB is reconfigured to HS-DSCH. In case of CAC failure the radio bearer stays on DCH. In the case the current primary cell is not present in the new active set, the HS-DSCH link is deleted right after the Active Set procedure (and before the Measurement Control procedure) and the UE releases the HSDPA link. A new HS-DSCH link is then setup using a normal SRLR procedure on the new primary cell after the Measurement Control.
8.2 Mobility
2.3 Inter-frequency HSDPA HHO with Measurements

Core Network
SRNC
HSDPA cell Frequency 2
R99 cell Frequency 1
1 109
The HSDPA Inter-freq mobility (HHO) with measurements (i.e. Compressed Mode on associated DCH) is supported with UA05. The feature values are to Enable HSDPA call handover to another cell based on criteria thresholds, avoiding drop calls and to allow HSDPA mobiles entering an HSDPA cell through an alarm handover to benefit from HSDPA service. UE solution supporting the Compressed Mode on DCH once in HSDPA operation (i.e. HS-PDSCH(s) usage).
8.3 Iub Flow Control
1 110
8.3 Iub Flow Control
3.1 Flow Control Principles
RNC Capacity Request Control FP
Iub
Data FP
Capacity Allocation Control FP
RNC Buffers QId0 QId1 QId2 QIdN QId0 QId1 QId2 QIdN
NodeB Buffers
1 111
With HSDPA, the effective throughput per UE is not deterministic and quite variable. A flow control mechanism has been introduced between the RNC Mac-d and the NodeB MAC-hs entities in order to fill the NodeB buffers with sufficient data to provide to the UEs and be quite reactive to throughput variations. This flow control mechanism is based on three main procedures: the Capacity Request procedure that provides means for the RNC to indicate for each session of each UE its buffer occupancy (at MAC-d level). the Capacity Allocation procedure generated by the NodeB to indicate to the RNC how many PDUs are required for the desired session and the interval in which data should be sent. This is based on the estimated throughput for this session and the amount of unsent data in NodeB transmission buffers. the HS-DSCH data transfer procedure in which the RNC sends the MAC-d PDUs grouped in FP frames (1 to 255 PDUs per FP frame). The updated buffer occupancy is also given. The RNC may choose to send all the required MAC-d PDUs in a single FP frame, or to space out (within the notified interval) the transmission in several FPs.
8.3.1 Flow Control Principles
3.2 HS-DSCH Capacity Allocation

Serving RNC
7. HS-DSCH Capacity Request
Priority Indicator, UE buffer Size
UE
Node B
HS-DSCH FP
HS-DSCH FP
8. HS-DSCH Capacity Allocation HS-DSCH FP

HS-DSCH credits, inter-TTI interval,
HS-DSCH FP
9. Data Transfer
MAC-hs
10. HS-SCCH
MAC-hs
After HS-DSCH Configuration
11. Data Transfer
NB.: The UE is in cell_DCH state

1 112
As soon as the SRNC detects the necessity to send HS-DL data on one HS-DSCH, it sends an HS-DSCH Capacity Request control frame within the HS-DSCH Frame Protocol to the CRNC. Parameters: Common Transport Channel Priority Indicator and User Buffer Size. The CRNC forwards this message (HS-DSCH Capacity Request control frame) to the Node B. So in this example sequence, the CRNC does not interfere with the HS-DSCH scheduling. Parameters: Common Transport Channel Priority Indicator and User Buffer Size. The Node B determines the amount of data (credits) that can be transmitted on the HS-DSCH and reports this information back to the DRNC in a HS-DSCH Capacity Allocation control frame in the HS-DSCH Frame Protocol. Parameters: Common Transport Channel Priority Indicator, HS-DSCH Credits, HS-DSCH Interval, HSDSCH Repetition period, Maximum MAC-d PDU length. The DRNC sends the HS-DSCH Capacity Allocation control frame to SRNC. So again, the DRNC does not react itself to that message in this example. Parameters: Common Transport Channel Priority Indicator, HS-DSCH Credits, HS-DSCH Interval, HSDSCH Repetition period, Maximum MAC-d PDU length. The SRNC starts sending DL data to the Node B. This is done via the two HS-DSCH Frame Protocol "hops" on Iur and Iub interface. The Node B schedules the DL transmission of DL data on HS-DSCH which includes allocation of PDSCH resources. The Node B transmits the control information for the concerned UE using the HS-SCCH. The Node B sends the HS-DSCH data to the UE on the HS-PDSCH(s).

1 113

Module 9 HSDPA A-L implementation
9 Objectives
After this section, you will be able to Compare HSDPA deployment options Evaluate HSDPA introduction impacts on UTRAN configuration Deployment Scenarios Configuration Impacts
1 115
9.1 Deployment Scenarios
1 116
9.1 Deployment Scenarios
1.1 Cell Topology

Coverage Options
HSDPA on shared carrier R99 only cell HSDPA cell R99/HSDPA cell
HSDPA on dedicated carrier
HSDPA on two carriers

1 117
HSDPA cells are not restricted to HSDPA services, they also offer all R99 services so there is no need to handover to the R99 layer to establish these services. Several deployment configurations are possible depending on the number of carriers and on the choice between dedicated carrier or shared carrier. Mono-frequency deployment with shared carrier leads to smooth transitioning from R99 only networks to HSDPA capable networks at minimum costs. Dual carrier networks with dedicated carriers for R99 offers the possibility to have independent management of the two types of traffic, providing more flexibility in terms of resource allocation, interference and capacity. Extra HSDPA capacity can be provided mixing dedicated and shared carrier cells inside a two-layered network. Some HSDPA hot-spots can also be introduced in single-carrier or dual-carrier networks.
9.2 Configuration Impacts
1 118
2.1 UTRAN HW Readiness

PA H S D DY REA RNC
CP RNSAP NBAP RANAP RRC
HSDPA L1 L2 (MAC-hs)
iCEM
BTS
. . .
PA H S D DY REA
MCPA DDM
UL DPDCH DPCCH DL DPDCH/DPCCH
iTRM iCCM iTRM iTRM DIGITAL SHELF
iCEM
. . .
MCPA
DDM
iCEM
. . .
UP RLC MAC
MCPA RF BLOCK
DDM
CEM
product parts or modules handling HSDPA
1 119
There are no UTRAN HW impacts triggered by the introduction of HSDPA, the evolution is managed via SW upgrade only. From an RNC point of view, all functionalities on both the CN and IN are exactly the same. There is just an evolution of the procedures and associated messaging protocols (NBAP, RRC...). From a BTSEquipment perspective, at the Layer 1 level, all functionalities on both the CCM and TRM boards (including the MCPA) are exactly the same. Only the introduction of the 16QAM modulation could have induced some impacts on the iCEM board but this constellation is generated as two QPSK modulations of different amplitudes. Consequently there are no HW impacts on the iCEM board as well.
2.2 Scalable BTS Configuration

UL HS-DPCCH DL HS-PDSCH HS-SCCH MAC-hs HARQ Scheduler Link Adaptation (AMC)
BTS
iCEM128
H-BBU H-BBU H-BBU D-BBU H-BBU
PA H S D DY REA
MCPA DDM
iTRM
iCEM128 UL Associated/R4 DPDCH Associated/R4 DPCCH DL Associated/R4 DPCH cmCHs
iCEM64
iCCM
iTRM
MCPA
DDM
iCEM64
D-BBU
MCPA
D-BBU D-BBU
DDM
CEM
iTRM
DIGITAL SHELF RF BLOCK
H-BBU
HSDPA dedicated DCH/cmCH dedicated
D-BBU
1 120
The HSDPA support on UMTS BTS requires Nortel second generation of CEM i.e. iCEM64 or iCEM128. Nortel CEM Alpha is not HSDPA hardware ready. Nevertheless, HSDPA support on Nortel UMTS BTS is possible assuming already installed CEM Alpha modules. CEM Alpha and iCEM modules can coexist within the NodeB digital shelf while providing HSDPA service with Nortel UMTS BTS. Base Band processing is performed by BBUs of CEM and iCEM. One restriction of current BBUs is that one BBU cannot process both Dedicated and HSDPA services. In order for the BTS to be able to manage both dedicated and HSDPA services, the BTS has to specialize BBUs as: D-BBU: BBU managing dedicated services, H-BBU: BBU managing HSDPA services. The partition between H-BBU and D-BBU is done by the BTS at BTS startup using OMC-B configuration information. Once this allocation is done, it can only change after a BTS-iCCM reset or an iCEM plug-in or plug-out.
2.3 BTS Configurations Examples

iCEM128
D-BBU D-BBU
MCPA iTRM
DDM
cell#0 cell#3 cell#1
iCEM64
H-BBU cell#0 cell#1 cell#2
iCCM iTRM
MCPA
DDM
STSR2 3 cells/H-BBU
F1 HSDPA cells F2 R99/HSDPA cells
cell#4 cell#2
iCEM64
H-BBU cell#0 cell#1 cell#2
MCPA
DDM
cell#5
iCEM128
H-BBU cell#0 H-BBU cell#1
MCPA iTRM
DDM
cell#0 cell#3 cell#1
iCEM128
H-BBU cell#2 D-BBU D-BBU D-BBU
iCCM iTRM
MCPA
DDM
cell#4 cell#2
STSR2 1 cell/H-BBU
F1 HSDPA cells F2 R99 cells
CEM
MCPA
DDM
cell#5
1 121
HSDPA is supported on STSR-1 and STSR-2 configurations (HSDPA can be deployed on one frequency or on two frequencies), OTSR configuration is not supported with HSDPA. The above figures present two different BTS configurations among the wide range of possible combinations. The first case represents a STSR2 with a multi-cell per H-BBU case, while the second figure illustrates a STSR2 configuration with one cell per H-BBU.
2.4 Multi-mode BBU with xCEM

WARNING 256 CE for DCH With a max of 128 CE for sig. Example: if 64 DCH Nb CE = 256 64 =192 CE for HSDPA
Limited before in the previous release
1 122
This feature introduces support for multi-mode Base-band Units (BBU) on the xCEM module. Multi-mode is understood as support of DCH + HSDPA + HSUPA channel types by the same BBU. This includes support of channel combinations {HSD+HSU}, {DCH+HSD}, {DCH+HSU}, and {DCH+HSD+HSU} for a given user. Multi-mode support includes the change from triple to single decoding. The xCEM board supports 256 DCH, with any 128 of them supporting HSDPA and/or HSUPA. This means that the initial xCEM capacity will be doubled with this feature by means of a SW upgrade. The additionally available capacity can be activated through the Capacity Licensing mechanism and requires purchase of respective licenses.
2.5 Interface Configuration with ATM

INVccGroup
VCC OAM VCC NodeBCP VCC CCP VCC DS traffic VCC NDS traffic VCC HSDPA traffic VPi/VCi VPi/VCi VPi/VCi VPi/VCi/PathId/QoSId VPi/VCi/PathId/QoSId VPi/VCi/PathId/QoSId
RNC
OAM CP CCP AAL5 ATM PCM
DS NDS HSDPA AAL2
New VCC New ATM Profile New QoSId
PCM link (1 up to 8 with IMA)
1 123
As HSDPA is a system evolution limited to UTRAN, HSDPA activation have no impact beyond the RNC. As HSDPA is not supported over Iur interface, the only interface modifications are related to Iub. HSDPA activation does not impact UTRAN interfaces Control Plane configuration. As mentioned earlier there is just a moderate evolution of the NBAP messaging. Evolution of RRC messaging does not impact the interface configuration needs for DS VCC. In fact the major evolution triggered by HSDPA introduction is the definition of a new type of VCC dedicated to HS-DSCH operation. There is just one HSDPA VCC per Iub, the configuration of this new VCC requires the definition of a dedicated ATM Profile together with the introduction of a new AAL2 QoS. The support of IMA with multi-PCM is necessary in order to be able to provide high user data rates, otherwise this may constitute the first bottleneck. Up to 8 PCM links can be managed by a single NodeB.
2.6 Smooth Evolution to IP

Optimized HSPA Offload Hybrid Iub
UA06
RNC
IMA = nE1 R99 over ATM E1 Leased Lines
x C C M
Node B
Ethernet
HSPA over IP Low Cost Backhaul
STM GigE
1 124
HYBRID IUB introduces a hybrid transport (ATM & IP) on the Iub interface on the RNC & Node B, as shown in Figure above. This functionality enables the operator to split delay sensitive traffic from non delay sensitive traffic. R99 traffic is carried on E1 to secure voice transportation as well as all delay sensitive traffic, whereas non-delay sensitive traffic is carried on IP over a private IP network. In the hybrid Iub interface the R99, signaling and OAM traffic remains on the ATM/PCM and the HSPA (HSDPA and E-DCH) is supported on IP/Ethernet. Hybrid Iub requires 100 BaseT Ethernet port (xCCM) in the NodeB and a Gigabit Ethernet board on the RNC side.
2.7 Core Network Impacts ATM configuration

HLR
new parameters Gr modified messaging
GGSN
Gn
SGSN
Iu-PS
RNC
RNC
VCC Streaming
SGSN
HSDPA specific procedures
VCC Interactive
R99 & HSDPA
VCC Background
R99 & HSDPA
PA H S D DY REA
PA H S D DY REA
1 125
VCC Conversational
HSDPA is a UTRAN only feature and the changes triggered by HSDPA introduction stop at the RNC. Beyond the RNC there is no R4 / HSDPA differentiation. HSDPA does not introduce any new procedure into the core network. There are just some changes in the QoS profiles and some new parameters introduced in the messaging. On Iu traffic is mapped on different VCCs depending on Traffic Class (Conversational, Streaming, Interactive or Background). R4 and HSDPA traffic with the same Traffic Class are mapped on the same VCC. There is no specific HSDPA VCC on Iu. HSDPA is expected to increase user traffic, which results in a higher throughput to be supported by the SGSN and the GGSN. Depending on the call profile, more traffic processing modules may be necessary. Dimensioning follows the same rules as for R4 traffic.
2.8 Core Network Impacts Iu-PS interface over Ethernet

Iu-PS over ATM Iu-PS over IP/Ethernet
1 126
Iu-PS interface is an open interface between the RNC and SGSN for the packet domain. ATM and IP stacks for Iu-PS are supported. On this interface, the SCCP supports transport of RANAP messages used by the Control Plane. ATM stack is like IU-CS interface refer to the description of previous slide. AAL5/ATM is be used to transport IP packets across the Iu interface towards the packet switched domain. IP stack uses the M3UA ( MTP-3 User Adaptation Layer) and SCTP ( Stream Control Transmission Protocol) to transport the signalling on IP network. UDP/IP is used for the User Plane. Dynamic management of GTP tunnel is ensured by user plane towards PS domain. The physical layer is supported by OC3/STM1 and aIP over Gigabit Ethernet. The Transport Network Control plane is not necessary on IU-PS.

1 127
End of Module HSDPA Description
1 128
Section 2 HSUPA Description

Module 1 HSUPA Fundamentals
1 Objectives
After this section, you will be able to: Describe the main objectives of the HSUPA solution. Identify the benefits of the new UL channels for the existing UMTS networks. Identify the characteristics of the HSUPA technique
Introduction
Definition Uplink before HSUPA
HSUPA Principles
Main characteristics Radio Resource Allocation NodeB level Main Benefits of HSUPA in UL
Exercise
Questions
22
HSUPA Description 9300 W-CDMA UA06 HSxPA Radio Principles
Table of Contents
Introduction
1.1 Introduction Definition 1.1 Definition Uplink before HSUPA 1.2 Uplink before HSUPA HSUPA Principles 1.2 HSUPA Principles 2.1 Main characteristics Main characteristics 2.2 Radio Resource Allocation Radio Resource Allocation 2.3 NodeB level 2.4 Main Benefits NodeB level of HSUPA in UL 1.3 Exercise Main Benefits of HSUPA in UL 3.1 Questions Exercise Self-Assessment on the Objectives End of Module Questions Page 7 8 9 10 11 12 13 14 15 16 17 18
23
1.1 Introduction
24
1.1 Introduction
1.1 Definition
- resource mgmt - retransmissions
Uplink
A A UP UP H HS
High Throughputs
Release 6 Release 6
Dedicated Channels
Throughput & Capacity

25
HSUPA Description 9300 W-CDMA UA06 HSxPA Radio Principles All Rights Reserved Alcatel-Lucent 2009
HSUPA (High Speed Uplink Packet Access) is the last item introduced by 3GPP with the aim to improve the Uplink (UL) data rate. HSUPA is characterized by a high data rate for PS calls over the UL air interface. The 3GPP objectives are to improve the performance of uplink dedicated transport channels by scheduling the Uplink UE data rates depending on the interference and on the Node B processing resources, while increasing the radio interface robustness with the HARQ (Hybrid Automatic Repeat Request) protocol associated with TTI of 2 ms and 10 ms. By reaching high spectrum efficiency and low latency for both the uplink and downlink with HSDPA/HSUPA, wireless operators will be able to provide seamless access services like VoIP, which can be challenging in UMTS R4 Network. HSUPA is not only a HSDPA for the reverse link. Of course, some of the mechanisms are inspired by the HSDPA solution (HARQ process, Incremental Redundancy, Scheduling) but more generally HSUPA is an enhancement of classical dedicated channels. Such new UL channels will be called in the following E-DCH channels. With HSUPA a new set of channels is proposed for UL and DL.
1.1 Introduction
1.2 Uplink before HSUPA

Low User Throughputs (<384 kbps) Poor spectral efficiency
HSDPA UE
Node B
RNC
Low Number of High data rate users
Low coverage For high data rate applications
26
Before the launch of the HSUPA solution, the operators have expressed their needs regarding the Access Network capabilities. Operator needs Higher coverage for high data rate applications A limited coverage for the UL DPCH @ 128kbps & 384kbps Higher number of high data rate users from a cell RF capacity standpoint NPole formula with 50% UL load, a limited number of high data rate DPCH in UL Higher user throughput on the Uu interface UMTS Rel99 allows UL peak rate @ 384kbps Most networks have been designed to ensure 64/128kbps Higher UL spectral efficiency for uneven traffic As HSDPA in DL, DCH usage in UL for uneven traffic leads to a waste of radio resource usage. PS call delay improvement To face these requirements, the 3GPP had to introduce the E-DCH new channel coupled with HSDPA: the HSUPA solution.
1.2 HSUPA Principles
27
2.1 Main characteristics
HSUPA
E-DCH, an enhanced Dedicated channel Fast scheduling at Node B level
(TTI: 10ms => mandatory), 2ms =>optional)
Fast retransmission of data QPSK modulation (~2 BPSK) Uplink Noise Rise management in nodeB Uplink resource management in nodeB
28
2.2 Radio Resource Allocation

9 R9 TS M
Dedicated Channel Dedicated Channel Dedicated Channel
HS
A DP
Shared Channel
HS
A UP
Enhanced Dedicated Channel Enhanced Dedicated Channel Enhanced Dedicated Channel
Allocated resources User traffic

29
The WCDMA system normally carries user data over dedicated transport channels, or DCHs, which brings maximum system performance with continuous user data. The DCHs are code multiplexed onto one RF carrier. In the future, user applications are likely to involve the transport of large volumes of data that will be bursty in nature and require high bit rates. HSDPA introduces a new transport channel type, High Speed Downlink Shared Channel (HS-DSCH) that makes efficient use of valuable radio frequency resources and takes into account packet data services burstiness. That new transport channel (HS-DSCH) shares multiple access codes, transmission power and use of infrastructure hardware between several users. The radio network resources can be used efficiently to serve a large number of users who are accessing bursty data. To illustrate this, when one user has received a data packet over the network, another user gets access to the resources and so forth. In other words, several users can be time multiplexed so that during silent periods, the resources are available to other users. With HSUPA, the resource is also shared among the HSUPA users but they each have an E-DCH (Enhanced Dedicated Channel). It uses a share of the uplink resources allocated in real time by the nodeB.
2.3 NodeB level Implementation Fast retransmission Uplink resource management

received power processing resources Iub bandwidth (UA6)
Benefits Lower latency Increased radio interface robustness

Overall UL QOS and throughput improvement
Optimized resource sharing

Increases more the nb of high data rate users
2 10
At nodeB level, we implement fast retransmission, and uplink resource management. The improvements allowed by this implementation are lower latency (better network responsiveness) Increased radio interface robustness, hence higher throughput Optimized resource sharing (resource allocated only if UEs use them so resources not used by some users are available for other users)
2.4 Main Benefits of HSUPA in UL

Bit rates UL throughput Nb high speed users Operational impacts: Spectral Efficiency UL resources Resource Sharing
Same hardware
Service Delay
Network Responsiveness
2 11
Introduction of new UL channels allowing high bit rate and global quick resources sharing is useful to map as a first step the best effort UL traffic (i.e. Interactive/Background traffic on E-DCH) keeping for DCH the UL Conversational/Streaming traffic class. E-DCH network introduction while being coupled with HSDPA (for which the same basic segmentation has been done DL Conversational/Streaming on DCH and DL Interactive/Background on HSDPA) enhances the spectral efficiency of UMTS technology versus live uneven traffic. Indeed, E-DCH/HSDPA maximizes the number of high data rate users from an air interface standpoint while minimizing the UL/DL service delay. By principle, E-DCH with HSDPA dynamically adapts and maximizes the peak data rate of each subscriber according to cell load and UTRAN resource availability.
1.3 Exercise
2 12
1.3 Exercise
3.1 Questions
What type of transport channel is introduced with HSUPA? Where are the main modifications implemented in the network? What is managed at that level? (Level = previous answer)
E-DCH, an Enhanced Dedicated Channel NodeB
Fast retransmissions Uplink resources Higher bit rates Higher number of high bit rate users Better resource sharing Higher spectral efficiency Lower service delay
Name 5 benefits of the HSUPA 1. technique.(In terms of throughput, 2. UL resources, network responsiveness) 3. 4. 5.
2 13

2 14

Module 2 HSUPA Channels
2 Objectives
After this section, you will be able to: Describe the new HSUPA channels that have been designed to allow high data rate for PS calls over the UL air interface. Introduction of new channels
HSDPA Channels HSUPA Channels Transport Channel Physical Channels Channels Roles
2 16
2.1 Introduction of new channels
2 17
1.1 HSDPA Channels
Logical
Signaling SRB Mobile x
DCCH
Traffic TRB Mobile x
DTCH
DTCH
Traffic TRB Mobile y
Transport
DL
DCH UL UL
DCH
HS-DSCH DL HS-PDSCH HS-SCCH HS-DPCCH
Physical
DPCCH
DPDCH
DPDCH
DPDCH
HS-DSCH HS-PDSCH HS-SCCH HS-DPCCH
Transport Physical Physical Physical
High Speed Downlink Shared CHannel High Speed Physical Downlink Shared CHannel High Speed Shared Control CHannel High Speed Dedicated Physical Control CHannel
2 18
Here is the whole set of existing channels: HSDPA channels:

HS-DSCH HS-PDSCH HS-SCCH HS-DPCCH Transport Physical Physical Physical High High High High Speed Speed Speed Speed Downlink Shared CHannel Physical Downlink Shared CHannel Shared Control CHannel Dedicated Physical Control CHannel
1.2 HSUPA Channels

Logical
Signaling SRB Mobile x
DCCH
DTCH
Traffic TRB Mobile y
DTCH
Traffic TRB Mobile x
Transport
UL
DCH DL
HS-DSCH DL
E-DCH UL
E-DPDCH
Physical
DPDCH
DPDCH
HS-PDSCH E-HICH HS-SCCH HS-DPCCH E-AGCH E-RGCH E-DPCCH
DPCCH
E-DCH E-DPDCH E-DPCCH E-HICH E-AGCH E-RGCH

2 19
Transport Physical Physical Physical Physical Physical
Enhanced Dedicated CHannel E-DCH Dedicated Physical Data CHannel E-DCH Dedicated Physical Control CHannel E-DCH HARQ Indicator CHannel E-DCH Absolute Grant CHannel E-DCH Relative Grant CHannel
Here are the new HSUPA channels: E-DCH Transport Enhanced Dedicated Channel What is E-DCH? It is an enhancement of classical dedicated channels. It can be divided into the following physical ones:
E-DPDCH Physical E-DCH Dedicated Physical Data Channel (data payload SF=16) E-DPCCH Physical E-DCH Dedicated Physical Control Channel (power control) E-HICH E-AGCH E-RGCH Physical E-DCH HARQ Indicator Channel (Ack / Nack SF=128) Physical E-DCH Absolute Grant Channel (scheduling) Physical E-DCH Relative Grant Channel (scheduling)
Note In the next section of this course, we are going to describe the frame structure of the new HSUPA channels.
1.3 Transport Channel New UL transport channel: E-DCH
Logical
Signaling SRB
DCCH
DTCH
Traffic TRB Mobile i
Transport
UL
DCH DL
HS-DSCH DL
E-DCH
UL
Physical
DPDCH
DPDCH
HS-PDSCH HS-SCCH HS-DPCCH E-HICH
E-DPDCH E-DPCCH
DPCCH
E-AGCH
E-RGCH
2 20
A specific E-DCH transport channel is defined. As the classical DCH transport channel it allows to offer transport services to higher layers. The E-DCH transport channel is defined by the following characteristics: Only for UL Two possible TTI : 10ms and 2ms Transport block size and Transport Block set size are free attributes of the transport format. Possibility of HARQ process with retransmission procedures applied at Node B. Max number of retransmission must be defined. Each transmitted blocks are numbered. Possibility of smart redundancy management at Rx. The Redundancy Version (RV) used for the transmission must be managed in order to apply Chase combining or Incremental Combining mechanisms. Turbo coding with rate 1/3 is used CRC is 24 bits length E-TFCI (Transport Format Combination Indication for E-DCH) indicates which format is currently used for the UL transmission.
1.4 Physical Channels

Logical
Signaling SRB
DCCH
DTCH
Traffic TRB
Transport
UL
DCH DL
HS-DSCH DL
E-DCH UL
Physical
DPDCH
DPDCH
HS-PDSCH HS-SCCH HS-DPCCH E-HICH
E-DPDCH E-DPCCH
DPCCH E-DCH E-DPDCH E-DPCCH E-HICH E-AGCH E-RGCH Transport Physical Physical Physical Physical Physical
Enhanced Dedicated CHannel E-DCH Dedicated Physical Data CHannel E-DCH Dedicated Physical Control CHannel E-DCH HARQ Indicator CHannel E-DCH Absolute Grant CHannel E-DCH Relative Grant CHannel
E-AGCH
E-RGCH
2 21
HSUPA includes a new set of new physical channels. Here are the basic functions of each channel: E-DPCCH and E-DPDCH for UL. The first one is devoted to control. The second is for UL traffic. E-HICH (HARQ Indicator Channel) in DL to indicate if the UL transmission are well received (ACK/NACK channel). E-AGCH (Absolute Grant Channel) and E-RGCH (Relative Grant Channel) in DL to indicate to the HSUPA UE (individually or per group) what are their allocated UL resources. This indication can be done using an explicit value (through e-AGCH) or relatively to the last allocated UL resources (with e-RGCH). We are going to deeply discuss the role of each physical channel in the following pages.
1.5 Channels Roles

Traffic & Signaling Scheduling
Dedicated
Dedicated
E-HICH
E-DPDCH
E-DPCCH
E-AGCH
E-RGCH
2 22
We can divide the new set of channels into 2 categories: traffic & scheduling. Scheduling channels E-AGCH carries E-DCH absolute grant. It indicates to the E-DCH UE (either individually or per group) what are their resources (absolute UL resources limitation). E-RGCH carries E-DCH relative grants. It is a dedicated channel for the Node B involved in the E-DCH active set. This channel allows each node B dealing with E-DPDCH to reduce the UE emitted power in order to avoid radio interferences. RGCH is not supported in UA5.0 Traffic & signaling channels E-HICH carries feedback information (ACK/NACK) sent by the Node B to indicate whether the packets are properly received. This channel is based on the Node B HARQ algorithm. Thanks to this channel, the Node B can send back to the UE indications about the faulty packets. E-DPDCH is the uplink channel that carries the user data ; TTI is either 10ms (mandatory supported by UE) or 2 ms (optional support). Modulation is the same as DCH. E-DPCCH is used to carry the uplink L1 signalling required to demodulate the E-DPCH: E-TFCI identity of the E-TFC selected, RSN (number of H-ARQ retransmissions) and happy bit (telling if the grants allocated to this UE are sufficient vs the amount data waiting in the transmission buffer).

2 23

Module 3 HSUPA Scheduling
3 Objectives
After this section, you will be able to: Identify the general principles of the scheduling mechanisms, including the grant allocation rules.
Scheduling Overview Grant Allocation for Scheduling

Grant Allocation Principles EDCH active set E-DCH Macro-Diversity Types of Scheduler UL Load Estimation Scheduling and granting criteria General Principles Channel Assignment
2 25
3.1 Scheduling Overview
2 26
1.1 General Principles

Main Steps
Frame #0 Frame #1 Frame #i
Scheduling info (SI) Format definition (TB) Traffic data (throughput)
1 3 4
Iub interface
2 5 6
2 27
Absolute Grant Ack / Nack Relative Grants
Like the HSDPA solution, the Node B is in charge of allocating the resources in terms of TTI, one after the other. Here are the main steps involved in the dialogue between the UE and the BTS:
1. 2.
The UE sends Scheduling Information (SI) to tell the Node B that it has data to send (via E-DPDCH). The Node B sends an Absolute Grant corresponding to the maximum uplink power resource the UE can use (via E-AGCH). According to the grant it has received, the UE can select an E-TFCI in the E-TFCS table that is compatible with the power granted, to send data in UL (via E-DPCCH). The Transport Block size is agreed. The UE sends data in uplink along with a throughput that can dynamically vary according to the grants of power it receives. The Node B sends either ACK or NACK on E-HICH. If the Node B sends a NACK, the UE retransmits the data based on the same process. The Node B may send Relative Grant on E-RGCH at any time to adapt (increase or decrease) the maximum uplink power resource used by UE.
3.
4.
5.
6.
All these steps can take place at every TTI (Transmission Time Intervall). The TTI can be either 10 ms or 2 ms (optional).
1.2 Channel Assignment

Scheduler
Absolute Grant Ack / Nack Relative Grants
2 5 6
E-DPDCH
E-AGCH
E-DPCCH
E-DPDCH
E-HICH
E-RGCH
6 1 3 4
Scheduling info Format definition Traffic data

2 28
This slide shows the role of each HSUPA channel when the UE requests to send data. Scheduler goals The Scheduler is the key element of the HSUPA solution. It is in charge of two major tasks: It manages E-DCH cell resources between UEs, It deals with uplink radio interferences. What is Scheduling Information? It is a message reported by UE to indicate the current status of its waiting list. The UE available power results from: UE Power headroom)/ highest priority level /queue total size percentage occupied by the queue of higher priority One main constraint of the scheduler consists in supporting fairness among users according to their Queue priority level: 15 levels of priority, ensure a minimum access for each active UE. With the introduction of the MAC-e protocol in charge of the scheduling, the Node B becomes smarter as a decision-making centre. Protocol layers functions , including MAC-e, are thoroughly described in section 4 of this course.
3.2 Grant Allocation for Scheduling
2 29
2.1 Grant Allocation Principles

Total interference contribution
Allocated Power / interference contribution decides which transport format can be used, so which throughput is available
Absolute & relative grants
BTS UEn Interference contribution
UE1 IC UE2 IC UE1 UE2
UE3 IC
UEn
UE knows which Transport format it can use Required power to use the ETFC
RNC sends correspondence info at call setup
UE3
ETFC ETFC ETFC ETFC ETFC z ETFC ETFC ETFC ETFC ETFC
Node-B Grants a certain power
Acronyms TFC: Transport Format Combination (E-TFC => E-DCH) TFCI: Transport Format Combination Indicator (E-TFCI => E-DCH)
2 30
UE might use all or part of the allocated power
The scheduling principles give the ability to the Node-B to control the set of TFCs a UE may use. More precisely, the MAC protocol layer is in charge of the selection of the appropriate Transport format for each Transport channel, using the Transport Format Combination Set (TFCS) assigned by the RRC. Grants are allocated to each E-DCH UE. These UEs can then tune the power level at which they are allowed to transmit. Each UE can adapt its throughput according to the grants by selecting the E-TFC in the E-TFCS that is compatible with the granted power. Grants are valid until new ones are sent. Mobiles can be addressed individually (primary E-RNTI) or in groups (secondary E-RNTI). A UE may be active or inactive on E-DCH. Any inactive UE has no grant allocated (grants are zero). To send data, it has to send a Scheduling Information (SI) message to ask for grants. Grants functions The scheduling system is based on grants. Grants are computed by the scheduler: to ensure some fairness between al users. to prevent the global UL interferences level from exceeding a threshold (RTWPmax standing for Received Total Wideband Power). to make sure each UE will adapt its throughput on E-DPDCH according to the grants it has received.
2.1 Grant Allocation Principles [cont.]

Types of grants Absolute grant
Node-B
Absolute value E-AGCH Scheduling: (e-RNTI, Scheduling Grant)

H GC -A E
Ha y pp
Bi
Help! More resources!
CH PC -D H E GC -R E
Relative grant
+/E-RGCH Scheduling : (up, DTx, down)
2 31
The serving cell directly controls the UE requests through the scheduling channels based on absolute / relative grants: Absolute grants (i.e. E-AGCH) are allocated to the UE by the serving cell. Relative grants (i.e. E-RGCH) are very useful in order to dynamically regulate (up / down) the power of the UE. They prevent the serving cell from interfering (called basting) with non serving cells. (No RGCH in UA5.0) The E-RGCH is in charge of sending scheduling messages to the UEs belonging to the UE Active Set: Serving cell: E-RGCH = up, DTx, down Non serving cell: E-RGCH = DTx, down (where DTX stands for Discontinuous Transmission). Receiving one down command, the e-DCH UE reduces its uplink data throughput (i.e. E-TFCI). At one time, a given mobile phone listens to a signature sequence carried by a E-RGCH channelization code (up to 40 different sequences can be carried by a E-RGCH code). The happy bit carried by the E-DPCCH indicates if the grants allocated to this UE are sufficient to face the amount of data waiting in the transmission buffer.
2.2 EDCH active set

Node-B Serving EDCH Radio Link Set Non Serving EDCH Radio Link Set Non Serving EDCH Radio Link Set Node-B
Node-B NodeB Serving EDCH cell
1 HICH AGCH RGCH
RGCH
1 RGCH for this UE 1 HICH for this UE 1 Serving EDCH cell: cell from which the UE receives the Absolute Grant 1 Serving EDCH RLS: set of cells containing the Serving EDCH cell from which the UE can receive and combine 1 single RGCH (and 1 HICH). It contains cells from the same nodeB. 1 or more non-serving EDCH RLS: cells which belong to the EDCH active set and from which the UE can receive an RGCH HSUPA capable UE
2 32
E-DPDCH + EDPDCH
Max 4 RL in the E-active set. UA5.0: EDCH active set =serving EDCH RLS
There is one single serving radio-link and up to four non-serving radio-links, forming the E-DCH active set. This E-DCH Active Set is a sub-set of the active set. Channel Assignments The UE is assigned one E-HICH channel per radio-link, allowing to perform a HARQ per-radio-link control of the link. The UE is assigned one E-AGCH channel (on the serving cell). At the serving cell level, the UE is assigned one E-AGCH channel and possibly one E-RGCH (Up, down or DTX commands) channel on which it will be assigned grants. We call non serving RLS the other cells that belong to the E-DCH active set, excluding the serving RLS. These RLS are able to send a Relative Grant to the UE. At the non-serving cell level, the UE is assigned one E-RGCH channel (down or DTX commands) to allow to control the level of interferences that it generates.
2.3 E-DCH Macro-Diversity

EDCH Non Serving RLS EDCH Serving RLS#1
Node-B Node-B
EDCH Non Serving RLS

Node-B
Node-B
E-DPDCH and EDPCCH HICH Relative Grant Absolute Grant Associated DCH
2 33
HSUPA capable UE
EDCH macro diversity: HSUPA channel repartition 1 EDCH serving cell (ie 1 AGCH) Multiple nodeB EDCH control (ie EDPCCH) and data (ie EDPDCH) One or more HICH and RGCH the E-active set. Is a subset of the active set
Here are the functions of each involved cell shown in the slide above: The serving cell (RLS#1) is the unique cell that directly controls the UE requests through the scheduling channels (absolute / relative grants). The non serving cells (RLS#2 & RLS#3 above) are only involved in case of the SHO (soft handover) situation. Since their main objective consists in dealing with active UEs, they shouldnt waste their own radio resources to ensure radio-diversity. The e-DCH Macro diversity can be defined in terms of HSUPA channels repartition: One single serving e-DCH cell (i.e. E-AGCH) Multiple Node-B E-DCH control (i.e. E-DPCCH) & data (i.e. E-DPDCH) demodulation One or more E-HICH & E-RGCH (from serving and non-serving cells) In short, the E-DCH macro-diversity depends on the available processing resources.
2.4 Types of Scheduler

UL Load Interference Contribution Allocation of the whole capacity, shared equally by all mobiles. =>the higher the cell capacity, the lower the user data rate.
Rate scheduling
(UA05 & UA06)
Time
Interference Contribution UL Load Allocation at each TTI, allowing mobile throughput to peak. =>the higher the targeted user data rate, the lower the cell capacity.
Time scheduling
(UA06)
Time
2 34
The main target of the scheduler is to grant UEs so that the total UL load of the cell stays near the target load (RTWPmax), but not above. If the uplink load gets above this limit, then the scheduler will reduce the grants of the E-DCH links. In case of radio overload (due to other traffics : CCH, DCH, inter-cell interferences and other interferences), the grants of E-DCH links may get down to 0. If the UL load is below the limit then the E-DCH UEs will be granted more. Two kinds of scheduler are available : time scheduling scheme: similar to HSDPA. Allocation at each TTI, allowing mobiles throughput to peak. i.e. the higher the targeted user data rate, the lower the cell capacity rate scheduling scheme. Allocation of the whole capacity shared equally by all mobiles. i.e. the higher the cell capacity, the lower the user data rate.
2.5 UL Load Estimation

RTWP = Received Total Wideband Power Rise Over Thermal: RoT = RTWP / Thermal Noise FDDCell
RTWPref + totalRotMax
typical: 6dB (=75% UL load)
BTSCell
Available load rtwpMaxCellLoadNonEdch

typical: 50% (=3dB) Increase to cope with EDCH interf.
E-DCH traffic
R99 CAC, BTS level. Measure sent to RNC for cell color management
R99 traffic + Interference RTWPref Thermal Noise
R99 traffic + Interference
Thermal Noise
No E-DCH
2 35
With E-DCH
Rise Over Thermal: RoT = RTWP / Thermal Noise Two thresholds are defined: - Max RTWP for total UL traffic (R99/E-DCH). - Max RTWP for non E-DCH traffic only used for R99 CAC at the cell level. E-DCH traffic is assigned the unused UL load up to the max RTWP. Once an R99 call is accepted, it will not be dropped even if the non E-DCH load exceeds the max specified. Non E-DCH load (i.e. R99 + interference) will increase to cope with the E-DCH interference (as it was the case for HSDPA). RTWP measure is regularly sent by the BTS to the RNC for cellColor. The RNC calculates RoT using Thermal Noise value.
2.6 Scheduling and granting criteria
NOK
RoT < RoTmax RoT < RoTmax
OK
Scheduling Criteria
Algorithm:Rate or time
UE UE Sorting Sorting (de-grant mgt) (de-grant mgt)
UE UE Scheduling Scheduling
Fairness:data already served, Prio,
Resource Status Resource Status Update Update
Grant Grant Management Management
Grant Grant Transmission Transmission
Granting / de-granting Criteria

Shared resources:UL cell load, Processing resources, nb AGCH and RGCH, Iub bandwidth UE resources: Power headroom, data
2 36
HSUPA scheduling strategy will result from a trade-off between: The max number of HSUPA users per cell, The targeted average user data rate. Scheduling criteria The scheduling algorithm / strategy UA05: Rate scheduling i.e. the higher the cell capacity, the lower the user data rate. UA06: Time scheduling i.e. the higher the targeted user data rate, the lower the cell capacity. Fairness a) UA05: amount of data already served b) UA06: Priority Information + UL radio link QoS + Iub bandwidth Granting & De-granting Criteria Grant on shared resources UL cell load, Processing resource availability, Number of E-AGCH, E-RGCH available Grant on private UE resources UE power headroom information, UE payload (data already served). Note: RoT = Rise over Thermal

2 37

Module 4 HSUPA HARQ
4 Objectives
After this section, you will be able to: Identify the general principles of the scheduling mechanisms with H-ARQ. Compare HSUPA characteristics with HSDPA ones
H-ARQ Process
Exercices
Stop And Wait HARQ Processes HARQ Mechanisms Soft HO Data Transmission Example HSUPA versus HSDPA
2 39
4.1 H-ARQ Process
2 40
4.1 H-ARQ Process
1.1 Stop And Wait HARQ Processes

HARQ
Wait for Transmission UE has resources for transmission Update RV Parameters Transmit Data
E-HICH
Wait for ACK/NACK Reception ACK/NACK ACK Insert DTX Indication
ACK/NACK/DTX?
NACK
DTX
Reset & Free HARQ Process
Nret = Nret + 1
TB
YES Nret > Nret_max NO
HARQ HARQ
TB
2 41
Once a UE is scheduled, a HARQ process is assigned that may correspond to either a new Transport Block transmission or a TB retransmission. The RV parameters are computed accordingly and data is transmitted. The HARQ process is then waiting for feedback information (ACK / NACK / DTX): In case of ACK reception, the HARQ process is reset and corresponding MAC-d PDUs are removed from memory. This HARQ process can now be used for a new transmission. In case of NACK reception, the number of retransmissions must be incremented. If the maximum number of retransmissions is not reached, the HARQ process is inserted in the NACK list of HARQ processes asking for retransmission. In case of DTX indication, the same actions as for NACK reception are performed, except that a parameter must be updated to notify DTX detection (this changes the RV parameter update). After a NACK reception or a DTX indication, the HARQ processes are just waiting for being re-scheduled for a new retransmission. Note DTX stands for Discontinuous Transmission: it is used on Radio interface to switch-off the radio activity during the silent times until the conversation resumes. DTX indication is used when there is no ACK/NACK reception.
4.1 H-ARQ Process
1.2 HARQ Mechanisms

RV0 RV1 RV2
Data 1 Data 1 Data 2 Data 2 Data 3 Data 3 Data 4 Data 4 Data 5 Data 5 Data Data 2 Data 6 Data 7 Data 8 Data 2 Data 2 Data 6 Data 9 Data 10 Data 11 Data 12 Data 13
Ack Nack Ack Transmissions Ack Ack Nack Ack/nack Nack Ack Ack Ack Ack Ack Ack Ack Ack Ack
Data 1 Data 2 Data 3 Data 4 Data 5 Data 2 Data 6 Data 7 Data 8 Data 2 Data 6 Data 9 Data 10 Data 11 Data 12 Data 13
Process Process Process Process
0 1 2 3
To next step (demultiplexing) combining

Data 1 Data 3 Data 4 Data 5 Data 7 Data 8
combining combining
Data 2 Data 6 Data 9 Data 10 Data 11 Data 12 Data 13
2 42
The HARQ process (Hybrid Automatic Repeat reQuest) is based on a similar scheme as for HSDPA, directly handled by Node B and UE. The E-HICH relies on the Node B HARQ algorithm. It handles retransmissions. Thanks to this channel, the Node B can send back to the UE indications about the faulty packets. There are few differences between HSDPA & HSUPA solutions: HSUPA works in SHO and is based on synchronous retransmissions in the uplink. Downlink: HARQ based on synchronous ACK/NACK There is a well-defined timing relationship between reception of the transport block and transmission of the acknowledgement by the Node B. Uplink: HARQ based on synchronous retransmissions Fix number of Stop-and-Wait HARQ processes 8 processes for 2ms TTI 4 processes for 10ms TTI Maximum number of retransmissions configured per MAC-d flow.
4.1 H-ARQ Process
1.3 Soft HO Data Transmission Example

Physical Channels
E-AGCH 1. Absolute Grant E-DPCCH 2a. E-TFCI(1) 6a. E-TFCI(2) 10a. E-TFCI(1) E-DPDCH 3a. Data Tx(1) 7b. Data Tx(2) 11a. Data Tx(1) E-HICH 4a. NACK(1) 8a. ACK(2) 12a. NACK(1) E-DPCCH 2b. E-TFCI(1) 6b. E-TFCI(2) 10a. E-TFCI(1) E-DPDCH 3b. Data Tx(1) 7b. Data Tx(2) 11b. Data Tx(1) E-HICH 4b. NACK(1) 8b. ACK(2) 12b. ACK(1)
2 43
Transport Channels
Serving E-DCH cell E-DCH FP 5. Void ! 9a. Data Tx(2) 13a. Void
RNC UE Ctxt
RLS
UE
Nonserving E-DCH cell
14. Data Reordering/ Combining
E-DCH FP 5. Void 9b. Data Tx(2) 13b. Data Tx(1)
RLS
This operation occurs in soft handover situations (SHO): Intra Node B and inter Node B macro-diversity are supported by the HSUPA solution. Multiple Node Bs transmit HARQ ACK/NACK in DL. The reliability of the signalling is essential to avoid desynchronisation of the Node Bs buffers and ACK/NACK errors. In softer handover, cells belonging to the same Node B transmit the same HARQ ACK/NACK information (same RLS). Resynchronisation of HARQ instances at the Node B are implicitly performed, based on Retransmission Sequence Number.
4.2 Exercices
2 44
4.2 Exercices
2.1 HSUPA versus HSDPA

Question: what are the differences and similarities between HSDPA and HSUPA?
HSDPA
1. HS-PDSCH, a Shared channel 2. Fast scheduling at Node B level (TTI: 2ms) 3. Fast retransmission of data (H-ARQ usage) 4. Adaptable radio modulation (QPSK and 16-QAM) 5. Downlink radio quality & downlink resource management
HSUPA
1. E-DCH, an enhanced Dedicated channel 2. Fast scheduling at Node B level (TTI: 10ms => mandatory), 2ms =>optional) 3. Fast retransmission of data (H-ARQ usage) 4. Basic radio modulation QPSK only (BPSK) 5. Uplink Noise Rise & uplink resource management
2 45
Obviously, HSDPA and HSUPA are two different techniques that share lots of basic mechanisms. 1+1 Coupling the usage of both HSDPA in DL and HSUPA, these mechanisms highly enhance the spectral efficiency of UMTS technology versus live sporadic traffic. Indeed, HSxPA maximizes the number of high data rate users from a air interface usage standpoint while minimizing the UL/DL service delay with high peak rate. By principle, HSUPA with HSDPA dynamically adapts and maximizes the peak data rate of each subscriber according to cell load and UTRAN resource availability. Implementation The feature is a software-only upgrade based solution as far as the minimum processing power required in the Node-B is available i.e. one iCEM BBU (E-BBU) at least to handle the Node-B HSUPA L1/L2 software.

2 46

Module 5 HSUPA Protocols
5 Objectives
After this section, you will be able to: Describe the new MAC entities belonging to the MAC architecture. Identify the functional roles of the MAC-e and MAC-es within the global architecture. Identify the frame structure of each physical channel and their own characteristics. MAC Entities Physical Channel Frame Structure Frame Protocols Exercise
2 48
5.1 MAC Entities
2 49
5.1 MAC Entities
1.1 Protocol Layers
RLC (Radio Link Control) Logical Channels MAC (Medium Access Control) Transport Channels
Transport sublayer Physical Channels Physical sublayer PHY (PHYsical Layer)
2 50
UMTS relies on the concept of logical channels, characterized by the type of information that is transferred and transport channels which are described by how and with what characteristics the data is transferred over the air interface. The mapping between the logical and transport channels is performed by the MAC (Medium Access Control) sub-layer. MAC main functions: Mapping between logical channels and transport channels Selection of appropriate Transport Format Priority handling between data flows of one UE Priority handling between UEs Identification of UEs on common channels Multiplexing/ demultiplexing of higher layer PDUs Traffic volume monitoring Ciphering Access Service Class selection for random access transmission
5.1 MAC Entities
1.2 UTRAN Protocol Layers
DTCH DCCH
DCCH DTCH
MAC -d
MAC -d
MAC -es / MAC -e MAC -e MAC -e EDCH FP
MAC -es EDCH FP
PHY
PHY
TNL
TNL
TNL
TNL
Uu UE Node B
Iub
D RNC
Iur SRNC
2 51
Here are the main functions of the new protocol layers within the UTRAN subsystem: At UE level: MAC-es / MAC-e handles HARQ retransmissions, scheduling and MAC-e multiplexing, EDCH TFC selection. At Node B level: MAC-e handles HARQ retransmissions, scheduling and MAC-e de-multiplexing. At SRNC level: MAC-es provides in-sequence delivery (reordering) and handles duplication avoidance (combining) in case of inter Node B soft handover. Note Layers above MAC are left unchanged. In section 4, we will discuss more deeply the functions of the protocol layers.
5.1 MAC Entities
1.3 MAC Entities

Logical Channels
BCCH PCCH BCCH CCCH CTCH DCCH DTCH
MAC Control (RRC)
MAC-b
MAC-c/sh
MAC-d
MAC-hs
MAC-es /MAC-e
Transport Channels
BCH PCH FACH RACH DCH DCH HS-DSCH (downlink) E-DCH (uplink)
2 52
The diagram above describes the MAC architecture. It is built upon MAC entities. The four entities are assigned the following names: MAC-b is the MAC entity that handles the following transport channels. It is located in the Node B. broadcast channel (BCH) MAC-c/sh, is the MAC entity that handles the following transport channels: paging channel (PCH) forward access channel (FACH) random access channel (RACH) MAC-d is the MAC entity that handles the following transport channels: dedicated transport channel (DCH) MAC-hs is the MAC entity that handles the following transport channels: high speed downlink shared channel (HS-DSCH). MAC-e/es are the MAC entities that handle the following transport channels: Enhanced dedicated transport channel (E-DCH) Note The exact functions completed by the entities are different in the UE from those completed in the UTRAN.
1.3 MAC Entities
1.3.1 NodeB
MAC flows -d
MAC-e
Cell resources between UE
Scheduling
Flow Control MACes PDUs Scheduling /
De-multiplexing
requests grants MACe PDUs
Control
HARQ entity
Fast transmisson. retrans
HARQ entity
TRFC selection
Associated Downlink signalling
E-HICH/ E-AGCH/E-RGCH
Associated Uplink signalling
E-DPCCH
E-DPDCH
2 53
The MAC-e and E-DCH scheduler comprises the following entities: E-DCH Scheduling: This function manages E-DCH cell resources between UEs. Based on scheduling requests, Scheduling Grants are determined and transmitted. E-DCH Control: The E-DCH control entity is responsible for reception of scheduling requests and transmission of Scheduling Grants. De-multiplexing: This function provides de-multiplexing of MAC-e PDUs. MAC-es PDUs are forwarded to the associated MAC-d flow. HARQ: One HARQ entity is capable of supporting multiple instances (HARQ processes) of stop and wait HARQ protocols. Each process is responsible for generating ACKs or NACKs indicating delivery status of E-DCH transmissions. The HARQ entity handles all tasks that are required for the HARQ protocol.
5.1.3 MAC Entities
1.3.2 RNC
To MAC -d
MAC -es
Disassembly
Disassembly
Disassembly
MAC Control
Reordering/ Combining
Reordering/ Combining
Reorderi ng/ Combining
Reordering Queue Distribution
Reordering Queue Distribution
MAC -d flow #1
MAC -d flow #n
From MAC -e in NodeB #1 2 54

From MAC -e in NodeB #k
The MAC-es comprises the following entities:

1. Reordering Queue Distribution:
The reordering queue distribution function routes the MAC-es PDUs to the correct reordering buffer based on the SRNC configuration.
2. Reordering:
This function reorders received MAC-es PDUs according to the received TSN and Node-B tagging i.e. (CFN, subframe number). MAC-es PDUs with consecutive TSNs are delivered to the disassembly function upon reception. Mechanisms for reordering MAC-es PDUs received out-of-order are left up to the implementation. There is one Re-ordering Process per logical channel.
3. Macro diversity selection:
The function is performed in the MAC-es, in case of soft handover with multiple Node-Bs (The soft combining for all the cells of a Node-B takes place in the Node-B). This means that the reordering function receives MAC-es PDUs from each Node-B in the E-DCH active set.
4. Disassembly:
The disassembly function is responsible for disassembly of MAC-es PDUs. When a MAC-es PDU is disassembled the MAC-es header is removed, the MAC-d PDUs are extracted and delivered to MAC-d.
5.1 MAC Entities
1.4 MAC-e Scheduling

Max RoT provided by the RNC
NOK
Uplink interferences level acceptable?
RoT
OK
UE UE Sorting Sorting (de-grant mgt) (de-grant mgt)
UE UE Scheduling Scheduling
Processing capacity
Processing performed in the nodeB
Resource Status Resource Status Update Update
Grant Grant Management Management
Scheduling
Grant Grant Transmission Transmission
2 55
The grants computed by the scheduler are limited by two factors: the global uplink interferences level must not go above a certain threshold (RTWPmax standing for Received Total Wideband Power).. the BTS processing capabilities dedicated to E-DCH. The RNC will provide the RTWPmax and RTWPref to the BTS. This will be interpreted as the maximum Rise Over Thermal that the scheduler shall consider. The BTS will use a self-learned RTWPref for the scheduling, so the RTWPmax considered by the BTS may be different (above or below) than the one given by the RNC. BTS impacts The scheduling functions are managed in the BBU (1 BBU per iCEM64 & 2 BBU per iCEM128). One E-BBU (a specific BBU managing HSUPA services) can handle up to 15 UEs. 1 BBU HSUPA per Node B => 15 UEs for the Node B (BBU=Base Band Unit; iCEM=Channel Element Module)
5.2 Physical Channel Frame Structure
2 56
2.1 E-DPDCH / E-DPCCH Frame Structure

Tslot=2560 chips, 10x2k bits (k=0 7)
E-DPDCH Structure
(Uplink Data Channel)
Slot #0 Slot #1
Data (N bits)
Slot #2
Slot #i
Slot #14
One E-DPDCH subframe (TTI=2ms =3 time slots) One radio frame (10 ms)
Tslot=2560 chips
E-DPCCH Structure
(Uplink Control Channel)
Slot #0
ETFCI
RSN (HARQ)
Happy Bit
Slot #1
Slot #2
Slot #i
Slot #14
Carries control signaling:

ETFCI: 7 bits (selected TFC) RSN: 2 bits (number of HARQ retransmissions) Happy bit: 1 bit (grant OK for UE)
One E-DPDCH subframe (TTI=2ms =3 time slots) One radio frame (10 ms)
2 57
(The E-DCH transport channel is associated with 2 UL physical channels: E-DPDCH & E-DPCCH. ) E-DPDCH (UL) It carries the UL traffic. The Spreading Factors: 256, 128, 64, 32, 16, 8, 4, 2 TTI is either 10 ms (mandatory) or 2 ms (UE capability). Multi-code is used only at SF=2 and SF=4. E-DCH introduces the use of H-ARQ in uplink on the E-DPDCH (like HSDPA in downlink) directly handled by Node B and UE, allowing for fast retransmissions. The number of H-ARQ processes is 8 (for TTI 2ms) or 4 (for TTI 10ms). Recombining is done using Chase Combining or Incremental Redundancy. Slot Format: Slot Format #i 0 1 2 3 4 5 6 7 Channel Bit Rate (kbps) 15 30 60 120 240 480 960 1920 SF 256 128 64 32 16 8 4 2 Bits/ Frame 150 300 600 1200 2400 4800 9600 19200 Bits/ Subframe 30 60 120 240 480 960 1920 3840 Bits/Slot Ndata 10 20 40 80 160 320 640 1280
2.2 E-HICH Frame Structure

E-AGCH Structure
Power Grant Grant Scope CRC (by E-RNTI)
Carries EDCH absolute grant:

Power granted (5 bits) Grant scope: 1bit CRC XORed by E-RNTI (UE Id) (16 bits) Tslot=2560 chips
b1,0 b1,0
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
One subframe (TTI=2ms =3 time slots)
One radio frame (10 ms)
E-HICH Structure
b1,0

+1 = ACK
Carries H-ARQ ack:
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
One subframe (TTI=2ms =3 time slots) One radio frame (10 ms)
0 = NACK by non serving nodeB (=DTX) -1= NACK by serving nodeB
E-RGCH Structure
b1,0 b1,0
b1,0
Carries relative grant:

+1 = up (serving nodeB only) 0 = DTX -1= down
2 58
Slot #0
Slot #1
Slot #2
Slot #i
Slot #14
One subframe (TTI=2ms =3 time slots) One radio frame (10 ms)
E-AGCH (DL) It carries E-DCH Absolute Grant. The structure is similar to HS-SCCH (UE specific CRC) It indicates to the E-DCH UE what are their allocated UL resources (absolute UL power resources limitation). It uses E-RNTI to target UE or groups of Ues, It works with serving E-DCH cell only The SF is fixed to 256. AGCH can be transmitted in 2ms. In 10ms TTI, the AGCH lasts for 10ms. It consists of repetitive sending of 2ms messages. E-HICH (DL) It shares the same OVSF codes as the E-RGCH and has the same structure. UEs are differentiated by the signature. There is a set of 40 signatures per code, allowing to address several UEs at the same time. E-HICH carries the H-ARQ acknowledgement indicator: +1 = ACK ; 0 = NACK by a non-serving Node B (means DTX); -1 = NACK by the serving Node B. The indicator is multiplied by the signature of the UE for the E-HICH (40 bits) When the E-DCH is in soft handover (not supported in this release), the UE will consider that the HARQ process has been correctly received if at least one Node B reports an ACK. On the non serving cell, the HICH lasts for 10ms(not used in UA5.0) E-RGCH (DL) (Not available in UA5.0) It carries E-DCH Relative Grants: 1/0/-1 transmitted from serving RLS to indicate UP/HOLD/DOWN 0/-1 transmitted from non serving RLS to indicate HOLD/DOWN It works with serving and non-serving E-DCH cells. It shares the same OVSF codes as the E-HICH and has the same structure. It allows to increase or decrease the resource limitation. UEs are differentiated by the signature: the E-RGCH relies on signature to target a UE or group of UEs. A given mobile listens to a signature sequence carried by an E-RGCH channelization code. 40 different sequences can be carried by a E-RGCH channelization code (can send information to 40 UEs per TTI per E-RGCH+E-HICH)
2.3 OVSF for DL control channels

SF128 SF256 SF16 SF32 SF64 SF4 SF8
0 0 1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Common channels (1 S-CCPCH)

2 4 5 6 7 8 9 10 11 18 19 20 11
S-CCPCH #2 S-CCPCH #3 HS-SCCH (2 for ex) E-HICH and E-RGCH E-AGCHs

DL HSUPA channels are allocated just after the HS-SCCH codes
1 3
2 1 3
4 2 5
6 3 7
Free OVSF codes HS-PDSCH
Dynamic DL code tree management
2 59
5.3 Frame Protocols
2 60
5.3 Frame Protocols
3.1 Iub Frame Protocol Configuration

Same VCC (possible addition for capacity reasons), Different CID
EDCH FP contents
User data transmission Only the correctly decoded MAC-es PDU HARQ failure indications RNC congestion indications DDI info (logical channel, MAC-D flow, MAC-D PDU size) CFN: indicates when HARQ decoded correctly (identifies the TB) +subframe nb in case of 2ms TTI N: nb of HARQ retransmissions
2 61
The E-DCH Frame Protocol for the Iub interface has several objectives: User data transmission of E-DCH traffic between BTS and RNC, HARQ failure indication from BTS to RNC, Transport Network Congestion indication from RNC to BTS. The FP data PDU contains the MAC-es PDUs that have been correctly decoded in the MAC-e PDU of the TTI. If the MAC-e PDU contains several MAC-d flows then they are demultiplexed and sent on their respective transport bearers (in UA5.0, only 1 MAC-d flow is supported on E-DCH so this is not applicable) so using distinct E-DCH FP DATA frames. For a HSUPA data session, there at least 3 Frame Protocol contexts used over the Iub, as illustrated by the picture above.
1.
The first Frame Protocol supports the associated DCH, i.e. uplink and downlink signaling, and is mapped on a dedicated CID (DS QoS). Another Frame Protocol on DCH may be used support a CS service established in parallel of the PS I/B service. The E-DCH Frame Protocol supports the uplink part of the user packet data traffic. It is mapped on a dedicated CID on the UBR QoS VCC (which has lower priority that DS and NDS VCC) which is the same VCC as the HS-DSCH one (but using different CIDs).
2.
3.
CID= AAL2 Channel ID, CFN=Connection Frame Number, TB=Transport Block
5.4 Exercise
2 62
5.4 Exercise
4.1 Physical Channels

Associated DPDCH for SRB traffic Associated DPCCH HS-DPCCH Feedback information (CQI, Ack/Nack) HS-SCCH Signaling part (UE id, ) HS-PDSCH for Mono PS I/B traffic E-DPDCH for Mono PS I/B traffic (and optional SI) E-DPCCH Feedback information (e-TFCI, RSN, Happy bit) E-HICH Feedback information Ack/Nack, signature) E-AGCH Scheduling information (e-RNTI, Absoute Grant)
Node-B
HSPA-capable Rel6 UE
R6 R99 R5
Task: Identify the physical channels used when making traffic in HSUPA. In UA5.0 (No multiservice)
2 63

2 64

Module 6 HSUPA Scenarios
6 Objectives
After this section, you will be able to: Describe the main procedures associated with E-DCH call establishment and mobility
Call setup Procedure

Call Establishment Initial connection RAB allocation phase
Primary cell change
6.3 DCH Fallback Procedure
Intra-Frequency Mobility HSUPA over Iur
2 66
6.1 Call setup Procedure
2 67
1.1 Call Establishment

How is HSUPA triggered by the network?
3. DCH ? E-DCH ? Channel Type Selection 1. Request for service (e.g. Web Browsing)
RNC Node B Core Network
UE
4. E-DCH Establishment
2. RAB Assignment Request
2 68
6.1.1 Call Establishment
Channel Type Selection

E-DCH or DCH ? RAB assignment request from CN
RAB Traffic Class
Service = PS?
HSDPA in DL ?
Cell Capability
E-DCH in Cell?
E-DCH selection
UE Capabilities
HSUPA UE?
2 69
With the introduction of HSUPA in the UTRAN, a new type of transport channel can be allocated to serve the RAB requested from the CN. Thus, the channel type selection algorithm allows selecting either DCH or E-DCH in UL depending on the RAB characteristics received from the CN. At reception of a RAB assignment Request, the SRNC selects the transport channel type between DCH and E-DCH according to the following constraints: RAB traffic class Only PS RABs with traffic class interactive and background are transported on HS-DSCH UE capability to support E-DCH E6DCH can be selected only if UE supports it, as indicated by the UE capability Support of E-DCH, and if UE supports the combination of already established DL DCH and HS-DSCH, as indicated by the UE capability. Cell capability to support HS-DSCH E-DCH can be selected only if the serving cell also supports HSDPA. Channel type selection is performed prior to call admission control. Then depending on the channel type selection, either DCH RAC or HSxPA RAC is triggered.
1.2 Initial connection

UE Node B RNC SGSN
RRC/RACH / RRC connection Request Cause Access Stratum Release Indicator (R6? R5?) NBAP/ RL setup Request NBAP/ RL setup Response
RRC/FACH/RRC connection Setup RRC/DCH/ RRC Connection Setup Complete EDCH? HSDPA? + UE Category RRC/DCCH/Initial Direct Transfer (Service Request) GMM/Service Request RRC /DCCH/ Measurement control X 4
2 70
This step is similar to non E-DCH calls. The RRC connection request establishment cause might be used for traffic segmentation, as well as Access stratum release indicator. After RRC connection complete, the RNC has a full knowledge of the UE capabilities.
1.3 RAB allocation phase

UE NodeB RNC SGSN
Security functions: Authentication and Ciphering + Security mode
GMM activate PDP context Request

e-DCH-MACdFlow-ID, PowerOffsets AGCH, RGCH, HICH, PowerOffset EDPCCH), Reference ETFCI PO, TTI HARQ (RV table, max retrans )
RANAP/RAB Assignment Request NBAP/Radio Link Reconfiguration Prepare
AGCH OVSF code ERNTI (1&2) RGCH HICH OVSF code HICH signature initial serving grant value
NBAP/Radio Link Reconfiguration Ready
NBAP/Radio Link Reconfiguration Commit

Same as RL Reconf Prep + ERNTI (1&2) AGCH, RGCH,HICH OVSF HICH signature Initial serving grant
RRC/Radio Bearer Setup RRC/Radio Bearer Setup Complete
RANAP/RAB Assignment Response GMM activate PDP context accept
2 71
In this phase, only the NBAP Radio Link Reconfiguration procedure and RRC Radio Bearer Reconfiguration are modified because of E-DCH.
6.2 Primary cell change
2 72
2.1 Intra-Frequency Mobility
Node-B
Node-B
Node-B
Non Serving Cell#1
Serving cell
DCH in Macro diversity
Non Serving Cell#2
Non Serving Cell#3
Primary cell change
UE
E-DCH control and data E-HICH Absolute Grant Associated DCH (in SHO)
E-DCH macro-diversity in UA06

2 73
Mobility of associated DCH Soft and softer handovers are handled on the associated DCHs. The Active Set is managed differently according to the reporting mode (periodic or intra-frequency event triggered). Mobility of HS-DSCH As specified by the 3GPP standards, HS-DSCH is established in only one cell: never in soft handover. In Nortel implementation, HS-DSCH is established on the primary cell (since good radio conditions and not changing too often). Each time the primary cell changes, the HS-DSCH RL is deleted on the former primary and established under the new primary, using a synchronous reconfig. If the new cell does not support HSDPA then the RB is reconfigured to DCH. Moreover, anytime an HSDPA-capable mobile (operating in DCH mode) enters an HSDPA primary cell it is reconfigured to HSDPA. Mobility of E-DCH There is only one serving E-DCH radio-link and it is established in the same cell as the HS-DSCH radio-link. The mobility of the E-DCH serving link is based on the same principles as the HS-DSCH one. In case of primary cell change, the E-DCH serving link and the HS-DSCH link are moved at the same time (one procedure). If the new primary cell does not support HSUPA then the RB is reconfigured to DCH in UL (maintained on HS-DSCH in DL if the cell supports HSDPA). On the opposite, it is reconfigured to E-DCH if the mobile returns to HSUPA coverage.
Primary cell change E-DCH

RNC Primary cell change RL Reconfiguration Prepare RL Reconfiguration Ready RL Reconfiguration Prepare RL Reconfiguration Ready RL Reconfiguration Commit (Activation CFN) RL Reconfiguration Commit (Activation CFN) RB Reconfiguration (Activation CFN, new E-RNTI, Serving E-DCH RL, E-AGCH info, E-HICH info) source Node B target Node B UE
Measurement Control (new neighbouring list)

Activation CFN RB Reconfiguration Complete
2 74
E-DCH is established only on Primary cell of the Active Set (UA5.0) Each time the primary cell changes, the E-DCH RL is deleted on the former primary and it is reestablished under the new primary, using a synchronous reconfiguration. The HS-DSCH is reconfigured at the same time.
Event 1J
CPICH_EC/No
Event1J
E-ASET Cell ASET Cell entering reporting range leaving reporting range InE-ASET Cell
Event 1J (specific to E-DCH Macro Diversity): Definition: The CPICH of a cell that is in DCH AS but not in EDCH AS becomes better than the CPICH of a cell that is already in E-DCH AS
2 75
Event 1J (specific to E-DCH Macro Diversity): Definition: The CPICH of a cell that is in DCH AS but not in E-DCH AS (cell B) becomes better than the CPICH of a cell that is already in E-DCH AS (cell A). Action triggered: Cell A is removed from the E-DCH AS and replaced by cell B (provided that cell B supports current E-DCH Configuration). Remark: Event 1J is only configured when the Full-Event Triggered reporting of measurements mode is used for intra-frequency mobility. Primary Cell change: When Primary Cell changes, E-DCH serving cell is changed to the new Primary Cell. If the new Primary Cell does not support current E-DCH Configuration: - E-DCH Configuration is changed to match E-DCH capabilities of the new Primary Cell. - If E-DCH Configuration is changed to a more restrictive one (e.g. 10ms TTI 2ms TTI), any cell of E-DCH AS not supporting the new E-DCH Configuration is removed from E-DCH AS. If the new Primary Cell does not support E-DCH, the E-DCH RB is reconfigured to UL DCH. Remark: All cells removed from DCH AS and present in E-DCH AS are also removed from E-DCH AS
2.2 HSUPA over Iur
2 76
The feature ensures a seamless mobility for HSUPA calls while a user moves from a SRNC to a D-RNC through the Iur interface. The HSUPA over Iur capability is required in both the S-RNC and D-RNC to allow the handling of the configuration, maintenance, release of active HSUPA call over Iur. In HSUPA mode, the SRNC configures the radio link with E-DPCH and E-DCH Information and the characteristics of HSUPA service is decided by the property of Primary Cell. As a Serving RNC, the decision to configure an existing RL over Iur with HSUPA is taken when a cell belonging to a neighbouring RNC is added to the active set and the cell is able to be compliant with the existing HSUPA service. The request is sent to the neighbouring RNC using a RNSAP radio link setup/addition/reconfiguration prepare message with E-DPCH and E-DCH information. The UE is configured accordingly. As a Drift RNC, a radio link is configured to HSUPA when the DRNC receives a RNSAP radio link setup/addition/reconfiguration prepare message with E-DPCH and E-DCH Information. Bearing in mind the Iur dimensioning constraint for certain customers, the feature can be deactivated, in which case a DCH fall back solution is offered to maintain the call continuity when crossing the Iur. This may also be needed for IOT scenarios.
2 77
HSPA to DCH Fallback (1)
Primary cell change
Max users HSU or HSD Rab assignment
NBAP or RNSAP failure
Core Network
Inter RNC HHO Alarm HHO
2 78
HSPA to DCH fallback feature allows establishing or reconfiguring the PS I/B RAB into DCH in case of HSDPA or HSUPA CAC failure. The following HSxPA CAC failure scenarios trigger such a fallback: RAB assignment (to establish or to release) IU release Primary Cell change Inter-RNC UE involved Hard Handover Alarm Hard Handover In case of HSPA CAC failure, i.e. lack of resources, HSPA to DCH fallback feature allows reconfiguring UL and/or DL into DCH as if UE was not HSUPA and/or HSDPA capable, mainly based on failure causes: Internal to RNC: maximum number of HSDPA or HSUPA users External to RNC: NBAP or RNSAP failure causes

2 79

Module 7 HSUPA A-L implementation
3JK10674AAAAWBZZA Issue 1
9300 W-CDMA UA06 HSxPA Radio Principles TMO18043 Issue 1
7 Objectives
Upon completion of this module, you should be able to:
Describe the different scenarios of deployment for UMTS Radio Access networks. Identify the main parameters associated with the HSUPA / E-DCH solution. Recognize the main hardware and software requirements for the BTS configuration.
Deployment Scenario BTS Hardware Configuration HSUPA power Control
2 81
7.1 Deployment Scenario
2 82
HSXPA/ R99 DEPLOYED IN 1 SHARED FREQUENCY
F1
Layer with R99/ HSxPA
HSXPA capable UE
HSDPA capable UE
R99 UE
2 83
This configuration does not require any 3G inter-layer mobility and iMCTA CAC by default to save the R99 call by performing HHO to 2G neighboring cells when necessary. Concerning Performance aspect, HSXPA throughput could be limited by Power & by Codes and R99 could potentially be impacted by interference generated during HSXPA activity period. In term of hardware cost, it is the cheapest one with only 1 E-BBU and 1 H-BBU mandatory.
HSXPA AND R99 DEPLOYED IN 2 DEDICATED CARRIERS
Layer with HSDPA / HSUPA
F2
HSDPA / HSUPA capable UE
Traffic Segmentation feature (UA4.2) launched at RRC connection establishment Or iMCTA feature (Intelligent MultiCarrier Traffic Allocation)
R99 Layer
F1
R99 UE
2 84
In this configuration, mobiles are spread over the layers: either by Traffic Segmentation feature (UA4.2) launched at RRC connection establishment: it allows to separate R99 UEs from R5/R6 UEs. It is not applicable in the case there are 2 layers which are both HSDPA. or at RAB assignment by the iMCTA service feature, or at primary cell change by the iMCTA service feature. Since HSxPA traffic and R99 traffic separated, neither HSxPA interference in R99 carrier nor HSxPA Throughput limited by Power are expected. Concerning capacity, Free codes and power available on layer 1 will not be available for HSXPA traffic (and vice-versa). The Hardware requirements are at least 1 H-BBU, 1 E-BBU & 1 TRM (if 1 carrier previously). Globally, it should be a likely configuration chosen if already 2 dedicated carrier deployed in UA4.2 or traffic increase. Interesting U5.0 cell topology for 2 main reasons: to avoid R99/ HSXPA cohabitation issue & so safe configuration for R99/HSXPA performance. Traffic segmentation usage & avoid bad impact of Compress Mode for static HSxPA UEs.
MIXED HSxPA/ R99 SHARED CARRIER AND R6 HSxPA DEDICATED CARRIER
Layer with HSxPA
F2
HSDPA / HSUPA capable UE
Layer with HSxPA/R99
F1
R99 UE
HSDPA capable UE
2 85
RRC Traffic Segmentation is not possible in this configuration since the system can not distinguish R6 and R5 HSDPA calls. Therefore, only usage of iMCTA Service is possible to redirect R6 HSxPA on F2 Moreover, HCS activation is mandatory to select always F1 R99 could be potentially impacted by interference generated during HSxPA activity period and by Compressed Mode generated at each HSUPA call established on F1. On contrary, this is an optimum configuration for HSUPA Throughput since no cohabitation between HSUPA and UL DCH traffic is forecasted. iMCTA service partitioning is favored vs. load balancing and could lead to waste of resources. The minimum hardware requirements are at least At least 2 H-BBU, 1 E-BBU & 1 TRM (if 1 carrier previously). Globally, this is an expensive UA5.0 Cell Topology which is possible in localized HSDPA hot spots inside mono-carrier area. Interesting U5.0 cell topology for 2 main reasons: to reach the best HSUPA Performance (only R6 PS calls on F2) to allow R5 HSDPA service continuity in F1 inside mono-frequency area
MIXED HSxPA/ R99 SHARED CARRIER AND HSXPA/ R99 SHARED CARRIER
F2
Layer with R99/ HXUPA

R99 UE HSDPA capable UE
HSXPA capable UE
Layer with HSxPA/R99
F1
R99 UE
HSDPA capable UE
2 86
RRC Traffic Segmentation is not possible in this configuration since the system can not distinguish R6 and R5 HSDPA calls. Therefore, only usage of iMCTA Service is possible to redirect R6 HSXPA on F2. Moreover, HCS activation is mandatory to select always F1 R99 potentially impacted by interference generated during HSXPA activity period and by Compressed Mode generated at each HSUPA call established on F1. R99 PS UL Traffic could degrade HSUPA Throughput. Load balancing between frequencies is possible for R99 calls. The minimum hardware requirements are at least 2 H-BBU, 1 E-BBU & 1 TRM (if 1 carrier previously). This is an expensive UA5.0 Cell Topology interesting for its resource usage capabilities but no guarantee on the HSUPA Performance. Therefore no deployment is currently forecasted in UA5.0.
DEDICATED R99 CARRIER AND HSxPA/ R99 SHARED CARRIER
R99 UE
F2
Layer with R99/ HXUPA
HSXPA capable UE Traffic Segmentation feature (UA4.2) launched at RRC connection establishment Or iMCTA feature (Intelligent MultiCarrier Traffic Allocation)
R99 Layer
F1
R99 UE
2 87
This is a scenario foreseen by some customers that wants to expand R99 capacity. RRC Traffic Segmentation & iMCTA service will be used to redirect the R5+ call on HSDPA layer. HSxPA throughput could be limited by DL Power limitation or by DL OVSF Code limitation. Therefore, it is recommended to assess the DL Power Usage & the OVSF Code Usage to activate properly the Dynamic Code Tree Management. Load Balancing is triggered to re-direct R99 call when shared carrier is loaded (Red or Yellow color). The minimum Hardware required is at least 1 H-BBU, 1 E-BBU & 1 TRM (if 1 carrier previously). This is a probable configuration chosen if high traffic of R99 inside HSxPA/ R99 shared carrier area. Interesting U5.0 cell topology for 2 main reasons: to use iMCTA load balancing to share R99 load Traffic segmentation usage and to avoid bad impact of Compress Mode for static HSxPA UEs
7.2 BTS Hardware Configuration
2 88
iCEM architecture (1)

MAC-e HARQ decoding E-DSC(s) scheduling UL Link demodulation/decoding DL scheduling PhCH(s)
MAC-hs HARQ HS-DSCH scheduling Link Adaptation (adaptive coding & modulation) UL DPCCH(s) HS-DPCCH(s) DL HS-PDSCH(s) HS-SCCH(s) UL DPCCH(s) E-DPCCH(s) E-DPDCH(s) DL E-HICH E-AGCH E-RGCH UL Associated/R99 DPDCH(s) Associated/R99 DPCCH(s) CCH(s) DL Associated/R99 DPDCH/DPCCH(s) CCH(s)
Nortel Networks UMTS BTS

iCEM128
H-BBU E-BBU D-BBU
iTRM
MCPA
DDM
iCEM128 iCEM64 xCEM CEMa
D-BBU H-BBU
iCCM
iTRM
MCPA
DDM
D-BBU D-BBU D-BBU D-BBU D-BBU D-BBU
iTRM Digital Shelf
MCPA
DDM Radio Shelf
2 89
This slide shows the repartition of the roles between BBUs within the CEM boards. It indicates where the radio links (physical channels) and retransmissions mechanisms (HARQ, scheduling,) are managed. Here is the Node-B HSxPA software mapping architecture: CEM BBU (H-BBU) with HSDPA software to handle HSDPA radio links CEM BBU (E-BBU) with HSUPA software to handle E-DCH radio links CEM BBU (D-BBU) with classical UMTS L1 software to handle the DCHs, the associated HSDPA DCH and the Cell CCHs. iCEM 64 has 1 BBUs that can be used as any of the above types. iCEM 128 has 2 BBUs that can be used as any of the above types. xCEM has 4 BBUs that can be used as any of the above types. The CEM alpha can only be used for R99.
iCEM architecture (2)
HS-DPCCH HS-PDSCH(s) HS-SCCH(s)
H-BBU
iCEM 64 Or iCEM 128
E-DPCCH E-DPDCH E-HICH E-AGCH E-RGCH DPCCH / DPDCH
E-BBU
iCEM 64 Or iCEM 128
iCEM 64
D-BBU
Or iCEM 128 Or CEM a
DPCCH & DPDCH
: Dedicated PhCH
2 90
: Shared PhCH
Local cell allocation for HSUPA When a local cell has to be configured in HSUPA, the BTS has to allocate the local cell on 3 BBUs: 1 D-BBU for the DCH part 1 H-BBU for the HSDPA part 1 E-BBU for the HSUPA part Note In UA5.1, an E-BBU can work only in shared mode. The E-BBU is managing 1 LCG (3 cells) on iCEM and 2 LGC (6 cells) on xCEM per NodeB. Only 1 iCEM E-BBU per NodeB is supported in UA5.1 in standard configuration
E-BBU Capacity on iCEM

iCEM
2 91
The iCEM capacity for HSUPA is given by the E-BBU limitation in terms of: Maximum number of users = 15 Maximum number of codes = 3 x ( 2x SF4) Throughput at MAC-E level = 2.1 Mbps Number of cell per BBU = 3 The xCEM capacity for HSUPA is given by the E-BBU limitation in terms of: Maximum number of users = 64 Throughput at air interface = 7.7 Mbps Number of Cells = 6 capacity for HSUPA is given by the E-BBU limitation in terms of: Maximum number of users Throughput Number of Cells le: E-BBU Resources allocation at call admission
2 PERFORMANCE
E-BBU Capacity on xCEM

WARNING 256 CE for DCH With a max of 128 CE for sig. Example: if 64 DCH Nb CE = 256 64 =192 CE for HSDPA
Limited before in the previous release
2 92
This feature introduces support for multi-mode Base-band Units (BBU) on the xCEM module. Multi-mode is understood as support of DCH + HSDPA + HSUPA channel types by the same BBU. This includes support of channel combinations {HSD+HSU}, {DCH+HSD}, {DCH+HSU}, and {DCH+HSD+HSU} for a given user. Multi-mode support includes the change from triple to single decoding. The xCEM board supports 256 DCH, with any 128 of them supporting HSDPA and/or HSUPA. This means that the initial xCEM capacity will be doubled with this feature by means of a SW upgrade. The additionally available capacity can be activated through the Capacity Licensing mechanism and requires purchase of respective licenses.
2 PERFORMANCE
xCEM HSPA capacity evolutions on 2 carriers
xCEM configuration example Strategy : STSR 2, 2xCEM, 2 carriers HSDPA + E-DCH
2 93
The feature increases HSPA capacity and performance, in particular the Queuing Delay, if many HSUPA users want to become active at the same time the number of HSUPA users supported per cell the performance for HSDPA traffic that does not conform to FTP/HTTP, in particular for traffic with very low packet sizes. This will become essential for VoIP traffic in a future release.
For HSUPA, the MAC-e scheduler on the xCEM supports at least 2 E-AGCH channels per cell target is 48 E-AGCH channels per xCEM board. the Node B supports at least 4 E-HICH Channelization codes per cell. The Node B provides a signature administration for 40 signatures per E-HICH channelization code. A pre-defined number of 1..4 signatures will be reserved for common E-RGCH usage, the remainder is available for dedicated E-RGCH/E-HICH usage on each E-HICH Channelization code. For HSDPA, the xCEM will support 4 HS-SCCH channels per cell (24 HS-SCCH channels per board).
7.3 HSUPA power Control
2 94
7.3 HSUPA power Control
E-DCH signaling channels Power Control

The power control for AGCH is based on CQI
HS-DSCH
DL Data Transfer (PS I/B)
E-DCH
UL Data Transfer (PS I/B)
In UA5.1.1 AGCH Power Control based on CQI
RNC Iub
E-AGCH
Absolute Grant
HS-DPCCH
Feedback Information (CQI)
The final AGCH Tx power = E-DCH reference Tx power + eagchPowerOffSet (OMC-B) The E-DCH reference Tx power is given by a hard-coded LUT using the CQI
2 95
The power control for AGCH is based on CQI The AGCH is only sent by the serving radio leg Since HS-DSCH is the DL RB for HSUPA CQI is always available Fast update period (each CQI) The final AGCH Tx power PAGCH is then given by PAGCH = PEDCH base + eagchPowerOffSet (OMC-B) The reference Tx power is given by a hard-coded Look Up Table using the CQI and the mean square error of the CQI, i.e. PEDCH base = LUT(CQI, MSE(CQI))+PCPICH+-mean(CQI)+ The MSE takes the channel variations into account is set to +3 dB in UA05.1 The OMC-B parameter eagchPowerOffset allows further control of the Tx power This offset is a positive or negative constant offset across all CQI values The parameter range is from 45 dB to +65 dB
7 Answer the Questions

1. 2. 3.
What is the minimum number of BBUs to be present on a BTS to activate HSUPA ? Which is the physical channel used to control the EDPCCH and EDPDCH power? What is the maximum number of simultaneous EDCH active users on E-BBU?
2 96
End of Module HSUPA Description
2 97
Last But One Page

1
@@PRODUCT @@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent
All Rights Reserved Alcatel-Lucent @@YEAR @@COURSENAME - Page 2

Wcdma

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Wcdma

Caricato da

Copyright:

Formati disponibili

9300 W-CDMA UA06 HSxPA Radio Principles

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

Terms of Use and Legal Notices

All rights reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

4. Topic/Section is Positioned Here 5. Topic/Section is Positioned Here 6. Topic/Section is Positioned Here

4. H-ARQ for Fast Retransmission 1. Topic/Section is Positioned Here

5. HSDPA Scheduling Mechanism

2. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent 2009

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

Welcome to UA06 HSxPA Radio Principles

All Rights Reserved Alcatel-Lucent 2009

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

About this Student Guide

9300 W-CDMA UA06 HSxPA Radio Principles

Where you can get further information

All Rights Reserved Alcatel-Lucent 2009

About this Student Guide [cont.]

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

Instructional objectives 1 To be able to XXX

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2009

Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:

Section 1 HSDPA Description

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 1

HSDPA Solution Main Facts

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 2

1.1 What is HSDPA?

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 3

1.1 What is HSDPA?

1.1 HSDPA Key Points

Radio Access Technology

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 4

1.1 What is HSDPA?

1.2 What HSDPA has been designed for?

In the following material we will only refer to HSDPA in FDD mode

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 5

1.1 What is HSDPA?

1.3 A new shared channel: HS-DSCH

1.2 HSDPA Solution Main Facts

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 7

1.2 HSDPA Solution Main Facts

2.1 Theoretical Peak User Data Rates

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 8

1.2 HSDPA Solution Main Facts

2.2 HSDPA Market Applications

All Rights Reserved Alcatel-Lucent 2009 Section 1 Page 9