Raw Data Rate

7/30/2019 Raw Data Rate

http://slidepdf.com/reader/full/raw-data-rate 1/81

INTRODUCTION The main purpose of this document is the translation of the source bit rate into

physical channel bit rate. This process requires a detailed overview of the

technological constraints involved in radio transmission. For sometechnologies, UMTS, HSDPA and HSUPA it is also important to take into account

the radio QoS considerations, specially the Radio Access Bearer and its related

parameters.



WiFi PHYSICAL TECHNICAL DESCRIPTION

The 802.11 standard specifications defines one Medium Access Control (MAC)

layer and two PHY sublayers, the Physical Layer Convergence Procedure (PLCP)

which map the MAC frames onto the medium, and the Physical MediumDependent (PMD) system which is in charge of transmitting the frames.

Depending on the standard version there are several different PMD systems,

the Frequency Hopping Spread Spectrum (FHSS), the Direct Sequence Spread

Spectrum (DSSS) and the Orthogonal Frequency Division Multiplexing (OFDM)

one.

We must take into account that the relation between the raw data rate and the

payload data rate is not only influenced by headers of the different layers, but

also is influenced by the MAC functionalities like CTS to Self, CTS / RTS, etc. So

after modeling the physical frames for each versions of the standard, we must

take an overview of the different MAC methods.

The standard versions with the OFDM based Phy layer, as well as the ones

based on spread spectrum techniques, make use of the PLCP (Physical Layer

Convergence Precedure), which is a boundary between MAC and wireless

medium. The PLCP takes each 802.11 frame that a station wishes to transmit

and forms what the 802.11 standard refers to as a PLCP protocol data unit

(PPDU). The resulting PPDU includes the following fields in addition to the frame

fields imposed by the MAC Layer.

Each stream of m bytes generated by a legacy Internet application is

encapsulated in the TCP/UDP and IP protocols that add their headers before

delivering the resulting IP datagram to the MAC layer for transmission over the

wireless medium. Each MAC data frame is made up of: i) a MAC header , say

MAChdr , containing MAC addresses and control information,3 and ii) a variable

length data payload, containing the upper layers data information. Finally, to



support the physical procedures of transmission (carrier sense and reception) a

physical layer preamble (PLCP preamble) and a physical layer header (PLCP

header) have to be added to both data and control frames. Specifically, the

standard defines two different formats for the PLCP: Long PLCP and Short PLCP.

It is important to notice that these different headers and data fields are

transmitted at different data rates to ensure the interoperability between802.11 and 802.11b cards.

The Phy frames for the different standard versions are presented next:

The OFDM Frame format is the next:

The 802.11 b Frame

The 802.11g standard includes mandatory and optional components. It usesOFDM, (from 802.11a) and CCK (from 802.11b as the mandatory modulation

schemes with 24 Mbps as the maximum mandatory data rate. The 802.11g

standard defines both short and long preambles as mandatory.



Each standard version has got several different Modulations and Coding

Schemes (MCS). The MCS is the combination of one specific modulation and an

associated throughput. Both the 802.11 a and g also includes channel

codification with fixed coding rates.

The current MCS schemes and the associated maximum throughput for each

one of the standard versions are showed next:

802.11

The Direct sequence is a spread spectrum technique that can be used to

transmit a signal over a much wider frequency band. The changes in the radio

carrier are present across a wide band and the receiver can perform correlationprocesses to look for changes. To turn back the spread process, a correlator

scheme is used which gives a great level of protection against the interference.

The 802.11 direct sequence systems uses a rate of 11 million chips per second.

The codification is made by dividing the chip stream into series of 11 bit barker

words, and the resulting transmission rate is up to 1 million symbols per

http://var/www/apps/conversion/tmp/scratch_2/



second. Each barker word can encode 1 (DBPSK) or 2 (DQPSK) bits so the

achievable throughput can be 1 or 2 Mbps.

PHY

Layer

Modulat

ion

Bits/Sym

bol

Max

Throughput

FHSS /DSSS DBPSK 1 1 Mbps

FHSS /

DSSSDQPSK 2 2 Mbps

Table 1 802.11 PHY Layer parameters

802.11 b

To increase the number of bits per symbol and therefore the data rate while

using a differential phase shift modulation would require to process small

phase shifts, which is difficult in the presence of multipath interference.

Therefore, another technique is required, and the solution is to use a more

efficient encoding method, the Complementary Code Keying (CCK), which uses

8 bits code words and can encode 4 or 8 bits into a word. In this case, thetransmission is set up in 1.375 million symbols per second.

PHY

Layer

Coding /

Modulation

Bits/Sym

bol

Max

ThroughputDSSS 1 DBPSK 1 MbpsDSSS 2 DQPSK 2 MbpsDSSS 4 CCK 5.5 MbpsDSSS 8 CCK 11 Mbps

Table 2 802.11b PHY Layer parameters

802.11 g

The transmission scheme employed in the PHY layer is Orthogonal Frequency

Division Multiplexing (OFDM). The OFDM based PHY layer divides the available

channel bandwidth (20 MHz) into 52 subcarriers; 4 of them are used as pilot

ones and the other 48 are used to encode a single transmission data. The

subcarriers spacing is 312.5 KHz and the symbol rate is 250.000 symbols per

second across the 48 channels transmitted in parallel. In an OFDM based

system, all the channels overlap but they do not interfere with each other due

to its orthogonal property. This means that at the frequency center of the

subcarrier where there is an amplitude peak level, the other two overlapping

subcarriers have zero amplitude. In OFDM, the main problem is not the ISI due

to the delay spread between different signal paths, but it is necessary to copewith the Inter Carrier Interference (ICI) problem. The way to solve this problem

is to reserve the beginning portion of the symbol time as a guard time.

For assuring backwards compatibility, the 802.11g version implements all the

previous modulations schemes and it also defines a set of modulations

schemes that can be applied to each one of the subcarriers. The set of



modulations comprises BPSK, QPSK, 16 QAM and 64 QAM as modulations

schemes and can be seen in the next two charts.

PHY

Layer

Coding /

Modulation

Bits/Sym

bol

Max

Throughput

DSSS DBPSK 1 1 MbpsDSSS DQPSK 2 2 MbpsDSSS CCK 4 5.5 MbpsDSSS CCK 8 11 Mbps

Table 3 802.11g PHY Layer parameters. Backward compatibility

PHY

Layer

Modulat

ion

Code

Rate

Bits/Car

rier

Bits

/Symbol

Max

Rate

OFDM BPSK R = ½ 1 24 6 MbpsOFDM BPSK R = ¾ 1 36 9 Mbps

OFDM QPSK R = ½ 2 4812

Mbps

OFDM QPSK R = ¾ 2 7218

Mbps

OFDM 16 QAM R = ½ 4 9624

Mbps

OFDM 16 QAM R = ¾ 4 14436

Mbps

OFDM 64 QAM R = 2/3 6 21648

Mbps

OFDM 64 QAM R = ¾ 6 28854

MbpsTable 4 802.11g PHY Layer parameters

Another technological feature implemented in both the 802.11 a and g versionsof the standard is the channel codification, making use of convolutional codes

with different coding rates, from ½ up to 3/4.

802.11 a

This OFDM based PHY layer is the same as the 802.11 g one, however, the

802.11a is not compatible with anyone of the other current standard versions.

PHY

Layer

Modulat

ion

Code

Rate

Bits/Car

rier

Bits

/Symbol

Max

Rate

OFDM BPSK R = ½ 1 24 6 MbpsOFDM BPSK R = ¾ 1 36 9 Mbps

OFDM QPSK R = ½ 2 4812

Mbps

OFDM QPSK R = ¾ 2 7218

Mbps

OFDM 16 QAM R = ½ 4 9624

MbpsOFDM 16 QAM R = ¾ 4 144 36



Mbps

OFDM 64 QAM R = 2/3 6 21648

Mbps

OFDM 64 QAM R = ¾ 6 28854

MbpsTable 5 802.11a PHY Layer parameters

The Medium Access Control has several functionalities like the control of the

transmission medium, security issues and some well know challenges such as

the hidden node problem. The coordination functions for access the medium in

802.11 are provided by the Distributed Coordination Function (DCF). A critical

issue for an efficient data communication in wireless networks is to specify a

set of procedures to determine how to access the medium.

The way to determine if the medium is available for transmitting is carrier

sensing. This mechanism is based on the Carrier Sense Multiple Access withCollision Avoidance protocol (CSMA/CA). This mechanism consists of multiple

accesses with carrier detection to avoid collision. It is important to remark that

there is not difference between uplink and downlink connections to transmit,

due to the fact that both of them share the same bandwidth, so Access Points

(AP) will be considered another station in the medium access procedure. When

a station with a packet to transmit senses the channel and it is busy, the

station waits until the channel becomes idle for a Distributed Interframe Space

(DIFS) time. After that it starts a back-off process which consists on generating

a random value chosen from a uniform distribution between 0 and a parameter

known as Contention Window (CW). The backoff timer is decreased for as long

as the channel is sensed as idle, stopped when a transmission is detected on

the channel, and reactivated when the channel is sensed as idle again for more

than a DIFS The station is enabled to transmit its frame when the backoff timer

reaches zero. The backoff time is slotted. The Backoff Window, is also referred

to as Contention Window. At the first transmission attempt CW =CWmin, and it

is doubled at each retransmission up to CWmax . In the standard CWmin and

CWmax values depend on the physical layer adopted.

Obviously, it may happen that two or more stations start transmitting

simultaneously and a collision occurs. In the CSMA/CA scheme, stations are not

able to detect a collision by hearing their own transmission, therefore, animmediate positive acknowledgement scheme is employed to ascertain the

successful reception of a frame. Specifically, upon reception of a data frame,

the destination station initiates the transmission of an acknowledgement frame

(ACK) after a time interval called Short InterFrame Space (SIFS). The SIFS is

shorter than the DIFS (see Figure 3) in order to give priority to the receiving

station over other possible stations waiting for transmission. If the ACK is not



received by the source station, the data frame is presumed to have been lost,

and a retransmission is scheduled. The ACK is not transmitted if the received

frame is corrupted. A Cyclic Redundancy Check (CRC) algorithm is used for

error detection.

Due to some transmission problems like the hidden node one, another more

sophisticated methods have been developed; the Clear To Send (CTS) to Self and the Request To Send (RTS) and Clear To Send (CTS).

According to the CTS To Self mechanism, one station sends a CTS messagewhich is received from all the other stations, and then they will defer theirupcoming transmissions, so the station that send the CTS messageimmediately start its transmission.



According to the RTS-CTS mechanism, before transmitting a data frame, the

source station sends a short control frame, named RTS, to the receiving station

announcing the upcoming frame transmission. Upon receiving the RTS frame,

the destination station replies by a CTS frame to indicate that it is ready to

receive the data frame. Both the RTS and CTS frames contain the total duration

of the transmission.

For each standard version, the CSMA CA and Phy parameters have different

values which are presented next:

203 usg

207 usg



The formulas employed for the calculation of the estimated throughput at

the TCP Payload taking into account all these parameters are the next:

Where:

m is the number of bytes generated by the application.

TDATA is the time required to transmit a MAC data frame using one of the NIC

data rate, i.e., 1, 2, 5.5 or 11 Mbps; this includes the PHYhdr , MAChdr ,

MACpayload and FCS bits for error detection.

TACK is the time required to transmit a MAC ACK frame; this includes the

PHYhdr , and MAChdr .

CW min/2 · Slot_time is the average back off time.

The formula for the CTS To self is showed next



When the RTS/CTS mechanism is used, the overheads associated with the

transmission of the RTS

and CTS frames must be added to the denominator of (1). Hence, in this case,

the maximum

throughput ThRTS /CTS , is defined as

Where TRTS and TCTS indicate the time required to transmit the RTS and CTS

frames, respectively. The CTS frame and the RTS will be transmitted at the

highest rate understood by all stations attached to the access point. The CTS

size is 14 bits and the RTS size is 20 bits. Also it must be added with the PLCP

preamble transmission time, which varies depending on the standard version.

We must notice that the the 802.11 MAC requires positive acknowledgement of

every transmission, so each TCP packet must therefore be wrapped up in a

frame exchange. The frame is compound by the TCP data segment and the TCP

ACK. In addition to the payload it is important that we take into account all the

headers.

Other thing we must notice is that if we are working with the 802.11e standard

version, the selected value for the average back off time, CW min/2 · Slot_time

is not such a good approximation. The correct way to deal with this issue is

modeling the backoff time and the CW size in a different and more complex

way. So it is compulsory to model the TxOP, the AIFS and the CWmin and



CWmax parameters for each access class in order to obtain realistic values. An

example of the value assignation to these parameters set by the EDCF and is

the next:

By modeling these parameters we can find that the throughput saturation

value for each AC slightly gets lower as the number of terminal increases. One

of the main issues that affect the network throughput is the CW size, that is,

the time that one station must wait before attempting a transmission indeed if

the air medium is free. Other fact to take into account is that not always the

different Access Classes are in a saturation condition.

UMTS PHYSICAL TECHNICAL DESCRIPTION

The UMTS architecture is based on CDMA as the medium multiple access

techonlogy. The channel spacing is 5 MHz wide, and that’s the reason why it is

considered WCDMA. The chip rate is 3.84 Mcps with a 10 msg frame length. It

is divided in 15 slots.

RADIO QoS CONSIDERATIONS

3GPP has defined the concept of Radio Access Bearer (RAB) as a user plane

connection provided by the UMTS Terrestrial Radio Access Network (UTRAN)

between a User Equipment (UE) and the Core Network. The RAB Assignment

procedure is initiated by the CN to establish the RAB for the selected service.

This means that the general characteristics of a RAB (data rates, QoS, etc) are

normally set by the Core Network (CN) based on subscription and/or

requirements of the media or set of medias using the RAB. The actual

configuration for a RAB is decided by UTRAN based on the RAB information

received from the CN.

The RAB configuration has a direct impact on network resource usage.

Between the RNC and the UE data is always transferred inside frames which

length is within a set of allowed frame sizes. The set of allowed frame sizes is

configured when the RAB is setup. The RAB bandwidth determines the QoS



received by the application, and the set of allowed frame sizes for the RAB

determines the amount of bandwidth wasted for padding.

In UMTS, there is a one-to-one mapping of RABs to PDPs. So multi-RAB

capability gives the possibility to have two or more simultaneous RABs to

support simultaneous communication over the radio access network withmultiple service access points.

Both Rel ‘99 and HSDPA multi-RABs are described in 3GPP TS 34.108 and 3GPP

TR 25.993. For Rel ‘99 multi-RABs, the radio bearers are multiplexed on MAC-d

level into one single dedicated transport channel (DCH), with a maximum rate

of 8, 16, 64, 128 or 384 Kbps for both downlink and uplink. The maximum bit

rate is shared by the two RABs, meaning the sum of the instantaneous bit rates

on the bearers transmitted in a TTI (Transmission Time Interval) is less than or

equal to the maximum bit rate on the DCH. The transport channel is shared,

and also has lower transport formats in order to adapt to lower data rates when

there is less data to transmit.

Multi-PS RAB are required to support radio QoS. For HSDPA Multi-RABs, there is

no multiplexing on the MAC-d level for the downlink. Instead, the radio bearers

are carried as different MAC-d flows down to the RBS, where the data is put

into separate priority queues for scheduling on the HS-DSCH (Downlink Shared

Channel used in HSDPA). The available HS-DSCH bandwidth is shared between

the various flows. The uplink radio bearers will continue to be Rel ‘99, and

follow the mapping described previously.

All the multi-RAB combinations are realized according to the typical radioparameter sets described for the UL and DL radio bearers in 3GPP TS 34.108

and 3GPP TR 25.993. Each PS RAB typically has a separate user activity

supervision algorithm, whereby channel switching occurs.

RAB Combination allows the radio bearer management to combine different

classes of PDP context to provide different services simultaneously, e.g. VoIP

and video streaming. Specific RAB combinations will be too many to list.

Following are examples of RAB combination types:

Up to 3 HSDPA PDPs with I/B QoS (DCH Upstream) + CS 12.2K AMR Voice Up to 3 DCH/DCH UL/DL PDPs with I/B QoS + CS 12.2K AMR Voice

Up to 2 PDP with I/B QoS + 1 PDP with Streaming QOS (DCH/HS-DSCH) +

CS 12.2K AMR Voice

The transmission of data within a RAB in UMTS works as follows. Data (namely

IP packets) generated by an application at the UE is stored in an internal buffer.

This buffer is emptied periodically, every Transmission Time Interval (TTI),



when a radio frame is created with the data stored at the buffer up to a certain

maximum frame size (MFS). In case the amount of data in the buffer is less

than MFS, a frame of size smaller than MFS may be created.

Once the frame has been created as described above, it is transported through

the air interface to the Node B, where an IP packet containing the frame iscreated. The IP packet is then transported through the Radio Access Network

(RAN) to the RNC. The RNC terminates the radio protocol; it extracts the radio

frames from the IP transport packets, and the data from these frames,

discarding the padding, and transmits the resulting data (which are IP packets)

further into the Core Network (CN).



EXAMPLE

The AMR RAB is established with one or more RAB co-ordinated sub-flows with

predefined sizes and QoS parameters. In this way, each RAB sub-flow

Combination corresponds to one AMR frame type. For AMR, the first RAB sub-

flow (sub-flow 1) corresponds with the Class A bits. In case there are three RAB

sub-flows, the third RAB sub-flow (sub-flow 3) corresponds with the Class C bits.

On the Iu interface, these RAB parameters define the corresponding

parameters regarding the transport of AMR frames.

Some of the QoS parameters in the RAB assignment procedure are determined

from the Bearer Capability Information Element used at call set up. These QoS

parameters as defined in [3], can be set as follows:

Table 5-1: Example of mapping of BC IE into QoS parameters for UMTS AMR

RAB service attribute RAB service attribute value Comments

Traffic Class ConversationalRAB Asymmetry Indicator Symmetric, bidirectional Symmetric RABs are used for uplink anddownlink

Maximum bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75kbit/s

This value depends on the highest moderate in the RFCS

Guaranteed bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75kbit/s

One of the values is chosen, dependingon the lowest rate controllable SDUformat (note 2)

Delivery Order Yes (note 1)

Maximum SDU size 244 / 204 / 159 / 148 / 134 / 118 / 103 / 95bits

Maximum size of payload field in Iu UP,according to the highest mode rate in theRFCS

Traffic Handling Priority Not applicable Parameter not applicable for theconversational traffic class. (note 1)

Source statistics descriptor Speech (note 1)

SDU Parameters RAB sub-flow 1(Class A bits)

RAB sub-flow2 (Class Bbits)

RAB sub-flow 3(Class Cbits)

The number of SDU, their number of RABsub-flow and their relative sub-flow size issubject to operator tuning (note 3)

SDU error ratio 7 * 10-3 - - (note 3)

Residual bit error ratio 10-6 10-3 5 * 10-3 (note 3 – applicable for every sub-flow)

Delivery of erroneous SDUs yes - - Class A bits are delivered with error indication;Class B and C bits are delivered withoutany error indication.

SDU format information 1-9 (note 4)

Sub-flow SDU size 1-9 (note 5) (note 5) (note 5)

NOTE 1:These parameters apply to all UMTS speech codec types.NOTE 2:The guaranteed bit rate depends on the periodicity and the lowest rate controllable SDU size.

NOTE 3:These parameters are subject to operator tuning.NOTE 4:SDU format information has to be specified for each AMR core frame type (i.e. with speech bits and comfortnoise bits) included in the RFCS as defined in [2].

NOTE 5:The sub-flow SDU size corresponding to an AMR core frame type indicates the number of bits in the class A,class B and class C fields. The assigned SDU sizes shall be set so that the SCR operation is always possible.

The conversational traffic class shall be used for the speech service, which is

identified by the ITC parameter of the bearer capability information element in



the SETUP message.

UPLINK UMTSFirst of all we are going to make a briefly overview on the UMTS channel

structure.Logical Channels are the Dedicated Traffic Channel (DTCH) and theDedicated Control Channel (DCCH). These channel are mapped into the

transport Dedicated Channel (DCH). Finally, this channel is mapped into the

Dedicated Physical Control Channel (DPCCH) and the Dedicated Physical Data

Channel (DPDCH).

Among the five types of uplink dedicated physical channels, we are focusing on

the uplink Dedicated Physical Data Channel (uplink DPDCH), the uplink

Dedicated Physical Control Channel (uplink DPCCH). The uplink DPDCH is usedto carry the DCH transport channel. There may be zero, one, or several uplink

DPDCHs on each radio link.

The uplink DPCCH is used to carry control information generated at Layer 1.

The Layer 1 control information consists of known pilot bits to support channel

estimation for coherent detection, transmit power-control (TPC) commands,

feedback information (FBI), and an optional transport-format combination

indicator (TFCI). The transport-format combination indicator informs the

receiver about the instantaneous transport format combination of the transport

channels mapped to the simultaneously transmitted uplink DPDCH radio frame.

There is one and only one uplink DPCCH on each radio link.

Figure 1 shows the frame structure of the uplink DPDCH and the uplink DPCCH.

Each radio frame of length 10 ms is split into 5 subframes, each of 3 slots, each

of length Tslot = 2560 chips, corresponding to one power-control period. The

DPDCH and DPCCH are always frame aligned with each other.



Pilot N ilot bits

TPC N TPC bits

Data N data bits

Slot #0 Slot #1 Slot #i Slot #14

T slot = 2560 chips, 10 bits

1 radio frame: T = 10 ms

DPDCH

DPCCH FBI

N FBI bits TFCI

N TFCI bits

T slot = 2560 chips, N data = 10*2 bits (k=0..6)

Slot #2 Slot #3

Subframe #0 Subframe #1 Subframe #2 Subframe #3 Subframe #4

1 subframe = 2 ms

Figure 1: Frame structure for uplink DPDCH/DPCCH

The parameter k in figure 1 determines the number of bits per uplink DPDCH

slot. It is related to the spreading factor SF of the DPDCH as SF = 256/2 k. The

DPDCH spreading factor may range from 256 down to 4. The spreading factor

of the uplink DPCCH is always equal to 256, i.e. there are 10 bits per uplink

DPCCH slot.

The exact number of bits of the uplink DPDCH and the different uplink DPCCHfields (Npilot, N TFCI, NFBI, and N TPC) is given by table 1 and table 2. What slot format

to use is configured by higher layers and can also be reconfigured by higher

layers.

The channel bit and symbol rates given in table 1 and table 2 are the rates

immediately before spreading. The pilot patterns are given in table 3 and table

4, the TPC bit pattern is given in table 5. The DPDCH, the DPCCH are I/Q code

multiplexed and the modulation is BPSK so 1 symbols equals to 1 bit



Table 1: DPDCH fields

SlotFormat #i

Channel BitRate (kbps)

ChannelSymbol Rate(ksps)

SF Bits/Frame

Bits/Slot

Ndata

0 15 15 256 150 10 10

1 30 30 128 300 20 202 60 60 64 600 40 403 120 120 32 1200 80 804 240 240 16 2400 160 1605 480 480 8 4800 320 3206 960 960 4 9600 640 640

There are two types of uplink dedicated physical channels; those that include

TFCI (e.g. for several simultaneous services) and those that do not include TFCI

(e.g. for fixed-rate services). These types are reflected by the duplicated rows

of table 2.

Table 2: DPCCH fields

SlotFormat #i

Channel BitRate(kbps)

ChannelSymbolRate(ksps)

SF Bits/Frame

Bits/Slot

Npil

ot

NT

PC

NTF

CI

NF

BI

Transmitted slotsperradioframe

0 15 15 256

150 10 6 2 2 0 15

0A 15 15 256

150 10 5 2 3 0 10-14

0B 15 15 256

150 10 4 2 4 0 8-9

1 15 15 256

150 10 8 2 0 0 8-15

2 15 15 256

150 10 5 2 2 1 15

2A 15 15 256

150 10 4 2 3 1 10-14

2B 15 15 256

150 10 3 2 4 1 8-9

3 15 15 25

6

150 10 7 2 0 1 8-15

4 15 15 256

150 10 6 4 0 0 8-15

A Transport Block (TB) [25.302] basic unit of data exchanged between MAC andPHY and every transport block belongs to one and only one transport channel.In RRC signalling, a transport block corresponds to RLC PDU (Protocol DataUnit). Several transport blocks can be transferred at the same time on the



same transport channel between MAC and PHY. The set of all transport blocksexchanged at the same time on one transport channel is called a transportblock set (TBS).

The Transport Format (TF) is the basic format offered by Layer 1 to the MAC forthe delivery of a TBS in a TTI. Transport format is a format applied to a

transport block set on a given transport channel for a given TTI. Thisparameter controls how much data is transferred on the transport channel inthat particular transmission time interval and how the data is coded etc. by thephysical layer. Transport blocks and transport block sets can have severalcharacteristics, which are described by the following attributes:

· Transport block size -Dynamic· Transport block set size - Dynamic· Transmission time interval (TTI) - semistatic· coding type and coding rate) -semistatic· Size of CRC error detection/protection method - semistatic· Rate matching parameters -semistatic

