1.

LTE Quick Reference

2 . Basic

3.Lte channels

4.Mac layer

LTE Quick Reference Go Back To Index Home : www.sharetechnote.com

EPS Bearer

'Bearer' in the dictionary means "Carrier" or "Porter" which carries something from a point to another point. Under the context o
communication technology, I would define the 'Bearer' as a 'pipe line' connecting two or more points in the communication syste
in which data traffic follow through.

Taking this definition, we can define 'EPS Bearer' as a pipe line through which data traffic flows within EPS (Evolved Packet switch
System).

EPS Bearer can be illustrated as the Red path in the following illustration.
As shown above, EPS bearer has several components in it. It means EPS beare is a complex of multiple element bearers as in the
following diagram.

It would seem to be a simple diagram, but as you see EPS bearer includes all the components from Radio Link to the final packet
core. It means understanding EPS bearer means understanding the whole LTE network.

I would leave it up to you to study the very details of each component.

If you have any experience or knowledge on the other technology like WCDMA, you can think of EPS Bearer as an entity similar to
WCDMA PS Bearer.

If you see the diagram shown above, you would notice that this bearer has two main part. One is 'Radio Bearer' and the other par
Core network bearer.

In UMTS case, the 'Radio Bearer' part is configured by 'Radio Bearer Setup' message and the Core Network Bearer is configured b
Activate PDP Context procedure .

In LTE, the both 'Radio Bearer' part and 'Core Network Bearer' both configured by a single message, 'RRC Connection
Reconfiguration'. Actually within 'RRC Connection Reconfiguration' message there is one part for Radio configuration and another
part for Core Network configuration. See the following two links for the details.

RRC : RRC Connection Reconfiguration + NAS : Attach Accept + NAS : Activate Default EPS Bearer Context Req

RRC : RRC Connection Reconfiguration + NAS : Activate Dedicated EPS Bearer Context Request

There are two types of EPS Bearer. One is 'Default EPS Bearer' and the other one is 'Dedicated EPS Bearer'. Simply put, we can
describe as follows.

i) Default EPS Bearer :

Be established during Attach Process

Allocate IP address to UE

Does not have specifc QoS (only Nominal QoS is applied).

Similar to Primary PDP Context in UMTS

ii) Dedicated EPS Bearer

Normally be established during the call setup after idle mode. (but can be established during the attach as well).

Does not allocate any additional IP address to UE

Is linked to a specified default EPS bearer

Have a specific (usually guaranteed) QoS

Similar to Secondary PDP Context in UMTS

Basic Call Flow in LTE

Posted on May 11, 2014 by admin — No Comments ↓

Home › LTE Basic Call Flow › Basic Call Flow in LTE

Share
What happens while UE first time switch on?
 Fig1.0 Basic Call Flow
Following is a sequence diagram showing not only the message but also basic configurations of each layer. More detailed description
of each layer in the context of full protocol stack will be explained in “Protocol Stack” section.
After Power on UE …
 1) Frequency Search (Scan the entire frequency bands)
2) Cell Search – will search for PSS Normally a UE would find multiple cells in this process
3) (a) MIB decoding (b) SIB decoding
4) Cell Selection/ Cell Reselection
5) Initial RACH Process >
6) RRC : RRC Connection Request
7) RRC : RRC Connection Setup
8) RRC : RRC Connection Setup Complete + NAS : Attach Request
9) RRC : DL Information Transfer + NAS : Authentication Request
10) RRC : UL Information Transfer + NAS : Authentication Response
11) RRC : DL Information Transfer + NAS : Security Mode Command
12) RRC : UL Information Transfer + NAS : Security Mode Complete
13) RRC : Security Mode Command
14) RRC : Security Mode Complete
15) RRC : RRC Connection Reconfiguration + NAS : Attach Accept
16) RRC : RRC Connection Reconfiguration Complete + NAS : Attach Complete
17) RRC : RRC Connection Release < MO or MT call > : In MT call, Paging should be sent.
18) RRC : PRACH Preamble
19) RRC : RACH Response
20) RRC : RRC Connection Request
21) RRC : RRC Connection Setup
22) RRC : RRC Connection Setup Complete + NAS : Service Request
23) RRC : Security Mode Command
24) RRC : Security Mode Complete
25) RRC : RRC Connection Reconfiguration + NAS : Activate Dedicated EPS Bearer Context Request
26) RRC : RRC Connection Reconfiguration Complete + NAS : Activate Dedicated EPS Bearer Context Accept
27) RRC : UL Information Transfer + NAS : Deactivate Dedicated EPS Bearer Context Accept
28) RRC : RRC Connection Release
(1)Frequency Search (Scan the entire frequency bands) When the UE powers on, it checks if it is possible to camp on the last
registered PLMN (Public Land Mobile Network). If no any stored system on the UE, UE will perform the initial cell selection:
 Scan all RF frequencies band (ex 900MHz,1800MHz,1900MHz….) and which band are using by network
 Detect the operating frequency with the strongest RSRP
 Fig 1.1
