Speaker: Dr.

Phone Lin, Professor

Evolution for 3G
Long Term Evolution (LTE)
• Architecture, Protocol Stack, and Functionality
Introduction to E-UTRAN
• Protocol Stack, and Functionality

2
International Telecommunication Union (ITU)
• Identified the frequencies around 2GHz for
International Mobile Telephony 2000 (IMT 2000)
IMT 2000 spectrum allocation at 2GHz
• LTE, WCDMA

3
Air Interface
• UTRA-UTRAN Long Term Evolution (LTE) Study Item (TSG-RAN)
Network Architecture
• System Architecture Evolution (SAE) Study Item (TSG-SA)

4
5
 Objective:
• To develop a framework for the evolution of the 3GPP radio-access
technology towards a high-data-rate, low-latency and packet-
optimized radio-access technology
Metric Requirement
Peak data rate DL: 100Mbps (3 to 4 times to that of HSDPA)
UL: 50Mbps (2 to 3 times to that of HSUPA)
Mobility support Up to 500kmph but optimized for low speeds from 0 to 15kmph
Control plane latency < 100ms (for idle to active)
(Transition time to active state)
User plane latency < 5ms
Control plane capacity > 200 users per cell
Coverage (Cell sizes) 5 – 100km with slight degradation after 30km
Spectrum flexibility 1.25, 2.5, 5, 10, 15, and 20MHz

6
Architecture and Protocol Stack

7
 UTRAN S12
Iu SGSN Evolved
Packet
Core (EPC)
Gb Wx*
GERAN
S3 S4 S6a
HSS PCRF
MME
PDN S7 Rx+
S1-MME Gateway S7a
X2 E-NB S11 S7b
S10 Operator IP
S5 SGi
S1-U Service
EUTRAN Serving S2a S2b (IMS)
Gateway
LTE-Uu S6c
Wm*
ePDG
Wn* 3GPP AAA
Wa*
Server
Non 3GPP WLAN
• Evolved Packet System (EPS) Architecture IP Access Access NW
– EPS consists of LTE (Long Term Evolution), which is dedicated to the
evolution of the radio interface, and SAE (System Architecture Evolution), which
focuses on Core Network architecture evolution.
– LTE  E-UTRAN
– SAE  EPC (Evolved Packet Core) 8
Evolved Radio Access Network (eRAN)
• Consists of the eNodeB (eNB)
• Offers Radio Resource Control (RRC) functionality
• Radio Resource Management, admission control, scheduling, ciphering/deciphering of user
and control plane data, and compression/decompression in DL/UL user plane packet headers
Serving Gateway (SGW)
• Routes and forwards user data packets
• Acts as the mobility anchor for the user plane
- During inter-eNB handovers
- Between LTE and other 3GPP technologies
• Pages idle state UE when DL data arrives for the UE
Packet Data Network Gateway (PDN GW)
• Provides connectivity to the UE to external packet data networks
• A UE may have simultaneous connectivity with more than one PDN GW
• Performs policy enforcement, packet filtering, and charge support
• Acts as mobility anchor between 3GPP and no-3GPP technologies
Mobility Management Entity (MME)
• Manages and stores UE contexts
- UE/user identities, UE mobility state, user security parameters
• Paging message distribution
9
LTE-Uu
S1-MME
• Reference point for the control plane protocol between E-
UTRAN and MME. It uses Stream Control Transmission
Protocol (SCTP) as the transport protocol
NAS NAS
Relay
RRC RRC S1-AP S1-AP
PDCP PDCP SCTP SCTP
RLC RLC IP IP
MAC MAC L2 L2
L1 L1 L1 L1
UE LTE-Uu eNodB S1-MME MME

10
S11 (MME-SGW)
• GPRS Tunnelling Protocol for the control plane (GTP-C)
• Has the same protocol stack as
- S10 (MME-MME)
- S5 or S8a (SGW-PGW)
- S4 (SGSN-SGW) GTP-C GTP-C

- S3 (SGSN-MME) UDP UDP

IP IP
L2 L2
L1 L1

MME S11 SGW

11
 UE - PGW user plane with E-UTRAN
Application

