Radio Resource Management: LTE Air Interface Course

Radio Resource Management
LTE Air Interface Course
1 Nokia Siemens Networks

RRM in eNodeB
Radio Admision Control
Scheduling
Link Quality Control
Adaptive Modulation and Coding
Modulation and Transport Block Size
Outer Link Quality Control
Power Control
Handover Control
Discontinous Transmission (DTX)
Differences with UMTS RRM

Scope of RRM
Scope of RRM:
Management and optimized utilization of the (scarce) radio resources:
Provision for each service/bearer/user an adequate QoS (if applicable)
Increasing the overall radio network capacity and optimizing quality
RRM is located in eNodeB eNB
See next slide
X2
LTE-Uu
Evolved Node B
(eNB)
LTE-UE
Evolved Node B (eNB)
eNB Functions
Inter-cell RRM: HO, load balancing between cells
Radio Bearer Control: setup , modifications and

release of Radio Resources Only network element defined as part of
eUTRAN
Connection Mgt. Control: UE State Management,
Replaces the old Node B / RNC
MME-UE Connection
combination from 3G.
Radio Admission Control
Provides all radio management functions
eNode B Meas. collection and evaluation To enable efficient inter-cell radio
management for cells not attached to the
Dynamic Resource Allocation (Scheduler)
same eNB, there is a inter-eNB interface
IP Header Compression/ de-compression X2 specified. It will allow to coordinate
inter-eNB handovers without direct
Access Layer Security: ciphering and integrity involvement of EPC during this process.
protection on the radio interface
MME Selection at Attach of the UE

User Data Routing to the S-GW/ P-GW
Transmission of Paging Msg coming from MME
Transmission of Broadcast Info (e.g. System info,
MBMS)
5 Nokia Siemens Networks Presentation / Author / Date
RRM in eNodeB
Scheduling
Power Control
Handover Control

Radio Admission Control ( RAC)
Objective: To admit or to reject the requests for establishment of Radio Bearers (RB) on a
cell basis
Based on number of RRC connections and number of active users per cell
Non QoS aware
Operator configures both max. number of established RRC connections and max. number
of active users per cell by O&M threshold
RRC connection is established when the SRBs have been admitted and successfully
configured
UE is considered as active when Radio bearer is established
Upper bound for maximum number of supported connections depends on the BB
configuration of eNB
RL T: All RRC connection setup request are admitted by default to avoid RAC complexity
Improvement in RL10: Possibility of giving priority to the HO cases based on the HO
cause

RRM in eNodeB
Scheduling
Power Control
Handover Control

LTE vs. R99 Scheduling
NodeB Rel. 99 eNodeB LTE
Dedicated pipe for every UE Fast pipe is shared among UEs
Channel quality
time/frequency/space

Fast Fading in Time and Frequency Domain
S f
20 dB
50
30
1MHz
10
10 cm
-10
0 0.1 0.2 0.3 0.4 0.5 0.6 r
0.7

Scheduler Types
A variety of scheduling strategies is available. The scheduling strategy is based on a certain metric.
Examples are:
- Round-Robin
No quality indication is taken into consideration. The resources are mainly shared in an equal manner.
- Max C/I.
The UE with the best channel conditions gets the highest priority. The cell throughput is maximised.
Starvation of UEs with channels of low quality may be a disadvantage.
- Proportional Fair.
This algorithm defines priorities based on the quality and the averaged scheduled rate.
- QoS
Different strategies exist to get QoS related information integrated.
E.g. Depending on the priority of the service and/or the UE, RT/NRT service type. a scheduling weight
can be introduced.
Combinations of the different types can also be applied.

Example: Proportional Fair Scheduling

Downlink Scheduler
Algorithm
Start
Determine which PRBs are available (free) and Evaluation of available resources (PRBs/RBGs)
can be allocated to UEs for dynamic allocation on PDSCH
Allocate PRBs needed for common channels like