2) Cell Search – will search for PSS Normally a UE would find multiple cells in this process In LTE, there are two downlink
synchronization signals which are used by the UE to obtain the cell identity and frame timing.
 Primary synchronization signal (PSS)
 Secondary synchronization signal (SSS)

The division into two signals is aimed to reduce the complexity of the cell search process

Primary and Secondary Secondary Sync: Cell synchronization is the very first step when UE wants to camp on any cell. From this,
UE acquires physical cell id (PCI), time slot and frame synchronization, which will enable UE to read system information blocks from
a particular network. First, the UE has to synchronize with the network at the frame and slot level.
i)Detect PSS (Primary Synchronization Signal) for symbol timing
 The Primary Synchronization Signal is responsible for slot synchronization.
 The Synchronization Signal are sent only on time slots (1st and 11th) of each frame.
 PSS is send at the last OFDM symbol of the 1st and 11th slot of each frame.
 ii) Identification of cell ID (0,1,2) : From PSS, UE is also able to obtain physical layer identity (0 to 2).

Query_1: How does UE know to look for the PSS synchronization signal?

Well, UE doesn’t need to worry much for this. As, the synchronization signal are always sent only on the center 62 sub carriers
irrespective of the channel bandwidth (1.25,3,5,10,20). Therefore, UE will look for the central sub carriers, i.e at the last OFDM
symbol of the 1st time slot and again at the last OFDM symbol of the 11th slot. With this UE synchronizes at the slot level.

Detect SSS (Secondary Synchronization Signal) for radio frame timing :

 The Secondary Synchronization Signal is responsible for frame synchronization.
 Using both these signals, the UE derives the Physical Cell ID of the corresponding cell.
Question_2 : How does UE know to look for the SSS synchronization signal?

Once, when the PSS is identified, SSS is always send at the slot before the PSS is present. In other words, SSS
immediately precedes the PSS.

Question_3 : Let’s see how the UE derives the Cell ID using these two signals:

From PSS: PHYSICAL LAYER CELL IDENTITY is derived. It carries the value of 0, 1 and 2.
From SSS: PHYSICAL LAYER CELL IDENTITY GROUP is derived. It can take the value to 0 to 167.

i) Detection of cell ID group (0, ….,167): From SSS, UE is able to obtain physical layer cell identity group number (0 to 167).Using
physical layer identity and cell identity group number, UE knows the PCI for this cell now.

ii) physical layer cell identities (PCI) : In LTE 504 physical layer cell identities (PCI) are allowed and are divided into unique 168
cell layer identity groups where each group consist of three physical layer identity. As mentioned earlier, UE detects physical layer
identity from PSS and physical layer cell identity group from SSS. Assuming physical layer identity = 1 and cell identity group=2 then
the PCI for given cell is

PCI = 3*(Physical layer cell identity group)+ physical layer identity = 3*2+1 = 7

Once UE knows the PCI for a given cell, it also knows the location of cell Reference signals as shown in figure .

Reference signals are used in channel estimation, cell selection / reselection and handover
procedures.

So total number of ID become 168 x 3 = 504

Once the UE synchronizes with the network, it proceeds to read MIB and then requires the following info for camping on a cell:

 PLMN id
 Tracking Area Id
 Cell Id
 Radio and Core n/w capabilities (for it’s n/w selection)
The above information is being broadcast by the network in order to help the UE for it’s selection process.

This broadcast is known as SYSTEM INFORMATION which is MIB and SIB’s.

 The call flow for the UE to read the System information is mentioned below:

3)(a)MIB Decoding

i) DL Bandwidth, Number of Transmit Antenna, Reference Signal Transmit Power

ii) System Frame Number (SFN)
iii) PHICH Configurationiv) Transmit every 40 ms(used for HARQ ACK/NACK)
iv)The MIB uses a fixed schedule with a periodicity of 40 ms and repetitions made within 40 ms.
v)The first transmission ofthe MIB is scheduled in subframe #0 of radio frames for which the SFN mod 4 = 0, and repetitions are
scheduled insubframe #0 of all other radio frames.

MasterInformationBlock ::= SEQUENCE {

dl-Bandwidth ENUMERATED { n6, n15, n25, n50, n75, n100},
phich-Config PHICH-Config,
systemFrameNumber BIT STRING (SIZE (8)),
spare BIT STRING (SIZE (10))
}
Query: How does the UE read MIB?

 The MIB is transmitted on physical channel (BCCH-BCH-PBCH) and it always occupies the central 72 sub carriers in the
Frequency domain irrespective of the channel bandwidth.
 The first transmission of the MIB is scheduled in sub-frame number 0 of radio frames for which the SFN mod 4 = 0
 repetitions are scheduled in sub-frame 0 of all other radio frames
