Raw Data Rate

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 some
technologies, 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 Medium
Dependent (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 between
802.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 uses
OFDM, (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 correlation
processes 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
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 /
DSSS
DQPSK 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, the
transmission is set up in 1.375 million symbols per second.
PHY
Layer
Coding /
Modulation
Bits/Sym
bol
Max
Throughput
DSSS 1 DBPSK 1 Mbps
DSSS 2 DQPSK 2 Mbps
DSSS 4 CCK 5.5 Mbps
DSSS 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 cope
with 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 Mbps
DSSS DQPSK 2 2 Mbps
DSSS CCK 4 5.5 Mbps
DSSS 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 Mbps
OFDM QPSK R = 2 48
12
Mbps
OFDM QPSK R = 2 72
18
Mbps
OFDM 16 QAM R = 4 96
24
Mbps
OFDM 16 QAM R = 4 144
36
Mbps
OFDM 64 QAM R = 2/3 6 216
48
Mbps
OFDM 64 QAM R = 6 288
54
Mbps
Table 4 802.11g PHY Layer parameters
Another technological feature implemented in both the 802.11 a and g versions
of 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 QPSK R = 2 48
12
Mbps
OFDM QPSK R = 2 72
18
Mbps
OFDM 16 QAM R = 4 96
24
Mbps
OFDM 16 QAM R = 4 144 36
Mbps
OFDM 64 QAM R = 2/3 6 216
48
Mbps
OFDM 64 QAM R = 6 288
54
Mbps
Table 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 with
Collision 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, an
immediate 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 message
which is received from all the other stations, and then they will defer their
upcoming transmissions, so the station that send the CTS message
immediately 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 thats 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 with
multiple 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 radio
parameter 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 is
created. 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 Conversational
RAB Asymmetry Indicator Symmetric, bidirectional Symmetric RABs are used for uplink and
downlink
Maximum bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75
kbit/s
This value depends on the highest mode
rate in the RFCS
Guaranteed bit rate 12.2 / 10.2 / 7.95 / 7.4 / 6.7 / 5.9 / 5.15 / 4.75
kbit/s
One of the values is chosen, depending
on the lowest rate controllable SDU
format (note 2)
Delivery Order Yes (note 1)
Maximum SDU size 244 / 204 / 159 / 148 / 134 / 118 / 103 / 95
bits
Maximum size of payload field in Iu UP,
according to the highest mode rate in the
RFCS
Traffic Handling Priority Not applicable Parameter not applicable for the
conversational traffic class. (note 1)
Source statistics descriptor Speech (note 1)
SDU Parameters RAB sub-flow 1
(Class A bits)
RAB sub-flow
2 (Class B
bits)
RAB sub-
flow 3
(Class C
bits)
The number of SDU, their number of RAB
sub-flow and their relative sub-flow size is
subject 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 without
any 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 comfort
noise 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 UMTS
First of all we are going to make a briefly overview on the UMTS channel
structure.Logical Channels are the Dedicated Traffic Channel (DTCH) and the
Dedicated 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 used
to 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 T
slot
= 2560 chips, corresponding to one power-control period. The
DPDCH and DPCCH are always frame aligned with each other.

Pilot
N
pilot
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
f
= 10 ms
DPDCH
DPCCH
FBI
N
FBI
bits
TFCI
N
TFCI
bits
T
slot
= 2560 chips, N
data
= 10*2
k
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 DPCCH
fields (N
pilot
, N
TFCI
, N
FBI
, 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
Slot
Format #i
Channel Bit
Rate (kbps)
Channel
Symbol Rate
(ksps)
SF Bits/
Fram
e
Bits/
Slot
N
data
0 15 15 256 150 10 10
1 30 30 128 300 20 20
2 60 60 64 600 40 40
3 120 120 32 1200 80 80
4 240 240 16 2400 160 160
5 480 480 8 4800 320 320
6 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
Slot
Form
at #i
Chann
el Bit
Rate
(kbps)
Channel
Symbol
Rate
(ksps)
SF Bits/
Fra
me
Bit
s/
Slo
t
N
pil
ot
N
T
PC
N
TF
CI
N
F
BI
Transmit
ted slots
per
radio
frame
0 15 15 25
6
150 10 6 2 2 0 15
0A 15 15 25
6
150 10 5 2 3 0 10-14
0B 15 15 25
6
150 10 4 2 4 0 8-9
1 15 15 25
6
150 10 8 2 0 0 8-15
2 15 15 25
6
150 10 5 2 2 1 15
2A 15 15 25
6
150 10 4 2 3 1 10-14
2B 15 15 25
6
150 10 3 2 4 1 8-9
3 15 15 25
6
150 10 7 2 0 1 8-15
4 15 15 25
6
150 10 6 4 0 0 8-15
A Transport Block (TB) [25.302] basic unit of data exchanged between MAC and
PHY and every transport block belongs to one and only one transport channel.
In RRC signalling, a transport block corresponds to RLC PDU (Protocol Data
Unit). Several transport blocks can be transferred at the same time on the
same transport channel between MAC and PHY. The set of all transport blocks
exchanged at the same time on one transport channel is called a transport
block set (TBS).
The Transport Format (TF) is the basic format offered by Layer 1 to the MAC for
the 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. This
parameter controls how much data is transferred on the transport channel in
that particular transmission time interval and how the data is coded etc. by the
physical layer. Transport blocks and transport block sets can have several
characteristics, 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 block
size, but the size can vary between different transport block sets. The transport
block set size indicates the total number of bits in that particular transport
block set. The TTI value defines the time interval between two
subsequent transport block set transfers between MAC and PHY. This
parameter controls how much data is transferred on the transport channel in
that particular transmission time interval and how the data is coded etc. by the
physical layer.
Layer 1 can multiplex several transport channels together for transmitting
these channels simultaneously. For each transport channel, there is a list of
possible Transport Formats defined in the Transport Format Set (TFS). The TFS
is a set of TFs associated to a Traffic Channel, where the semistatic part of all
the TFs in the TFS is the same.
Transport Format Combination (TFC) is an authorised combination of the
combination of currently valid transport formats that can be submitted
simultaneously to Layer 1 for transmission on a Coded Composite Transport
Channel (CCTrCH) of a UE a Transport Format Combination Set (TFCS) is
defined as a set of TFCs on a CCTrCH. The assignment of a suitable TFCS is
done in Layer 3 in the RNC or correspondingly in the UE. When scheduling
and mapping the data transmission onto the physical layer, the MAC layer
chooses between the different TFCs given in the TFCS and thereby has control
over 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 for
the dynamic part of the transport format. For example, a variable rate DCH has
a transport format set (one transport format for each rate), whereas a fixed
rate DCH has only a single transport format. The semi-static part of all
transport 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 different
bit rates and TTI values, given the different channel coding types and CRC
sizes, we would be much more likely to detect any transport blocks containing
errors on TrCH2 than on TrCH1. Thus by defining the transport formats we also
affect the Quality of Service (QoS) provided to the connection. Also the choice
of the rate matching attribute gives a means of controlling the different
protection given to different transport channels.
Dr. A. Chockalingam Dept of ECE, IISc, Bangalore 26
Transport Formats / Configurations
TTI TTI TTI TTI TTI TTI
TTI TTI TTI TTI TTI TTI
TB TB
DCH1 DCH1
DCH2 DCH2
TB TB TB TB
TB TB TB TB TB TB
TB TB
Transport Block Set Transport Block Set
(TBS) (TBS)
TB TB
TB TB
Transport Format (TF) Transport Format (TF)
Transport Format Transport Format
Set (TFS) Set (TFS)
Combination (TFC) Combination (TFC)
Combination Set Combination 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 doesnt 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 Level
Information 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. CodingR=1/3
Radio frame FN=4N+1 Radio frame FN=4N+2 Radioframe FN=4N+3 Radio frame FN=4N
Informationdata
CRC attachment
Tail bitattachment
Rate matching
2nd interleaving
600
490 110 490 110 490 110 490
SMU#1 490 SMU#2 490 SMU#1
110
SMU#2
110
SMU#3
110
SMU#4
110
600 600 600
402
804
260
Tail8
CRC16
244
244
110
360
360
112
Tail8
100
CRC12
1st interleaving
Radio Frame Segmentation
CRC attachment
Informationdata
Tail bit attachment
Conv. CodingR=1/3
Rate matching
1stinterleaving
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, T
f
= 10 ms
TPC
N
TPC
bits
Slot #0 Slot #1 Slot #i Slot #14
T
slot
= 2560 chips, 10*2
k
bits (k=0..7)
Data2
N
data2
bits
DPDCH
TFCI
N
TFCI
bits
Pilot
N
pilot
bits
Data1
N
data1
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 T
slot
= 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
Slot
Format
#i
Channel
Bit Rate
(kbps)
Channel
Symbol
Rate
(ksps)
SF Bits/
Slot
DPDCH
Bits/Slot
DPCCH
Bits/Slot
Transmitted
slots per
radio frame
NTr
NData1 NData2 NTPC NTFCI NPilot
0 15 7.5 512 10 0 4 2 0 4 15
0A 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 which
different 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 /2
k
, k = 0, , 6.
The formula for estimating the number of transmitted bits in a radio frame is
the next:
Chip
s
Symbol
s
Bits
Frame
384
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 kbps
256 15 Ks/s 30 kbps
128 30 Ks/s 60 kbps
64 60 Ks/s 120 kbps
32 120 Ks/s 240 kbps
16 240 Ks/s 480 kbps
8 480 Ks/s 960 kbps
4 960 Ks/s 1920 kbps
4 with 3 parallel
codes
2880 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 doesnt 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 3
TrCH#a 0, 39 or 81bits
TrCH#b 103 bits
Transport block size
TrCH#c 60 bits
#1 NTrCHa=1*81, NTrCHb=1*103, NTrCHc=1*60 bits
TFCS
CRC 12 bits (attached only to TrCh#a)
CRC parity bit attachment for 0 bit transport block Applied only to TrCH#a
Coding CC,
coding rate = 1/3 for TrCh#a, b
coding rate = 1/2 for TrCh#c
TTI 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 12
Position 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 1x60
TF2, bits 1x42 1x63 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 in
3GPP 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 transport
channel can vary between different transmission time intervals. The rate
matching adapts this resulting symbol rate to the limited set of possible symbol
rates of a physical channel. Rate matching means that bits on a transport
channel are repeated or punctured according to the defined rate matching
attribute, which is semistatic and can only be changed through higher layer
signaling.
Viterbi decodingR=1/3
Radio frame FN=4N+1 Radio frame FN=4N+2 Radio frame FN=4N+3 Radio frame FN=4N
Information data
CRC detection
Tail bit discard
2nd interleaving
420
343 77 343 77 343 77 343
#1 343 #2 343 #177 #2 77 #3 77 #477
420 420 420
686
804
260
Tail8
CRC16
244
244
77
308
360
112
Tail8
100
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 Frame
Segmentation
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 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 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 the
maximum number of bits i
HSDPA / HSPA + PHYSICAL TECHNICAL DESCRIPTION
High 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
k
bits (k=4)
Data
N
data 1
bits
1 subframe: T
f
= 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 = M1016; 2
k
(k = 4)
Number of bits in each slot with QPSK = 320 bits.
Number of bits in each slot with 16QAM = 640 bits.
Bits/ HS-DSCH
subframe
Modulation QAM Symbols /
subframe
SF Chips by
subframe
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 and
code.
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 only
a 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 SMLs 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 is
equal 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. For
example, an inter-TTI interval of 1 indicates that data will be transmitted to the
UE in every TTI (if there are enough active HARQ processes to provide data in
every TTI). How often data is actually transmitted to the UE depends also upon
the 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 can
see the 3GPP TS 25.306 Table 5.1a recommended parameters for each device
type, where it can be found the minimum TTI interval for each device type. The
relation 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 TTI
Interval
Number of HARQ
Processes
1 1 - 6
2 1 3
3 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
its Incremental Redundancy memory, etc. A network must ensure that it
respects a UE's capabilities when transmitting to it.
HS-DSCH
category
Maximum
number of
HS-DSCH
codes
received
Minimum
inter-TTI
interval
Maximum
number of bits
of an HS-DSCH
transport block
received within
an HS-DSCH
TTI
NOTE 1
Total number
of soft
channel bits
(User defined
IR Buffer Size)
Supported
modula-tions
without MIMO
operation
or dual cell
operation
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 172800
Category 10 15 1 27952 172800
Category 11 5 2 3630 14400
QPSK
Category 12 5 1 3630 28800
Category 13 15 1 35280 259200 QPSK, 16QAM,
64QAM Category 14 15 1 42192 259200
Category 15 15 1 23370 345600
QPSK, 16QAM
Category 16 15 1 27952 345600
Category 17
NOTE 2
15 1
35280 259200
QPSK, 16QAM,
64QAM
23370 345600
Category 18
NOTE 3
15 1
42192 259200
QPSK, 16QAM,
64QAM
27952 345600
Category 19 15 1 35280 518400 QPSK, 16QAM,
64QAM Category 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
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 1
st
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 TTIs 3
Number of HARQ Processes Proces
ses
2
Information Bit Payload (
INF
N )
Bits
3202
Number Code Blocks Blocks 1
Binary Channel Bits Per TTI Bits 4800
Total Available SMLs in UE SMLs 19200
Number of SMLs per HARQ Proc. SMLs 9600
Coding Rate 0.67
Number of Physical Channel Codes Codes 5
Modulation QPSK
Note: The HS-DSCH shall be transmitted continuously with
constant power but only every third TTI shall be
allocated to the UE under test. The values in the table
defines H-Set 1. H-Set 1A for DC-HSDPA is formed
by applying H-Set 1 to each of the carriers available
in DC-HSDPA mode.
1st Rate Matching --- (User Defined UE IR Buffer Allocation Value)
Redundancy Version Selection (Total Number Bits /
Code 1
Code 2
Phy Ch Segmentation (960,
This is an User Type Device Category 1 (19200 bits of Total Available SMLs in
UE, as it can be seen on table ()). The Number of SMLs 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 Bits 12 9678
3226
CRC 24 3202
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 = k
i
+ k
0,j
The Formula corresponding to table 9.2.3.2 where it can be found k
0,j
values is
the next:
Formula corresponding to table 9.2.3.2:
If kt < 40
8 * ) 14 ( ) (
t t
k k L +
else
]
27
27
5274
8 * ) (
min
1 296
1
min
,
_
L
p
p L k L
t
k
t
end
Table 9.2.3.2: Values of k0,i for different numbers of channelization codes and modulation
schemes, octet aligned (QPSK, 16QAM and 64QAM)
Combination i Modulation
scheme
Number of
channelization codes
i
k
, 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 204
39 10 209
40 11 215
41 12 220
42 13 224
43 14 228
44 15 233
The following table provides the mapping between kt (as per the definition in
subclause 9.2.3.1) and the HS-DSCH Transport Block Size (L(kt)) corresponding
to table 9.2.3.2:
Index
TB
Size Index
TB
Size Index
TB
Size Index
TB
Size
1 120 86 1000 171 4592 256 21000
2 128 87 1016 172 4672 257 21384
3 136 88 1040 173 4760 258 21768
4 144 89 1056 174 4848 259 22160
5 152 90 1072 175 4936 260 22560
6 160 91 1096 176 5024 261 22968
7 168 92 1112 177 5112 262 23384
8 176 93 1136 178 5208 263 23808
9 184 94 1152 179 5296 264 24232
10 192 95 1176 180 5392 265 24672
11 200 96 1200 181 5488 266 25120
12 208 97 1216 182 5592 267 25568
13 216 98 1240 183 5688 268 26032
14 224 99 1264 184 5792 269 26504
15 232 100 1288 185 5896 270 26976
16 240 101 1312 186 6008 271 27464
17 248 102 1336 187 6112 272 27960
18 256 103 1360 188 6224 273 28464
19 264 104 1384 189 6336 274 28976
20 272 105 1408 190 6448 275 29504
21 280 106 1432 191 6568 276 30032
22 288 107 1456 192 6688 277 30576
23 296 108 1488 193 6808 278 31128
24 304 109 1512 194 6928 279 31688
25 312 110 1536 195 7056 280 32264
26 320 111 1568 196 7184 281 32848
27 328 112 1600 197 7312 282 33440
28 336 113 1624 198 7440 283 34040
29 344 114 1656 199 7576 284 34656
30 352 115 1688 200 7712 285 35280
31 360 116 1712 201 7856 286 35920
32 368 117 1744 202 7992 287 36568
33 376 118 1776 203 8136 288 37224
34 384 119 1808 204 8288 289 37896
35 392 120 1840 205 8440 290 38576
36 400 121 1872 206 8592 291 39272
37 408 122 1912 207 8744 292 39984
38 416 123 1944 208 8904 293 40704
39 424 124 1976 209 9064 294 41440
40 440 125 2016 210 9224 295 42192
41 448 126 2048 211 9392
42 456 127 2088 212 9560
43 464 128 2128 213 9736
44 472 129 2168 214 9912
45 480 130 2200 215 10088
46 488 131 2240 216 10272
47 496 132 2288 217 10456
48 504 133 2328 218 10648
49 512 134 2368 219 10840
50 528 135 2408 220 11032
51 536 136 2456 221 11232
52 544 137 2496 222 11432
53 552 138 2544 223 11640
54 560 139 2592 224 11848
55 576 140 2632 225 12064
56 584 141 2680 226 12280
57 592 142 2736 227 12504
58 608 143 2784 228 12728
59 616 144 2832 229 12960
60 624 145 2880 230 13192
61 640 146 2936 231 13432
62 648 147 2984 232 13672
63 664 148 3040 233 13920
64 672 149 3096 234 14168
65 688 150 3152 235 14424
66 696 151 3208 236 14688
67 712 152 3264 237 14952
68 728 153 3328 238 15224
69 736 154 3384 239 15496
70 752 155 3448 240 15776
71 768 156 3512 241 16064
72 776 157 3576 242 16352
73 792 158 3640 243 16648
74 808 159 3704 244 16944
75 824 160 3768 245 17256
76 840 161 3840 246 17568
77 848 162 3912 247 17880
78 864 163 3976 248 18200
79 880 164 4048 249 18536
80 896 165 4120 250 18864
81 912 166 4200 251 19208
82 928 167 4272 252 19552
83 952 168 4352 253 19904
84 968 169 4432 254 20264
85 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 and
12
E
13 C
14 D
15 C
16 D
17 C
18 D
19 C
20 D
Table A
CQI value
Transport
Block Size
Number of
HS-PDSCH
Modulation
Reference 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-QAM
0
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
CQI value
Transport
Block Size
Number of
HS-PDSCH
Modulation
Reference power
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-QAM
0
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
Transport
Block Size
Number of
HS-PDSCH
Modulation
Reference power
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-QAM
0
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
Transport
Block Size
Number of
HS-PDSCH
Modulation
Reference power
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-QAM
0
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
CQI value
Transport
Block Size
Number of
HS-PDSCH
Modulation
Reference power
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 starts
at the start of each radio frame and the 5
th
subframe ends at the end of each
radio frame.

Data, N
data
bits
Slot #1 Slot #14 Slot #2 Slot #i Slot #0
T
slot
= 2560 chips, N
data
= M*10*2
k
bits (k=07)
Tslot = 2560 chips
1 subframe = 2 ms
1 radio frame, T
f
= 10 ms
E-DPDCH E-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/Symbol
M
SF Bits/
Frame
Bits/
Subframe
Bits/Slot
Ndata
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-DCH
category
Maximum
number of E-
DCH codes
transmittedpe
r transport
block
Minimum
spreading
factor
Support for
10 and 2 ms
TTI EDCH
Maximum number of
bits of an E-DCH
transport block
transmitted within a
10 ms E-DCH TTI
Maximum number of
bits of an E-DCH
transport block
transmitted within a 2
ms E-DCH TTI
Category 1 1 SF4 10 ms TTI
only
7110 -
Category 2 2 SF4 10 ms and
2 ms TTI
14484 2798
only
14484 -
2 ms TTI
20000 5772
only
20000 -
2 ms TTI
20000 11484
Category 7 4 SF2 10ms and 2
ms 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 2
Number of HARQ Processes Processes 8
Information Bit Payload
(N
INF
)
Bits 120
Binary Channel Bits per TTI
(N
BIN
)
(3840 / SF x TTI sum for all
channels)
Bits 480
Coding Rate (N
INF
/ N
BIN
) 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 N
INF
= 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 the
subframe 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 most
suited 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/A
1 120 31 355 61 1053 91 3119 121 9241
2 124 32 368 62 1091 92 3234 122 9582
3 129 33 382 63 1132 93 3353 123 9935
4 133 34 396 64 1173 94 3477 124 10302
5 138 35 410 65 1217 95 3605 125 10681
6 143 36 426 66 1262 96 3738 126 11075
7 149 37 441 67 1308 97 3876 127 11484
8 154 38 458 68 1356 98 4019
9 160 39 474 69 1406 99 4167
10 166 40 492 70 1458 100 4321
11 172 41 510 71 1512 101 4480
12 178 42 529 72 1568 102 4645
13 185 43 548 73 1626 103 4816
14 192 44 569 74 1685 104 4994
15 199 45 590 75 1748 105 5178
16 206 46 611 76 1812 106 5369
17 214 47 634 77 1879 107 5567
18 222 48 657 78 1948 108 5772
19 230 49 682 79 2020 109 5985
20 238 50 707 80 2094 110 6206
21 247 51 733 81 2172 111 6435
22 256 52 760 82 2252 112 6672
23 266 53 788 83 2335 113 6918
24 275 54 817 84 2421 114 7173
25 286 55 847 85 2510 115 7437
26 296 56 878 86 2603 116 7711
27 307 57 911 87 2699 117 7996
28 318 58 944 88 2798 118 8290
29 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 7252
1 186 44 2742 87 7288
2 204 45 3042 88 7428
3 354 46 3060 89 7464
4 372 47 3078 90 7764
5 522 48 3298 91 7800
6 540 49 3316 92 7908
7 674 50 3334 93 7944
8 690 51 3378 94 8100
9 708 52 3396 95 8136
10 726 53 3414 96 8436
11 858 54 3732 97 8472
12 876 55 3750 98 8564
13 1026 56 3972 99 8600
14 1044 57 3990 100 8772
15 1062 58 4068 101 8808
16 1194 59 4086 102 9108
17 1212 60 4404 103 9144
18 1330 61 4422 104 9220
19 1348 62 4628 105 9256
20 1362 63 4646 106 9444
21 1380 64 4740 107 9480
22 1398 65 4758 108 9780
23 1530 66 5076 109 9816
24 1548 67 5094 110 9876
25 1698 68 5284 111 9912
26 1716 69 5302 112 10116
27 1734 70 5412 113 10152
28 1866 71 5430 114 10452
29 1884 72 5748 115 N/A
30 1986 73 5766 116 10532
31 2004 74 5940 117 10568
32 2022 75 5958 118 10788
33 2034 76 6084 119 10824
34 2052 77 6102 120 11124
35 2070 78 6420 121 11178
36 2370 79 6438 122 11188
37 2388 80 6596 123 11242
38 2406 81 6614 124 11460
39 2642 82 6756 125 11478
40 2660 83 6774
41 2678 84 7092
42 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 17173
1 120 31 419 61 1465 91 5122 121 N/A
2 125 32 437 62 1528 92 5341 122 18667
3 130 33 455 63 1593 93 5568 123 19462
4 135 34 475 64 1661 94 5805 124 20291
5 141 35 495 65 1731 95 6053 125 21155
6 147 36 516 66 1805 96 6310 126 22056
7 154 37 538 67 1882 97 6579 127 22995
8 160 38 561 68 1962 98 6859
9 167 39 585 69 2046 99 7152
10 174 40 610 70 2133 100 7456
11 182 41 636 71 2224 101 7774
12 189 42 663 72 2319 102 8105
13 197 43 691 73 2417 103 8450
14 206 44 721 74 2520 104 8810
15 215 45 752 75 2628 105 9185
16 224 46 784 76 2740 106 9577
17 233 47 817 77 2856 107 9985
18 243 48 852 78 2978 108 10410
19 254 49 888 79 3105 109 10853
20 265 50 926 80 3237 110 11316
21 276 51 965 81 3375 111 11798
22 288 52 1007 82 3519 112 12300
23 300 53 1049 83 3669 113 12824
24 313 54 1094 84 3825 114 13370
25 326 55 1141 85 3988 115 13940
26 340 56 1189 86 4158 116 14534
27 354 57 1240 87 4335 117 15153
28 370 58 1293 88 4520 118 15798
29 385 59 1348 89 4712 119 16471
B.2b 2ms TTI E-DCH Transport Block Size Table 3
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 1902 60 6614 90 14184 120 21966
1 186 31 1986 61 6774 91 14538 121 22302
2 204 32 2004 62 7110 92 14874 122 22430
3 354 33 2034 63 7270 93 15210 123 22638
4 372 34 2052 64 7446 94 15546 124 22996
5 522 35 2370 65 7782 95 15882
6 540 36 2388 66 7926 96 16218
7 558 37 2642 67 8118 97 16554
8 674 38 2660 68 8454 98 16890
9 692 39 2706 69 8582 99 17226
10 708 40 2724 70 8790 100 17562
11 858 41 3042 71 9126 101 N/A
12 876 42 3060 72 9238 102 N/A
13 894 43 3298 73 9462 103 18252
14 1026 44 3316 74 9798 104 18476
15 1044 45 3378 75 9894 105 18588
16 1194 46 3396 76 10134 106 18924
17 1212 47 3750 77 10470 107 19132
18 1230 48 3990 78 10550 108 19260
19 1330 49 4086 79 10806 109 19596
20 1348 50 4422 80 11160 110 19788
21 1362 51 4646 81 11224 111 19932
22 1380 52 4758 82 11496 112 20268
23 1530 53 5094 83 11880 113 20444
24 1548 54 5302 84 12168 114 20604
25 1566 55 5430 85 12536 115 20940
26 1698 56 5766 86 12840 116 21100
27 1716 57 5958 87 13192 117 21276
28 1866 58 6102 88 13512 118 21612
29 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 15051
1 120 31 405 61 1371 91 4636 121 15675
2 124 32 422 62 1428 92 4828 122 16325
3 130 33 440 63 1487 93 5029 123 17001
4 135 34 458 64 1549 94 5237 124 17706
5 141 35 477 65 1613 95 5454 125 18440
6 147 36 497 66 1680 96 5680 126 19204
7 153 37 517 67 1749 97 5915 127 20000
8 159 38 539 68 1822 98 6161
9 166 39 561 69 1897 99 6416
10 172 40 584 70 1976 100 6682
11 180 41 608 71 2058 101 6959
12 187 42 634 72 2143 102 7247
13 195 43 660 73 2232 103 7547
14 203 44 687 74 2325 104 7860
15 211 45 716 75 2421 105 8186
16 220 46 745 76 2521 106 8525
17 229 47 776 77 2626 107 8878
18 239 48 809 78 2735 108 9246
19 249 49 842 79 2848 109 9629
20 259 50 877 80 2966 110 10028
21 270 51 913 81 3089 111 10444
22 281 52 951 82 3217 112 10877
23 293 53 991 83 3350 113 11328
24 305 54 1032 84 3489 114 11797
25 317 55 1074 85 3634 115 12286
26 331 56 1119 86 3784 116 12795
27 344 57 1165 87 3941 117 13325
28 359 58 1214 88 4105 118 13877
29 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 11850
1 186 42 5094 83 12132
2 204 43 5412 84 12186
3 354 44 5430 85 12468
4 372 45 5748 86 12522
5 522 46 5766 87 12804
6 540 47 6084 88 12858
7 690 48 6102 89 13140
8 708 49 6420 90 13194
9 858 50 6438 91 13476
10 876 51 6756 92 13530
11 1026 52 6774 93 13812
12 1044 53 7092 94 13866
13 1194 54 7110 95 14148
14 1212 55 7428 96 14202
15 1362 56 7464 97 14484
16 1380 57 7764 98 14556
17 1530 58 7800 99 14820
18 1548 59 8100 100 14892
19 1698 60 8136 101 15156
20 1716 61 8436 102 15228
21 1866 62 8472 103 15492
22 1884 63 8772 104 15564
23 2034 64 8808 105 15828
24 2052 65 9108 106 15900
25 2370 66 9144 107 16164
26 2388 67 9444 108 16236
27 2706 68 9480 109 16500
28 2724 69 9780 110 16572
29 3042 70 9816 111 17172
30 3060 71 10116 112 17244
31 3378 72 10152 113 17844
32 3396 73 10452 114 17916
33 3732 74 10488 115 18516
34 3750 75 10788 116 18606
35 4068 76 10824 117 19188
36 4086 77 11124 118 19278
37 4404 78 11178 119 19860
38 4422 79 11460 120 19950
39 4740 80 11514
40 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 mapped
into 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
ms 10 307200
s f
T T
long and consists of 20 slots of length
ms 5 . 0 T 15360
s slot
T
, numbered from 0 to 19. A subframe is defined as two
consecutive slots where subframe i consists of slots i 2 and 1 2 + 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 (BW
Channel
) and
the Transmission bandwidth configuration (N
RB
).
Table 5.6-1 Transmission bandwidth configuration NRB in E-UTRA channel bandwidths
Channel bandwidth
BWChannel [MHz]
1.4 3 5 10 15 20
Transmission bandwidth
configuration NRB
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
RB
sc
UL
RB
N N
subcarriers and
UL
symb
N
SC-FDMA symbols. The resource grid is illustrated in
Figure 5.2.1-1. The quantity
UL
RB
N depends on the uplink transmission
bandwidth configured in the cell and shall fulfil
UL max,
RB
UL
RB
UL min,
RB
N N N
where 6
UL min,
RB
N and 110
UL max,
RB
N are the smallest and largest uplink
bandwidths, respectively, supported by the current version of this specification.
The set of allowed values for
UL
RB
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.
UL
symb
N SC-FDMA symbols
One uplink slot
slot
T
0 l 1
UL
symb
N l
s
u
b
c
a
r
r
i
e
r
s
s
u
b
c
a
r
r
i
e
r
s
RB
sc
UL
symb
N N
Resource block
resource elements
Resource element ) , ( l k
0 k
1
RB
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 ,..., 0
RB
sc
UL
RB
N N k and
1 ,..., 0
UL
symb
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 as
UL
symb
N
consecutive SC-FDMA symbols in
the time domain and
RB
sc
N consecutive subcarriers in the frequency domain,
where
UL
symb
N
and
RB
sc
N are given by Table 5.2.3-1. A physical resource block
in the uplink thus consists of
RB
sc
UL
symb
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
RB
sc
N
UL
symb
N
Normal cyclic prefix 12 7
Extended cyclic prefix 12 6
The relation between the physical resource block number
PRB
n
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
sc
DL
RB
N N
subcarriers and
DL
symb
N OFDM symbols. The resource grid structure is illustrated
in Figure 6.2.2-1. The quantity
DL
RB
N depends on the downlink transmission
bandwidth configured in the cell and shall fulfil
DL max,
RB
DL
RB
DL min,
RB
N N N
where 6
DL min,
RB
N and 110
DL max,
RB
N are the smallest and largest downlink
bandwidths, respectively, supported by the current version of this specification.
The set of allowed values for
DL
RB
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 port
4 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
RB
sc
DL
RB
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
) (
,
p
l k
a
. When there is no risk for confusion, or no particular
antenna port is specified, the index
p
may be dropped.
DL
symb
N OFDM symbols
One downlink slot
slot
T
0 l 1
DL
symb
N l
s
u
b
c
a
r
r
i
e
r
s
s
u
b
c
a
r
r
i
e
r
s
RB
sc
DL
symb
N N
Resource block
resource elements
Resource element ) , ( l k
0 k
1
RB
sc
DL
RB
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 as
DL
symb
N
consecutive OFDM symbols in the
time domain and
RB
sc
N consecutive subcarriers in the frequency domain, where
DL
symb
N
and
RB
sc
N are given by Table 6.2.3-1. A physical resource block thus
consists of
RB
sc
DL
symb
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 1
DL
RB
N in the frequency
domain. The relation between the physical resource block number
PRB
n
in the
frequency domain and resource elements
) , ( l k
in a slot is given by
1
1
]
1
RB
sc
PRB
N
k
n
Table 6.2.3-1: Physical resource blocks parameters.
Configuration
RB
sc
N
DL
symb
N
Normal cyclic
prefix
kHz 15 f
12
7
Extended cyclic
prefix
kHz 15 f
6
kHz 5 . 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,
VRB
n .
Virtual resource blocks of localized type
Virtual resource blocks of localized type are mapped directly to physical
resource blocks such that virtual resource block
VRB
n
corresponds to physical
resource block
VRB PRB
n n
. Virtual resource blocks are numbered from 0 to
1
DL
VRB
N , where
DL
RB
DL
VRB
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 (
DL
RB
N )
Gap ( gap
N
)
1
st
Gap (
gap,1
N
)
2
nd
Gap (
gap,2
N
)
6-10
1
2 /
DL
RB
N
N/A
11 4 N/A
12-19 8 N/A
20-26 12 N/A
27-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 transmission
Data is allocated to the UEs in terms of resource blocks, i.e. one UE can be
allocated integer multiples of one resource block in the frequency domain.
These resource blocks do not have to be adjacent to each other. In the time
domain, the scheduling decision can be modified every transmission time
interval of 1 ms. The scheduling decision is done in the base station (eNodeB).
The scheduling algorithm has to take into account the radio link quality
situation of different users, the overall interference situation, Quality of Service
requirements, service priorities, etc. Figure 1 shows an example for allocating
downlink user data to different users (UE 1 6). The user data is carried on the
Physical Downlink Shared Channel (PDSCH).
Downlink control channels
The Physical Downlink Control Channel (PDCCH) is mainly used to convey the
scheduling decisions to individual UEs, i.e. scheduling assignments for uplink
and downlink. The PDCCH is located in the first OFDM symbols of a subframe.
An additional Physical Control Format Indicator Channel (PCFICH) carried on
specific resource elements in the first OFDM symbol of the subframe is used to
indicate the number of OFDM symbols for the PDCCH (1, 2, 3, or 4 symbols are
possible depending on BW).
The information carried on PDCCH is referred to as downlink control
information (DCI). Depending on the purpose of the control message,
different formats of DCI are defined.
Carried by Type Purposes
DCI F0 PUSCH PUSCH type 2.
PUCCH formats
types 1a, 1b, 2,
2a, 2b.
Convey uplink
scheduling grants.
Contiguous RB in
UL.
DCI F1 PDCCH 0,1,2 The assignment of a
downlink shared
channel resource
when no spatial
multiplexing is
used.
DCI F2 PDCCH 0,1,2 DCI formats 2 and
2A provide downlink
shared channel
assignments in case
of closed loop or
open loop spatial
multiplexing,
respectivel
DCI F3 PDCCH Power control for
UL.
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 is
provided for one code word only). The information provided contains
everything what is necessary for the UE to be able to identify the resources
where to receive the PDSCH in that subframe and how to decode it. Besides the
resource block assignment, this also includes information on the modulation
and coding scheme and on the hybrid ARQ protocol. DCI formats 2 and 2A
provide downlink shared channel assignments in case of closed loop or open
loop spatial multiplexing, respectively. In these cases, scheduling information is
provided for two code words within one control message. Additionally there is
DCI format 0 to convey uplink scheduling grants, and DCI formats 3 and 3a to
convey transmit power control (TPC) commands for the uplink.
There is different ways to signal the resource allocation within DCI, in order to
trade off between signaling overhead and flexibility. For example, DCI format 1
may use resource allocation types 0 or 1 as described in the following. An
additional resource allocation type 2 method is specified for other DCI formats.
In resource allocation type 0, resource block assignment information
includes a bitmap indicating the resource block groups (RBGs) that are
allocated to the scheduled UE where a RBG is a set of consecutive virtual
resource blocks (VRBs) of localized type. The allocated resource block groups do
not have to be adjacent to each other. Resource block group size (P) is a
function 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
1
P N N
RBG
/
DL
RB
where
]
P N /
DL
RB
of the RBGs are of size P and if 0 mod
DL
RB
> P N then
one of the RBGs is of size
]
P N P N /
DL
RB
DL
RB
. The bitmap is of size
RBG
N bits with
one bitmap bit per RBG such that each RBG is addressable. The RBGs shall be
indexed in the order of increasing frequency and non-increasing RBG sizes
starting at the lowest frequency. The order of RBG to bitmap bit mapping is in
such way that RBG 0 to RBG 1
RBG
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
DL
RB
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 block
assignment on PDCCH is therefore split up into 3 parts: one part indicates the
selected resource block group subset.
The first field with 1
) ( log
2
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 a
single 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
TYPE1
RB
N and is defined as
1 1
1 ) ( log /
2
DL
RB
TYPE1
RB
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 mapped
onto 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
1A
PRB
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
m
Q
= 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 (
m
Q
) 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
m
Q
TBS Index
TBS
I
0 2 0
1 2 1
2 2 2
3 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 14
16 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
reserved 30 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 28 0
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 DCI
formats 2, 2A and 2B as specified below. For a transport block that is not
mapped to two-layer spatial multiplexing, the TBS is determined by the
procedure in Section 7.1.7.2.1. For a transport block that is mapped to
two-layer spatial multiplexing, the TBS is determined by the procedure in
Section 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 a
CQI index if:
- the combination could be signalled for transmission on the PDSCH in the
CQI reference resource according to the relevant Transport Block Size
table, and
- the modulation scheme is indicated by the CQI index, and
- the combination of transport block size and modulation scheme when
applied to the reference resource results in the effective channel code rate
which is the closest possible to the code rate indicated by the CQI index.
If more than one combination of transport block size and modulation
scheme results in a effective channel code rate equally close to the code
rate indicated by the CQI index, only the combination with the smallest
of 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.6016
5 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
VRB
n
. 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 (
UL
RB CRBs
N L
then
START CRBs
UL
RB
) 1 ( RB L N RIV +
else
) 1 ( ) 1 (
START
UL
RB CRBs
UL
RB
UL
RB
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 the
procedure defined in Section 8.1, and
compute the number of coded symbols for control information.
For 28 0
MCS
I , the modulation order (
m
Q
) is determined as follows:
If the UE is capable of supporting 64QAM in PUSCH and has not been
configured by higher layers to transmit only QPSK and 16QAM, the
modulation order is given by
'
m
Q 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,
'
m
Q is first
read from Table 8.6.1-1. The modulation order is set to ) , 4 min(
'
m m
Q Q .
If the parameter ttiBundling provided by higher layers is set to TRUE, then
the resource allocation size is restricted to 3
PRB
N and the modulation
order is set to
2
m
Q
.
For 31 29
MCS
I , if 29
MCS
I , the CQI request bit in DCI format 0 is set to 1 and
4
PRB
N , the modulation order is set to
2
m
Q
. 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 28 0
MCS
I . If there is no PDCCH
with DCI format 0 for the same transport block using 28 0
MCS
I , the
modulation order shall be determined from
the most recent semi-persistent scheduling assignment PDCCH, when the
initial PUSCH for the same transport block is semi-persistently scheduled,
or,
the random access response grant for the same transport block, when the
PUSCH 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
'
m
Q
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 0
20 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 28 0
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 31 29
MCS
I , if 29
MCS
I , the CQI request bit in DCI format 0 is set to 1 and
4
PRB
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 28 0
MCS
I . If there is no initial
PDCCH with DCI format 0 for the same transport block using 28 0
MCS
I , the
transport block size shall be determined from
the most recent semi-persistent scheduling assignment PDCCH, when the
initial PUSCH for the same transport block is semi-persistently scheduled,
or,
the random access response grant for the same transport block, when the
PUSCH 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 N
RB
1. Calculate the number of channel bits Nch 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 NRB
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 attached
to each Code Block (otherwise L = 0 Bit)
The EnodeB is supposed to have scheduled the considered UE with all the RBs
allowed. The information is codified in the DCI and the parameters are the 1.4
MHz 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 the
next:
6RB 12 = 72 sc
1 symbol/slot is employed for UL demodulation reference signals, which are
used for channel estimation for coherent demodulation, and are transmitted in
the 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 Table
7.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/a
For 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 PDCCH
for 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 the
number of allocated RB (that is, the channel BW), the Modulation scheme and
the Target Coding Rate (via a CQI information from the UE). The number of bits
per subframe is calculated next:
First, take into account the Control Channel information corresponding to both
the primary and secondary syncronization channels (P-SCH, S-SCH). They are
located at the 6 and 5 symbol respectively of the first slot (number 0) of the
frame, 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 72
subcarriers.
The PBCH is the Physical BroadCast Channel and it is located next to the S-SCH
symbol and it occupies symbols 0,1,2,3 of the second slot (number 1) of the
subframe number 0. It also occupies 72 subcarriers.
The reference signal is transmitted on symbol 0 and 4 of each slot and it
occupies one resource element every 6 subcarriers if we are using a single
antenna. Otherwise, the number of subcarriers spacing vary. For example, for
two 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 first
symbols of each subframe (first slot) and it can occupy 0,1,2,3,4 symbols
depending 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 PBCH
symbol 0 of slot 1 or PDCCH symbol 0 of slot 0. Only the r.e. placed at the 4
th
symbol of both slot are not coincident with anyone of this control information
channels. The re placed in the 0 symbol of slot 0 is coincident with PDCCH and
the placed in the 0 symbol of slot 1 partially overlap with the PBCH. So the re
not overlapping are (symb 4) 4 r.e. per 12 sc equals 24 re. The partially
overlapped at symbol 0 of slot 1. In this case, as the DBCH occupy the whole
72 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 bits
PDSCH
2984 8 (subframes) / 10 msg = 2387.2 kbps.
Calculation Proccess.
ANNEX A
Codeword: A codeword represents user data before it is formatted for
transmission. One or two codewords, CW0 and CW1, can be used depending on
the 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 the
case of the less common downlink multi-user MIMO (MU-MIMO), each codeword
is sent to only one UE.
Layer: The term layer is synonymous with stream. For spatial multiplexing, at
least two layers must be used. Up to four are allowed. The number of layers is
denoted by the symbol (pronounced nu). The number of layers is always less
than or equal to the number of antennas.

Raw Data Rate

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Raw Data Rate

Hochgeladen von

Copyright:

Verfügbare Formate

INTRODUCTION

Das könnte Ihnen auch gefallen