An example of a TF: Dynamic part: {320 bits, 640 bits}, Semi-static part:{10ms, convolutional coding only, static rate matching parameter = 1}. TBS =320, TBSs = 640, that is, there are 2 TB in a TBS.

All transport blocks within one transport block set have a fixed transport blocksize, but the size can vary between different transport block sets. The transportblock set size indicates the total number of bits in that particular transportblock set. The TTI value defines the time interval between twosubsequent transport block set transfers between MAC and PHY . Thisparameter controls how much data is transferred on the transport channel inthat particular transmission time interval and how the data is coded etc. by the

physical layer.

Layer 1 can multiplex several transport channels together for transmittingthese channels simultaneously. For each transport channel, there is a list of possible Transport Formats defined in the Transport Format Set (TFS). The TFSis a set of TFs associated to a Traffic Channel, where the semistatic part of allthe TFs in the TFS is the same.



Transport Format Combination (TFC) is “an authorised combination of thecombination of currently valid transport formats that can be submittedsimultaneously to Layer 1 for transmission on a Coded Composite TransportChannel (CCTrCH) of a UE a Transport Format Combination Set (TFCS) isdefined as a set of TFCs on a CCTrCH. The assignment of a suitable TFCS isdone in Layer 3 in the RNC – or correspondingly in the UE. When scheduling

and mapping the data transmission onto the physical layer, the MAC layerchooses between the different TFCs given in the TFCS and thereby has controlover the dynamic part of the transport format

The representation of a specific transport format within a TFS is called a Transport Format Indicator (TFI). A TFS is formed when the transmission rate of the transport channel varies and thus it includes multiple parameter sets forthe dynamic part of the transport format. For example, a variable rate DCH hasa transport format set (one transport format for each rate), whereas a fixedrate DCH has only a single transport format. The semi-static part of alltransport formats are the same within a TFS.

We can now calculate that the maximum bit rate for TrCH1 is 160 bits / 40 ms= 4 kbits/s and for TrCH2 150 bits / 10 ms = 15 kbits/s. In addition to differentbit rates and TTI values, given the different channel coding types and CRCsizes, we would be much more likely to detect any transport blocks containingerrors on TrCH2 than on TrCH1. Thus by defining the transport formats we alsoaffect the Quality of Service (QoS) provided to the connection. Also the choiceof the rate matching attribute gives a means of controlling the differentprotection given to different transport channels.



Dr. A. Chockalingam Dept of ECE, IISc, Bangalore 26

Transport Formats / Configurations

TTITTI TTITTI TTITTI

TTITTI TTITTI TTITTI

TBTB

DCH1DCH1

DCH2DCH2

TBTB TBTB

TBTB TBTB TBTB

TBTB

Transport Block SetTransport Block Set

(TBS)(TBS)

TBTB

TBTB

Transport Format (TF)Transport Format (TF)Transport FormatTransport Format

Set (TFS)Set (TFS)

