UMTS Protocols 2

Outlines
Radio Interface Protocol Architecture.
Logical Channels & Transport Channels.
MAC Protocol.

1) MAC Services.
2) MAC Functions.
3) MAC Entities.
RLC Protocol.
1) RLC Functions.
2) RLC Modes.
2

Radio Interface Protocol

Architecture.

Radio Interface Protocol

Architecture.
The Radio Interface Layers :1- The Physical Layer (L1).
2- The Data Link Layer (L2).
2-1 MAC : Medium Access Control.
2-2 RLC : Radio Link Control.
2-3 PDCP : Packet Data Convergence
Protocol.
2-4 BMC : Broadcast / Multicast Control .
3- The Network Layer (L3).
RRC : Radio Resource Control .
4

Logical Channels & Transport

Channels

Transport Channels

Transport Channel(1)
Random Access Channel (RACH)
Used to carry control information from the terminals in the

cell area. This is used, for example, when a terminal

requests to set up a connection to the network.
The RACH is always received from the entire cell and thus in
practice the data rates need to be rather low .
Forward Access Channel (FACH)
Used to carry downlink control information to a terminal
known to be located in the cell area.
The FACH is used, for example, after a random access
message has been received by the BTS and control
information needs to be sent to the terminal.
7

Transport Channel(2)
Paging Channel (PCH)
Carries paging procedure related data, which is used when the

network needs to initiate communication with a specific terminal, for

example when a speech call is coming to the terminal.
The paging message can be transmitted in a single cell or in up to a
few hundred cells, depending on the system configuration and
location area size.
The PCH is always transmitted over the entire cell and all terminals in
the cell area must be able to receive the paging information.
Broadcast Channel (BCH)
Downlink channel used for broadcast of system information into cell.
Ex: Random access codes, cell access slots, and cell-type transmit
diversity
methods.
8

Transport Channel(3)
Downlink Shared Channel (DSCH) TDD only

Downlink channel shared by several UEs carrying dedicated

control or traffic data.
Uplink Shared Channel (USCH) TDD only
Uplink channel shared by several UEs carrying dedicated control
or traffic data.
Dedicated Channel (DCH)
Channel dedicated to one UE used in uplink or downlink.
EX : speech frames, measurement reports and control
commands from UE.
Enhanced Dedicated Channel (E-DCH)
Channel dedicated to one UE used in uplink only.
Provides data speeds of up to 5.8 Mbps in the uplink direction.
9

Logical Channels
Relate to the content and what kind of data
are
transmitted through the radio interface
Logical Channel

Traffic Channel

DTCH
(UL/DL)

CTCH
(DL)

Control Channel

BCCH
(DL)

PCCH
(DL)

DCCH
(UL/DL)

CCCH
(UL/DL
)

10

Logical Control Channel

11

Logical Traffic Channel

12

Radio Interface Protocol

Architecture.

13

Medium Access Control

RLC

Logical Channels

MAC

Transport Channels

Physical
14

MAC Protocol
MAC is a Layer 2 protocol and it resides

between Physical Layer (L1) and RLC Layer (L2).

The internal configuration of MAC is done by the
RRC layer (L3).
The interface between PHY and MAC are the
transport channels .
The interface between RLC and MAC are the
logical channels.
MAC protocol is not symmetrical protocol as it
is different in UL and DL .
15

MAC Services
Data Transfer :

This service provides unacknowledged transfer of

MAC SDUs between peer MAC entities without data
segmentation & peer-to-peer transportation of LRC
PDUs.
Reallocation of radio resources and MAC
parameters :
This service performs, on request of RRC,execution
of RR reallocation and change of MAC parameters .
Reporting of Measurements:
Traffic Volume Measurements are reported to RRC.
16

MAC Functions (1)

Mapping between logical channels and

transport channels.
Selection of appropriate Transport Format for
each Transport Channel depending on
instantaneous source rate.
Priority handling between data flows of one UE.
Priority handling between UEs by means of
dynamic scheduling.
Identification of UEs on common transport
channels.
17

MAC Functions (2)

Multiplexing/ Demultiplexing of upper layer

PDUs into/from transport block sets delivered

to/from the physical layer on dedicated
transport channels.
Traffic volume measurement.
Transport Channel type switching.
Ciphering for transparent mode RLC.
Access Service Class selection for RACH and
CPCH transmission.
18