IP IP
Relay Relay
PDCP GTP-U
PDCP GTP-U GTP-U GTP-U
RLC RLC UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC L2 L2 L2 L2
L1 L1 L1 L1 L1 L1
UE LTE-Uu eNodB S1-U SGW S5/S8a PDN GW SGi

UE - PGW user plane with 3G access via the S4 interface

Application

IP IP IP
Relay Relay
Relay Relay
Relay Relay
PDCP PDCP GTP-U PDCP GTP-U GTP-U GTP-U
PDCP GTP-U PDCP GTP-U GTP-U GTP-U GTP-U GTP-U
RLC RLC
UDP/IP RLC
RLC UDP/IP
UDP/IP RLC
UDP/IP UDP/IP
UDP/IP UDP/IP UDP/IP UDP/IP
MAC MAC
L2 MAC
MAC L2
L2 MAC
L2 L2
L2 L2 L2 L2
SM RF GSM
L1bisRF GSM
GSM RF
RF L1bis
L1bis GSM
L1 RF L1bis
L1 L1 L1 L1
NodB UE Uu
Iu SGSN
NodB Iu
S4 SGSN
SGW S4
S5/S8a SGW
PDN GW SGi S5/S8a PDN GW SGi
12
Protocol Stack, Functionality

13
eNB
Inter Cell RRM

RB Control

Connection Mobility Cont.

MME
Radio Admission Control
NAS Security
eNB Measurement
Configuration & Provision
Idle State Mobility
Handling
Dynamic Resource
Allocation (Scheduler)
EPS Bearer Control
RRC

PDCP
S-GW P-GW
RLC
Mobility UE IP address
MAC Anchoring allocation
S1
PHY Packet Filtering
internet

E-UTRAN EPC

14
The S1 control plane interface
(S1-MME) S1-AP
• The SCTP layer provides the
guaranteed delivery of
application layer messages.
• The transport network layer is
built on IP transport, similarly to SCTP
the user plane but for the
reliable transport of signalling IP
messages SCTP is added on top
of IP. Data link layer
• The application layer signalling
protocol is referred to as S1-AP Physical layer
(S1 Application Protocol).

15
S1 User Interface User plane
PDUs
• Provides non guaranteed
delivery of user plane PDUs
between the eNB and the S-
GW.
GTP-U
• The transport network layer
UDP
is built on IP transport and
GTP-U is used on top of IP
UDP/IP to carry the user
Data link layer
plane PDUs between the eNB
and the S-GW. Physical layer

16
EPS Bearer Service Management function:
• Setup, modify, release.
Mobility Functions for UEs in EMM-CONNECTED:
• Intra-LTE Handover
• Inter-3GPP-RAT Handover.
S1 Paging function
NAS Signalling Transport function
S1-interface management functions
• Error indication and Reset
Initial Context Setup Function
• supports the establishment of the necessary overall initial
UE Context in the eNB to enable fast Idle-to-Active
transition.
17
Architecture

MME / S-GW MME / S-GW

S1

S1
X2 S1
S1

eNB eNB E-UTRAN

X2

X2

eNB
18
The X2 control plane interface (X2-CP)
• The transport network layer is built on SCTP on
top of IP.
• The application layer signalling protocol is
referred to as X2-AP (X2 Application Protocol).
Functions
• Intra LTE-Access-System Mobility Support for UE
in EMM-CONNECTED:
- Context transfer from source eNB to target eNB;
- Control of user plane tunnels between source
eNB and target eNB;
- Handover cancellation.
• Uplink Load Management;
• General X2 management and error handling
functions:
- Error indication.

19
X2 user plane interface (X2-U)
• The X2-U interface provides non
guaranteed delivery of user plane
PDUs between eNBs.
• The transport network layer is built
on IP transport and GTP-U is used
on top of UDP/IP to carry the user
plane PDUs.
The X2-U interface protocol stack is
identical to the S1-U protocol stack.

20
The physical layer performs the following main functions:
• Error detection on transport channel;
• Support for Hybrid ARQ;
• Power weighting;
• Physical channel modulation/demodulation & link adaptation;
• Frequency and time synchronization;
• Physical layer mapping;
• Support for handover
• Support for multi-stream transmission and reception (MIMO)

21
Downlink: OFDM/OFDMA
Uplink: SC-FDMA (Single Carrier-Frequency Division
Multiple Access)