SIB, paging, and random access procedure (RAP) Resource allocation and scheduling
for common channels
Final allocation of UEs (bearers) onto PRB.

Considering only the PRBs available after the DL scheduling of UEs:
Scheduling of UEs/bearers to PRBs/RBGs
previous steps
Pre-Scheduling: All UEs with data available for End
transmission based on the buffer fill levels

Start
Time Domain Scheduling: Parameter MAX- Pre-Scheduling:
#_UE_DL decides how many UEs are allocated Select UEs eligible for scheduling
in the TTI being scheduled -> Determination of Candidate Set 1
Frequency Domain Scheduling for Candidate Time domain scheduling

of UEs according to simple criteria
Set 2 UEs: Resource allocation in Frequency -> Determination of Candidate Set 2
Domain including number and location of Frequency domain scheduling
allocated PRBs of UEs/bearers
-> PRB/RBG allocation to UEs/bearers
End

Uplink Scheduler
Channel Unaware
Time domain: a) b)
Evaluation of the #PRBs that will be
assigned to UEs
Available number of PRBs per user
Multiple of 2, 3 or 5
Max. # of UEs which can be scheduled per
TTI time frame is restricted by an O&M
parameter. RL T and RL10 limit the
number to a max. of 10 UEs per TTI
Example of allocation in frequency domain:

Frequency Domain:
Full Allocation: All available PRBs are
Uses a random function to assure equal assigned to the UEs scheduled per TTI
distribution of PRBs over the available
frequency range ( random frequency
hopping) Fractional: Not all PRBs are assigned,
still the hoping function handles the
unassigned PRB as if they were
allocated to keep the equal distribution
per TTI
RRM in eNodeB
Scheduling
Power Control
Handover Control

Link Adaptation by AMC (UL/DL)
Motivation of link adaptation: Modify the signal transmitted to and by a particular user
according to the signal quality variation to improve the system capacity and coverage
reliability.
If SINR is good then higher MCS can be used -> more bits per byte -> more
throughput.
If SINR is bad then lower MCS should be use ( more robust)
Flexi Multimode BTS performs the link adaptation for DL and UL on a TTI basis
The selection of the modulation and the channel coding rate is based:
Downlink data channel: CQI report from UE
Downlink common channel (PDCCH): signaling payload, CQI report
Uplink: BLER measurements in Flexi LTE BTS

PDSCH AMC Algorithm
START
Retrieve Default MCS
Dynamic AMC
active?
HARQ
retransmission?
Determine avaraged CQI Use the same MCS as for

Use Default MCS
value for allocated PRBs initial transmission
Determine MCS
END

RRM in eNodeB
Scheduling
Power Control
Handover Control

Modulation and TB Size
Modulation and Coding Scheme (MCS)

3GPP TS 36.211 specifies QPSK, 16QAM and 64QAM for the Physical
Downlink/Uplink Shared Channel
Affects the amount of resources that will be used for user data
Transport Block Set (TBS)

Number of user data bits transmitted to single user during one TTI (1ms)
The TB occupies two resource blocks in time domain
3GPP TS 36.213 specifies tables to:

link the MCS Index -> Modulation Order (modulation type) and TBS Index
link the TBS Index -> Transport Block Size (TBS) for a specific number of Physical
Resource Blocks (PRB)
The exact maping is shown in the next slides