(b)SIB decoding
i) Cell Access Related Information – PLMN Identity List, PLMN Identity, TA Code, Cell identity & Cell Status
ii) Cell Selection Information – Minimum Receiver Level
iii) Scheduling Information – SI message type & Periodicity, SIB mapping Info, SI Window length
Till now, the UE has synchronized itself with the Cell with the help of PSS and SSS; followed by reading the MIB. Now, UE will
proceed to read SIB1 and SIB2 which carriers important information for the UE to select a Cell. To know more about SIB’s and it’s
working, click here
After the above process the UE is synchronized with the network in the Downlink direction and have read SIB1 and SIB 2. Now, it
needs to synchronize in the Uplink direction
For this to happen, RAP (Random Access Procedure) is initiated
(5) Initial RACH Process (Random access procedure)
 In order to be synchronized with the network, RACH procedure is used. Suppose a UE wants to access the
network, so first it will try to attach or syncronise with the network. In LTE a separate channel PRACH (
Physical Random Access Channel) is provided for initial access to the network.
When does UE need to perform Random Access Procedure :- As per specifications, RACH can be performed in
below mentioned scenarios :-
 Initial Access – UE is trying to access the network in RRC idle state.
 During RRC connection re-establishment procedure .
 Handover
 When uplink synchronization is lost :- It means from a certain duration network has not received
anything from UE in uplink.
 When UE does not have any PUCCH resources available for SR(Scheduling Request) .
 When timing advance is needed for positioning purpose in RRC connected state for UE.
To initiate the procedure UE lower layes will send a Random Access Request(RACH Request) after
receiving request from UE RRC.UE receives a lot of information from eNodeB in System Information
(SIB2). It’s important to understand those terminologies first.You can also refer LTE SIB2 parameters
section.
 RACH Configurations
 PRACH Configurations
How UE decides about when and where it needs to send RACH Request:- It is decided on the basis of parameters
received in SIB2 PRACH configurations. UE can use 6 Resource blocks for sending the RACH Request.
From PRACH Config Index – There is a mapping in spec 36211 table 5.7.1-2 from which UE can find the
available subframes where it can send a RACH. For example:- Prach Config index value = 7, From table it is
clear that UE can send a RACH Req in any system frame but subframe should be 2 and 7.
From PRACH Frequency Offset – This value is also received in SIB2 by UE. It governs which frequency
resource UE can use for the RACH Req. Example:- If the value of PRACH Freq Offset is 10. UE can use the 6
PRB’s starting from PRB 10 for RACH Request.
What exactly RACH Request contains:-
1. Preamble Index :- There are total of 64 preambles available which are divided into two groups Group A and
Group B. UE decides the preamble index from a group on the basis of parameters received in SIB2:-
numberofRaPreambles :- eNodeB sends this value in SIB2 which denotes the total number of preambles
available for UE to send a Rach Request.
sizeOfRaPreamblesGroupA :- It represents the number of preambles available within Group A.
So number of preamble in Group B = numberofRaPreambles – sizeOfRaPreamblesGroupA
MessageSizeGroupA :- It is used for selecting a preamble from a group. Its value is in bits.
Now UE needs to decide the group from which it needs the preamble. Group is decided on the basis of size
of MSG3( RRC connection request ).

If Msg3 size > messageSizeGroupA , preamble will be selected from GroupB else preamble will be selected
from Group A.

The actual formula for selecting a preamble is given in spec 36321 sec 5.1.2. That contain factors other
than MSG3 size as well. But mainly this is how UE decides the Group. From the selected group, randomly
UE selects a preamble index.
How UE decides the Power used for Rach request Transmission:- Now UE need to decide the power which will be
used for RACH Request transmission.

Power is decided on the factors received in SIB2 as:-

preambleInitialReceivedtargetPower:- Power factor which will be used for first transmission of Rach Request.Value varies from -
120dBm to -90 dBm .

powerRampingStep:- This is mainly used when eNodeB is not able to detect the Rach Request then UE will re transmit the RACH
Request by increasing the power to powerRampingStep factor.

power used for Rach Request transmission = preambleInitialReceivedTargetPower + DELTA_PREAMBLE +

(PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep

DELTA_PREAMBLE = This is preamble format based delta offset. There are four formats available for preamble which are called
as preamble formats. We will be explaining them in detail later. Most of the time preamble format 0 is used.

For Example:-
In Sib2, preambleInitialReceivedtargetPower = -100
powerRampingStep = 2

First Transmission of Rach Request:-

PREAMBLE_TRANSMISSION_COUNTER = 1
For preamble format 0, DELTA_PREAMBLE = 0
Power used = -100 + 0 + (1- 1) *2 = -100

Suppose eNodeB is not able to receive it

Second transmission of Rach request:-
PREAMBLE_TRANSMISSION_COUNTER = 2 Power used = -100 + 0 + (2-1) * 2 = -98

UE will send the RACH Request containing these values in the specified subframe by using the specified resources.

What is steps followed by UE for sending a Rach request:-

 Fig 1.2 Step followed by UE for sending RACH request
How eNodeB behaves after receiving Random Access Request:-
1. Allocation of temporary RNTI(Radio Network temporary Identifier) :- After receiving RACH Request, enodeB
allocates a temporary identity to the UE which is made permanent after successful RACH procedure. The
permanent identity is called as CRNTI ( Cell RNTI ). This TC-RNTI is transmitted to the UE as part of RACH
Response which will be used for further communication between the UE and the network.
2. Timing Advance :- After receiving RACH Request, eNodeB PHY(Physical layer) calculates the timing advance
which is transmitted to the UE as part of response message.

As part of Rach response, absolute Timing advance value is transmitted.

Timing advance calculation for RACH Response message:-

As per 3GPP spec,

Ts = 1/(15000 * 2048) seconds

NTA = TA * 16 where TA = 11 bit value for random access response varying from 0,1,2 …. 1282
NTA = Amount of time alignment
So transmission of uplink radio frame from the UE shall start = (NTA + NTA offset) * Ts
NTA offset = 0 ( For type 1 frame structure) = ((NTA + 0) * 1)/ (15000 * 2048)
= (TA * 16)/(15000 * 2048 )seconds

Mainly this timing advance fundamental is used for eNodeB PHY to receive the UE message at correct
timing. It is possible that UE is far away from the eNodeB , so for eNodeB to receive the data from UE at
correct timing this timing adjustments are done.
 If timing advance is received in subframe n, UE should do the adjustment from the starting of subframe (n +6). After the
Random access response message, enodeB does not send absolute timing advance value. It will send a
value which UE will use to adjust the already stored timing advance value. We will explain this in Timing
advance section later.
Refer spec 36213 sec 4.2.3 and spec 36211 sec 8.1 for details about timing adjustments
3. Allocate uplink Resources ( UL GRANT ):- eNodeB will provide the required information in Random Access
Response(RAR) message for UE to send the MSG3( RRC Connection Request) .
UL Grant is a 20 bit message with contents from MSB to LSB as:-
 Hopping Flag :- This is 1 bit of information which governs whether frequency hopping is enabled or not. If
the value of the bit is 1 and resource block assignment is type 0 , UE should perform PUSCH frequency
hopping.
What is Frequency Hopping:-
 As we know that RB allocation is contiguous in uplink which means eNodeB allocates continuous RB’s
in frequency domain. As in downlink we have multiple resource allocation policies to achieve frequency
diversity. So in uplink, to achieve frequency diversity Frequency Hopping is used. eNodeB
communicates required parameters to UE’s in SIB2 which are needed for performing frequency
hopping at UE.
For Example:-
Suppose eNodeB has allocated 5 RB’s to a particular UE in uplink as shown below.

Fig 1.3 1subframe time domain

 It is clear that the allocation in uplink in terms of RB is contiguous. But eNodeB has enabled frequency
hopping for this UE.
 We are able to achieve frequency diversity in contiguous allocation as well due to hopping. In the
figure above, same color represents the hopping of UE data in different slots for a particular RB.
 There is a lot more to discuss in frequency hopping. we will be taking it later in that particular section.
 As of now,we can summarize it as :- Frequency hopping is used to provide frequency diversity in
uplink. Its main advantage is, suppose in frequency domain at RB0 channel conditions are bad but at
RB3 conditions are good. So in that case, UE can decode the data of RB0 after combining the same
colored data.
 Resource Block Assignment :- It is 10 bits of information embedded in UL Grant message.
How UE decodes the 10 bit RB Assignment :-
According to spec 36213 sec 6.1.1,UE decodes it as:-

If NULRB <= 44
Truncate the fixed size resource block assignment to its b least significant bits where,
b = ceiling ( log (N 2
UL
RB * (N UL
RB + 1)/2) )

and interpret the truncated resource block assignment according to the rules for a regular DCI format 0
else Insert b most significant bits with value zero where, b = (ceiling ( log (N 2
UL
RB * (N UL
RB + 1)/2) )) – 10
and interpret the expanded resource block assignment according to the rules for a regular DCI format 0

For Example :-

Lets assume the 10 bits of the information as :- 1 1 1 1 1 1 1 1 1 1

Assume Total number of uplink RB’s in system = 100

b = (ceiling ( log (N 2
UL
RB * (N UL
RB + 1)/2) )) – 10
= (ceiling ( log 2(100 *101/2))) – 10

= (ceiling ( 12.3)) – 10
= 13 -10
=3

So, RB assignment will be :- 0 0 0 1 1 1 1 1 1 1

RB assignment ( value in decimal) = 127
Now we need to interpret it according to the rules of DCI format 0.

Number of RB’s allocated = Floor( 127 /100 ) + 1

=1+1
=2

RB start index = 127 mod 100

= 27

 Modulation and Coding scheme to be used by UE:- It is 4 bits of information in UL grant message whose value
varies from 0 to 15. The modulation and coding is determined by UE from MCS indices 0 to 15 in table
8.6.1.1 from spec 36213.
 Power used by UE for PUSCH :- It is indicated in 3 bits as a TPC command whose value varies from 0 to 7.
TPC command to power mapping is mentioned in table below

Fig 1.4
 UL delay :- 1 bit of information which can be set to 0 or 1. It indicates whether the delay of PUSCH is
introduced or not.
 CSI field :- This 1 bit of information determines whether an aperiodic CQI, PMI and RI report can be
included in the PUSCH transmission. For contention based Random access CSI field is reserved.
eNodeB will prepare a response ( Random Access Response) with above discussed fields and send it to UE. But we need to
understand the timing of response message corresponding to Rach Request. Timing w.r.t to Rach Request and Random Access
Response:- RAR Response Window is the value transmitted in SIB2.
To know more about RACH is common in FDD and TDD(Contention/Non-Contention based RAP (Random Access Procedure)

In order that data can be transported across the LTE radio interface, various "channels" are used. These are used to
segregate the different types of data and allow them to be transported across the radio access network in an orderly
fashion.

Effectively the different channels provide interfaces to the higher layers within the LTE protocol structure and enable
an orderly and defined segregation of the data.
3G LTE channel types
There are three categories into which the various data channels may be grouped.

 Physical channels: These are transmission channels that carry user data and control messages.

 Transport channels: The physical layer transport channels offer information transfer to Medium Access
Control (MAC) and higher layers.
 Logical channels: Provide services for the Medium Access Control (MAC) layer within the LTE protocol
structure.

3G LTE physical channels

The LTE physical channels vary between the uplink and the downlink as each has different requirements and
operates in a different manner.
 Downlink:

o Physical Broadcast Channel (PBCH): This physical channel carries system information for UEs
need to access the network. It only carries what is termed Master Information Block, MIB, messages.
The modulation scheme is always QPSK and the information bits are coded and rate matched - the
bits are then scrambled using a scrambling sequence specific to the cell to prevent confusion with
data from other cells.
The MIB message on the PBCH is mapped onto the central 72 subcarriers or six central resource
blocks regardless of the overall system bandwidth. A PBCH message is repeated every 40 ms, i.e.
one TTI of PBCH includes four radio frames.
The PBCH transmissions have 14 information bits, 10 spare bits, and 16 CRC bits.

o Physical Control Format Indicator Channel (PCFICH) : As the name implies the PCFICH
informs the UE about the format of the signal being received. It indicates the number of OFDM
symbols used for the PDCCHs, whether 1, 2, or 3. The information within the PCFICH is essential
because the UE does not have prior information about the size of the control region.
A PCFICH is transmitted on the first symbol of every sub-frame and carries a Control Format
Indicator, CFI, field. The CFI contains a 32 bit code word that represents 1, 2, or 3. CFI 4 is
reserved for possible future use.
The PCFICH uses 32,2 block coding which results in a 1/16 coding rate, and it always uses QPSK
modulation to ensure robust reception.

o Physical Downlink Control Channel (PDCCH) : The main purpose of this physical channel is to
carry mainly scheduling information of different types:

 Downlink resource scheduling

 Uplink power control instructions

 Uplink resource grant

 Indication for paging or system information

The PDCCH contains a message known as the Downlink Control Information, DCI which carries the
control information for a particular UE or group of UEs. The DCI format has several different types which
are defined with different sizes. The different format types include: Type 0, 1, 1A, 1B, 1C, 1D, 2, 2A, 2B,
2C, 3, 3A, and 4.

o Physical Hybrid ARQ Indicator Cannel (PHICH) : As the name implies, this channel is used to
report the Hybrid ARQ status. It carries the HARQ ACK/NACK signal indicating whether a transport
block has been correctly received. The HARQ indicator is 1 bit long - "0" indicates ACK, and "1"
indicates NACK.
The PHICH is transmitted within the control region of the subframe and is typically only transmitted
within the first symbol. If the radio link is poor, then the PHICH is extended to a number symbols for
robustness.

o Uplink:

Physical Uplink Control Channel (PUCCH) : The Physical Uplink Control Channel, PUCCH
provides the various control signalling requirements. There are a number of different PUCCH
formats defined to enable the channel to carry the required information in the most efficient format
for the particular scenario encountered. It includes the ability to carry SRs, Scheduling Requests.
 The basic formats are summarised below:

PUCCH UPLINK CONTROL INFORMATION MODULATION BITS PER SUB- NOTES

FORMAT SCHEME FRAME

Format 1 SR N/A N/A

Format 1a 1 bit HARQ ACK/NACK with or without BPSK 1

SR

Format 1b 2 bit HARQ ACK/NACK with or without QPSK 2

SR

Format 2 CQI/PMI or RI QPSK 20

Format 2a CQI/PMI or RI and 1 bit HARQ ACK/NACK QPSK + BPSK 21

Format 2b CQI/PMI or RI and 2 bit HARQ ACK/NACK QPSK + BPSK 22

Format 3 Provides support for carrier

aggregation.

o Physical Uplink Shared Channel (PUSCH) : This physical channel found on the LTE uplink is the
Uplink counterpart of PDSCH

o Physical Random Access Channel (PRACH) : This uplink physical channel is used for random
access functions. This is the only non-synchronised transmission that the UE can make within LTE.
The downlink and uplink propagation delays are unknown when PRACH is used and therefore it
cannot be synchronised.

The PRACH instance is made up from two sequences: a cyclic prefix and a guard period. The
preamble sequence may be repeated to enable the eNodeB to decode the preamble when link
conditions are poor.

LTE transport channels

The LTE transport channels vary between the uplink and the downlink as each has different requirements and
operates in a different manner. Physical layer transport channels offer information transfer to medium access control
(MAC) and higher layers.
  Downlink:

o Broadcast Channel (BCH) :The LTE transport channel maps to Broadcast Control Channel (BCCH)

o Downlink Shared Channel (DL-SCH) : This transport channel is the main channel for downlink
data transfer. It is used by many logical channels.

o Paging Channel (PCH) : To convey the PCCH

o Multicast Channel (MCH) : This transport channel is used to transmit MCCH information to set up
multicast transmissions.

 Uplink:

o Uplink Shared Channel (UL-SCH) : This transport channel is the main channel for uplink data
transfer. It is used by many logical channels.

o Random Access Channel (RACH) : This is used for random access requirements.

LTE logical channels

The logical channels cover the data carried over the radio interface. The Service Access Point, SAP between MAC
sublayer and the RLC sublayer provides the logical channel.

 Control channels: these LTE control channels carry the control plane information:

o Broadcast Control Channel (BCCH) : This control channel provides system information to all
mobile terminals connected to the eNodeB.

o Paging Control Channel (PCCH) : This control channel is used for paging information when
searching a unit on a network.

o Common Control Channel (CCCH) : This channel is used for random access information, e.g. for
actions including setting up a connection.

o Multicast Control Channel (MCCH) : This control channel is used for Information needed for
multicast reception.

o Dedicated Control Channel (DCCH) : This control channel is used for carrying user-specific
control information, e.g. for controlling actions including power control, handover, etc..

Traffic channels:These LTE traffic channels carry the user-plane data:

o Dedicated Traffic Channel (DTCH) : This traffic channel is used for the transmission of user data.

o Multicast Traffic Channel (MTCH) : This channel is used for the transmission of multicast data.

It will be seen that many of the LTE channels bear similarities to those sued in previous generations of mobile
telecommunications.
This tutorial describes the specific details of the LTE MAC layer or the Medium Access Control
protocol. MAC is a radio network protocol which resides both in the UE and in the E-UTRAN.
Also, it should be noted that MAC protocol is available for both User plane and also for the
control plane.RRC (Radio Resource Control) protocol is in control of the configuration of
MAC that means RRC decides how MAC will behave. For example RRC tells MAC to configure
a specific PDU size.
MAC Architecture

E-UTRA defines two MAC entities; one in the UE and one in the E-UTRAN. Here is how it
looks for user plane and control plane.

The MAC layer is composed of a Hybrid Automatic Repeat request (HARQ) entity, a
multiplexing/de-multiplexing entity, a logical channel prioritization entity, and a control
entity.

Multiplexing and de-multiplexing entity

The multiplexing and de-multiplexing entity is in charge of composing and decomposing the
MAC PDUs and performs (de-) multiplexing of data from several logical channels into/from
one transport channel.

Logical channel prioritization entity

When the radio resources for a new transmission are allocated, the logical channel
prioritization entity instructs the multiplexing and de-multiplexing entity to generate MAC
PDUs from the MAC SDUs.

The logical channel prioritization entity also decides how much data from each configured
logical channel should be included in each MAC PDU whenever radio resource for a new
transmission is available. As stated above, this decision is delivered to the multiplexing and
demultiplexing entity.

HARQ entity

The HARQ entity performs the transmit HARQ operation and the receive HARQ operation.
The transmit HARQ operation includes transmission of transport blocks and, if necessary,
retransmission of the transport blocks, and, if configured, reception and processing of HARQ
ACK/NACK signaling. The receive HARQ operation includes reception of transport blocks,
combining and decoding of the received transport blocks and, if configured, generation of
HARQ ACK/NACK signaling.

Control entity

The control entity is responsible for a number of functions including DRX, resource requests,
alignment of the uplink timing, power headroom reporting, and so on.
The Random Access (RA) procedure is used to request uplink radio resource to transmit
uplink data when the UE does not have any dedicated uplink transmission resource, or to
respond to the network’s request.

MAC Layer Functions

MAC layer performs the following functions. Not all of these are performed by UE and
eNodeB. Also, it should be noted that some of these functions are available in uplink and
other in downlink.

What functions are supported

 Mapping between logical channels and transport channels

 Multiplexing of MAC SDUs from one or different logical channels onto transport blocks
(TB) to be delivered to the physical layer on transport channels
 Demultiplexing of MAC SDUs from one or different logical channels from transport
blocks (TB) delivered from the physical layer on transport channels
 Scheduling information reporting
 Error correction through HARQ
 Priority handling between UEs by means of dynamic scheduling
 Priority handling between logical channels of one UE
 Logical Channel
 Transport format selection

Transport Channels and Logical Channel

Channel structure in LTE is similar to that of UMTS but it is much simplified in LTE and the
numbers of transport channels and logical channels are also lowered. Unlike UTRA/HSPA,
LTE is based entirely on shared and broadcast channels and contains no dedicated channels
carrying data to specific UEs. This improves the efficiency of the radio interface and can
support dynamic resource allocation between different UEs depending on their traffic/QoS
requirements and their respective channel conditions.

Logical channels provide services at the SAP between MAC and RLC layers, while transport
channels provide services at the SAP between MAC and PHY layers.

Logical Channels

Logical channels are available between MAC and RLC layers and are used by MAC to provide
services to RLC. Logical channels tells what type of information is transferred. Depending on
the traffic types broadly the logical channels can be of two types:- logical control channels and
logical traffic channels.

Here are the different logical channels in LTE.

Logical Control Channels

Broadcast Control Channel (BCCH): BCCH is a downlink channel used to carry

broadcast system control information (e.g. SIBs)

Multicast Control Channel (MCCH): A point-to-multipoint downlink channel used for

transmitting control information to UEs in the cell. It is only used by UEs that receive
multicast/broadcast services.

Paging Control Channel (PCCH): PCCH is a downlink control channel to carry paging
information such as control information during mobile-terminated call.

Common Control Channel (CCCH): CCCH is used to carry control information between
UE and network when RRC connection is not available. CCCH is a bidirectional channel.
CCCH is used during random access procedure.

Dedicated Control Channel (DCCH): A point-to-point, bi-directional channel that

transmits dedicated control information between a UE and the network. This channel is used
when the RRC connection is available, that is, the UE is attached to the network.

Logical Traffic Channels

Logical traffic channels carry user plane information.

Dedicated Traffic Channel (DTCH): A point-to-point, bi-directional channel used

between a given UE and the network. It can exist in both uplink and downlink.

Multicast Traffic Channel (MTCH): A unidirectional, point-to-multipoint data channel

that transmits traffic data from the network to UEs. It is associated with the
multicast/broadcast service.

Transport Channels

Transport channels exist between MAC and physical layer. The transport channels are used by
PHY to offer services to its upper layer i.e. MAC.
A transport channel is basically characterized by how and with what characteristics data is
transferred over the radio interface, that is, the channel coding scheme, the modulation
scheme, and antenna mapping.

Compared to WCDMA/UMTS, in LTE there are no dedicated transport channels exists.

Transport channels can be of two types depending upon the direction of use, downlink
transport channels and uplink transport channels.

Downlink Transport Channels

Broadcast Channel (BCH): BCH is associated with the BCCH logical channel and is used
to broadcast system information over the entire coverage area of the cell. BCH has a
predefined transport format.

Downlink Shared Channel (DL-SCH): DL-SCH is used to transfer both downlink traffic
data and control data. DL-SCH supports HARQ, dynamic link adaptation, dynamic and semi-
persistent resource allocation, UE discontinuous reception, and multicast/broadcast
transmission. DL-SCH can be broadcast in the entire cell.

Paging Channel (PCH): Paging channel is only associated with PCCH logical channel. PCH
channel supports discontinuous reception (DRX) to enable UE power saving and can be used
in the entire cell coverage area.

Multicast Channel (MCH): Associated with MCCH and MTCH logical channels for the
multicast/broadcast service. It supports Multicast/Broadcast Single Frequency Network
(MBSFN) transmission, which transmits the same information on the same radio resource
from multiple synchronized base stations to multiple UEs.

Uplink Transport Channels

Uplink Shared Channel (UL-SCH): UL-SCH works similar as DL-SCH but in uplink. It
supports HARQ, both dynamic and semi-static resource allocation, dynamic link adaptation
and beamforming. It can be associated to CCCH, DCCH, and DTCH logical channels.

Random Access Channel (RACH): RACH is not associated with any logical channels and
is used for transmitting small amount of data, for example RACH can be used in case of inital
access.
Channel Mapping

Uplink Channel Mapping

In uplink following connections between logical channels and transport channels can exist.

CCCH can be mapped to UL-SCH

DCCH can be mapped to UL- SCH
DTCH can be mapped to UL-SCH

Downlink Channel Mapping

In downlink following channel mapping can be possible:

BCCH can be mapped to BCH

BCCH can be mapped to DL-SCH
PCCH can be mapped to PCH
CCCH can be mapped to DL-SCH
DCCH can be mapped to DL-SCH
DTCH can be mapped to DL-SCH
MTCH can be mapped to MCH
MCCH can be mapped to MCH

MAC layer in LTE can perform the following procedures:

 Random Access Procedure

 DL-SCH Data Transfer
 UL-SCH Data Transfer
 PCH Reception
 BCH Reception
 Discontinuous Reception
 MAC Reconfiguration
 MAC Reset

NOTE: Important procedures will be discussed in separate sections.

MAC PDU – Protocol Data Unit

A MAC PDU consists of a MAC header, zero or more MAC Service Data Units (MAC SDU),
zero, or more MAC control elements, and optionally padding.

MAC PDUs are byte aligned means they are multiple of 8 bits. MAC headers and SDUs are of
variable sizes. MAC SDUs (RLC PDUs) are also byte aligned.

A MAC PDU subheader consists of the six header fields R/R/E/LCID/F/L but for the last
 subheader in the MAC PDU and for fixed sized MAC control elements.
The last subheader in the MAC PDU and subheaders for fixed sized MAC control elements
consist solely of the four header fields R/R/E/LCID.
A MAC PDU subheader corresponding to padding consists of the four header fields
R/R/E/LCID.
MAC PDU subheaders have the same order as the corresponding MAC SDUs, MAC control
elements and padding.

MAC control elements are always placed before any MAC SDU.NOTE: A
maximum of one MAC PDU can be transmitted per TB per UE. A maximum of
one MCH MAC PDU can be transmitted per TTI

According to 3GPP, several types of data transfer services are offered by MAC. Each logical channel type is defined by the type of
information to be transferred.
A general classification of logical channels is into two groups:

 Control Channels (for the transfer of control plane information)

 Traffic Channels (for the transfer of user plane information).
Control Channels:
Control channels are used for transfer of control plane information only. The control channels offered by MAC are:

 Broadcast Control Channel (BCCH)

A downlink channel for broadcasting system control information.
 Paging Control Channel (PCCH)
A downlink channel that transfers paging information and system information change notifications.
This channel is used for paging when the network does not know the location cell of the UE.
 Common Control Channel (CCCH)
Channel for transmitting control information between UEs and network. This channel is used for UEs having no RRC connection with
the network.
 Dedicated Control Channel (DCCH)
A point-to-point bi-directional channel that transmits dedicated control information between a UE and the network. Used by UEs having
an RRC connection.
Traffic Channels:
Traffic channels are used for the transfer of user plane information only. The traffic channels offered by MAC are:

 Dedicated Traffic Channel (DTCH)

A Dedicated Traffic Channel (DTCH) is a point-to-point channel, dedicated to one UE, for the transfer of user information. A DTCH can
exist in both uplink and downlink.
 Multicast Traffic Channel (MTCH) (from Release 9)
A point-to-multipoint downlink channel for transmitting traffic data from the network to the UE. This channel is only used by UEs that
receive MBMS.
The figure below depicts the mapping between logical channels, transport channels and physical channels for downlink and uplink:

Figure 18: Downlink Channel Mapping

Figure 19: Uplink Channel Mapping
The protocol stack functions consist of the Medium Access Control (MAC), Radio Link Control
(RLC), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC). LTE is the
latest generation of the 3GPP standards. TheLTE standard specifies an IP-only network supporting
data rates up to 150 Mbps.

Let's have a close look at all the layers available in E-UTRAN Protocol Stack which we
have seen in previous chapter. Below is a more ellaborated diagram of E-UTRAN
Protocol Stack:

Physical Layer (Layer 1)

Physical Layer carries all information from the MAC transport channels over the air
interface. Takes care of the link adaptation (AMC), power control, cell search (for initial
synchronization and handover purposes) and other measurements (inside the LTE
system and between systems) for the RRC layer.
Medium Access Layer (MAC)
MAC layer is responsible for Mapping between logical channels and transport channels,
Multiplexing of MAC SDUs from one or different logical channels onto transport blocks
(TB) to be delivered to the physical layer on transport channels, de multiplexing of MAC
SDUs from one or different logical channels from transport blocks (TB) delivered from
the physical layer on transport channels, Scheduling information reporting, Error
correction through HARQ, Priority handling between UEs by means of dynamic
scheduling, Priority handling between logical channels of one UE, Logical Channel
prioritization.

Radio Link Control (RLC)

RLC operates in 3 modes of operation: Transparent Mode (TM), Unacknowledged Mode
(UM), and Acknowledged Mode (AM).

RLC Layer is responsible for transfer of upper layer PDUs, error correction through ARQ
(Only for AM data transfer), Concatenation, segmentation and reassembly of RLC SDUs
(Only for UM and AM data transfer).

RLC is also responsible for re-segmentation of RLC data PDUs (Only for AM data
transfer), reordering of RLC data PDUs (Only for UM and AM data transfer), duplicate
detection (Only for UM and AM data transfer), RLC SDU discard (Only for UM and AM
data transfer), RLC re-establishment, and protocol error detection (Only for AM data
transfer).

Radio Resource Control (RRC)

The main services and functions of the RRC sublayer include broadcast of System
Information related to the non-access stratum (NAS), broadcast of System Information
related to the access stratum (AS), Paging, establishment, maintenance and release of
an RRC connection between the UE and E-UTRAN, Security functions including key
management, establishment, configuration, maintenance and release of point to point
Radio Bearers.

Packet Data Convergence Control (PDCP)

PDCP Layer is responsible for Header compression and decompression of IP data,
Transfer of data (user plane or control plane), Maintenance of PDCP Sequence Numbers
(SNs), In-sequence delivery of upper layer PDUs at re-establishment of lower layers,
Duplicate elimination of lower layer SDUs at re-establishment of lower layers for radio
bearers mapped on RLC AM, Ciphering and deciphering of user plane data and control
plane data, Integrity protection and integrity verification of control plane data, Timer
based discard, duplicate discarding, PDCP is used for SRBs and DRBs mapped on DCCH
and DTCH type of logical channels.

Non Access Stratum (NAS) Protocols

The non-access stratum (NAS) protocols form the highest stratum of the control plane
between the user equipment (UE) and MME.

NAS protocols support the mobility of the UE and the session management procedures
to establish and maintain IP connectivity between the UE and a PDN GW.