22
Layer 2 is split into
the following
sublayers:
• Medium Access
Control (MAC)
• Radio Link
Control (RLC)
• Packet Data
Convergence
Protocol (PDCP)

23
The main service and functions include:
• Transfer of upper layer PDUs supporting Acknowledged
Mode (AM) or Unacknowledged Mode (UM);
- The UM mode is suitable for transport of Real Time (RT)
services because such services are delay sensitive and
cannot wait for retransmissions.
- The AM mode, on the other hand, is appropriate for non-RT
(NRT) services such as file downloads.
• Transparent Mode (TM) data transfer;
- The TM mode is used when the PDU sizes are known a priori
such as for broadcasting system information.
• Error Correction through ARQ
- CRC check provided by the physical layer; no CRC needed at
RLC level

24
• Segmentation according to the size of the TB:
- only if an RLC SDU does not fit entirely into the TB
- then the RLC SDU is segmented into variable sized RLC PDUs,
which do not include any padding;
• Re-segmentation of PDUs that need to be retransmitted
- if a retransmitted PDU does not fit entirely into the new TB
used for retransmission then the RLC PDU is re-segmented
• Concatenation of SDUs for the same radio bearer;
• In-sequence delivery of upper layer PDUs except at HO;
• Duplicate Detection;
• Protocol error detection and recovery;
• SDU discard;

25
A red dotted line indicates the occurrence of
segmentation

RLC SDU n n+1 n+2 n+3

RLC header

RLC PDU

26
 Logical channels
(characterized by the
information that is transferred)

Control channels Traffic channels

(carry control plane info) (carry uer plane info)

Broadcast Control Paging Control Multicast Control Multicast Traffic