DL MCSs
MCS ITBS MCS_index Mod order
From TS 36.213 (DL example shown here)
0-QPSK 0 0 2
1-QPSK 1 1 2
2-QPSK 2 2 2 MCS index -> from 0 to 28 -> it is decided by the
3-QPSK 3 3 2
4-QPSK 4 4 2
scheduler which should translate a specific CQI in an
5-QPSK 5 5 2 MCS index
6-QPSK 6 6 2
7-QPSK 7 7 2
8-QPSK 8 8 2
9-QPSK 9 9 2
Modulation Order -> indicates the modulation type
10-16QAM 9 10 4 (QPSK, ) by indicating the number of bits per
11-16QAM 10 11 4 symbol
12-16QAM 11 12 4
13-16QAM 12 13 4 QPSK = 2
14-16QAM 13 14 4
15-16QAM 14 15 4 16QAM = 4
16-16QAM 15 16 4
17-64QAM 15 17 6
64QAM = 6
18-64QAM 16 18 6
19-64QAM 17 19 6
20-64QAM 18 20 6 ITBS = TBS index
21-64QAM 19 21 6
22-64QAM 20 22 6 The TBS Index is mapped to a specific TBS size for a
23-64QAM 21 23 6 specific #RBs
24-64QAM 22 24 6
25-64QAM 23 25 6 Uses a different table
26-64QAM 24 26 6
27-64QAM 25 27 6
-> See next slide
28-64QAM 26 28 6

Example of mapping (DL-SCH) ITBS to a TBS size for a specific number of RBs (1..12 in this
example)

a) code rate vs MCS and b) code rate vs number of PRBs
120 100
90
100
80
70
80
code rate / %
60
code rate / %
60 50
40
40
30
20
20
10
0 0
0 5 10 15 20 25 30 0 10 20 30 40 50 60 70 80 90 100 110
MCS index number of PRBs
a) Examples for b) Examples for

- 2 symbols for signalling (dashed) - MCS = 28
- 3 symbols for signalling (solid) - MCS = 14
- NPRB=8 - MCS = 0 constant:
- 2 symbols for signalling - two antenna ports
- single transport block case
RRM in eNodeB
Scheduling
Power Control
Handover Control

Outer Link Quality Control (OLQC)
Feature: CQI Adaptation ( DL)

Only used in DL
Used for CQI measurement error compensation
CQI estimation error of the UE
CQI quantization error or
CQI reporting error
It adds a CQI offset to the CQI reports provided by UE. The corrected CQI report is provided
to the DL Link adaptation for further processing
CQI offset derived from ACK/NACK feedback

RRM in eNodeB
Scheduling
Power Control
Handover Control

Power Control Principle
The transmission power is adapted in order to achieve the desired QoS (BLER/BER).
This adaptation is necessary since the propagation channel is subject to several conditions, which generally vary in
space and/or time, e.g.
path loss
log normal fading
short term fading
UE speed
location (outdoor, indoor, in-car) etc.
Downlink power control determines the energy per resource element (EPRE). The term resource element energy
denotes the energy prior to CP insertion. The term resource element energy also denotes the average energy taken
over all constellation points for the modulation scheme applied.
Uplink power control determines the average power over a DFT-SOFDM symbol in which the physical channel is
transmitted. In contrast to UTRAN based on WCDMA however the requirements for UL power control are more
relaxed as a similar near-far problem of UTRAN does not exist. Compared with UTRAN the UL power control is
slower. The PUSCH and the PUCCH are subject to a combined open and closed loop power control algorithm, i.e.
to control the transmission power for UL channels a combination of an open (input: pathloss, sysinfo and signaling)
and a closed loop (TPC) method is used.
A cell wide overload indicator (OI) and a High Interference Indicator (HII) to control UL interference are exchanged over
X2. An indication is given which PRBs an eNodeB scheduler allocates to cell edge UEs and hence will be most
sensitive to inter-cell interference.
Power Control Principle
Ve Low
ry
lo
w
High
Very
high

DL Power Assignment Example
0 1 2 3 4 5 6
t

UL Power Control
Procedure for Slow UL Power control
UE controls the Tx power to keep the transmitted power spectral density (PSD)
constant independent of the allocated transmit bandwidth (#PRBs)
If no feedback from eNodeB ( in the PDCCH UL PC command) the UE performs open

loop PC based on path loss measurements
If feedback from eNodeB the UE corrects the PSD when receiving PC commands from
eNodeB ( in the PDCCH UL PC command)
PC commands ( up and down) based on UL quality and signal level measurements
Applied separately for PUSCH, PUCCH

Scope of UL PC is UE level ( performed separately for each UL in a cell)
2) SINR measurment
4) TX power level
3) Setting new power offset
adjustment with the new
offset
1) Initial TX power level

