Professional Documents
Culture Documents
Alcatel-Lucent
Alcatel-Lucent solution for load balancing
End-To-End
between 2G, 3G, LTE and Wifi
JULY 2011
V5.1
CONTENTS
1
INTRODUCTION ................................................................................................ 5
CONCLUSION ................................................................................................. 21
ACRONYMS .................................................................................................... 22
Alcatel-Lucent
LIST OF FIGURES
Figure
Figure
Figure
Figure
Figure
Figure
1:
2:
3:
4:
5:
6:
Alcatel-Lucent
History
Version
Date
Author
Comment
V1.0
29/10/09
Philippe DAUCHY
Document Creation
V2.0
18/11/09
Philippe DAUCHY
Document Update
V3.0
23/11/09
Philippe DAUCHY
Document Update
V4.0
10/12/09
Philippe DAUCHY
Document Update
V5.1
31/07/11
Eric Wu
Document Update
Philip Sapiano
Alcatel-Lucent
INTRODUCTION
LTE is being deployed in the areas where traffic demand justifies the investments. Such areas
are typically already served by 2G and 3G networks. Therefore the result will be a multilayer
network composed of both 2G, 3G and LTE layers, including traditional macro cells as well as
small cells (Metro Cells).
The challenge in a multilayer network is to intelligently distribute the load on the different
available layers to optimize the network resource usage while guaranteeing the quality of
service (QoS) of the different active connections and minimizing unnecessary redirections
between layers.
This is the task of a load balancing solution which aims at handling uneven distribution of the
traffic load over multiple cells. The purpose of load balancing is thus to influence the load
distribution in such a manner that radio resources remain highly utilized and the QoS of inprogress sessions is maintained to the greatest extent possible and call dropping probabilities
are kept sufficiently small. Load balancing algorithms may result in handover or cell
reselection decisions with the purpose of redistributing traffic from highly loaded cells to
under-utilized cells.
Alcatel-Lucent believes that load balancing will play a key role in optimizing radio network
resources and will contribute to a high end user experience while retaining high revenue for
the service provider. Alcatel-Lucent is one of the top three leaders at the 3GPP
standardization body on load balancing related topics.
This document describes the Alcatel-Lucent load balancing solution for optimizing the system
capacity of a multilayer network composed of 2G, 3G and LTE cells. It is structured as follows:
o
Section 2 presents the 3GPP mechanisms relevant for a load balancing solution.
Features related to the load balancing solution are listed in Section Error! Reference source
not found. Annex.
Alcatel-Lucent
STANDARDS PERSPECTIVE
3GPP standards applicable to the load balancing are listed in the table below:
Standard
Specification Description
TS 23.401
TS 36.423
TR 36.902
3GPP release 8 introduced several procedures allowing load balancing between network
elements of the LTE networks:
o
Between eNodeB two procedures are defined to exchange cell load information:
Load Indication and Resource Status Reporting Initiation.
Between eNodeB and MME the standard defines the mechanisms allowing to direct a
UE to an appropriate MME of a given MME pool area to achieve load balancing
between MMEs. This is achieved by setting a weight factor for each MME of the MME
pool area, such that the probability of the eNodeB selecting an MME is proportional to
its weight factor. The weight factor is typically set according to the capacity of an
MME node relative to other MME nodes.
Load balancing between available SGWs can also be performed by the MME when
selecting a given SGW to serve the UE.
3GPP release 9 adds more sophisticated mechanisms to support load balancing in LTE
networks and between LTE and other RATs (e.g. GERAN, UTRAN). 3GPP release 10 will add
mechanisms for heterogeneous networks including small cells, such as enhanced inter-cell
interference coordination.
In this release this document focuses on radio load balancing and will not address MME or SGW
load balancing solutions.
2.1
Alcatel-Lucent
eNodeB1
eNodeB2
Load Indication
Additionally, with 3GPP Release 10, the following may be included in the Load Indication
message:
o
Invoke Indication set to " Almost Blank Subframe (ABS) Information." This indicates the
sending eNB would like the receiving eNB to initiate the Load Indication procedure.
ABS Information. This indicates the subframes designated as almost blank subframes
by the sending eNB for the purpose of interference coordination. The receiving eNB
may take such information into consideration when scheduling UEs.
Radio Resource Status, which indicates the usage of the PRBs in downlink and uplink
(i.e. GBR, non-GBR and total).
S1 Transport Network Layer Indicator, which indicates the status of the S1 transport
network load experienced by the cell (i.e. low load, medium load, high load,
overload).
Hardware Load Indicator which indicates the status of the hardware load experienced
by the cell (i.e. low load, medium load, high load, overload).
With 3GPP Release 10, Almost Blank Subframe Status may be included, which
indicates ABS pattern information.
Alcatel-Lucent
eNodeB1
eNodeB2
2.2
Alcatel-Lucent
RIM signalling
Core Network
MME
SGSN
S3/Gn
RNC
S1
eNodeB
LTE
UTRAN
Iu
A strategy for moving UEs between layers when load reaches a dangerous level and
redirections need to be done. The two pillars of the load balancing solution are the
eMCTA and the self-optimizing approach. However in cases where this is not
sufficient, a strategy for moving UEs between layers will be triggered.
Alcatel-Lucent
This section starts with a description of the eMCTA function. Then the self-optimizing
approach for adjusting mobility parameters is described. To conclude the strategy for moving
UEs between layers is explained.
3.1
Criteria used for the definition of the operator strategy for service allocation on
available carriers
As depicted in Figure 4 the eMCTA will be triggered on specific events and will take decision
regarding the cells to be used to handle the new request. To take its decision the eMCTA uses
cell load information and the operator defined policy describing the traffic allocation to the
different carriers.
Operator policy
Enhanced MCTA
function
Cell to be
used
Event
In the following figure, the eMCTA framework is further explained. During the outgoing
mobility procedures in RRC connected mode, eMCTA process enables the eNB to take the
input Neighbor RAT/Carrier List; applies filters; provides the output Candidate
RAT/Carrier Sorted List as depicted in the following figure. eMCTA provides the most suited
RAT/Carriers candidates towards which radio measurements are configured while other
mobility features launch the most suited mobility procedure upon the corresponding
measurement event.
Alcatel-Lucent
10
The main events that can trigger the eMCTA function are:
o
A Call Admission Control failure during a new radio access bearer establishment.
A mobility procedure.
The result can be a potential redirection or handover of the UE to another layer depending on
load conditions, service type and operator policy.
The eMCTA function is located in each eNodeB. Because the LTE small cell uses the same
software as the LTE macro eNodeB, the eMCTA function is fully supported on the LTE small
cell. Standard 3GPP procedures are used to redirect the UE to other layers (3G or other
LTE carriers). If the 3G network is also provided by Alcatel-Lucent then a consistent load
balancing policy can be defined on the two networks.
3.1.1
Criteria used by eMCTA for the definition of the operator
strategy for service allocation on available carriers
The criteria used for the definition of the operator strategy for service allocation on available
carriers are:
o
Carrier Priority
These criteria are defined at the eUTRAN network management system level.
3.1.1.1
In order to allow different service-based allocation strategies, the carrier priorities are
defined per service type. When the eMCTA function is invoked, the algorithm tries to redirect
the call to the highest priority carrier for the requested service type. If priorities are equal,
then the carrier with the lowest load is selected preferentially. Depending on the rules
configured by the operator the carrier selection can be always done or can be done only if a
given load threshold has been reached in the serving cell.
Alcatel-Lucent
11
LTE
UTRAN
GERAN
VoIP
0 (highest)
N/A
Video
0 (highest)
2 (lowest)
Best Effort
0 (highest)
2 (lowest)
For LTE, service types are based on QoS Class Id (QCI) range defined in 3GPP. They are listed
in the table below (table 6.1.7 Standardized QCI characteristics extracted from TS 23.203).
The service-table provides one priority (value 0/highest-7/lowest) per service-type per
RAT/Carrier (Up to 16). The service-table is the unique entry make the sorting of the
candidate RAT/Carrier list.To be noted that multi-service calls (e.g. audio and video
conferencing) are handled according to the highest service type component.
QCI
Resource
Type
Service Type
Conversational Voice
GBR
IMS signalling
Non-GBR
Cell Load of current and best target cells on other carriers A load-based criterion is defined
for the originating cell and for the best target cells. Today it is foreseen that load of a cell
Alcatel-Lucent
12
will be defined by the concept of cell colour (as already the case in 3G). Three colours will
probably be defined to reflect the cell load; green, yellow and red.
When the serving cell radio resource is congested or in a heavily loaded condition, eMCTA will
trigger mobility behavior to neighbor cells.
The target cell load criterion is a new eMCTA filter. It applies when eMCTA is triggered upon
bad radio conditions, Alarm, preventive load control and reactive load control. A target cell
may have several load information (several IE on X2 and S1). The target load criteria applying
to neighboring cell located on the serving eNB will be based on load information with X2
format.
Based on 3GPP Rel9 definition:
RIM doesnt allow exchanging load information between two eNB which may not have
an X2 interface.
Load information exchanged over X2 may only be done in a periodic mode. Multi cell
reporting may apply. Max period value is 10 sec.
Load information exchange over S1 may only be done in mono reporting mode. Mono
cell reporting applies.
3GPP doesnt define event mode on S1 and X2 in order to refresh load information state.
In the originating cell, the load level is used to define the level of load above which the
eMCTA function is triggered. The originating cell eMCTA can be always triggered (i.e. cell is
green) or can be triggered only if the cell becomes loaded (i.e. cell is yellow) or congested
(i.e. cell is red).
In the target cell, the load level is used to avoid redirection to an overloaded cell.
3.1.2
During the network attachment procedure the MME may provide additional information on the
UE to the eUTRAN. This additional information may include:
o
S1AP CS Fallback Indicator IE, which indicates that fallback to CS domain needs to
be done for voice call.
SRVCC Operation Possible, which indicates that both the UE and MME are SRVCCcapable.
S1AP Handover Restriction List IE, , which may contain roaming, area or access
restrictions.
Alcatel-Lucent
13
The MME may also include the UE History Information IE in each handover request, which
contains information about cells that a UE has been served by in active state prior to the
target cell and in particular the duration of the time the UE stayed in the cell in seconds.
Those criteria can be used to direct the UE to the most appropriate RAT:
o
The UE history information will be used to redirect fast moving UEs to an umbrella
cell to avoid successive handovers.
The Figure 5 provides examples of eMCTA applications based on load, priority and services.
3G cell
Copyright 1996 Northern Telecom
Load F1 first
LTE cell
Sequential Loading
3G cell
Copyright 1996 Northern Telecom
Non loaded
cell
Move voice CS
fallback centric UE to
3G
Overloaded
cell
Load Balancing
LTE cell
3.2
Alcatel-Lucent
14
into account. The decentralized self-optimizing approach for adjusting mobility parameters
aims at dynamically adjusting mobility parameters to balance the load between cells in order
to optimize the system resource usage. When the load is equally distributed within the
system, the use of the default value is the best compromise. However when load starts to
become dangerously unbalanced between cells, adjusting handover parameters is a way to
effectively achieve load balancing by moving traffic from one cell to another. This approach is
depicted (simplified view) in Figure 6 with two cells. While the simplified representation
shows two cells of similar size, it should be noted that these could also be a macro cell and a
small cell.
Cell coverage
Threshold for HO to
neighbor cell
B
A
A
B
Load = 40%
B
B
A
A
A
A
A
A
Threshold
modified
Load = 60%
A
B
Load = 95%
A
A
A
B
A
A
B
B
After HO parameters
adjustment
A
A
Load = 75%
It is clear that the adjustments of the mobility parameters will be triggered only if there is a
need to balance the load. This means that the algorithm will be triggered only if a given load
threshold has been reached. In addition the algorithm will use neighbor cells load information
in order to avoid creating overload situations in neighbor cells or increasing the handover
failure rate.
Alcatel-Lucent will implement the 3GPP defined decentralized self-optimizing approach for
adjusting mobility parameters. The standard approach is based on the direct use of
information from the UE to optimize the mobility parameters. The Alcatel-Lucent solution will
go a step further by exploiting the rich geometric information via proprietary intelligent
algorithms.
The geometric approach
The geometric approach nicely complements the self-optimizing approach. Indeed, the quality
of the self optimization is greatly impacted by the initial values of the mobility parameters.
Geometric information means all aspects that govern how RF is perceived by the UEs in
Alcatel-Lucent
15
different geometrical locations. Therefore, the term geometry involves location information
of eNodeBs, antenna height and azimuth and frequency band. Alcatel-Lucent has developed an
extensive set of algorithms that addresses local geometrical challenges while exploiting local
opportunities to prescribe good initial parameter values based on geometry information. This
means that the decentralized self-optimizing approach for adjusting mobility parameters will
start off with an already good initial set of values to provide improved performance. AlcatelLucent sees these geometric algorithms as a strong differentiator for any type of deployment.
3.3
Alcatel-Lucent
16
Encourage more UEs to camp on other sectors by reducing Qhyst in SIB3 and/or
Qoffset in SIB4.
The eNodeB can utilize above means to deviate the idle UEs camping behavior.
3.4
The following strategies may be performed with overload on the WCDMA Metro :
1) RRC Redirection to an inter-frequency 3G or 2G Macro using the RRC connection reject
mechanism.
2) It could be possible to redirect a LTE capable UE to the LTE Metro, although care would
need to be taken here that the UE is not on the WCDMA layer due to congestion on the LTE
layer.
3) When the WCDMA Metro cell gets to the maximum number of users either pre-emption of
existing calls through RRC connection release or handing off active calls to macro are
possible.
The redirection case will be blind, but the scope is a whole 3G Frequency or 2G RAT, so as
long as the UE can find any suitable cell on the target layer, the redirection will succeed.
Alcatel-Lucent
17
The handover case can make use of mobile assisted measurements to guide the handover.
4) Service based handover - it is possible to dedicate the Metro Cell to data only to take the
highest resource consuming users (PS Data) onto the Metro cell, and leave lower resource
consuming services such a voice on the Macro.
In an isolated Metro cell it can be possible to shrink coverage as the cell starts to get to full
load to avoid attracting too many UEs.
In a mesh scenario, any coverage reduction to avoid overload should take into account the
necessary coverage overlap between small cells to avoid making coverage holes. Whitepaper
B3_5 provides further details on this.
3.4.2
Generally a UE will be expected to camp and reselect directly on the LTE Metro layer.
However, in the case that the UE is on the WCDMA metro cell e.g. redirected to the WCDMA
metro from the LTE Metro, or in the case where the footprints are different, SIB 19 broadcast
allows the UE to reselect to the LTE Metro layer.
In the case that the LTE Metro layer is overloaded, it is possible to prevent reselection to that
cell from the WCDMA Metro Cell by indicating that it is blacklisted in the system information
broadcast.
3.4.3
The loading of the WCDMA macro cell could be used to determine the optimal layer to
handover to or redirect to from the Metro Cell. It is not simple to get the information
transferred between the two technologies due to the following considerations :
1) The RAN Information Management (RIM) could be used to pass load information using the
SON Transfer RIM application through the Core Network. However, 48.018, section 8c.6.4
limits this procedure to inter-RAT exchange. This means that intra-system load information
sharing through the CN is against the current versions of 3GPP standards.
In addition, any information transfer through the CN would involve CN loading, and rapid
updates for many cells could be intensive for both the RNC and the CN.
2) The 3GPP standard allows cell load information to be passed through an Iur link. The Iur
link would require a new interface from the Metro Gateway to the RNC.
If such an interface were developed, the RNC would need to expect many more common
measurements than normally supported. The Metro Gateway would need to act as a
concentrator for the measurements and request one set of measurements to pass to the
relevant Metro Cells which see the Macro cells as neighbours.
3.4.4
The mechanisms for the WCDMA Macro to determine WCDMA Metro load are the same as for
the WCDMA Metro to determine WCDMA Macro load, but with the additional considerations :
If there is PSC reuse on the Metro Cell, the Macro will not know which cell is applicable to a
UE being handed over from the Macro to the Metro, and makes the load information
ambiguous (See Incoming HO Whitepaper).
Alcatel-Lucent
18
It is therefore doubtful whether the WCDMA macro could make good use of such load
measurements.
Inter-System Routing Policy per-flow or per-APN polices for routing packet flows
for UEs that are capable of routing IP traffic simultaneously over multiple radio
access interfaces. It is also used to support Non-seamless WLAN offload.
ANDSF function is defined in 3GPP 23.402. ANDSF supplies the UE with information for
discovering and selecting appropriate access networks according to service provider policies.
It implements a new standardized interface (S14) between a network server and the UE.
Phase 1 provides the basic functionality on the server and UE ANDSF functionality.
It includes support for the S14 interface, security mechanisms as required by 3GPP
33.402, and server provisioned inter-system mobility and network discovery policies.
UE Access is via 3GPP.
Phase 2 adds inter-working with the Network Assisted WLAN off-load feature to
provide real-time intelligence to assist with network selection decisions.
Phase 3 adds support for per-APN and per-flow policies to support MAPCON and
IFOM. This includes S14 support for Untrusted Non-3GPP Access via secure tunnels
to the EPC. Interworking with Intelligent Presence is provided for service provider
policy driven guidance of network connections on a per-application basis.
ALU Network Assisted WLAN off-load provides network intelligence to ANDSF so better
decisions may be made in selecting the network priorities communicated to the UE. For 3GPP
R8, Network Assisted WLAN off-load formulates the inter-system mobility policy by
incorporating information from several sources, including the UE, network probes, the
HSS/SPR, provisioned operator policy and subscriber preferences.
Factors that may be
considered in assessing network priorities include, expected performance on WLAN APs, UE
mobility, subscriber subscription level, access to operator services and current subscriber data
usage.
This allows tailoring of the mobility policy to maximize the QoE for individual
subscribers while taking into account the impact those subscriber have on the mobility
network.
For 3GPP R8, Network Assisted WLAN off-load provides a prioritized list that can be
communicated using the standard ANDSF S14 interface. In addition ALU provides enhanced
functions available with an extended S14 interface supported with partner ANDSF clients. The
enhancements provide:
Alcatel-Lucent
19
Alcatel-Lucent
20
CONCLUSION
LTE will be deployed in areas already covered by 2G and 3G networks. The result will be a
multilayer network composed of both 2G, 3G and LTE layers, and even small cells, as well as
WiFi. Balancing the load between all available layers will be an important feature to optimize
the system capacity. Alcatel-Lucent load balancing solution is composed of several
components described in this document. Those components aim at intelligently distributing
the load between available carriers and offering the operator the tools to fully define its load
sharing strategy to better address its needs.
Alcatel-Lucent
21
ACRONYMS
Acronym
Expansion
e-UTRAN
eMCTA
GBR
ICIC
LTE
MME
PRB
QCI
QoS
RAT
RIM
SIB
SRVCC
UE
Evolved UTRAN
Enhanced Multi-Carrier Traffic Allocation
Guaranteed Bit Rate
Inter-Cell Interference Coordination
Long Term Evolution
Mobility Management Entity
Physical Resource Block
QoS Class Id
Quality of Service
Radio Access Technology
RAN Information Management
System Information Block
Single Radio Voice Call Continuity
User Equipment
Alcatel-Lucent
22