Mapping (1)
Mapping between logical channels and transport

channels

19

Transport Format
Transport format : Format offered by the physical layer

to the MAC for the delivery of a Transport Block set

during TTI on a Transport Channel.
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.
Given the Transport Format Combination Set assigned by
RRC, MAC selects the appropriate transport format for
each active transport channel depending on source rate.
20

Transport Format

21

Transport Format Parts

The transport format constitutes of two parts:
The semi-static part : includes parameters are

fixed for all transport block sets of the corresponding

transport channel until the RRC parameters are
reconfigured.
The dynamic part : includes parameters whose value
can
change from one transport block set to another.
Both are configured by RRC.
It is the MAC layers responsibility to choose an
appropriate set of parameters from the allowed values
for the transmission.
22

Transport format set

23

Transport format set

TTI [Transmission Time Interval ] :defines the

time interval between two subsequent transport

block set transfers between MAC and PHY.
Rate matching : indicate how the transmission
process is carried out so that the block size
matches the radio frames. Rate matching will
either repeat bits to increase the rate or puncture
bits to decrease the rate.
Transport Format Indicator (TFI) : The
representation of a specific transport format
within a TFS.
24

Example on TF

Two transport channels mapped onto a single physical

channel

25

Example on TF

26

Inband Identification
At RACH : when several Random Access

packets are received at Node-B , The Physical

layer detects them and deliver them to the
MAC layer .
MAC distinguishes the valid random access
packets by different identifications.
So inband identification is needed as the MAC
handles access to, multiplex onto , the
transport channels .
27

Multiplexing /
Demultiplexing
MAC should support service multiplexing for
common transport channels, since the
physical layer does not support multiplexing
of these channels.
Multiplexing/ demultiplexing data between
Logical channels [ CCCH DCCH DTCH ] and
Transport channels [ FACH RACH ] in
10000consideration of The Appropriate
DTCH
11111
Prioritization

using
LID.
MAC
DCCH
FACH /
LID
00100
LIDRACH
: LogicalPDU
Channel Identifier .
00010

CCCH

28

Traffic Volume
Measurements
Traffic volume information is measured at the
MAC layer and the results are reported to RRC.
RRC takes the decisions and performs
Transport channel switching .
Switching : Execution of the switching
between common & dedicated channels
based on switching decision by RRC.
Ciphering : prevents unauthorized acquisition
of data performed in MAC only for
[ Transparent RLC Mode ].
29

Access Service Class

RACH & CPCH resources may be divided between

Access Service Classes in order to provide

different priorities of RACH & CPCH classes .
Each ASC will have a set of parameters
associated with it
RACH resources in TDD [ Time slot ] and in FDD
[ Access slot ].
CPCH resources only in FDD [ Access slot ] .
ASC is classified between [ ASC0 to ASC7 ] .
ASC0 : Highest Priority.
ASC7 : Lowest Priority .
30

MAC PDU

31

MAC PDU
TCTF : Target Channel Type Field : Provides identification of

the logical
channel in case of RACH and FACH
C/T : provides identification of logical channel when
multiple logical
channels are carried on the same transport channel.
UE-ID Type : Provides identification of UE on Common
Transport
Channel .
1- U-RNTI :For DCCH at DL.
2- C-RNTI : for DTCH at UL & DL.
UE-ID Type Field : to decode UE-ID in MAC header.
32

MAC Logical Architecture

33

MAC Entities
MAC-b : represents the control entity for BCH.

- There is one MAC-b entity in UE .

- There is one MAC-b entity in UTRAN .
MAC-c/sh : handles PCH,FACH,RACH (FDD)
handles DSCH,USCH (TDD)
- There is one MAC-b entity in UE .
- There is one MAC-b entity in UTRAN .
MAC d : handles DCH
- There is one MAC-b entity in UE .
- There is one MAC-b entity in UTRAN .

34

MAC Entities

35

Distribution of MAC Functions

(DSCH TDD only)

36

MAC c/sh

37

MAC c/sh
TCTF MUX : represents the handling of TCTF field in the