Transport FormatTransport Format

Combination (TFC)Combination (TFC)

Transport FormatTransport Format

Combination SetCombination Set

(TFCS)(TFCS)

Ie. Conversational Speech 12 kbps

TTI = 20 ms

Available TF for each RAB. Each RAB subflow goes in a different Transport

Channel. Each TCH has its TF which is applied to each TBSet.

TF RAB1 RAB2 RAB3

TF0v 0x81 0X1030x60 (silence)

TF1v 1x81 1X1031x60 (active voice)

One possible TFC can be (TF0,TF0,TF0) during silence.

Scheme for multiplexing and channel coding:



CRC attachment for error correction: 0, 8, 12, 16, 24 bits.

Transport Block Concatenation. All TB that are in the same TTI are joined. If the

number of bits is higher than the maximum length allowed for channel coding

(504 bits in convolutional coding and 5114 for Turbo-codes), it is split into same

length segments.

Channel coding:

Convolutional coding with ½ or 1/3 coding rates

Turbo-codes with 1/3 coding rates.

Radio frame equalization. Zero padding until the total number of bits is multiple

of the number of frames, so all frames have the same number of bits. The

number of frames can be 1, 2, 4, 8 depending on the TTI duration.

The first interleaving doesn´t vary the number of bits.

Radio Frame Segmentation. When TTI duration is higher than 10 ms, there is a

division to distribute the bits among the frames. Each segment goes in a

separate frame radio.



Rate matching. By means of this process, the transport channel rate is adapted

to the binary rate of the Phy channels. This is by measn of puncturing and

repetition process.

Table A.1: UL reference measurement channel physical parameters (12.2 kbps)

Parameter Unit LevelInformation bit rate kbps 12.2

DPDCH kbps 60

DPCCH kbps 15

DPCCH Slot Format #i - 0

DPCCH/DPDCH power ratio Db -5.46

TFCI - On

Repetition % 23

NOTE: Slot Format #2 is used for closed loop tests in subclause 8.6.2.Slot Format #2 and #5 are used for site selection diversity transmission tests

in subclause 8.6.3

Table A.2: UL reference measurement channel, transport channel parameters (12.2 kbps)

Parameters DTCH DCCH

Transport Channel Number 1 2

Transport Block Size 244 100

Transport Block Set Size 244 100

Transmission Time Interval 20 ms 40 ms

Type of Error Protection Convolution Coding Convolution Coding

Coding Rate 1/3 1/3

Rate Matching attribute 256 256

Size of CRC 16 12



60kbps DPDCH

Conv. Coding R=1/3

Radio frame FN=4N+1 Radio frame FN=4N+2 Radio frame FN=4N+3Radio frame FN=4N

Information data

CRC attachment

Tail bit attachment

Rate matching

2nd interleaving

600

490 110 490 110 490 110 490

SMU#1 490 SMU#2 490 SMU#1110

SMU#2110

SMU#3110

SMU#4110

600 600 600

402

804

260

Tail8

CRC16

244

244

110

360

360

112

Tail8100

CRC12

1st interleaving

Radio Frame Segmentation

CRC attachment

Information data

Tail bit attachment

Conv. Coding R=1/3

Rate matching

1st interleaving

DTCH DCCH

804

402

SMU#1 490 SMU#2 490

90 90 90 90

15kbps DPCCH

100

The assigned DPDCH channel is 60kbps. The information data payload is 244

bits The 244 bits of payload are derived from this process. The codec rate is

12.2 kbps and the number of generated bits per frame is 244. This can be seen

on table 1 of 3GPP TS 26.090. The mapping of these bits into the PDU is made

through RAB sub-flows. For example, for this codec rate there are three RAB

sub-flows, the RAB sub-flow 1 with 81 bits, the RAB sub-flow 2 with 103 bits

and the RAB sub-flow 3 with 60 bits. Each RAB sub-flow can be assigned to one

separate TF, and the combination of the three TF is the Transport Format

Combitnation (TFC).

The Radio Frame segmentation is performed because the TTI = 20 implies two

frames, so data it is equally distributed into two frames. DCCH is distributed

among 4 frames because its TTI is 40 ms value. Next, Rate matching is

performed according to the Rate Matching attribute. Next, DCCH information

bits are multiplexed with DTCH information.

DOWNLINK For the donwlink, there are dedicated and common channels. The dedicated

transport channel is the DCH which is mapped into the Dedicated Physical Data

Channel (DPDCH). It has also associated a dedicated control channel (DPCCH).

Within one downlink DPDCH, dedicated data generated at Layer 2 and above,

i.e. the dedicated transport channel (DCH), is transmitted in time-multiplex

with control information generated at Layer 1 (Pilot, TPC and TFCI) and the

Dedicated Physical Common Control Channel (DPCCCH)

Frame structure for Downlink DPCH.



One radio frame, Tf = 10 ms

TPC

NTPC bits

Slot #0 Slot #1 Slot #i Slot #14

Tslot = 2560 chips, 10*2k

bits (k=0..7)

Data2

Ndata2 bits

DPDCH

TFCI

NTFCI bits

Pilot

N pilot bits

Data1

Ndata1 bits

DPDCH DPCCH DPCCH

Figure 9 shows the frame structure of the downlink DPCH. Each frame of length

10 ms is split into 15 slots, each of length Tslot = 2560 chips, corresponding to

one power-control period.

The number of bits in different DPDCH fields are given in tables and the slot

format to use is configure by higher layers.



Table 11: DPDCH and DPCCH fields

SlotFormat

#i

ChannelBit Rate(kbps)

ChannelSymbol

Rate(ksps)

SF Bits/Slot

DPDCHBits/Slot

DPCCHBits/Slot

Transmittedslots per

radio frameNTr NData1 NData2 NTPC NTFCI NPilot

0 15 7.5 512 10 0 4 2 0 4 150A 15 7.5 512 10 0 4 2 0 4 8-14

0B 30 15 256 20 0 8 4 0 8 8-14

1 15 7.5 512 10 0 2 2 2 4 15

1B 30 15 256 20 0 4 4 4 8 8-14

2 30 15 256 20 2 14 2 0 2 15

2A 30 15 256 20 2 14 2 0 2 8-14

2B 60 30 128 40 4 28 4 0 4 8-14

3 30 15 256 20 2 12 2 2 2 15

3A 30 15 256 20 2 10 2 4 2 8-14

3B 60 30 128 40 4 24 4 4 4 8-14

4 30 15 256 20 2 12 2 0 4 15

4A 30 15 256 20 2 12 2 0 4 8-14

4B 60 30 128 40 4 24 4 0 8 8-14

5 30 15 256 20 2 10 2 2 4 15

5A 30 15 256 20 2 8 2 4 4 8-14

5B 60 30 128 40 4 20 4 4 8 8-14

6 30 15 256 20 2 8 2 0 8 15

6A 30 15 256 20 2 8 2 0 8 8-14

6B 60 30 128 40 4 16 4 0 16 8-14

7 30 15 256 20 2 6 2 2 8 15

7A 30 15 256 20 2 4 2 4 8 8-14

7B 60 30 128 40 4 12 4 4 16 8-14

8 60 30 128 40 6 28 2 0 4 15

8A 60 30 128 40 6 28 2 0 4 8-14

8B 120 60 64 80 12 56 4 0 8 8-14

9 60 30 128 40 6 26 2 2 4 15

9A 60 30 128 40 6 24 2 4 4 8-14

9B 120 60 64 80 12 52 4 4 8 8-14

10 60 30 128 40 6 24 2 0 8 15

10A 60 30 128 40 6 24 2 0 8 8-14

10B 120 60 64 80 12 48 4 0 16 8-14

11 60 30 128 40 6 22 2 2 8 15

11A 60 30 128 40 6 20 2 4 8 8-14

11B 120 60 64 80 12 44 4 4 16 8-14

12 120 60 64 80 12 48 4 8* 8 15

12A 120 60 64 80 12 40 4 16* 8 8-14

12B 240 120 32 160 24 96 8 16* 16 8-14

13 240 120 32 160 28 112 4 8* 8 15

13A 240 120 32 160 28 104 4 16* 8 8-14

13B 480 240 16 320 56 224 8 16* 16 8-14

14 480 240 16 320 56 232 8 8* 16 15

14A 480 240 16 320 56 224 8 16* 16 8-14

14B 960 480 8 640 112 464 16 16* 32 8-14

15 960 480 8 640 120 488 8 8* 16 15

15A 960 480 8 640 120 480 8 16* 16 8-14

15B 1920 960 4 1280 240 976 16 16* 32 8-14

16 1920 960 4 1280 248 1000 8 8* 16 15

16A 1920 960 4 1280 248 992 8 16* 16 8-14



To allow multicode transmission, the Combinated Compound Transport Channel

(CCTrCH) can be mapped on to several parallel downlink DPCHs using the same

spreading factores, and in this case the L1 control information is sent only on

the first downlink DPCH. In case there are several CCTrCHs (several different

services with the same UE as destiny) mapped to different DPCHs transmitted

to the same UE different spreading factors can be used on DPCHs to whichdifferent CCTrCHs are mapped. Also in this case, Layer 1 control information is

only transmitted on the first DPCH.

The symbol rates and the data rates in the downlink are calculated next:

The system chip rate is 3.84 Mchps · 10/15 ms (subframe) = 2560 chips. As it

is employed QPSK modulation for the downlink, 1 symbol equals to 2 bits. With

and spreading factor of: SF = 512 /2k , k = 0, · · · , 6.

The formula for estimating the number of transmitted bits in a radio frame is

the next:

Chip

s

Symbol

sBits

Frame384

00

38400 /

SF

76800 /

SF

Slot

(Subframe)

256

0

2560 /

SF

5120 /

SF

The data rates can be calculated as next;

Rsymb = 3840/SF (ksps)

Rbits = 7680/SF (kbps)

DPDCH Spreading

Factor

Channel

Symbol Rate

Channel Bit

Rate

512 7.5 Ks/s 15 kbps256 15 Ks/s 30 kbps

128 30 Ks/s 60 kbps64 60 Ks/s 120 kbps32 120 Ks/s 240 kbps16 240 Ks/s 480 kbps8 480 Ks/s 960 kbps4 960 Ks/s 1920 kbps

4 with 3 parallel

codes2880 Ks/s 5760 kbps



Scheme for multiplexing and channel coding:

CRC attachment for error correction: 0, 8, 12, 16, 24 bits.

Transport Block Concatenation. All TB that are in the same TTI are joined. If the

number of bits is higher than the maximum length allowed for channel coding

(504 bits in convolutional coding and 5114 for Turbo-codes), it is split into same

length segments.

Channel coding:

Convolutional coding with ½ or 1/3 coding rates

Turbo-codes with 1/3 coding rates.

Radio frame equalization. Zero padding until the total number of bits is multiple

of the number of frames, so all frames have the same number of bits. The

number of frames can be 1, 2, 4, 8 depending on the TTI duration.

The first interleaving doesn´t vary the number of bits.

Radio Frame Segmentation. When TTI duration is higher than 10 ms, there is a

division to distribute the bits among the frames. Each segment goes in a

separate frame radio.



Rate matching. By means of this process, the transport channel rate is adapted

to the binary rate of the Phy channels. This is by measn of puncturing and

repetition process.

Table 4: Parameter examples for 12.2 kbps data

The number of TrChs 3TrCH#a 0, 39 or 81bitsTrCH#b 103 bitsTransport block sizeTrCH#c 60 bits#1 NTrCHa=1*81, NTrCHb=1*103, NTrCHc=1*60 bits#2 NTrCHa=1*39, NTrCHb=0*103, NTrCHc=0*60 bitsTFCS#3 NTrCHa=1*0, NTrCHb=0*103, NTrCHc=0*60 bitsCRC 12 bits (attached only to TrCh#a)CRC parity bit attachment for 0 bit transport block Applied only to TrCH#aCoding CC,coding rate = 1/3 for TrCh#a, bcoding rate = 1/2 for TrCh#cTTI 20 ms



Table A.12: DL reference measurement channel, transport channel parameters (12.2 kbps)

Parameter DTCH DCCH

Transport Channel Number 1 2

Transport Block Size 244 100

Transport Block Set Size 244 100

Transmission Time Interval 20 ms 40 ms

Type of Error Protection Convolution Coding Convolution Coding

Coding Rate 1/3 1/3

Rate Matching attribute 256 256

Size of CRC 16 12Position of TrCH in radio frame fixed fixed

Transport channel parameters for Conversational / speech / DL: (12.2 7.4 5.9 4.75) kbps / CS RAB

Higher layer RAB/Signalling RB RAB subflow #1 RAB subflow #2 RAB subflow #3

RLC Logical channel type DTCH

RLC mode TM TM TM

Payload sizes, bit 0, 39, 42, 55, 61, 81 53, 63, 87, 103 60



Max data rate, bps 12 200

TrD PDU header, bit 0

MAC MAC header, bit 0

MAC multiplexing N/A

Layer 1 TrCH type DCH DCH DCH

TB sizes, bit 0, 39, 42, 55, 61, 81 53, 63, 87, 103 60

TFS (note 1) TF0, bits 1x0 (note 2) 0x103 0x60

TF1, bits 1x39 1x53 1x60TF2, bits 1x42 1x63 N/A

TF3, bits 1x55 1x87 N/A

TF4, bits 1x61 1x103 N/A

TF5, bits 1x81 N/A N/A

TTI, ms 20 20 20

Coding type CC 1/3 CC 1/3 CC 1/2

CRC, bit 12 N/A N/A

Max number of bits/TTI after channel coding

303 333 136

RM attribute 180 to 220 170 to 210 215 to 256

NOTE 1:The TrCH corresponding to RAB subflow #1 should be used as the guiding TrCH, (see clause 4.3 in3GPP TS 25.212 [14]).

NOTE 2:CRC parity bits are to be attached to RAB subflow#1 any time since number of TrBlks are 1 even if there

is no data on RAB subflow#1 (see clause 4.2.1.1 in 3GPP TS 25.212 [14]).

