OUT LINE:

1-Why HSDPA????
2-Architecture. 3-MAC-hs sub-layer.

4-Scheduling in HSDPA.
5-Hyprid Arq and soft combining in HSDPA. 6-Data flow of HSDPA.

1-Shared channel transmissions

In 3G the transmission is through dedicated channels. HSDPA introduced shared channel transmission,

where there is no dedicated channel or assigned codes, but there are a set of codes of SF 16 are time multiplexed between users through different TTIs. Shared channel transmission is simplified through introduction of HS-DSCH. The idea is that the node B performs 3G dedicated channel transmissions and the remaining power is assigned to HSDPA users, which maximizes the power efficiency of NB as it is always sending with max. power.

-Same as the WCDMA but there is extra MAC sublayer inserted in the node B to increase its functions which will decrease the signaling and will tend to faster adaptation to rapid variation. -Minimization of the architectural changes is desirable as it simplifies introduction of HSDPA in already deployed networks and also secures operation in environments where not all cells have been upgraded with HSDPA functionality.

-Each UE using HSDPA will receive HS-DSCH transmission from one cell, the serving cell. -Mobility from a cell supporting HSDPA to a cell that is not supporting HSDPA is easily handled. -Uninterrupted service to the user can be provided, albeit at a lower data rate, by using channel switching in the RNC and switch the user to a dedicated channel in the non-HSDPA cell. Similarly, a user equipped with an HSDPA-capable terminal may be switched from a dedicated channel to HSDPA when the user enters a cell with HSDPA support.

RNC functions:
RNC will :

Admission control
Decide if a new user can join this cell or no.

based on the Node B power.

-Done by measuring power of Node B.

Congestion control:
There are another signaling processes beside previous

ones as the streaming services. MAC-d priority queue must b taken into account.

How measurements are done:

3-MAC-hs sub-layer
As mentioned before, the MAC-hs is a new sub-layer

located in the Node B and responsible for: 1) the HS-DSCH scheduling, 2)rate control 3) hybrid-ARQ protocol operation. So the functions of the Node B has increased and now, it is the Scheduler.

-scheduling

determines system performance. -In HSDPA the scheduler (node B) decides which user , HS-DSCH should be transmitted and at what data rate. -efficient scheduling strategies require at least: information about the instantaneous channel conditions at the UE. information about the buffer status and priorities of the data flows.

-Every UE send channel condition indicator (CQI) to node at regular intervals. -This CQI is calculated at the UE based on the SNR of the pilot signal. -CQI is expressed as recommended transport-block sized taking into account the receiver performance. -So terminal with more advanced receiver will report large CQI and will receive data at higher rate than the one with less advanced receiver at same channel conditions.

Details of HSDPA scheduling:

In addition to to channel quality, scheduler should take into account buffer status and perriority queues.
Example :-streaming services.

-RRC signaling (handover between 2 cells). -UEs for which there is no data awaiting transmission should not be scheduled.

5-Hyprid-ARQ and soft combining

Hybrid-ARQ retransmissions are therefore

significantly less costly in terms of delay compared to RLC retransmissions. Due to: 1. There is no need for signaling between the Node B and the RNC for the hybrid-ARQ retransmission. Consequently, any Iub/Iur delays are avoided for retransmissions. 2. The RLC protocol is typically configured with relatively infrequent status reports of erroneous data blocks (once per several TTIs) to reduce the signaling load, while the HSDPA hybrid-ARQ protocol allows for frequent status reports (once per TTI), thus reducing the roundtrip time.

 In HSDPA, the hybrid ARQ operates per transport

block or, equivalently, per TTI that is, whenever the HS-DSCH CRC indicates an error, a retransmission representing the same information as the original transport block is requested. As there is a single transport block per TTI, the content of the whole TTI is retransmitted in case of an error. This reduces the amount of uplink signaling as a singleACK/NAKbit per TTI is sufficient.

 Having multiple transport blocks per TTI with the

possibility for individual retransmissions were quite small.

 Incremental redundancy is the basic scheme for soft

combining, that is, retransmissions may consist of a different set of coded bits than the original transmission. The rate matcher uses puncturing (or repetition) to match the number of code bits to the number of physical channel bits available. Node B decides whether to use incremental redundancy or Chase combining by selecting the appropriate puncturing pattern for the retransmission.

 The UE receives the coded bits and attempts to decode

them. In case the decoding attempts fails, the UE buffers the received soft bits and requests a retransmission by sending a NAK.
Once the retransmission occurs, the UE combines the

buffered soft bits with the received soft bits from the retransmission and tries to decode the combination.

6-Data flow

operation
The PDCP performs (optional) IP header compression.
The output from the PDCP is fed to the RLC protocol

entity. After possible concatenation, the RLC SDUs are segmented into smaller blocks of typically 40 bytes. An RLC PDU is comprised of a data segment and the RLC header.

 If logical-channel multiplexing is performed in MAC-

d, a 4-bit header is added to form a MAC-d PDU.

In MAC-hs, a number of MAC-d PDUs, possibly of

variable size, are assembled and a MAC-hs header is attached to form one transport block, subsequently coded and transmitted by the physical layer.