MAC
header .
Add/read UE ID : the UE ID is added for CPCH and RACH
transmissions.
UL : TF Selection: The possibility of TF selection exists
ASC Selection : MAC indicates ASC associated with PDU to
the physical layer ,to ensure that RACH & CPCH messages
with given ASC are send to appropriate time slot(s).
Scheduling / Priority handling : used to transmit the
information received from MAC-d on RACH & CPCH based
on Logical Channel Priorities .
38

MAC-d

39

MAC-d
Transport Channel Type Switching:

- Performed by MAC based on decision taken by RRC.

- If requested by RRC , MAC shall switch the mapping
of
one logical channel between common & dedicated
Transport channels.
C/T MUX : is used when multiplexing of several
dedicated logical channels onto one transport channel
is used .
Ciphering / Deciphering : For Transparent RLC
mode .
Flow Control : To limit buffering between MAC-d and
40
MAC-c/ sh entities .

MAC-d UTRAN side

41

Radio Interface Protocol

Architecture.

42

Radio Link Control

RRC PDCP BMC

TR-SAP

AM - SAP

UM - SAP

RLC

Logical Channels

MAC
43

RLC Functions
Data Transfer .
Segmentation & Reassembly .
Error Detection & Correction .
Flow Control .
Ciphering .
In-sequence delivery of upper layer PDUs.
Sequence number check.
Padding.
Concatenation.
44

RLC Modes
Provides segmentation/reassembly (payload units,

PU) and retransmission service for both user and

control data
Transparent mode (TM): no overhead is added
to higher layer data.
Unacknowledged mode (UM): no
retransmission protocol is used and data delivery
is not guaranteed.
Acknowledged mode (AM): Automatic Repeat
request (ARQ) mechanism is used for error
correction.

Packet Construction
PDUs from Upper Layers are Too Large

- Segmented into smaller units of equal size

PDUs from Upper Layers are Too Small
1- Concatenated with first segment of the next
incoming PDU from the upper layer.
2- Extended by adding padding bits.
Header is added to each segment and the
resulting packet is passed to the MAC Layer.
46

Packet Construction
AM&UM

47

Packet Construction TM

48

RLC Logical Architecture

There is one transmitting and one

receiving entity for TM and UM .

There is one combined transmitting and
receiving entity for AM .
The mode to be used is determined by
the SAP into which the higher layer
deliver their PDUs.
The mode chosen indicates which
services and functions are to be applied .
49

RLC Logical Architecture

50

RLC Logical
Architecture

51

RLC PDU types

1. Data PDUs : used to transfer user data .
1- TMD PDU.
2- AMD PDU.
3- UMD PDU.
2. Control PDUs : carry control information .
1- RESET.
2- STATUS.
3- RESET ACK.
Note : Control PDUs used only in AM.
52

Data PDUs
Transparent PDU : used to carry any length of

user data without adding any RLC Header.

Unacknowledged PDU : transfers user data
sequentially using the sequence number in
the header but does not provide any ACK to
the sender.
Acknowledged PDU : transfers user data
sequentially using the sequence number in
the header and also provide ACK to the sender
by means of Control PDUs like STATUS.
53

Control PDUs
STATUS PDU : used to inform the transmitter which

PDUs are received correctly and

which PDUs are missing .
RESET PDU : command the other end to reset its
protocol state variables & timers so
that the two ends maybe
synchronized with each other .
RESET ACK PDU : to ACK the RESET command .

Transparent Mode ( TM )
Transparent Mode Functions :
1. Segmentation and reassembly .
2.Transfer of user data .
3.SDU discard .

55

TM Trans. & Receive.

56

1-Receiving TM-RLC
Entity
The receiving TM-RLC entity
receives TMD PDUs through
the configured logical
channels from the lower
layer.
If segmentation is
configured by upper Layers?
If segmentation is not
configured by upper layers?
The receiving TM RLC entity
delivers RLC SDUs to upper
layers through the TM-SAP.
57

2-Transmitting TM-RLC
Entity
The transmitting TM-RLC

entity receives RLC SDUs

from upper layers through
the TM-SAP.
If segmentation has been
configured by upper layers ?
If segmentation has not
been configured by upper
layers ?
When the processing of a
RLC SDU is complete, the
resulting one or more TMD
PDU(s) are/is submitted to
the lower layer through
logical channel.

58