Because WCDMA provides flexible data rates, the number of bits on a transportchannel can vary between different transmission time intervals. The ratematching adapts this resulting symbol rate to the limited set of possible symbolrates of a physical channel. Rate matching means that bits on a transportchannel are repeated or punctured according to the defined rate matchingattribute, which is semistatic and can only be changed through higher layersignaling.



Viterbi decoding R=1/3

Radio frame FN=4N+1 Radio frame FN=4N+2 Radio frame FN=4N+3Radio frame FN=4N

Information data

CRC detection

Tail bit discard

2nd interleaving

420

343 77 343 77 343 77 343

#1 343 #2 343 #1 77 #2 77 #3 77 #4 77

420 420 420

686

804

260

Tail8

CRC16

244

244

77

308

360

112

Tail8100

CRC12

Rate matching

1st interleaving

CRC detection

Information data

Tail bit discard

Viterbi decoding R=1/3

DTCH DCCH

686

#1 343 #2 343

308

100

Radio FrameSegmentation

slot segmentation

30ksps DPCH(including TFCI bits)

Rate matching

1st interleaving

0 1 14••••

28 28

0 1

28• • • •

14

0 1 14••••

28 28

0 1

28• • • •

14

0 1 14••••

28 28

0 1

28• • • •

14

0 1 14••••

28 28

0 1

28• • • •

14

Figure A.5 (Informative): Channel coding of DL reference measurement channel (12.2 kbps)

The 244 bits of payload are derived from this process. The codec rate is 12.2

kbps and the number of generated bits per frame is 244. This can be seen on

table 1 of 3GPP TS 26.090. The mapping of these bits into the PDU is made

through RAB sub-flows. For example, for this codec rate there are three RABsub-flows, the RAB sub-flow 1 with 81 bits, the RAB sub-flow 2 with 103 bits

and the RAB sub-flow 3 with 60 bits. Each RAB sub-flow can be assigned to one

separate TF, and the combination of the three TF is the Transport Format

Combitnation (TFC).

The 100 bits of DCCH transport channel also must be considered due to the

fact that the DTCH and the DCCH are multiplexed in the DPDCH. The TTI is 20

ms.

So we have 244 bits plus 16 bits CRC and 8 bits for Tail bit attachment.

Applying the Convolutional coding rate of 1 / 3 it results in 804 bits. As themaximum number of bits i



HSDPA / HSPA + PHYSICAL TECHNICAL DESCRIPTIONHigh Speed Physical Downlink Shared Channel (HS-PDSCH)

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.

In UMTS the frame structure (TTI) lasts for 10 ms and is divided into 15 slots. In

HSDPA, the same frame structure is first divided into subframes. Each

subframe lasts for 2 ms and is compound of 3 slots. So each radio frame has 5

subframes and 15 slots, but unlike UMTS, it is common to refer to this

subframe structure as the Time Transmission Interval (TTI). The subframe and

slot structure of HS-PDSCH are shown in the next figure .

Slot #0 Slot#1 Slot #2

T slot = 2560 chips, M*10*2 bits (k=4)

Data

data 1 bits

1 subframe: T = 2 ms

On each physical channel, each HS-DSCH radio frame has got 3840000 x 0.02

= 7680 chips. The SF is set to 16, so that is 7680 / 16 = 480 QAM symbols.

Each QAM symbol can encode either 2 bits (QPSK) or 4 bits (16QAM). So we

have 960 bits/subframe or either 1920 bits/subframe. Other way to get to this

number is:

• Number of bits in each slot time = M·10·16; 2k (k = 4)

• Number of bits in each slot with QPSK = 320 bits.

• Number of bits in each slot with 16QAM = 640 bits.



Bits/ HS-DSCHsubframe

Modulation QAM Symbols /subframe

SF Chips bysubframe

Bits/Slot

960 QPSK (M = 2) 7680 / 16 = 480 16 7680 320

1920 16QAM (M = 4) 7680 / 16 = 480 16 7680 640

2880 64QAM (M = 6) 7680 / 16 = 480 16 7680 960

As the number of codes can go from 1 up to 15, the maximum number of bits

that an UE can accept goes from 960 bits/TTI · Number of codes or 1920

bits/TTI · Number of codes depending on the modulation scheme. This

maximum number of accepted bits is important for the rate matching process

in the transmitter.

• Spreading Factor = 16 allows data rates up to 240 ksymbols/sg per

channel.

• HS-DPSCH Data Rate with QPSK (M = 2) – 480 kbits/sg per channel and

code.

• HS-DPSCH Data Rate with 16QAM (M = 4) – 960 kbits/sg per channel andcode.

• HS-DPSCH Data Rate with 64QAM (M = 6) – 1440 kbits/sg per channel

and code.

Subframe structure for the HS-PDSCH

Slot format#i

Bit Rate (kbps) /Channel

Channel Symbol Rate(ksps)

Number bits /TTI

NºCodes

0(QPSK) 480 240 960xNº Codes 1 -15

1(16QAM) 960 240 1920xNº Codes 1 - 15

2(64QAM) 1440 240 2880XNº Codes 1 - 15

The MAC-hs layer in a real network dynamically adjusts the data rate going to a

particular UE based on the amount of data waiting to be transmitted to it and

the RF conditions that UE is experiencing. The amount of data transmitted to a

UE during a particular subframe is defined by the choice of modulation scheme,

number of HS-PDSCHs used and a transport block size index known as the

Transport Format and Resource Indicator (TFRI) value, all of which are signaled

on the HS-SCCH. From these elements the UE can compute the HS-DSCH

Transport Block Size (TBS)

1

that it has been sent (unlike regular DCHs onlya single transport block can be transmitted during a TTI on an HS-

1 The Transport Block Size (TBS) is named as Information Bit Payload in 3 GPP

TS 34.121, and the “Number of SML’s per HARQ process” is the User

Equipment Virtual Incremental Redundancy Buffer.



DSCH). The TFRI value and the process for decoding the TBS can be seen on

Annex ().

The Nominal Average Information Bit Rate transmitted is determined

by multiplying the transport block size (TBS) by the number of blocks

transmitted per second. The number of blocks transmitted in 12 ms isequal to the number of HARQ processes if the inter-TTI interval ·

number HARQ processes < 6. The formula is the next:

The inter-TTI interval signals when data is transmitted to the user. Forexample, an inter-TTI interval of 1 indicates that data will be transmitted to theUE in every TTI (if there are enough active HARQ processes to provide data inevery TTI). How often data is actually transmitted to the UE depends also uponthe User Defined Number of HARQ Processes. The number of HARQ processes

depending on the TTI interval is shown in the next chart, and on table () we cansee the 3GPP TS 25.306 Table 5.1a recommended parameters for each devicetype, where it can be found the minimum TTI interval for each device type. Therelation is also shown in Annex B.

The Fast Hybrid Automatic Repeat Request (Fast HARQ) rapidly retransmits the

missing transport blocks and combines the soft information from the original

transmission with any subsequent retransmission before the decoding process.

This functionality spans both the MAC-hs and the PHY layer. As the MAC-hs is

located at the NodeB the retransmission is rapidly performed. The hybrid

concept refers to a process of combining repeated data transmissions with

prior transmissions to increase the likelihood of successful decoding.

Looking at the table, we can see that these are the possible number of HARQ

processes by TTI Interval.

Inter TTIInterval

Number of HARQProcesses

1 1 - 62 1 – 33 1 – 2

HSDPA allows a very wide range of data rates. To give UE manufacturers some

flexibility over how much functionality they choose to put in their device, 3GPP

TS 25.306 Table 5.1a defines a set of HSDPA UE Categories that restrict those

data rates by specifying attributes such as the minimum inter-TTI value that a

UE can support, the maximum number of HS-PDSCHs it can receive, the size of

http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_rbtest_setup.php#CHDBHDCH




its Incremental Redundancy memory, etc. A network must ensure that it

respects a UE's capabilities when transmitting to it.

HS-DSCHcategory

Maximumnumber of

HS-DSCHcodes

received

Minimuminter-TTI

interval

Maximumnumber of bits

of an HS-DSCHtransport blockreceived within

an HS-DSCHTTI

NOTE 1

Total number of soft

channel bits(User definedIR Buffer Size)

Supportedmodula-tions

without MIMOoperation

or dual celloperation

Category 1 5 3 7298 19200

QPSK, 16QAM

Category 2 5 3 7298 28800

Category 3 5 2 7298 28800

Category 4 5 2 7298 38400

Category 5 5 1 7298 57600

Category 6 5 1 7298 67200

Category 7 10 1 14411 115200

Category 8 10 1 14411 134400

Category 9 15 1 20251 172800Category 10 15 1 27952 172800

Category 11 5 2 3630 14400QPSK

Category 12 5 1 3630 28800

Category 13 15 1 35280 259200 QPSK, 16QAM,64QAMCategory 14 15 1 42192 259200

Category 15 15 1 23370 345600QPSK, 16QAM

Category 16 15 1 27952 345600

Category 17NOTE 2

15 135280 259200

QPSK, 16QAM,64QAM

23370 345600 –

Category 18NOTE 3

15 142192 259200

QPSK, 16QAM,64QAM

27952 345600 –

Category 19 15 1 35280 518400 QPSK, 16QAM,64QAMCategory 20 15 1 42192 518400

NOTE 1: Depending on the HS-DSCH configuration, the indicated maximum number of bits of an HS-

DSCH transport block does not have to correspond exactly to an entry in the transport block size

table to be applied [9].

In the next chart is shown the maximum data rates for some UE categories.

The maximum data rates values can be achieved with the maximum number of

HARQ processes. The formula for the calculation process is ().



Note the User Defined Explicit UE IR Buffer Size per HARQ process column.

When the User Defined UE IR Buffer Allocation is set to Implicit , the total IR