Channel (BCCH) Channel (PCCH) Channel (MCCH) Channel (MTCH)
(DL channel for (DL channel for (DL p2m channel for (DL p2m channel for
broadcasting system transfering paging) transmitting MBMS transmission of MBMS
control info) control info data)

Common Control Dedicated Control Dedicated Traffic

Channel (CCCH) Channel (DCCH) Channel (DTCH)
(UL channel for (p2p channel bidirectional (Bidirectional channel
transmitting control info channel for exchanging dedicated to single UE)
and used by UE without control information and used
RRC connection) by Ues with RRC connection
27
The main services and functions include:
• Mapping between logical channels and transport channels;
• Multiplexing/demultiplexing of RLC PDUs belonging to one
or different radio bearers into/from transport blocks (TB)
delivered to/from the physical layer on transport channels;
• Traffic volume measurement reporting;
• Error correction through HARQ;
• Priority handling between logical channels of one UE;
• Priority handling between UEs by means of dynamic
scheduling;
• Transport format selection;
• Padding.

28
 Transport channels
(characterized by how the data is
transferred over radio interface)

Downlink channels Uplink channels

Broadcast Paging Uplink Shared Random Access

Control (BCH) Channel (PCH) Channel (UL-SCH) Channel (RACH)
(fixed transport (required to be (HARQ, dynamic link (limited control
format) broadcast) adaptation, support for UE information, collision
DRX, dynamic and semi- risk)
Downlink Shared Multicast static resource allocation)
Channel (DL-SCH) Channel (MCH)
(HARQ, dynamic link (support for SFN
adaptation, support for UE combining and
DRX, dynamic and semi- semi-static resource
static resource allocation) allocation)

29
 CCCH DCCH DTCH
Difference Uplink
Logical channels
• No dedicated transport
channel
- CTCH of UTRAN is not required

• All data broadcast in on Uplink

MBMS and on MTCH RACH UL-SCH
Transport channels

PCCH BCCH CCCH DCCH DTCH MCCH MTCH

Downlink
Logical channels

Downlink
Transport channels
PCH BCH DL-SCH MCH
30
31
DL-SCH and UL-SCH
• time-frequency resources are dynamically shared between
users in both uplink and downlink
Downlink Scheduling
• Dynamically determine, in each 1 ms interval, which terminal(s)
that are supposed to receive DL-SCH transmission and on what
resources.
- Resource block is a unit spanning 180kHz in the frequency domain
• Responsible for selecting
- Transport-block size, Modulation scheme, and Antenna mapping
Channel-dependent scheduling
• Channel Quality Indicator (CQI)
• All mobile terminals in the cell observe the same reference
signals transmitted by the eNodeB

32
Uplink Scheduling
• ENodeB
- Assings the time-frequency resources to mobile terminal
- Controls the TF the mobile terminal shall use
- No outband control signaling
• Mobile Terminal
- Selects from which radio bearer the data is taken
– Logical channel multiplexing
Estimating the uplink channel quality
• require a sounding reference signal transmitted from each
mobile terminal for which the eNodeB wants to estimate
the uplink channel quality
- overhead.

33
Transport Block (TB)
• In each Transmission Time Interval (TTI), at most one transport
block of a certain size is transmitted over the radio interface
Transport Format (TF)
• specifies how the TB is to be transmitted over the radio
interface.
• information about the transport-block size
• modulation scheme
• antenna mapping.
Rate control
• Transport-format selection.
- By varying the transport format, the MAC layer can thus realize
different data rates.

34
Principles
• N-process Stop-And-Wait HARQ is used to transmit
and retransmit TB
• Upon reception of a TB, the receiver makes an
attempt to decode the TB and informs the transmitter
about the outcome of the decoding operation
through a single ACK/NAK bit
- indicating whether the decoding was successful or if a
retransmission of the transport block is required.
Downlink: DL-SCH
• Asynchronous adaptive HARQ
- the retransmissions are scheduled similarly to the
initial transmissions.
35
Uplink: UL-SCH
• Synchronous HARQ;
- the time instant for the retransmissions is fixed once the
initial transmission has been scheduled
• Maximum number of retransmissions configured per UE

Combination with RLC ARQ

• Small round trip time and low overhead

36
The main service and functions for User plane
• Header compression/decompression: ROHC
• Transmission and Retransmission of user data
• In-sequence delivery of upper layer PDU at HO for RLC AM
• Duplicate detection of lower layer SDUs
• Ciphering of user plane data and control plane data
• Integrity protection of control plane data
User Plane Control Plane

SAE Bearers NAS Signalling

PDCP
Integrity
ROHC ROHC
Protection

Ciphering Ciphering Ciphering Ciphering

ROHC: Robust Header Compression 37

for Downlink Data

38
The main services and functions include:
• Broadcast of System Information related to the NAS
• Broadcast of System Information related to the AS
• Paging
• Establishment, maintenance and release of an RRC
connection between the UE and the E-UTRAN
• Security Function: key management
• Establishment, maintenance and release of point to point
Radio bearers
• Mobility functions
• Establishment, configuration, maintenance and release of
Radio Bearers for MBMS services
• QoS management functions

39
RRC_IDLE
• PLMN selection
• UE specific DRX configured by NAS
• Broadcast of system information
• Paging
• Cell re-selection mobility
• The UE shall have been allocated an id which uniquely
identifies the UE in a tracking area
• No RRC context stored in the eNB
• UE keeps its IP address in order to rapidly move to
LTE_ACTIVE when necessary
40
RRC_CONNECTED
• UE has an E-UTRAN-RRC connection
• UE has context in E-UTRAN
• E-UTRAN knows which the cell belong to
• Network can transmit and/or receive data from/to UE
• Network controlled mobility
• Neighbor cell measurements
• At PDCP/RLC/MAC level:
- Data transmission and/or reception to/from network
- control signalling channel monitoring in UE
- Channel quality report in UE
- DRX period configuration in eNB
41
LTE_IDLE:
• RRC_IDLE State
• mobile terminal sleeps most of the time in order to reduce
battery consumption.
LTE_ACTIVE:
• Mobile terminal is active with transmitting and receiving
data
• IP address and Cell Radio-Network Temporary Identifier
(C-RNTI) assignments
• RRC_CONNECTED state
• IN_SYNC: uplink is synchronized
• OUT_OF_SYNC: uplink is not synchronized
42
LTE_DETACHED:
• No RRC entity

43
 LTE
DEATTACH
LTE
RRC IDLE RRC IDLE DEATTACH
UE Evolved MME/UPE Old Inter AS HSS
RAN MME/UPE Anchor

1. Network Discovery and

Access System Selection RRC
RRC CONNECTED
CONNECTED 2. Attach Request 3. Send old registration
information

4. Send user information

5. Authentication

6. Register MME

7. Delete UE registration information

8. Confirm Registration

9. Selection of Intersystem
Mobility Anchor GW

10. User Plane Route Configuration

LTE 11. Configure IP LTE

DEATTACH Bearer QoS
ACTIVE

12. Attach Accept

LTE ACTIVE

13. Attach Confirm

44
Intra E-UTRAN
• Mobility Management in ECM-IDLE
• Mobility Management in ECM-CONNECTED
Example
• Intra-MME/Serving Gateway HO Procedure
- The HO procedure is performed without EPC
involvement, i.e. preparation messages are directly
exchanged between the eNBs.
- The release of the resources at the source side during
the HO completion phase is triggered by the eNB.

45
 UE Source eNB Target eNB MME Serving Gateway

0. Area Restriction Provided

1. Measurement Control

packet data packet data

UL allocation Legend

L3 signalling
2. Measurement Reports
L1/L2 signalling
3. HO decision
User Data
4. Handover Request

Handover Preparation
5. Admission Control
6. Handover Request Ack
DL allocation
RRC Conn. Reconf. incl.
7.
mobilityControlinformation
Detach from old cell
Deliver buffered and in transit
and
packets to target eNB
synchronize to new cell

Handover Execution
8. SN Status Transfer

Data Forwarding

Buffer packets from

Source eNB
9. Synchronisation

10. UL allocation + TA for UE

11. RRC Conn. Reconf. Complete

packet data
packet data
12. Path Switch Request
13. User Plane update
request

End Marker
14. Switch DL path

Handover Completion
packet data
End Marker
15.User Plane update
response
16.Path Switch Request Ack

17. UE Context Release

18. Release
Resources

46
0 The UE context within the source eNB contains information regarding roaming restrictions which where
provided either at connection establishment or at the last TA update.
1 The source eNB configures the UE measurement procedures according to the area restriction information.
Measurements provided by the source eNB may assist the function controlling the UE's connection mobility.
2 UE is triggered to send MEASUREMENT REPORT by the rules set by i.e. system information, specification etc.
3 Source eNB makes decision based on MEASUREMENT REPORT and RRM information to hand off UE.
4 The source eNB issues a HANDOVER REQUEST message to the target eNB passing necessary information to
prepare the HO at the target side (UE X2 signalling context reference at source eNB, UE S1 EPC signalling context
reference, target cell ID, KeNB*, RRC context including the C-RNTI of the UE in the source eNB, AS-configuration,
E-RAB context and physical layer ID of the source cell + MAC for possible RLF recovery). UE X2 / UE S1 signalling
references enable the target eNB to address the source eNB and the EPC. The E-RAB context includes necessary
RNL and TNL addressing information, and QoS profiles of the E-RABs.
5 Admission Control may be performed by the target eNB dependent on the received E-RAB QoS information to
increase the likelihood of a successful HO, if the resources can be granted by target eNB. The target eNB
configures the required resources according to the received E-RAB QoS information and reserves a C-RNTI and
optionally a RACH preamble. The AS-configuration to be used in the target cell can either be specified
independently (i.e. an "establishment") or as a delta compared to the AS-configuration used in the source cell
(i.e. a "reconfiguration").
6 Target eNB prepares HO with L1/L2 and sends the HANDOVER REQUEST ACKNOWLEDGE to the source eNB.
The HANDOVER REQUEST ACKNOWLEDGE message includes a transparent container to be sent to the UE as an
RRC message to perform the handover. The container includes a new C-RNTI, target eNB security algorithm
identifiers for the selected security algorithms, may include a dedicated RACH preamble, and possibly some
other parameters i.e. access parameters, SIBs, etc. The HANDOVER REQUEST ACKNOWLEDGE message may also
include RNL/TNL information for the forwarding tunnels, if necessary. 47
7 The target eNB generates the RRC message to perform the handover, i.e
RRCConnectionReconfiguration message including the mobilityControlInformation, to be sent by
the source eNB towards the UE. The source eNB performs the necessary integrity protection and
ciphering of the message. The UE receives the RRCConnectionReconfiguration message with
necessary parameters (i.e. new C-RNTI, target eNB security algorithm identifiers, and optionally
dedicated RACH preamble, target eNB SIBs, etc.) and is commanded by the source eNB to
perform the HO. The UE does not need to delay the handover execution for delivering the
HARQ/ARQ responses to source eNB.
8 The source eNB sends the SN STATUS TRANSFER message to the target eNB to convey the
uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of E-RABs for which
PDCP status preservation applies (i.e. for RLC AM). The uplink PDCP SN receiver status includes at
least the PDCP SN of the first missing UL SDU and may include a bit map of the receive status of
the out of sequence UL SDUs that the UE needs to retransmit in the target cell, if there are any
such SDUs. The downlink PDCP SN transmitter status indicates the next PDCP SN that the target
eNB shall assign to new SDUs, not having a PDCP SN yet. The source eNB may omit sending this
message if none of the E-RABs of the UE shall be treated with PDCP status preservation.
9 After receiving the RRCConnectionReconfiguration message including the
mobilityControlInformation , UE performs synchronisation to target eNB and accesses the target
cell via RACH, following a contention-free procedure if a dedicated RACH preamble was indicated
in the mobilityControlInformation, or following a contention-based procedure if no dedicated
preamble was indicated. UE derives target eNB specific keys and configures the selected security
algorithms to be used in the target cell.
10 The target eNB responds with UL allocation and timing advance.

48
11 When the UE has successfully accessed the target cell, the UE sends the
RRCConnectionReconfigurationComplete message (C-RNTI) to confirm the handover, along with
an uplink Buffer Status Report, whenever possible, to the target eNB to indicate that the
handover procedure is completed for the UE. The target eNB verifies the C-RNTI sent in the
RRCConnectionReconfigurationComplete message. The target eNB can now begin sending data to
the UE.
12 The target eNB sends a PATH SWITCH message to MME to inform that the UE has changed
cell.
13 The MME sends an UPDATE USER PLANE REQUEST message to the Serving Gateway.
14 The Serving Gateway switches the downlink data path to the target side. The Serving gateway
sends one or more "end marker" packets on the old path to the source eNB and then can release
any U-plane/TNL resources towards the source eNB.
15 Serving Gateway sends an UPDATE USER PLANE RESPONSE message to MME.
16 The MME confirms the PATH SWITCH message with the PATH SWITCH ACKNOWLEDGE
message.
17 By sending UE CONTEXT RELEASE, the target eNB informs success of HO to source eNB and
triggers the release of resources by the source eNB. The target eNB sends this message after the
PATH SWITCH ACKNOWLEDGE message is received from the MME.
18 Upon reception of the UE CONTEXT RELEASE message, the source eNB can release radio and C-
plane related resources associated to the UE context. Any ongoing data forwarding may
continue.

49
Simultaneous, tightly integrated, and efficiently
provisioning of unicast and MBMS services.
• MBMS can be provided on a set of cells dedicated to
MBMS transmission and/or on a set of cells
supporting both unicast and MBMS transmissions
MBMS transmission from several eNBs may be
coordinated

50
 MBMS
GW
|

M3
MBMS GW: MBMS Gateway
MCE: Multi-Cell/Multicast Coordination Entity
MCE M1
|

M1: user plane interface

M2: E-UTRAN internal control plane interface
M3: control plane interface between E-UTRAN and EPC
M2
|

eNB

51
Multi-cell/multicast Coordination Entity (MCE)
• Allocation of the radio resources used by all eNBs in the
MBSFN area for multi-cell MBMS transmissions using
MBSFN operation.
• decides the further details of the radio configuration
- modulation and coding scheme.
• Is involved in MBMS Session Control Signalling.
E-MBMS Gateway (MBMS GW)
• sending/broadcasting of MBMS packets with the SYNC
protocol to each eNB transmitting the service.
• uses IP Multicast as the means of forwarding MBMS user
data to the eNB.
• performs MBMS Session Control Signalling (Session
start/stop) towards the eUTRAN.
52
 DL-SCH

DL-SCH
MCH or

MCH or
MC H

MC H
MC H

MC H
single cell
single cell
multicell transmission mutlicell transmission transmission
transmission
on MCH on MCH on MCH or DL-SCH
on MCH or DL-SCH
from mixed cells from MBMS dedicated cells from MBMS dedicated
from a mixed cell
cell

53
Radio Bearer Control (RBC)
• The establishment, maintenance and release of Radio
Bearers involve the configuration of radio resources
associated with them.
• Considerations
- Overall resource situation in EUTRAN,
- QoS requirements of in-progress sessions
- QoS requirement for the new service
Radio Admission Control (RAC)
• Admit or reject the establishment requests for new radio
bearers.
• Ensure high radio resource utilization and at the same
time to ensure proper QoS for in-progress sessions

54
Connection Mobility Control (CMC)
• Management of radio resources in connection with idle or
connected mode mobility.
• In idle mode
- the cell reselection algorithms are controlled by setting of
parameters that define the best cell and/or determine when
the UE should select a new cell.
- E-UTRAN broadcasts parameters that configure the UE
measurement and reporting procedures.
• In connected mode,
- the mobility of radio connections has to be supported.
- Handover decisions may be based on UE and eNB
measurements.

55
Dynamic Resource Allocation (DRA) - Packet Scheduling (PS)
• Allocate and de-allocate resources to user and control plane packets.
• Selection of radio bearers whose packets are to be scheduled and
managing the necessary resources
- QoS requirements associated with the radio bearers,
- Channel quality information for UEs,
- Buffer status,
- Interference situation
Inter-cell Interference Coordination (ICIC)
• Manage radio resources such that inter-cell interference is kept under
control.
• A multi-cell RRM function that needs to take into account information
from multiple cells.
- resource usage status
- traffic load situation

56
Load Balancing (LB)
• Handle uneven distribution of the traffic load over
multiple cells.
• Influence the load distribution in such a manner that radio
resources remain highly utilized
• Result in hand-over or cell reselection decisions
Inter-RAT Radio Resource Management
• Management of radio resources in connection with inter-
RAT mobility,
• The handover decision may take into account the involved
RATs resource situation as well as UE capabilities and
Operator policies.

57
58
• This version of the specification does not support X2 connectivity of HeNBs.
• The S1 interface is defined as the interface:
• Between the HeNB GW and the Core Network,
• Between the HeNB and the HeNB GW,
• Between the HeNB and the Core Network,
• Between the eNB and the Core Network. 59
The HeNB GW appears to the MME as an eNB. The
HeNB GW appears to the HeNB as an MME. The S1
interface between the HeNB and the EPC is the same
whether the HeNB is connected to the EPC via a HeNB
GW or not.
The HeNB GW shall connect to the EPC in a way that
inbound and outbound mobility to cells served by the
HeNB GW shall not necessarily require inter MME
handovers. One HeNB serves only one cell.
The functions supported by the HeNB shall be the same
as those supported by an eNB (with the possible
exception of NNSF) and the procedures run between a
HeNB and the EPC shall be the same as those between
an eNB and the EPC.
60
[1] 3GPP. GPRS enhancements for E-UTRAN access. 3GPP TS 23.401 v8.0.0 2007-12
[2] 3GPP. Architecture enhancements for non-3GPP accesses. 3GPP TS 23.402 v8.0.0
2007-12
[3] 3GPP. 3GPP SAE: Report on technical options and conclusions. 3GPP TR 23.882
v1.4.2, 2006-10
[4] 3GPP. 3GPP SAE: CT WG1 aspects. 3GPP TR 24.801 v0.5.1, 2007-12
[5] 3GPP. E-UTRA and E-UTRAN; Radio interface protocol aspects. 3GPP TR 25.813
v7.1.0, 2006-10
[6] 3GPP. Feasibility study for evolved UTRA and UTRAN. 3GPP TR 25.912 v7.1.0,
2006-10
[7] 3GPP. Requirements for E-UTRA and E-UTRAN. 3GPP TR 25.913 v7.1.0, 2006-10
[8] 3GPP. 3GPP SAE: CT WG4 aspects. 3GPP TR 29.803 v0.5.0, 2007-11
[9] 3GPP. 3GPP SAE: CT WG3 aspects. 3GPP TR 29.804 v0.3.0, 2007-11
[10] 3GPP. E-UTRA and E-UTRAN; Overall description; 3GPP TS 36.300 v8.3.0
2007-12
[11] Hannes, E., Adners, F., Jonas, K., Michael, M., Stefan, P., Johan, T., and Mattias,
W., Technical Solutions for the 3G Long Term Evolution, IEEE Communication
Magazine, March 2006.

61