Unacknowledged Mode
(UM)
Unacknowledged Mode Functions :
1. Segmentation and reassembly.
2.Concatenation.
3.Padding.
4.Transfer of user data.
5.Flow Control.
6.Sequence number check.
7.Ciphering.
8.SDU discard.
59

Sequence number check

After receiving a packet , RLC examines the

sequence number :
1.Erroneous : The packet is discarded .
2.Non-erroneous : It is delivered to higher layers .
In this mode : the responsibility of the high layers
to
recover the missing packets using
an
appropriate error receiving
mechanism.
60

UM Trans. & Receive.

61

1-Receiving UM-RLC
Entity
The receiving UM-RLC entity

receives UMD PDUs through the

configured logical
channels from the lower layer.
The receiving UM RLC entity
deciphers the received UMD
PDUs (except for the UMD PDU
header).
It removes RLC headers from
received UMD PDUs, and
reassembles RLC SDUs
RLC SDUs are delivered by the
receiving UM RLC entity to the
upper layers through the UM-SAP.

62

2-Transmitting UM-RLC
Entity
The transmitting UM-RLC entity receives

RLC SDUs from upper layers through the

UM-SAP.
The transmitting UM RLC entity segments
the RLC SDU into UMD PDUs of appropriate
size, if the RLC SDU is larger than the
length of available space in the UMD PDU.
The UMD PDU may contain segmented
and/or concatenated RLC SDUs and Length
Indicators are used to define boundaries
between RLC SDUs within UMD PDUs.
If ciphering is configured and started, an
UMD PDU is ciphered (except for the UMD
PDU header) before it is submitted to the
lower layer.
The transmitting UM RLC entity submits
UMD PDUs to the lower layer through
logical channel.

63

Acknowledged Mode
(AM)
Acknowledged Mode Functions :
1. Segmentation and reassembly.
2. Concatenation.
3. Padding.
4. Transfer of user data.
5. Error correction.
6. In-sequence delivery of upper layer PDUs.
7. Duplicate detection.
8. Flow Control.
9. Protocol error detection and recovery.
10. Ciphering.
11.SDU discard.
64

Error Detection &

Correction

65

Guaranteed, Error-Free
Delivery
RLC checks the sequence number of the
packet that come from MAC layer .
Correct : receive & reassembly and send to
higher layers.
Incorrect : the receiver discards the packet
and attempts to recover that error by :1- ARQ : Automatic Repeat Request .
2- Receiving End .
3- Desired Packets .
66

TM Trans. & Receive.

67

1-Receiving AM-RLC
Entity

68

1-Receiving AM-RLC
Entity

The receiving side of the AM-RLC entity receives AMD and Control

PDUs through the configured logical channels from the lower layer.
AMD PDUs are routed to the Deciphering Unit and then delivered to
the Reception buffer.
The AMD PDUs are placed in the Reception buffer until a complete
RLC SDU has been received.
The Receiver acknowledges successful reception or requests
retransmission of the missing AMD PDUs by sending one or more
STATUS PDUs to the AM RLC peer entity, through its transmitting
side.
The associated AMD PDUs are reassembled by the Reassembly Unit
and delivered to upper layers through the AM-SAP.
RESET and RESET ACK PDUs are delivered to the RLC Control Unit
for processing. If a response to the peer AM RLC entity is needed by
the RLC Control Unit to the transmitting side of the AM RLC entity.
69

2-Transmitting AM-RLC
Entity

70

2-Transmitting AM-RLC
Entity

The transmitting side of the AM-RLC entity receives RLC SDUs from upper

layers through the AM-SAP.

RLC SDUs are segmented and/or concatenated into AMD PDUs of a fixed
length.
After the segmentation and/or concatenation are performed, the AMD PDUs
are placed in the Retransmission buffer at the MUX.
The MUX multiplexes AMD PDUs from the Retransmission buffer that need to
be
retransmitted, and the newly generated AMD PDUs delivered from the
Segmentation/Concatenation function.
The PDUs are delivered to the function that completes the AMD PDU header
and potentially replaces padding with piggybacked status information. A
Piggybacked
STATUS PDUs can be of variable size in order to match the amount of free
space in the AMD PDU.
The ciphering (if configured) is then applied to the AMD PDUs.
AMD PDUs are submitted through logical channels to the lower layers .
71

MAC Modes

72