buffer size for the Current UE HS-DSCH Category ("total number of soft channel

bits" in 3GPP TS 25.306 Table 5.1a) is divided equally among the active HARQ

processes. This setting determines the size of the IR buffer allocated to each

HARQ process. This field is important for rate matching process as it will be

seen in figure (). In this case, the explicit definition values match up with the

implicit ones.

When User Defined UE IR Buffer Allocation is set to Explicit, this setting

determines the size of the IR buffer allocated to each HARQ process. The total

IR buffer size is thus determined by multiplying the User Defined Explicit UE IR

Buffer Size by the User Defined Number of HARQ Processes. Note that different

UE categories support different total IR buffer sizes ("total number of soft

channel bits" in 3GPP TS 25.306 Table 5.1a).

Next, it is presented a general overview for the physical channel conformation.

Transport Block Size (Inf. Bit Payload Annex A)

CRC Addition

Code Block Segmentation

24

Turbo Encoding (R = 1/3) 12

http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.php#CHDCDEIA

http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_rbtest_setup.php#CHDBCFIF


http://wireless.agilent.com/rfcomms/refdocs/wcdma/wcdma_gen_bse_hsdpa_info.php#CHDCDEIA





The TBS value is selected from Annex A, and it can be fixed by the CQI

information provided by the UE feedback, as it will be pointed below. Next, it is

performed the CRC addition and the Turbo encoding with a code rate of R =

1/3. Then, it is performed the 1st rate matching. The matched value is set up

depending on the User Defined UE IR Buffer Allocation Value, which can be

calculated as stated above (Referencia cruzada Tabla). After this process, it is

performed the RV selection. This value match up with the Total Number of

Bits / TTI that can be accepted by de Device Type, as stated in the Table () and

it depends on the modulation scheme reported by CQI, which fixes the

maximum number of bits per TTI 960, 1920 or 2880, and on the total number

of channel codes allocated. This information is also provided by the CQI

information. Last stage is the physical channel segmentation of these bits,

which are mapped to as many codes as allocated and the maximum number of

bits can be either 960 for QPSK, 1920 for 16 QAM and 2880 for 64 QAM.

Then, the effective coding rate can be calculated as the relation between the

Redundancy Version Selection and the Transport Block Size and its goes from

0.15 up to 0.97.An example of this process is showed now:

Parameter Unit Value

Nominal Avg. Inf. Bit Rate kbps 534

Inter-TTI Distance TTI’s 3

Number of HARQ Processes Processes

2

Information Bit Payload ( INF N ) Bits 3202

Number Code Blocks Blocks 1

Binary Channel Bits Per TTI Bits 4800

Total Available SML’s in UE SML’s 19200

Number of SML’s per HARQ Proc. SML’s 9600

Coding Rate 0.67

Number of Physical Channel Codes Codes 5

Modulation QPSK

Note: The HS-DSCH shall be transmitted continuously withconstant power but only every third TTI shall beallocated to the UE under test. The values in the tabledefines H-Set 1. H-Set 1A for DC-HSDPA is formedby applying H-Set 1 to each of the carriers availablein DC-HSDPA mode.

1st Rate Matching --- (User Defined UE IR Buffer Allocation Value)

Redundancy Version Selection (Total Number Bits /

Code 1Code 2

Phy Ch Segmentation (960,





This is an User Type Device Category 1 (19200 bits of Total Available SML’s in

UE, as it can be seen on table ()). The Number of SML’s is 19200 / 2 = 9600

bits, where 2 is the Num. of HARQ Processes. This value, according to the Inter

TTI Distance can be 1 or 2. The nominal Avg Inf Bit Rate can be calculated as

3202 · 2 / 12 ms = 534 kbps. The RV value is calculated from the information of

the UE Type and modulation. As it is Category 1 and the modulation is QPSK,the number of bits per TTI is 960. As there are up to 5 codes allocated, the RV

number is set to 4800. The resulting RV selection bits are mapped to the 5

channels of 960 bits each one.

Inf. Bit Payload

CRC Addition

Turbo-Encoding

(R=1/3)

3202

Code Block

Segmentation

1st Rate Matching 9600

Tail Bits129678

3226

CRC243202

RV Selection 4800

Physical Channel

Segmentation 960

So as it has been already appointed, to aid the network in block size selection

the UE transmits a CQI (Channel Quality Indicator) on the uplink HS-DPCCH that

tells the network how much data it can receive. The CQI indicates the

modulation format, number of HS-PDSCHs and block size that the UE could

have received during the previous 2ms subframe with a 90% chance of success. The HSDPA CQI tables depending on user device category can be seen

on Annex ().

ANNEX A FOR TRANSPORT BLOCK SIZE CALCULATION IN HSDPA

Calculation process for TBS: kt = ki + k0,j

The Formula corresponding to table 9.2.3.2 where it can be found k0,j values is

the next:

Formula corresponding to table 9.2.3.2:

If k t < 40

8*)14()(t t k k L +=

else



27

27

5274

8*)(

min

1296

1

min

=

=

=

−

L

p

p Lk L t k

t

end

Table 9.2.3.2: Values of k 0,i for different numbers of channelization codes and modulationschemes, octet aligned (QPSK, 16QAM and 64QAM)

Combination i Modulation

scheme

Number of

channelization codesik ,0

0 QPSK 1 1

1 2 58

2 3 81

3 4 97

4 5 109

5 6 119

6 7 128

7 8 136

8 9 142

9 10 148

10 11 153

11 12 158

12 13 163

13 14 167

14 15 171

15 16QAM 1 58

16 2 97

17 3 119

18 4 136

19 5 148

20 6 158

21 7 167

22 8 174

23 9 181

24 10 187

25 11 192

26 12 197

27 13 201

28 14 206

29 15 209

30 64QAM 1 81

31 2 119

32 3 142



33 4 158

34 5 171

35 6 181

36 7 190

37 8 197

38 9 20439 10 209

40 11 215

41 12 220

42 13 224

43 14 228

44 15 233

The following table provides the mapping between k t (as per the definition in

subclause 9.2.3.1) and the HS-DSCH Transport Block Size (L(k t )) corresponding

to table 9.2.3.2:

Index

TB

Size Index

TB

Size Index

TB

Size Index

TB

Size1 120 86 1000 171 4592 256 210002 128 87 1016 172 4672 257 213843 136 88 1040 173 4760 258 217684 144 89 1056 174 4848 259 221605 152 90 1072 175 4936 260 225606 160 91 1096 176 5024 261 229687 168 92 1112 177 5112 262 233848 176 93 1136 178 5208 263 238089 184 94 1152 179 5296 264 24232

10 192 95 1176 180 5392 265 2467211 200 96 1200 181 5488 266 2512012 208 97 1216 182 5592 267 2556813 216 98 1240 183 5688 268 2603214 224 99 1264 184 5792 269 2650415 232 100 1288 185 5896 270 2697616 240 101 1312 186 6008 271 2746417 248 102 1336 187 6112 272 2796018 256 103 1360 188 6224 273 2846419 264 104 1384 189 6336 274 2897620 272 105 1408 190 6448 275 2950421 280 106 1432 191 6568 276 30032

22 288 107 1456 192 6688 277 3057623 296 108 1488 193 6808 278 3112824 304 109 1512 194 6928 279 3168825 312 110 1536 195 7056 280 3226426 320 111 1568 196 7184 281 3284827 328 112 1600 197 7312 282 3344028 336 113 1624 198 7440 283 3404029 344 114 1656 199 7576 284 34656



30 352 115 1688 200 7712 285 3528031 360 116 1712 201 7856 286 3592032 368 117 1744 202 7992 287 3656833 376 118 1776 203 8136 288 3722434 384 119 1808 204 8288 289 3789635 392 120 1840 205 8440 290 38576

36 400 121 1872 206 8592 291 3927237 408 122 1912 207 8744 292 3998438 416 123 1944 208 8904 293 4070439 424 124 1976 209 9064 294 4144040 440 125 2016 210 9224 295 4219241 448 126 2048 211 939242 456 127 2088 212 956043 464 128 2128 213 973644 472 129 2168 214 991245 480 130 2200 215 1008846 488 131 2240 216 1027247 496 132 2288 217 10456

48 504 133 2328 218 1064849 512 134 2368 219 1084050 528 135 2408 220 1103251 536 136 2456 221 1123252 544 137 2496 222 1143253 552 138 2544 223 1164054 560 139 2592 224 1184855 576 140 2632 225 1206456 584 141 2680 226 1228057 592 142 2736 227 1250458 608 143 2784 228 1272859 616 144 2832 229 12960

60 624 145 2880 230 1319261 640 146 2936 231 1343262 648 147 2984 232 1367263 664 148 3040 233 1392064 672 149 3096 234 1416865 688 150 3152 235 1442466 696 151 3208 236 1468867 712 152 3264 237 1495268 728 153 3328 238 1522469 736 154 3384 239 1549670 752 155 3448 240 1577671 768 156 3512 241 16064

72 776 157 3576 242 1635273 792 158 3640 243 1664874 808 159 3704 244 1694475 824 160 3768 245 1725676 840 161 3840 246 1756877 848 162 3912 247 1788078 864 163 3976 248 1820079 880 164 4048 249 1853680 896 165 4120 250 18864



81 912 166 4200 251 1920882 928 167 4272 252 1955283 952 168 4352 253 1990484 968 169 4432 254 2026485 984 170 4512 255 20632

ANNEX B

ANNEX C



Category Used CQI mapping table

1-6 A

7 and 8 B

9 C

10 D

11 and12

E

13 C

14 D

15 C

16 D

17 C

18 D

19 C

20 D

Table A



CQI valueTransportBlock Size

Number of HS-PDSCH

ModulationReference power

adjustment

NIR Xrv

0 N/A Out of range

1 137 1 QPSK 0 9600 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3565 5 16-QAM 0

17 4189 5 16-QAM 0

18 4664 5 16-QAM 0

19 5287 5 16-QAM 0

20 5887 5 16-QAM 0

21 6554 5 16-QAM 0

22 7168 5 16-QAM0

23 7168 5 16-QAM -1

24 7168 5 16-QAM -2

25 7168 5 16-QAM -3

26 7168 5 16-QAM -4

27 7168 5 16-QAM -5

28 7168 5 16-QAM -6

29 7168 5 16-QAM -7

30 7168 5 16-QAM -8

Table B




Number of HS-PDSCH


adjustment

NIR Xrv

0 N/A Out of range

1 137 1 QPSK 0 19200 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3565 5 16-QAM 0

17 4189 5 16-QAM 0

18 4664 5 16-QAM 0

19 5287 5 16-QAM 0

20 5887 5 16-QAM 0

21 6554 5 16-QAM 0

22 7168 5 16-QAM0

23 9719 7 16-QAM 0

24 11418 8 16-QAM 0

25 14411 10 16-QAM 0

26 14411 10 16-QAM -1

27 14411 10 16-QAM -2

28 14411 10 16-QAM -3

29 14411 10 16-QAM -4

30 14411 10 16-QAM -5

Table C



CQI or CQIS value

TransportBlock Size

Number of HS-PDSCH


adjustment

NIR Xrv or Xrvpb

0 N/A Out of range

1 137 1 QPSK 0 28800 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3565 5 16-QAM 0

17 4189 5 16-QAM 0

18 4664 5 16-QAM 0

19 5287 5 16-QAM 0

20 5887 5 16-QAM 0

21 6554 5 16-QAM 0

22 7168 5 16-QAM0

23 9719 7 16-QAM 0

24 11418 8 16-QAM 0

25 14411 10 16-QAM 0

26 17237 12 16-QAM 0

27 17237 12 16-QAM -1

28 17237 12 16-QAM -2

29 17237 12 16-QAM -3

30 17237 12 16-QAM -4

Table D



CQI or CQIS value

TransportBlock Size

Number of HS-PDSCH


adjustment

NIR Xrv or Xrvpb

0 N/A Out of range

1 137 1 QPSK 0 28800 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3565 5 16-QAM 0

17 4189 5 16-QAM 0

18 4664 5 16-QAM 0

19 5287 5 16-QAM 0

20 5887 5 16-QAM 0

21 6554 5 16-QAM 0

22 7168 5 16-QAM0

23 9719 7 16-QAM 0

24 11418 8 16-QAM 0

25 14411 10 16-QAM 0

26 17237 12 16-QAM 0

27 21754 15 16-QAM 0

28 23370 15 16-QAM 0

29 24222 15 16-QAM 0

30 25558 15 16-QAM 0

Table E




Number of HS-PDSCH


adjustment

NIR Xrv

0 N/A Out of range

1 137 1 QPSK 0 4800 0

2 173 1 QPSK 0

3 233 1 QPSK 0

4 317 1 QPSK 0

5 377 1 QPSK 0

6 461 1 QPSK 0

7 650 2 QPSK 0

8 792 2 QPSK 0

9 931 2 QPSK 0

10 1262 3 QPSK 0

11 1483 3 QPSK 0

12 1742 3 QPSK 0

13 2279 4 QPSK 0

14 2583 4 QPSK 0

15 3319 5 QPSK 0

16 3319 5 QPSK -1

17 3319 5 QPSK -2

18 3319 5 QPSK -3

19 3319 5 QPSK -4

20 3319 5 QPSK -5

21 3319 5 QPSK -6

22 3319 5 QPSK-7

23 3319 5 QPSK -8

24 3319 5 QPSK -9

25 3319 5 QPSK -10

26 3319 5 QPSK -11

27 3319 5 QPSK -12

28 3319 5 QPSK -13

29 3319 5 QPSK -14

30 3319 5 QPSK -15

HSUPA / HSUPA + PHYSICAL TECHNICAL DESCRIPTION

The E-DPDCH is used to carry the E-DCH transport channel. There may be zero,

one, or up to 6 E-DPDCH on each radio link. The E-DPCCH is a physical channel



used to transmit control information associated with the E-DCH. There is at

most one E-DPCCH on each radio link. E-DPDCH and E-DPCCH are always

transmitted simultaneously, except for two cases when E-DPCCH is transmitted

without E-DPDCH (3GPP TS 25.211 section 5.2.1.3):

Figure 2B shows the E-DPDCH and E-DPCCH (sub)frame structure. Each radio

frame is divided in 5 subframes, each of length 2 ms; the first subframe startsat the start of each radio frame and the 5th subframe ends at the end of each

radio frame.

Data, N data bits

Slot #1 Slot #14Slot #2 Slot #iSlot #0

Tslot = 2560 chips, N data = M*10*2kbits (k=0…7)

Tslot = 2560 chips

1 subframe = 2 ms

1 radio frame, T f = 10 ms

E-DPDCHE-DPDCH

E-DPCCH 10 bits

Subframe #0 Subframe #1 Subframe #2 Subframe #3 Subframe #4

Slot #3

Figure 2B: E-DPDCH frame structure

An E-DPDCH may use BPSK or 4PAM modulation symbols. In figure 2B, M is the

number of bits per modulation symbol i.e. M=1 for BPSK and M=2 for 4PAM.

The E-DPDCH slot formats, corresponding rates and number of bits are

specified in Table 5B. The E-DPCCH slot format is listed in Table 5C.

The number of bits per subframe can be estimated as in HSDPA, that is, there

are 7680 chips in a subframe. These value divided by the Spread Factor gives

us the number of symbols per subframe. Then it is only necessary to set the

number of bits per modulation symbol. Other way is to apply the next formula:

Then, the number of bits / subframe = Number of bits per Slot · 3

Another possible equation is the next:

Number of bits / subframe = (3840 / SF) x TTI(ms) sum for all channels. If

there are two channels, TTI = 4 ms.



The data rate of each channel (ksymb / sg) depends on the Spread Factor and

on the modulation type.

Table 5B: E-DPDCH slot formats

Slot Format #i Channel Bit Rate(kbps)

Bits/SymbolM

SF Bits/Frame

Bits/Subframe

Bits/SlotNdata

0 15 1 256 150 30 10

1 30 1 128 300 60 20

2 60 1 64 600 120 40

3 120 1 32 1200 240 80

4 240 1 16 2400 480 160

5 480 1 8 4800 960 320

6 960 1 4 9600 1920 640

7 1920 1 2 19200 3840 1280

8 1920 2 4 19200 3840 1280

9 3840 2 2 38400 7680 2560

The different user devices are presented next, and also the minimum spread

factor is also set up for each category.

Table 5.1g: FDD E-DCH physical layer categories

E-DCHcategory

Maximumnumber of E-DCH codes

transmittedper transport

block

Minimumspreading

factor

Support for 10 and 2 msTTI EDCH

Maximum number of bits of an E-DCHtransport block

transmitted within a10 ms E-DCH TTI

Maximum number of bits of an E-DCHtransport block

transmitted within a 2ms E-DCH TTI

Category 1 1 SF4 10 ms TTIonly

7110 -

Category 2 2 SF4 10 ms and2 ms TTI

14484 2798

Category 3 2 SF4 10 ms TTI

only

14484 -


20000 5772

Category 5 2 SF2 10 ms TTIonly

20000 -


20000 11484

Category 7 4 SF2 10ms and 2ms TTI

20000 22996

Category 8 4 SF2 2 ms TTI - 11484

Category 9 4 SF2 2 ms TTI - 22996

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

UEs of Categories 1 to 6 support QPSK only.

UEs of Category 7 supports QPSK (2 ms TTI, 10 ms TTI) and 16QAM (2 ms TTI).

UEs of Category 8 support only QPSK in Dual Cell E-DCH operation.

UEs of Category 9 support QPSK and 16QAM in Dual Cell E-DCH operation.



As an example we have this table with the process for obtaining the physical

channel for an uplink


Maximum. Inf. Bit Rate kbps 60

TTI ms 2Number of HARQ Processes Processes 8

Information Bit Payload

(NINF)

Bits 120

Binary Channel Bits per TTI

(NBIN)

(3840 / SF x TTI sum for all

channels)

Bits 480

Coding Rate (NINF/ NBIN) 0.25

Physical Channel Codes SF for each

physical

channel

{16}

E-DPDCH/DPCCH power

ratio

E-DPCCH/DPCCH power

ratio

dB

dB

4.08

-9.54

Information Bit Payload NINF = 120

CRC Addition

3 x (NINF+24) = 432

Code Block Segmentation 120+24 = 144

Turbo Encoding (R=1/3)

RV Selection 480

Physical Channel Segmentation 480

24 NINF = 120

12

The Maximum Inf Bit Rate is obtained by calculating the Coding rate and

applying it to the Nominal bit rate of this channel. The SF for the Phy channel is

16, and the Binary Channel Bits per TTI is 480, so looking at table () it is slot

format 2, so the nominal data rate is 240 kbps. The coding rate can be

obtained taking into account that the selected TBS is 120 bits and thesubframe capacity is 480 bits, that is, 0.25 relation. So 240 · 0.25 = 60 kbps.

The TBS sizes values can be found in Annex A, and they are closely related with

the Scheduling methods as well as power control. The network has two

methods for controlling the UE's transmit power on the E-DPDCH; it can either

use a non-scheduled grant or a scheduled grant. In the non-scheduled grant



the network simply tells the UE the maximum block size that it can transmit on

the E-DCH during a TTI. This block size is signaled at call setup and the UE can

then transmit a block of that size or less in each TTI until the call ends or the

network modifies the non-scheduled grant via an RRC reconfiguration

procedure. The block size deterministically maps to a power level, which is also

configured by the network during call setup. The non-scheduling grant is mostsuited for constant-rate delay-sensitive application such as voice-over-IP.

The more interesting method is the scheduled grant. In this case the UE

maintains a Serving Grant that it updates based on information received from

the network. The Serving Grant directly specifies the maximum power the UE

can use on the E-DPDCH in the current TTI. As E-DCH block sizes map

deterministically to power levels, the UE can translate its Serving Grant to the

maximum E-DCH block size it can use in a TTI (the mapping of power levels is

determined by the E-TFCI Reference Power Offsets that are signaled at call

setup).

ANNEX A

E-DCH Transport Block Size Tables for FDD

The mapping between the chosen E-TFCI and the corresponding E-DCH

transport block size is given in the following tables:

B.1 2ms TTI E-DCH Transport Block Size Table 0

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

0 18 30 342 60 1015 90 3008 120 N/A1 120 31 355 61 1053 91 3119 121 92412 124 32 368 62 1091 92 3234 122 95823 129 33 382 63 1132 93 3353 123 99354 133 34 396 64 1173 94 3477 124 103025 138 35 410 65 1217 95 3605 125 106816 143 36 426 66 1262 96 3738 126 110757 149 37 441 67 1308 97 3876 127 114848 154 38 458 68 1356 98 40199 160 39 474 69 1406 99 4167

10 166 40 492 70 1458 100 432111 172 41 510 71 1512 101 448012 178 42 529 72 1568 102 464513 185 43 548 73 1626 103 481614 192 44 569 74 1685 104 499415 199 45 590 75 1748 105 517816 206 46 611 76 1812 106 536917 214 47 634 77 1879 107 556718 222 48 657 78 1948 108 577219 230 49 682 79 2020 109 5985



20 238 50 707 80 2094 110 620621 247 51 733 81 2172 111 643522 256 52 760 82 2252 112 667223 266 53 788 83 2335 113 691824 275 54 817 84 2421 114 717325 286 55 847 85 2510 115 7437

26 296 56 878 86 2603 116 771127 307 57 911 87 2699 117 799628 318 58 944 88 2798 118 829029 330 59 979 89 2901 119 8596

NOTE: Non applicable E-TFCI values are marked as N/A.


E-TFCI TB Size

(bits)

E-TFCI TB Size

(bits)

E-TFCI TB Size

(bits)

0 18 43 2724 86 72521 186 44 2742 87 72882 204 45 3042 88 74283 354 46 3060 89 74644 372 47 3078 90 77645 522 48 3298 91 78006 540 49 3316 92 79087 674 50 3334 93 79448 690 51 3378 94 81009 708 52 3396 95 813610 726 53 3414 96 843611 858 54 3732 97 847212 876 55 3750 98 856413 1026 56 3972 99 860014 1044 57 3990 100 877215 1062 58 4068 101 880816 1194 59 4086 102 910817 1212 60 4404 103 914418 1330 61 4422 104 922019 1348 62 4628 105 925620 1362 63 4646 106 944421 1380 64 4740 107 948022 1398 65 4758 108 978023 1530 66 5076 109 981624 1548 67 5094 110 987625 1698 68 5284 111 991226 1716 69 5302 112 1011627 1734 70 5412 113 1015228 1866 71 5430 114 1045229 1884 72 5748 115 N/A30 1986 73 5766 116 10532



31 2004 74 5940 117 1056832 2022 75 5958 118 1078833 2034 76 6084 119 1082434 2052 77 6102 120 1112435 2070 78 6420 121 1117836 2370 79 6438 122 11188

37 2388 80 6596 123 1124238 2406 81 6614 124 1146039 2642 82 6756 125 1147840 2660 83 677441 2678 84 709242 2706 85 7110


B.2a 2ms TTI E-DCH Transport Block Size Table 2

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

0 18 30 402 60 1405 90 4913 120 171731 120 31 419 61 1465 91 5122 121 N/A2 125 32 437 62 1528 92 5341 122 186673 130 33 455 63 1593 93 5568 123 194624 135 34 475 64 1661 94 5805 124 202915 141 35 495 65 1731 95 6053 125 211556 147 36 516 66 1805 96 6310 126 220567 154 37 538 67 1882 97 6579 127 229958 160 38 561 68 1962 98 6859

9 167 39 585 69 2046 99 715210 174 40 610 70 2133 100 745611 182 41 636 71 2224 101 777412 189 42 663 72 2319 102 810513 197 43 691 73 2417 103 845014 206 44 721 74 2520 104 881015 215 45 752 75 2628 105 918516 224 46 784 76 2740 106 957717 233 47 817 77 2856 107 998518 243 48 852 78 2978 108 1041019 254 49 888 79 3105 109 1085320 265 50 926 80 3237 110 1131621 276 51 965 81 3375 111 1179822 288 52 1007 82 3519 112 1230023 300 53 1049 83 3669 113 1282424 313 54 1094 84 3825 114 1337025 326 55 1141 85 3988 115 1394026 340 56 1189 86 4158 116 1453427 354 57 1240 87 4335 117 1515328 370 58 1293 88 4520 118 1579829 385 59 1348 89 4712 119 16471




B.2b 2ms TTI E-DCH Transport Block Size Table 3E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

E-TFCI TB

Size

(bits)

0 18 30 1902 60 6614 90 14184 120 219661 186 31 1986 61 6774 91 14538 121 223022 204 32 2004 62 7110 92 14874 122 224303 354 33 2034 63 7270 93 15210 123 226384 372 34 2052 64 7446 94 15546 124 229965 522 35 2370 65 7782 95 158826 540 36 2388 66 7926 96 162187 558 37 2642 67 8118 97 165548 674 38 2660 68 8454 98 168909 692 39 2706 69 8582 99 17226

10 708 40 2724 70 8790 100 1756211 858 41 3042 71 9126 101 N/A12 876 42 3060 72 9238 102 N/A13 894 43 3298 73 9462 103 1825214 1026 44 3316 74 9798 104 1847615 1044 45 3378 75 9894 105 1858816 1194 46 3396 76 10134 106 1892417 1212 47 3750 77 10470 107 1913218 1230 48 3990 78 10550 108 1926019 1330 49 4086 79 10806 109 19596

20 1348 50 4422 80 11160 110 1978821 1362 51 4646 81 11224 111 1993222 1380 52 4758 82 11496 112 2026823 1530 53 5094 83 11880 113 2044424 1548 54 5302 84 12168 114 2060425 1566 55 5430 85 12536 115 2094026 1698 56 5766 86 12840 116 2110027 1716 57 5958 87 13192 117 2127628 1866 58 6102 88 13512 118 2161229 1884 59 6438 89 13848 119 21774



E-

TFCI

TB Size

(bits)

E-

TFCI

TB Size

(bits)

E-

TFCI

TB Size

(bits)

E-

TFCI

TB

Size

(bits)

E-

TFCI

TB

Size

(bits)



0 18 30 389 60 1316 90 4452 120 150511 120 31 405 61 1371 91 4636 121 156752 124 32 422 62 1428 92 4828 122 163253 130 33 440 63 1487 93 5029 123 170014 135 34 458 64 1549 94 5237 124 177065 141 35 477 65 1613 95 5454 125 18440

6 147 36 497 66 1680 96 5680 126 192047 153 37 517 67 1749 97 5915 127 200008 159 38 539 68 1822 98 61619 166 39 561 69 1897 99 641610 172 40 584 70 1976 100 668211 180 41 608 71 2058 101 695912 187 42 634 72 2143 102 724713 195 43 660 73 2232 103 754714 203 44 687 74 2325 104 786015 211 45 716 75 2421 105 818616 220 46 745 76 2521 106 852517 229 47 776 77 2626 107 8878

18 239 48 809 78 2735 108 924619 249 49 842 79 2848 109 962920 259 50 877 80 2966 110 1002821 270 51 913 81 3089 111 1044422 281 52 951 82 3217 112 1087723 293 53 991 83 3350 113 1132824 305 54 1032 84 3489 114 1179725 317 55 1074 85 3634 115 1228626 331 56 1119 86 3784 116 1279527 344 57 1165 87 3941 117 1332528 359 58 1214 88 4105 118 1387729 374 59 1264 89 4275 119 14453


E-TFCI TB Size

(bits)

E-TFCI TB Size

(bits)

E-TFCI TB Size

(bits)

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

10 876 51 6756 92 1353011 1026 52 6774 93 1381212 1044 53 7092 94 1386613 1194 54 7110 95 14148



14 1212 55 7428 96 1420215 1362 56 7464 97 1448416 1380 57 7764 98 1455617 1530 58 7800 99 1482018 1548 59 8100 100 1489219 1698 60 8136 101 15156

20 1716 61 8436 102 1522821 1866 62 8472 103 1549222 1884 63 8772 104 1556423 2034 64 8808 105 1582824 2052 65 9108 106 1590025 2370 66 9144 107 1616426 2388 67 9444 108 1623627 2706 68 9480 109 1650028 2724 69 9780 110 1657229 3042 70 9816 111 1717230 3060 71 10116 112 1724431 3378 72 10152 113 17844

32 3396 73 10452 114 1791633 3732 74 10488 115 1851634 3750 75 10788 116 1860635 4068 76 10824 117 1918836 4086 77 11124 118 1927837 4404 78 11178 119 1986038 4422 79 11460 120 1995039 4740 80 1151440 4758 81 11796

1. LTE PHYSICAL TEHCNICAL DESCRIPTION The Phy layer of LTE is based on the use of OFDMA for the downlink and SC-

FDMA for the uplink. LTE rather than having dedicated resources reserved for a

single user, is based on a dynamically allocated resource sharing. The possible

modulation schemes employed for both downlink and uplink are the QPSK, the

16QAM and the 64QAM.

As a consequence, LTE contains only common transport channels which are the

interface between the Medium Access Control (MAC) sublayer and the Phy

layer. The transport channel for the uplink is the Uplink Shared Channel (UL-

SCH) and for the downlink is the Downlink Shared Channel (DL -SCH). The

mapping of these channel onto Phy ones is the next; the UL-SCH is mappedinto the Physical Uplink Shared Channel (PUSCH), and the DL-SCH is mapped

into the Physical Downlink Shared Channel (PDSCH).

Frame structure type 1 is applicable to both full duplex and half duplex FDD.

Each radio frame is ms10307200 sf =⋅= T T long and consists of 20 slots of length

ms5.0T15360 sslot =⋅=T , numbered from 0 to 19. A subframe is defined as two

consecutive slots where subframe i consists of slots i2 and 12 +i .



For FDD, 10 subframes are available for downlink transmission and 10

subframes are available for uplink transmissions in each 10 ms interval. Uplink

and downlink transmissions are separated in the frequency domain. In half-

duplex FDD operation, the UE cannot transmit and receive at the same time

while there are no such restrictions in full-duplex FDD.

Figure 4.1-1: Frame structure type 1.

This table shows the relation between the Channel bandwidth (BWChannel) and

the Transmission bandwidth configuration (NRB).

Table 5.6-1 Transmission bandwidth configuration N RB in E-UTRA channel bandwidths

Channel bandwidthBWChannel [MHz]

1.4 3 5 10 15 20

Transmission bandwidthconfiguration N RB

6 15 25 50 75 100

Slot structure and physical resources in Uplink

Resource grid

The transmitted signal in each slot is described by a resource grid of RBsc

ULRB N N

subcarriers andULsymb N SC-FDMA symbols. The resource grid is illustrated in

Figure 5.2.1-1. The quantity ULRB N depends on the uplink transmission

bandwidth configured in the cell and shall fulfil



ULmax,RB

ULRB

ULmin,RB N N N ≤≤

where 6ULmin,

RB = N and 110ULmax,

RB = N are the smallest and largest uplink

bandwidths, respectively, supported by the current version of this specification.

The set of allowed values for ULRB N is given by [7].

The number of SC-FDMA symbols in a slot depends on the cyclic prefix length

configured by the higher layer parameter UL-CyclicPrefixLength and is given in

Table 5.2.3-1.

ULsymb N SC -FDMA symbols

One uplink slot slotT

0=l 1ULsymb −= N l

s u b c a r r i e r s


RBsc

ULsymb N N ×

Resource block

resource elements

Resource element ),( l k

0=k

1RB

sc

UL

RB−= N N k

Figure 5.2.1-1: Uplink resource grid.

Resource elements

Each element in the resource grid is called a resource element and is uniquely

defined by the index pair ( )l k , in a slot where 1,...,0RBsc

ULRB −= N N k and 1,...,0

ULsymb −= N l

are the indices in the frequency and time domains, respectively. Resource

element ( )l k , corresponds to the complex value l k a , . Quantities l k a ,



corresponding to resource elements not used for transmission of a physical

channel or a physical signal in a slot shall be set to zero.

Resource blocks

A physical resource block is defined asULsymb N consecutive SC-FDMA symbols in

the time domain and RBsc N consecutive subcarriers in the frequency domain,

whereULsymb N and RB

sc N are given by Table 5.2.3-1. A physical resource block

in the uplink thus consists of RBsc

ULsymb N N × resource elements, corresponding to

one slot in the time domain and 180 kHz (12 subcarriers · 15 Khz of separation

between sc.) in the frequency domain.

Table 5.2.3-1: Resource block parameters.

Configuration RBsc N

ULsymb N

Normal cyclic prefix 12 7

Extended cyclic prefix 12 6

The relation between the physical resource block number PRBn in the frequency

domain and resource elements ),( l k in a slot is given by

Slot structure and physical resource elements in Downlink

Resource grid The transmitted signal in each slot is described by a resource grid of RB

scDLRB N N

subcarriers and DLsymb N OFDM symbols. The resource grid structure is illustrated

in Figure 6.2.2-1. The quantity DLRB N depends on the downlink transmission

bandwidth configured in the cell and shall fulfil

DLmax,RB

DLRB

DLmin,RB N N N ≤≤

where 6DLmin,

RB = N and 110DLmax,

RB = N are the smallest and largest downlink

bandwidths, respectively, supported by the current version of this specification.

The set of allowed values for DLRB N is given by [6]. The number of OFDM

symbols in a slot depends on the cyclic prefix length and subcarrier spacing

configured and is given in Table 6.2.3-1.

In case of multi-antenna transmission, there is one resource grid defined per

antenna port. An antenna port is defined by its associated reference signal. The



set of antenna ports supported depends on the reference signal configuration

in the cell:

- Cell-specific reference signals, associated with non-MBSFN transmission, support a configuration of

one, two, or four antenna ports and the antenna port number p shall fulfil 0= p , { }1,0∈ p , and

{ }3,2,1,0∈ p , respectively.

- MBSFN reference signals, associated with MBSFN transmission, are transmitted on antenna port4= p .

- UE-specific reference signals are transmitted on antenna port(s) 5= p , 7= p , 8= p , or }8,7{∈ p .

- Positioning reference signals are transmitted on antenna port 6= p .

Resource elements

Each element in the resource grid for antenna port p is called a resource

element and is uniquely identified by the index pair ( )l k , in a slot where

1,...,0 RBsc

DLRB −= N N k and 1,...,0 DL

symb −= N l are the indices in the frequency and time

domains, respectively. Resource element ( )l k , on antenna port p corresponds

to the complex value)(

, pl k a . When there is no risk for confusion, or no particular

antenna port is specified, the index p may be dropped.



DLsymb N OFDM symbols

One downlink slot slotT

0=l 1DLsymb −= N l



RBsc

DLsymb N N ×

Resource block

resource elements

Resource element ),( l k

0=k

1RBsc

DLRB −= N N k

Figure 6.2.2-1: Downlink resource grid.

Resource blocks

Resource blocks are used to describe the mapping of certain physical channels

to resource elements. Physical and virtual resource blocks are defined.

A physical resource block is defined asDLsymb N consecutive OFDM symbols in the

time domain and RBsc N consecutive subcarriers in the frequency domain, where

DLsymb N and RB

sc N are given by Table 6.2.3-1. A physical resource block thus

consists of RBsc

DLsymb N N × resource elements, corresponding to one slot in the time

domain and 180 kHz in the frequency domain.



Physical resource blocks are numbered from 0 to 1DLRB − N in the frequency

domain. The relation between the physical resource block number PRBn in the

frequency domain and resource elements ),( l k in a slot is given by

= RBsc

PRB N

k

n

Table 6.2.3-1: Physical resource blocks parameters.

ConfigurationRBsc N DL

symb N

Normal cyclic

prefixkHz15=∆ f

127

Extended cyclic

prefix

kHz15=∆ f 6

kHz5.7=∆ f 24 3

A virtual resource block is of the same size as a physical resource block. Two

types of virtual resource blocks are defined:

- Virtual resource blocks of localized type

- Virtual resource blocks of distributed type

For each type of virtual resource blocks, a pair of virtual resource blocks over two slots in a subframe is

assigned together by a single virtual resource block number, VRBn .

Virtual resource blocks of localized type

Virtual resource blocks of localized type are mapped directly to physical

resource blocks such that virtual resource block VRBn corresponds to physical

resource block VRBPRB nn = . Virtual resource blocks are numbered from 0 to

1DLVRB − N , where DL

RBDLVRB N N = .

Virtual resource blocks of distributed type

Virtual resource blocks of distributed type are mapped to physical resource

blocks as described below.

Table 6.2.3.2-1: RB gap values.

System BW (DLRB N )

Gap ( gap N )

1st Gap (

gap,1 N )

2nd Gap (

gap,2 N )

6-10 2/DL

RB N N/A



11 4 N/A

12-19 8 N/A

20-26 12 N/A27-44 18 N/A

45-49 27 N/A

50-63 27 9

64-79 32 16

80-110 48 16

The virtual resource mapping to RB gaps can be found in section 6.2.3.2 in

3GPP TS 36.211 V9.0.0

Downlink data transmissionData is allocated to the UEs in terms of resource blocks, i.e. one UE can beallocated integer multiples of one resource block in the frequency domain.

These resource blocks do not have to be adjacent to each other. In the timedomain, the scheduling decision can be modified every transmission timeinterval of 1 ms. The scheduling decision is done in the base station (eNodeB).

The scheduling algorithm has to take into account the radio link qualitysituation of different users, the overall interference situation, Quality of Service

requirements, service priorities, etc. Figure 1 shows an example for allocatingdownlink user data to different users (UE 1 – 6). The user data is carried on thePhysical Downlink Shared Channel (PDSCH).



Downlink control channels The Physical Downlink Control Channel (PDCCH) is mainly used to convey thescheduling decisions to individual UEs, i.e. scheduling assignments for uplinkand downlink. The PDCCH is located in the first OFDM symbols of a subframe.An additional Physical Control Format Indicator Channel (PCFICH) carried onspecific resource elements in the first OFDM symbol of the subframe is used toindicate the number of OFDM symbols for the PDCCH (1, 2, 3, or 4 symbols arepossible depending on BW).

The information carried on PDCCH is referred to as downlink controlinformation (DCI). Depending on the purpose of the control message,different formats of DCI are defined.

Carried by Type PurposesDCI F0 PUSCH PUSCH type 2.

PUCCH formatstypes 1a, 1b, 2,2a, 2b.

Convey uplinkscheduling grants.Contiguous RB inUL.

DCI F1 PDCCH 0,1,2 The assignment of adownlink sharedchannel resource

when no spatialmultiplexing isused.

DCI F2 PDCCH 0,1,2 DCI formats 2 and2A provide downlinkshared channelassignments in caseof closed loop oropen loop spatial



multiplexing,respectivel

DCI F3 PDCCH Power control forUL.

DCI format 1 is used for the assignment of a downlink shared channel resource

when no spatial multiplexing is used (i.e. the scheduling information isprovided for one code word only). The information provided containseverything what is necessary for the UE to be able to identify the resourceswhere to receive the PDSCH in that subframe and how to decode it. Besides theresource block assignment, this also includes information on the modulationand coding scheme and on the hybrid ARQ protocol. DCI formats 2 and 2Aprovide downlink shared channel assignments in case of closed loop or openloop spatial multiplexing, respectively. In these cases, scheduling information isprovided for two code words within one control message. Additionally there isDCI format 0 to convey uplink scheduling grants, and DCI formats 3 and 3a toconvey transmit power control (TPC) commands for the uplink.

There is different ways to signal the resource allocation within DCI, in order totrade off between signaling overhead and flexibility. For example, DCI format 1may use resource allocation types 0 or 1 as described in the following. Anadditional resource allocation type 2 method is specified for other DCI formats.

In resource allocation type 0, resource block assignment informationincludes a bitmap indicating the resource block groups (RBGs) that areallocated to the scheduled UE where a RBG is a set of consecutive virtual

resource blocks (VRBs) of localized type. The allocated resource block groups donot have to be adjacent to each other. Resource block group size (P) is afunction of the system bandwidth as shown in Table 7.1.6.1-1. The total

number of RBGs ( RBG N ) for downlink system bandwidth of

DL

RB N

is given by P N N RBG /DL

RB= where P N /DLRB of the RBGs are of size P and if 0modDL

RB > P N then

one of the RBGs is of size P N P N /DLRB

DLRB ⋅− . The bitmap is of size RBG N bits with

one bitmap bit per RBG such that each RBG is addressable. The RBGs shall beindexed in the order of increasing frequency and non-increasing RBG sizesstarting at the lowest frequency. The order of RBG to bitmap bit mapping is in

such way that RBG 0 to RBG 1RBG − N are mapped to MSB to LSB of the bitmap.

The RBG is allocated to the UE if the corresponding bit value in the bitmap is 1,the RBG is not allocated to the UE otherwise.

Table 7.1.6.1-1: Type 0 Resource Allocation RBG Size vs. Downlink System Bandwidth

System

Bandwidth

RBG

Size

DLRB N (P)



≤10 1

11 – 26 2

27 – 63 3

64 – 110 4

In resource allocation type 1, a bitmap indicates physical resource blocks

inside a selected resource block group subset. The resource block assignment

information of size RBG N indicates to a scheduled UE the VRBs from the set of

VRBs from one of P RBG subsets. The virtual resource blocks used are of

localized type. Also P is the RBG size associated with the system bandwidth as

shown in Table 7.1.6.1-1. A RBG subset p , where P p <≤0 , consists of every

P th RBG starting from RBG p

. The information field for the resource blockassignment on PDCCH is therefore split up into 3 parts: one part indicates the

selected resource block group subset.

The first field with )(log2 P bits is used to indicate the selected RBG subset

among P RBG subsets.

The second field with one bit is used to indicate a shift of the resource

allocation span within a subset. A bit value of 1 indicates shift is triggered. Shift

is not triggered otherwise.

The third field includes a bitmap, where each bit of the bitmap addresses asingle VRB in the selected RBG subset in such a way that MSB to LSB of the

bitmap are mapped to the VRBs in the increasing frequency order. The VRB is

allocated to the UE if the corresponding bit value in the bit field is 1, the VRB is

not allocated to the UE otherwise. The portion of the bitmap used to address

VRBs in a selected RBG subset has size TYPE1RB N and is defined as

1)(log/ 2DLRB

TYPE1RB −−= P P N N

In resource allocation type 2, physical resource blocks are not directly

allocated. Instead, virtual resource blocks are allocated which are then mappedonto physical resource blocks. The information field for the resource block

assignment carried on PDCCH contains a resource indication value (RIV) from

which a starting virtual resource block and a length in terms of contiguously

allocated virtual resource blocks can be derived. Both localized and distributed

virtual resource block assignment is possible which are differentiated by a one-

bit-flag within the DCI. In the localized case, there is a one-to-one mapping

between virtual and physical resource blocks.





Modulation order and Transport Block Size (TBS)

To determine the modulation order and transport block size(s) in the physical

downlink shared channel, the UE shall first

− read the 5-bit “modulation and coding scheme” field ( MCS I ) in the DCI

and second if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then

− for DCI format 1A:

o set the Table 7.1.7.2.1-1 column indicator PRB N to 1APRB N from Section

5.3.3.1.3 in [4]

− for DCI format 1C:

o use Table 7.1.7.2.3-1 for determining its transport block size.

else

7.1.7.1Modulation order determination

The UE shall use mQ = 2 if the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-

RNTI, otherwise, the UE shall use MCS I and Table 7.1.7.1-1 to determine the

modulation order ( mQ ) used in the physical downlink shared channel.



Table 7.1.7.1-1: Modulation and TBS index table for PDSCH

MCS Index

MCS I

Modulation Order

mQ

TBS Index

TBS I

0 2 0

1 2 1

2 2 23 2 3

4 2 4

5 2 5

6 2 6

7 2 7

8 2 8

9 2 9

10 4 9

11 4 10

12 4 11

13 4 12

14 4 13

15 4 1416 4 15

17 6 15

18 6 16

19 6 17

20 6 18

21 6 19

22 6 20

23 6 21

24 6 22

25 6 23

26 6 24

27 6 25

28 6 26

29 2

reserved30 4

31 6

7.1.7.2Transport block size determination

If the DCI CRC is scrambled by P-RNTI, RA-RNTI, or SI-RNTI then

− for DCI format 1A:

o the UE shall set the TBS index ( TBS I ) equal to MCS I and determine

its TBS by the procedure in Section 7.1.7.2.1.

− for DCI format 1C:

o the UE shall set the TBS index ( TBS I ) equal to MCS I and determine

its TBS from Table 7.1.7.2.3-1.

else



for 280 MCS ≤≤ I , the UE shall first determine the TBS index ( TBS I ) using MCS I

and Table 7.1.7.1-1 except if the transport block is disabled in DCIformats 2, 2A and 2B as specified below. For a transport block that is notmapped to two-layer spatial multiplexing, the TBS is determined by theprocedure in Section 7.1.7.2.1. For a transport block that is mapped totwo-layer spatial multiplexing, the TBS is determined by the procedure inSection 7.1.7.2.2.

The status of the downlink channel is proviced via the PUSCH channel from the

UE to the eNodeB. This is performed through the CQI.

The CQI indices and their interpretations are given in Table 7.2.3-1.

Based on an unrestricted observation interval in time and frequency, the UE

shall derive for each CQI value reported in uplink subframe n the highest CQI

index between 1 and 15 in Table 7.2.3-1

A combination of modulation scheme and transport block size corresponds to aCQI index if:

- the combination could be signalled for transmission on the PDSCH in theCQI reference resource according to the relevant Transport Block Sizetable, and

- the modulation scheme is indicated by the CQI index, and

- the combination of transport block size and modulation scheme whenapplied to the reference resource results in the effective channel code ratewhich is the closest possible to the code rate indicated by the CQI index.If more than one combination of transport block size and modulationscheme results in a effective channel code rate equally close to the coderate indicated by the CQI index, only the combination with the smallestof such transport block sizes is relevant.



Table 7.2.3-1: 4-bit CQI Table

CQI index modulation code rate x 1024 efficiency

0 out of range

1 QPSK 78 0.1523

2 QPSK 120 0.2344

3 QPSK 193 0.3770

4 QPSK 308 0.60165 QPSK 449 0.8770

6 QPSK 602 1.1758

7 16QAM 378 1.4766

8 16QAM 490 1.9141

9 16QAM 616 2.4063

10 64QAM 466 2.7305

11 64QAM 567 3.3223

12 64QAM 666 3.9023

13 64QAM 772 4.5234

14 64QAM 873 5.1152

15 64QAM 948 5.5547

Data Transmission Uplink

Scheduling of uplink resources is done by eNodeB. The eNodeB assigns certain

time/frequency resources to the UEs and informs UEs about transmission

formats to use. In uplink, data is allocated in multiples of one resource block.

Uplink resource block size in the frequency domain is 12 subcarriers, i.e. the

same as in downlink. However, not all integer multiples are allowed in order to

simplify the DFT design in uplink signal processing. UEs are always assigned

contiguous resources in the LTE uplink.

The uplink transmission time interval is 1 ms (same as downlink). User data is

carried on the Physical Uplink Shared Channel (PUSCH). The UE derives the

uplink resource allocation as well as frequency hopping information from the

uplink scheduling grant that was received four subframes before. DCI

(Downlink Control Information) format 0 is used on PDCCH to convey the uplink

scheduling grant.

When a UE has ACK/NACK to send in response to a downlink PDSCH

transmission, it will derive the exact PUCCH resource to use from the PDCCH

transmission (i.e. the number of the first control channel element used for the

transmission of the corresponding downlink resource assignment). When a UE

has a scheduling request or CQI to send, higher layers will configure the exact

PUCCH resource. The sounding reference signal provides uplink channel quality

information as a basis for scheduling decisions in the base station.



The resource allocation information indicates to a scheduled UE a set of

contiguously allocated virtual resource block indices denoted by VRBn . A

resource allocation field in the scheduling grant consists of a resource

indication value (RIV ) corresponding to a starting resource block ( START RB ) and a

length in terms of contiguously allocated resource blocks ( CRBs L ≥ 1). The

resource indication value is defined by

if 2/)1(ULRBCRBs N L ≤− then

STARTCRBsULRB )1( RB L N RIV +−=

else

)1()1( STARTULRBCRBs

ULRB

ULRB RB N L N N RIV −−++−=

A UE shall discard PUSCH resource allocation in the corresponding PDCCH with

DCI format 0 if consistent control information is not detected.

Modulation order and redundancy version determination

To determine the modulation order, redundancy version and transport block

size for the physical uplink shared channel, the UE shall first

− read the “modulation and coding scheme and redundancy version” field (

MCS I ), and

− check the “CQI request” bit, and

− compute the total number of allocated PRBs ( PRB N ) based on theprocedure defined in Section 8.1, and

− compute the number of coded symbols for control information.

For 280 MCS ≤≤ I , the modulation order ( mQ ) is determined as follows:

− If the UE is capable of supporting 64QAM in PUSCH and has not beenconfigured by higher layers to transmit only QPSK and 16QAM, the

modulation order is given by 'mQ in Table 8.6.1-1.

− If the UE is not capable of supporting 64QAM in PUSCH or has been

configured by higher layers to transmit only QPSK and 16QAM,'

mQ is firstread from Table 8.6.1-1. The modulation order is set to ),4min( '

mm QQ = .

− If the parameter ttiBundling provided by higher layers is set to TRUE, then

the resource allocation size is restricted to 3PRB ≤ N and the modulation

order is set to 2=mQ .



For 3129 MCS ≤≤ I , if 29MCS = I , the “CQI request” bit in DCI format 0 is set to 1 and

4PRB ≤ N , the modulation order is set to 2=mQ . Otherwise, the modulation order

shall be determined from the DCI transported in the latest PDCCH with DCI

format 0 for the same transport block using 280 MCS ≤≤ I . If there is no PDCCH

with DCI format 0 for the same transport block using 280 MCS ≤≤ I , themodulation order shall be determined from

− the most recent semi-persistent scheduling assignment PDCCH, when theinitial PUSCH for the same transport block is semi-persistently scheduled,or,

− the random access response grant for the same transport block, when thePUSCH is initiated by the random access response grant.

The UE shall use MCS I and Table 8.6.1-1 to determine the redundancy version

(rv idx ) to use in the physical uplink shared channel.

Table 8.6.1-1: Modulation, TBS index and redundancy version table for PUSCH

MCS Index

MCS I

Modulation

Order'

mQ

TBS

Index

TBS I

Redundancy

Version

rvidx

0 2 0 0

1 2 1 0

2 2 2 0

3 2 3 0

4 2 4 0

5 2 5 0

6 2 6 0

7 2 7 0

8 2 8 0

9 2 9 0

10 2 10 0

11 4 10 0

12 4 11 0

13 4 12 0

14 4 13 0

15 4 14 0

16 4 15 0

17 4 16 0

18 4 17 0

19 4 18 020 4 19 0

21 6 19 0

22 6 20 0

23 6 21 0

24 6 22 0

25 6 23 0

26 6 24 0

27 6 25 0



28 6 26 0

29

reserved

1

30 2

31 3

8.6.2 Transport block size determination

For 280 MCS ≤≤ I , the UE shall first determine the TBS index ( TBS I ) using MCS I and

Table 8.6.1-1. The UE shall then follow the procedure in Section 7.1.7.2.1 to

determine the transport block size.

For 3129 MCS ≤≤ I , if 29MCS = I , the “CQI request” bit in DCI format 0 is set to 1 and

4PRB ≤ N , then there is no transport block for the UL-SCH and only the control

information feedback for the current PUSCH reporting mode is transmitted by

the UE. Otherwise, the transport block size shall be determined from the initial

PDCCH for the same transport block using 280 MCS ≤≤ I . If there is no initialPDCCH with DCI format 0 for the same transport block using 280 MCS ≤≤ I , the

transport block size shall be determined from

− the most recent semi-persistent scheduling assignment PDCCH, when theinitial PUSCH for the same transport block is semi-persistently scheduled,or,

− the random access response grant for the same transport block, when thePUSCH is initiated by the random access response grant.

EXAMPLES

A.2.1.2 Determination of payload size

The algorithm for determining the payload size A is as follows; given a desired

coding rate R and radio block allocation NRB

1. Calculate the number of channel bits N ch that can be transmitted during the first transmission of a given

sub-frame.

2. Find A such that the resulting coding rate is as close to R as possible, that is,

ch N A R /)24(min +− ,

subject to

a) A is a valid TB size according to section 7.1.7 of TS 36.213 [6] assuming an allocation of N RB

resource blocks.

b) Segmentation is not included in this formula, but should be considered in the TBS calculation.



c) For RMC-s, which at the nominal target coding rate do not cover all the possible UE categories

for the given modulation, reduce the target coding rate gradually (within the same modulation),

until the maximal possible number of UE categories is covered.

3. If there is more than one A that minimises the equation above, then the larger value is chosen per

default.

UL QPSK Table A.2.2.1.1-1 Reference Channels for QPSK with full RB allocation


Channel bandwidth MHz 1.4 3 5 10 15 20

Allocated resource blocks 6 15 25 50 75 100

DFT-OFDM Symbols per Sub-Frame 12 12 12 12 12 12

Modulation QPSK QPSK QPSK QPSK QPSK QPSK

Target Coding rate 1/3 1/3 1/3 1/3 1/5 1/6

Payload size Bits 600 1544 2216 5160 4392 4584

Transport block CRC Bits 24 24 24 24 24 24

Number of code blocks per Sub-Frame(Note 1)

1 1 1 1 1 1

Total number of bits per Sub-Frame Bits 1728 4320 7200 14400 21600 28800

Total symbols per Sub-Frame 864 2160 3600 7200 10800 14400

UE Category 1-5 1-5 1-5 1-5 1-5 1-5

Note 1: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attachedto each Code Block (otherwise L = 0 Bit)

The EnodeB is supposed to have scheduled the considered UE with all the RBsallowed. The information is codified in the DCI and the parameters are the 1.4MHz channel BW ( 6 RB) and the modulation scheme, QPSK, as well as the



desiring coding rate (extracted from the CQI information). So the process is thenext:

6RB · 12 = 72 sc

1 symbol/slot is employed for UL demodulation reference signals, which areused for channel estimation for coherent demodulation, and are transmitted inthe fourth symbol (i.e symbol number 3) of the slot.. So we have 6 symbols /slot, that is, 12 symbols /subframe. The number of symbols per subframe is 72· 12 = 864, as the modulation is QPSK, that is 1728 bits per subframe.Applying the formula, min(1/3 – (A + 24) 1728) = 552 and looking at the Table7.1.7.2.1-1in 36.213, the nearest value is 600 bits of payload.

For the Downlink,

Table A.3.2-3 Fixed Reference Channel for Maximum input level for UE Categories 3-5 (FDD)


Channel bandwidth MHz 1.4 3 5 10 15 20

Allocated resource blocks 6 15 25 50 75 100

Subcarriers per resource block 12 12 12 12 12 12 Allocated subframes per Radio Frame 10 10 10 10 10 10

Modulation 64QAM 64QAM 64QAM 64QAM 64QAM 64QAM

Target Coding Rate 3/4 3/4 3/4 3/4 3/4 3/4

Number of HARQ Processes Processes 8 8 8 8 8 8

Maximum number of HARQ transmissions 1 1 1 1 1 1

Information Bit Payload per Sub-Frame

For Sub-Frames 1,2,3,4,6,7,8,9 Bits 2984 8504 14112 30576 46888 61664

For Sub-Frame 5 Bits n/a n/a n/a n/a n/a n/a

For Sub-Frame 0 Bits n/a 6456 12576 28336 45352 61664

Transport block CRC Bits 24 24 24 24 24 24

Number of Code Blocks per Sub-Frame(Note 4)

For Sub-Frames 1,2,3,4,6,7,8,9 1 2 3 5 8 11

For Sub-Frame 5 n/a n/a n/a n/a n/a n/aFor Sub-Frame 0 n/a 2 3 5 8 11

Binary Channel Bits Per Sub-Frame

For Sub-Frames 1,2,3,4,6,7,8,9 Bits 4104 11340 18900 41400 62100 82800

For Sub-Frame 5 Bits n/a n/a n/a n/a n/a n/a

For Sub-Frame 0 Bits n/a 8820 16380 38880 59580 80280

Max. Throughput averaged over 1 frame kbps 2387.2 7448.8 12547 27294 42046 55498

Note 1: 2 symbols allocated to PDCCH for 20 MHz, 15 MHz and 10 MHz channel BW. 3 symbols allocated to PDCCHfor 5 MHz and 3 MHz. 4 symbols allocated to PDCCH for 1.4 MHz

Note 2: Reference signal, Synchronization signals and PBCH allocated as per TS 36.211 [4]Note 3: If more than one Code Block is present, an additional CRC sequence of L = 24 Bits is attached to each Code

Block (otherwise L = 0 Bit)

Where the information provided by eNodeB in the DCI format (1 or 2) is thenumber of allocated RB (that is, the channel BW), the Modulation scheme andthe Target Coding Rate (via a CQI information from the UE). The number of bitsper subframe is calculated next:

First, take into account the Control Channel information corresponding to boththe primary and secondary syncronization channels (P-SCH, S-SCH). They arelocated at the 6 and 5 symbol respectively of the first slot (number 0) of theframe, that is, the 0 subframe, as well as the 10 slot of the frame (subframe 5).



They occupy 62 subcarriers each one although they are transmitted over 72subcarriers.

The PBCH is the Physical BroadCast Channel and it is located next to the S-SCHsymbol and it occupies symbols 0,1,2,3 of the second slot (number 1) of thesubframe number 0. It also occupies 72 subcarriers.

The reference signal is transmitted on symbol 0 and 4 of each slot and itoccupies one resource element every 6 subcarriers if we are using a singleantenna. Otherwise, the number of subcarriers spacing vary. For example, fortwo antennas, the Resource Elements for OFDM symbols (0 and 4) and sub-carrier frequencies (3, 6, 9, and 12 in each Resource Block) of each slot.

The PDCCH control information associated to the data is transmited in the firstsymbols of each subframe (first slot) and it can occupy 0,1,2,3,4 symbolsdepending on the BW.



For example, for 1.4 MHz channel Bandwidth:

Number of subcarriers: 6 RB · 12sc = 72 sc

Total Number of Resource Element per subframe = 72 sc · 14 = 1008 re(Normal prefix)

Number of symbols allocated to PDCCH: 4 with 72 sc = 288 re

Number of associated re to P-SCH and S – SCH = 72 + 72 = 144 re

Number of associated re to PBCH: 72sc · 4(symb) = 288 re

Number of associated re to Reference signal non coincident with the PBCHsymbol 0 of slot 1 or PDCCH symbol 0 of slot 0. Only the r.e. placed at the 4th

symbol of both slot are not coincident with anyone of this control informationchannels. The re placed in the 0 symbol of slot 0 is coincident with PDCCH andthe placed in the 0 symbol of slot 1 partially overlap with the PBCH. So the renot overlapping are (symb 4) 4 r.e. per 12 sc equals 24 re. The partiallyoverlapped at symbol 0 of slot 1. In this case, as the DBCH occupy the whole72 sc, the re are also overlapped with them. So we have 24 re.

72 sc · (14 symb/sub – 4 Note1) = 4320 bits / subframe – other control bits =4104 per subframe.



¾ effective channel codde rate = (Num DL info bits + CRC) / num PHY bitsPDSCH

2984 · 8 (subframes) / 10 msg = 2387.2 kbps.

Calculation Proccess.

ANNEX A

Codeword: A codeword represents user data before it is formatted fortransmission. One or two codewords, CW0 and CW1, can be used depending onthe prevailing channel conditions and use case. In the most common case of single-user MIMO (SU-MIMO), two codewords are sent to a single UE, but in thecase of the less common downlink multi-user MIMO (MU-MIMO), each codewordis sent to only one UE.

• Layer: The term layer is synonymous with stream. For spatial multiplexing, atleast two layers must be used. Up to four are allowed. The number of layers isdenoted by the symbol ν (pronounced nu). The number of layers is always lessthan or equal to the number of antennas.

Documents

Raw Data Rate