RRM in eNodeB
Scheduling
Power Control
Handover Control

Handover Types
other RAT
intersystem HO
3 intersystem HO
triggered by other RAT 2
triggered by e.g.
- coverage of E-UMTS
E-UMTS macro cell - service
- load
interfrequency HO
1b
E-UMTS micro cells
1a
Intra-frequency HO intra-frequency HO
(intra eNB) (inter eNB, inter MME)

Handover Principles
-> Lossless
Packets are forwarded from the source to the target
-> Network-controlled
Target cell is selected by the network, not by the UE
Handover control in E-UTRAN (not in packet core)
-> UE-assisted
Measurements are made and reported by the UE to the network
-> Late path switch

Only once the handover is successful, the packet core is involved

Handover Algorithm
A Handover will be initiated by a measurement report, which is sent via the Radio
Resource Control (RRC) protocol. Upon the reception of this measurement
report, the handover algorithm will decide whether a handover should take place.
In response to the handover decision, the handover execution will be carried out
using the corresponding procedures. After the handover execution, the handover
algorithm will be informed, whether the handover was successful or not.
The Handover procedure is composed of a number of single functions:

Measurements
Filtering of measurements
Reporting of measurement results
Hard handover algorithm
Execution of handover

Handover Procedure
Before Handover Late path
Radio handover
handover preparation switching
S-GW + P-GW S-GW + P- S-GW + P-GW S-GW + P-GW
GW
MME MME MME MME
Target
Source eNB
eNB X2
= Data in radio = S1 signalling

= Signalling in radio = X2 signalling
= GTP tunnel
= GTP signalling
Handover Preparation
1. The source eNB configures the
UE measurement procedures UE Source Target MME GW
with MEASUREMENT
CONTROL
2. UE is triggered to send
MEASUREMENT REPORT to 1. Measurement control
the source eNB. It can be event
triggered or periodic 2. Measurement report
3. Source eNB makes handover
decision based on UE report + 3. HO
load and service information decision
4. The source eNB issues a 4. HO request

HANDOVER REQUEST to the
target eNB 5.
Admission
5. Target eNB performs admission control
control 6. HO request ack.
6. Target eNB sends the
HANDOVER REQUEST
ACKNOWLEDGE to the source
eNB
Handover Execution
7. Source eNB generates the
HANDOVER COMMAND towards
UE UE Source Target MME GW
Source eNB starts forwarding packets to
target eNB
8. Source eNB sends status information
to target eNB 7. HO command
9. UE performs the final Forward
packets to
synchronisation to target eNB and target
accesses the cell via RACH
8. Status transfer
procedure
Buffer
DL pre-synchronisation is obtained packets
during cell identification and from
measurements source
9. Synchronization
10. Target eNB gives the uplink
allocation and timing advance 10. UL allocation and timing
information advance
11. UE sends HANDOVER CONFIRM 11. Handover confirm
to target eNB
Target eNB can begin to send data to UE
Handover Completion
12.Target eNB sends a PATH SWITCH
message to MME to inform that the UE
has changed cell UE Source Target MME GW
13.MME sends a USER PLANE UPDATE
REQUEST message to Serving Gateway
14.Serving Gateway switches the downlink
data path to the target side 12. Path switch request
15.Serving Gateway sends a USER PLANE 13. User plane update

UPDATE RESPONSE message to MME request
14.
16.MME confirms the PATH SWITCH Switch
message with the PATH SWITCH ACK downlin
k path
message
17.By sending RELEASE RESOURCE the 15. User plane
target eNB informs success of handover update response
to source eNB and triggers the release of 16. Path switch request
resources 17. Releaseack.
resources
18.Upon reception of the RELEASE
RESOURCE message, the source eNB 18.
Release
can release radio and C-plane related resources
resources associated to the UE context
RRM in eNodeB
Scheduling
Power Control
Handover Control

