Beruflich Dokumente
Kultur Dokumente
Contents
1 Radio Protocols Architecture 2
2 RRC Tasks and States 8
3 Layer 2 Functions and Data Flow 13
4 Protocols Configuration Example 20
TM5117EN02GLA01
2 2010 Nokia Siemens Networks
Air Interface Protocols
L
3 RRC
Radio Bearer
PDCP
L
RLC
2
Logical Channel
MAC
Transport Channels
L
Physical Layer
1
Physical Channels
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The EUTRAN radio protocol model specifies the protocols terminated between UE
and eNB. The protocol stack follows the standard guidelines for radio protocol
architectures (ITU-R M1035) and is thus quite similar to the WCDMA protocol stack
of UMTS.
The protocol stack defines three layers: the physical layer (layer 1), data link and
access layer (layer 2) and layer 3 hosting the access stratum and non-access
stratum control protocols as well as the application level software (e.g. IP stack).
physical layer: The physical layer forms the complete layer 1 of the protocol stack
and provides the basic bit transmission functionality over air. In LTE the physical
layer is driven by OFDMA in the downlink and SC-FDMA in the uplink. FDD and
TDD mode can be combined (depends on UE capabilities) in the same physical
layer. The physical layer uses physical channels to transmit data over the radio
path. Physical channels are dynamically mapped to the available resources
(physical resource blocks and antenna ports). To higher layers the physical
layer offers its data transmission functionality via transport channels. Like in
UMTS a transport channel is a block oriented transmission service with certain
characteristics regarding bit rates, delay, collision risk and reliability. Note that in
contrast to 3G WCDMA or even 2G GSM there are no dedicated transport or
physical channels anymore, as all resource mapping is dynamically driven by
the scheduler.
MAC (Medium Access Control): MAC is the lowest layer 2 protocol and its main
function is to drive the transport channels. From higher layers MAC is fed with
logical channels which are in one-to-one correspondence with radio bearers.
Each logical channel is given a priority and MAC has to multiplex logical
channel data onto transport channels. In the receiving direction obviously
demultiplexing of logical channels from transport channels must take place.
Further functions of MAC will be collision handling and explicit UE identification.
An important function for the performance is the HARQ functionality which is
official part of MAC and available for some transport channel types.
TM5117EN02GLA01
4 2010 Nokia Siemens Networks
Air Interface Protocols
NAS
NAS Protocol(s)
Protocol(s) Application
Application Layer
Layer
(Attach/TA
(Attach/TA Update/)
Update/)
IP
IP // TCP
TCP || UDP
UDP ||
(E-)RRC
(E-)RRC
(Radio
(Radio Resource
Resource Control)
Control)
Radio Bearer
PDCP
PDCP PDCP
PDCP PDCP
PDCP PDCP
PDCP PDCP
PDCP ROHC (RFC 3095)
(Packet
(Packet Data
Data (Packet
(Packet Data
Data (Packet
(Packet Data
Data (Packet
(Packet Data
Data (Packet
(Packet Data
Data
Convergence Convergence Convergence Convergence Convergence
Convergence Convergence Convergence Convergence Convergence Security
Protocol)
Protocol) Protocol)
Protocol) Protocol)
Protocol) Protocol)
Protocol) Protocol)
Protocol)
RLC
RLC RLC
RLC RLC
RLC RLC
RLC RLC
RLC Segment./Reassembly
(Radio
(Radio Link
Link (Radio
(Radio Link
Link (Radio
(Radio Link
Link (Radio
(Radio Link
Link (Radio
(Radio Link
Link
Control)
Control) Control)
Control) Control)
Control) Control)
Control) Control)
Control) ARQ
Medium
Medium Access
Access Control
Control (MAC)
(MAC) De/Multiplexing
HARQ
Transport Channels
CRC
FDD
FDD || TDD
TDD -- Layer
Layer 11
(( DL:
DL: OFDMA,
OFDMA, UL:UL: SC-FDMA
SC-FDMA )) Coding/Rate Matching
Interleaving
Modulation
Physical Channels
Resource Mapping/MIMO
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RLC (Radio Link Control): Each radio bearer possesses one RLC instance
working in either of the three modes: UM (Unacknowledged), AM
(Acknowledged) or TM (Transparent). Which mode is chosen depends on the
purpose of the radio bearer. RLC can thus enhance the radio bearer with ARQ
(Automatic Retransmission on reQuest) using sequence numbered data frames
and status reports to trigger retransmission. Note that it shall be possible to
trigger retransmissions also via the HARQ entity in MAC. The second
functionality of RLC is the segmentation and reassembly that divides higher
layer data or concatenates higher layer data into data chunks suitable for
transport over transport channels which allow a certain set of transport block
sizes.
PDCP (Packet Data Convergence Protocol): Each radio bearer also uses one
PDCP instance. PDCP is responsible for header compression (ROHC RObust
Header Compression; RFC 3095) and ciphering/deciphering. Obviously header
compression makes sense for IP datagram's, but not for signaling. Thus the
PDCP entities for signaling radio bearers will usually do ciphering/deciphering
only.
RRC (Radio Resource Control): RRC is the access stratum specific control
protocol for EUTRAN. It will provide the required messages for channel
management, measurement control and reporting, etc.
NAS Protocols: The NAS protocol is running between UE and MME and thus
must be transparently transferred via EUTRAN. It sits on top of RRC, which
provides the required carrier messages for NAS transfer.
TM5117EN02GLA01
6 2010 Nokia Siemens Networks
Air Interface Protocols
MME
UE eNB MME
NAS NAS
RRC RRC
PDCP PDCP
RLC RLC
MAC MAC
PHY PHY
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM5117EN02GLA01
8 2010 Nokia Siemens Networks
Air Interface Protocols
The RRC protocol for EUTRAN is responsible for the basic configuration of the radio
protocol stack. But one should note, that some radio management functions
(scheduling, physical resource assignment for physical channels) are handled by
layer 1 and layer 2 autonomously. MAC and layer 1 signaling has usually delays that
are within 10 ms, whereas RRC signaling usually takes something around 100 ms
and more to complete an operation.
NAS
NAS Protocol(s)
Protocol(s) Application
Application Layer
Layer
NAS System Information (BCCH) (Attach/TA
(Attach/TA Update/)
Update/)
E-UTRAN System Info. (BCCH) IP
IP // TCP
TCP || UDP
UDP ||
Paging (PCCH) (E-)RRC
(E-)RRC
(Radio
(Radio Resource
Resource Control)
Control)
RRC Connection Management
Medium
Medium Access
Access Control
Control (MAC)
(MAC)
MBMS
Transport Channels
Mgmt. of MBMS radio bearers
Physical Channels
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM5117EN02GLA01
10 2010 Nokia Siemens Networks
Air Interface Protocols
RRC will use one or two radio bearers exclusively used for signaling (Signaling
Radio Bearers). One will be for high, the other for low priority. The PDCP entities of
these signaling radio bearers will be used for ciphering, but not for header
compression.
The RRC protocol in EUTRAN defines two state for a UE: RRC_IDLE and
RRC_CONNECTED. In the first state, the UE is not attached to a eNB and does free
cell re-selection. In the second state the UE is connected to a eNB and the eNB
handles all mobility related aspects of the UE via handovers. There is of course a
close relationship between LTE-states and RRC states.
RRC_IDLE RRC_CONNECTED
UE in DRX (NAS configuration); UE in DRX/DTX (e-Node B
UE receives BCCH; configuration);
UE monitors PCH; UE uses mainly DCCH/DTCH;
UL/DL data transmission
cell reselection; possible;
UE monitors PDCCH to get
no RRC context in e-NodeB RRC Connection Establishment scheduling assignments;
(via CCCH) UE reports channel quality (CQI)
to e-NodeB to assist channel
dependent scheduling;
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM5117EN02GLA01
12 2010 Nokia Siemens Networks
Air Interface Protocols
Data transmission is handled through the protocol stack according to the following
flow:
TM5117EN02GLA01
14 2010 Nokia Siemens Networks
Air Interface Protocols
NAS
NAS
(E-)RRC
(E-)RRC IP
IP (user
(user plane)
plane)
RB RB RB RB
PDCP
ROHC ROHC ROHC
Security Security Security Security
Multiplexing
HARQ
Transport Block
(1 per TTI) TB ACK|NACK
TrCH
FDD
FDD || TDD
TDD -- Layer
Layer 11
((
UL:
UL: SC-FDMA
SC-FDMA ))
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MAC maps different logical channels and signaling data to the UL-SCH.
00000 CCCH
01011-11011 Reserved
11011 C-RNTI
11111 Padding
The transmission path through layer 2 for downlink is similar to that of the uplink
direction.
Of course the eNB has to process the radio bearers of several UE.
Thus the scheduler in the eNB has to balance the traffic between different users. This
is done by taking each radio bearer as individual quality of service instance into
account.
TM5117EN02GLA01
16 2010 Nokia Siemens Networks
Air Interface Protocols
UE #1 UE #N
NAS
NAS NAS
NAS
(E-)RRC
(E-)RRC IP
IP (user
(user plane)
plane) (E-)RRC
(E-)RRC IP
IP (user
(user plane)
plane)
RB RB RB RB
PDCP PDCP
ROHC ROHC
PCCH BCCH
RLC Segment- Segment- RLC Segment- Segment- (Paging) (SysInfo)
ation ation ation ation
HARQ HARQ
ACK|NACK
ACK|NACK
TB TB
Transport Block(s) TB
Transport Block(s) TB
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Furthermore the MAC layer supports mapping of several logical channels to the
transport channel.
RNTI types are defined to handle the mapping of the different types of logical
channels.
- C-RNTIs for DCCH and DTCH;
+ C-RNTI
+ temporary C-RNTI
+ semi-persistant C-RNTI
- P-RNTI for PCCH;
- RA-RNTI for Random Access Response on DL-SCH;
- Temporary C-RNTI for CCCH during the random access procedure;
- SI-RNTI for BCCH.
I.e. the MAC scheduling via PDCCH is performed by using the appropriate RNTI.
A MAC PDU consist of a MAC header and there might be MAC control elements,
MAC SDUs and Padding. The header itself is made of subheaders.
The subheader consists of various fields:
R: Reserved bit
LCID: Logical Channel ID
E: Extension bit tells if more subheader will follow
F: Indicates the length of the length field (7 or 15 bit)
L: Length field gives the length of the corresponding MAC SDU or control element in
byte
The LCID for DL-SCH are defined in the following way:
00000 CCCH
01011-11011 Reserved
11111 Padding
TM5117EN02GLA01
18 2010 Nokia Siemens Networks
Air Interface Protocols
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM5117EN02GLA01
20 2010 Nokia Siemens Networks
Air Interface Protocols
Protocol Configuration for the User Plane: The E-Mail application will be
transmitted using UDP (connectionless protocol) and the FTP Application will be sent
using the TCP (connection oriented). The reason for this is that the transmission of
the FTP should be more reliable from the QoS point of view. This is also the reason
why 2 different user plane data radio bearers (DRBs) have to be used for this
scenario. Both applications are then using the IP (Internet Protocol). The DRBs are
established using the signaling radio bearers SRBs.
The user plane radio bearers are transported further using the acknowledged mode
RLC. The radio bearer 1 which is caring the e-mail will be mapped on the logical
channel DTCH1 (Dedicated Traffic Channel) and the radio bearer 2 which is caring
the FTP download will be mapped on the DCCH2. The logical channels will be further
explained in chapter 5.
TM5117EN02GLA01
22 2010 Nokia Siemens Networks
Air Interface Protocols
RLC AM AM AM AM
MAC
Physical Layer
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PDCP H H Payload
Payload
PDCP PDCP
PDCP SDU PDCP SDU
Header Header
RLC
PDCP PDU PDCP PDU
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TM5117EN02GLA01
24 2010 Nokia Siemens Networks
Air Interface Protocols
In this example, two IP packets are transmitted over the air interface:
The first IP packet it is assumed to come from the E-Mail application and the scond
IP packet is comming from the FTP download.
One IP packet is containing the header and the payload. The header length is
dependent on the IP version used: IPv4 or IPv6 (a higher length for IPv6). The
payload is containing the user data (E-Mail or FTP transfer) together with UDP/TCP
control fields.
PDCP layer: The IP packets are passed through the PDCP layer which is performing
IP header compression and ciphering. Therefore a PDCP header is required. The
PDCP SDU (Service Data Unit data comming from higher layers to the PDCP
layer) together with the PDCP header are forming together the PDCP PDU
(Protocol Data Unit). The PDCP PDUs are passed down to the RLC layer.
RLC layer: the RLC configuration is AM (acknowledged mode) for both applications
from this example. The second functionality of the RLC layer is segmenatation/
reasembly. In the example shown the segmentation process is ilustrated for the data
comming from the second application (the FTP transfer). An RLC header is needed
for both reliable data transfer (acknowledge mode) and to be able to perform
reasembly at the receiver side.
MAC layer: the MAC layer is multiplexing together a number of RLC PDUs(Packet
Data Units) to form a Transport Block. How many RLC PDUs are to be multiplexed in
one transport bloc is dependent on the transport block size which is sent over the air
interface in on TTI (Transmission Time Interval) = 1 ms. The size of the transport
block is decided by the scheduler which should take into account the quality of the
radio link (link adaptation mechanism): it depends on the chosen Modulation and
Coding Scheme (MCS), the number of resources allocated on the air interface. Thus,
the link adaptation mechanism affects both the RLC and MAC processing
(segmentation at RLC and multiplexing at the MAC layer). Thus, the MAC layer
should add one header to indicate the multiplexing of the RLC PDUs into the
transport block.
Physical Layer: the physical layer attaches one CRC (cyclic redundancy coding) for
error correction reasons. Details on the transport channel processing at the physical
layer are provided in chapter 6.
TM5117EN02GLA01
26 2010 Nokia Siemens Networks