Discontinuous Transmission in DL (DTX)
Sleep periods needed for mobiles in RRC Connected Mode to save UE battery
power
Basic idea UE is not monitoring PDCCH in some specified subframes and it

sleeps:
ON period to be defined (UE active and monitoring PDCCH)
OFF period (UE sleeping not monitoring PDCCH)
The ON/OFF periods should be set-up in such way to maintain the QoS (latency) of
the application
Example web browsing: ON period = 1 ms (1 subframe)
OFF period 100 ms (100 subframes)
DTX is configured via higher layer parameters

RRM in eNodeB
Scheduling
Power Control
Handover Control

Differences with RRM WCDMA:
Softer and Soft handovers are not supported by the LTE system
LTE requirements on power control are much less stringent due to the different
nature of LTE radio interface i.e. OFDMA (WCDMA requires fast power control to
address the Near-Far problem and intra-frequency interferences)
On the other hand LTE system requires much more stringent timing
synchronization for OFDMA signals.

Radio Resource Management: LTE Air Interface Course

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Radio Resource Management: LTE Air Interface Course

Uploaded by

Copyright:

Available Formats

Radio Resource Management

LTE Air Interface Course

1 Nokia Siemens Networks

3 Nokia Siemens Networks

RRM is located in eNodeB eNB

See next slide

Radio Bearer Control: setup , modifications and

MME Selection at Attach of the UE

6 Nokia Siemens Networks

7 Nokia Siemens Networks Presentation / Author / Date

8 Nokia Siemens Networks

NodeB Rel. 99 eNodeB LTE

Dedicated pipe for every UE Fast pipe is shared among UEs

9 Nokia Siemens Networks

10 Nokia Siemens Networks

Combinations of the different types can also be applied.

11 Nokia Siemens Networks

12 Nokia Siemens Networks

Allocate PRBs needed for common channels like

Final allocation of UEs (bearers) onto PRB.

transmission based on the buffer fill levels

in the TTI being scheduled -> Determination of Candidate Set 1

Frequency Domain Scheduling for Candidate Time domain scheduling

-> PRB/RBG allocation to UEs/bearers

13 Nokia Siemens Networks Presentation / Author / Date

Example of allocation in frequency domain:

15 Nokia Siemens Networks

16 Nokia Siemens Networks Presentation / Author / Date

Retrieve Default MCS

Determine avaraged CQI Use the same MCS as for

17 Nokia Siemens Networks

18 Nokia Siemens Networks

Modulation and Coding Scheme (MCS)

Transport Block Set (TBS)

3GPP TS 36.213 specifies tables to:

19 Nokia Siemens Networks Presentation / Author / Date

20 Nokia Siemens Networks Presentation / Author / Date

21 Nokia Siemens Networks Presentation / Author / Date

a) Examples for b) Examples for

23 Nokia Siemens Networks

Feature: CQI Adaptation ( DL)

CQI offset derived from ACK/NACK feedback

24 Nokia Siemens Networks Presentation / Author / Date

25 Nokia Siemens Networks

27 Nokia Siemens Networks

28 Nokia Siemens Networks

If no feedback from eNodeB ( in the PDCCH UL PC command) the UE performs open

Applied separately for PUSCH, PUCCH

29 Nokia Siemens Networks Presentation / Author / Date

30 Nokia Siemens Networks

E-UMTS micro cells

31 Nokia Siemens Networks

-> Late path switch

32 Nokia Siemens Networks

The Handover procedure is composed of a number of single functions:

33 Nokia Siemens Networks

= Data in radio = S1 signalling

4. The source eNB issues a 4. HO request

15.Serving Gateway sends a USER PLANE 13. User plane update

38 Nokia Siemens Networks

Basic idea UE is not monitoring PDCCH in some specified subframes and it

DTX is configured via higher layer parameters

39 Nokia Siemens Networks