LA50 ENB CallP CAC and Congestion MNGT v0102

ALU solution for eNodeB / C-Plane
Admission Control & Congestion Mgt

Framework Overview LA5
CallP Architecture
April, 2012
Admission Control/Congestion Mgt Framework Overview
New UE connection
New incoming bearer
Multi-bearer Connection in mobility
Bearer modification
Nb of connections Admission Control

Nb of bearers
Radio Transport
Av. PRBs consumption
CAC CAC
transport BW
Admission
No Yes
Congestion Mgt
(@ Admission) LA4
Pre-emption
No
possible Cell Load monitoring
Yes
Cell Load
Accept new bearer and take above
appropriate action based on QCI & threshold No
PRBs consumption
ARP parameters
Yes
Offload
Offload
Reject eRAB Release eMCTA UE /
(of incoming (of existing bearers) (redirection of existing multi-bearer bearers
connection/bearer) connections to other layer or RAT)
Setup Target eNB cel load
Input criterion
2 | eNodeB C-Plane - Admission Control & Congestion Management| Dec 2010 All Rights Reserved Alcatel-Lucent 2010
1a Radio Call Admission Control
Radio Call Admission Control:
Checks eNB & cells resources before admitting new calls / bearers
Criteria 3 resources (#UE, #bearers, PRB usage) & 7 steps
1. Number of UEs on the eNB ==> MAX configurable / License [LA2]
2. Number of UEs on the cell ==> MAX configurable [LA2]
3. Number of VoIP on the cell ==> MAX configurable [LA2]
4. Number of bearers on the eNB (GBR or non-GBR) ==> MAX configurable [LA2]
5. Number of bearers on the cell (GBR or non-GBR) - per PLMN check starting [LA5]
included ==> MAX configurable [LA2]
6. Number of bearers per QCI [LA3] / group of QCI [LA4] on the cell - per PLMN
check starting [LA5] included ==> MAX configurable
7. DL PRBs usage on a per cell basis - per PLMN check starting [LA5] included ==>
MAX configurable [LA2] / MAX computed based on cell bw [LA4]
8. UL PRBs usage on a per cell basis - per PLMN check starting [LA5] included ==>
MAX configurable [LA2] / MAX computed based on cell bw [LA4]
Priority Level - ARP based
[LA2] - In case of multiple E-RABs the CAC is performed according to the

ARP provided in the incoming message (1: highest, 15: lowest).
[LA4] - Each bearer is classified as a HIGH Priority or LOW Priority bearer

mapping between ARP (Priority Level) and High/Low Priority is operator
configurable
EXAMPLE
ARP (Priority Level) in [1..8] range mapped to High Priority class
ARP (Priority Level) in [9..15] range mapped to Low Priority class
[LA4] - EC calls:
In the standard the operator is allowed to designate the ARP priority value to use
for bearers used to make Emergency VoIP calls
Admission Thresholds Two thresholds approach: PRB (1)
[LA3] TH1/TH2 differentiation between new & existing calls

Thresholds (TH1, TH2) defined for
DL/UL PRBs usage in the cell
The threshold levels are configurable as a percentage of the system total
maximum limits
Used for differentiation between new calls and already existing calls (ho, re-estab)
TH2 used as admission threshold for Re-establishment and mobility
whatever the priority of the bearer
TH1 used as admission threshold for new call / bearer admission whatever
the priority of the bearer
Admission Thresholds Two thresholds approach: PRB & #bearers (2)
[LA4] TH1/TH2 differentiation between HIGH & LOW Priority bearers

Thresholds (TH1, TH2) defined for
Number of bearers in the cell
DL/UL PRBs usage in the cell
The threshold levels are configurable as a percentage of the system total
maximum limits
Used for differentiation between Low and High Priority bearers as well as for
mobility
TH2 used as admission threshold for
High Priority bearers setup
Re-establishment and mobility whatever the priority of the bearer
TH1 used as admission threshold for
Low Priority bearers
[LA4] EC: This approach applies for bearers used to make Emergency VoIP calls as
well. The operator could choose to classify EC ARP value as High Priority if they want
to apply the TH2 threshold, to improve the admission success rate for emergency
VoIP
[LA4] Admission of bearers - #bearers in the cell criterion

High Priority bearer admission - Pre-emption allowed
If number of bearers < TH2 then the bearer is accepted
If number of bearers > TH2
if enough eRAB(s) to pre-empt to reduce #bearers below TH2 then
bearer accepted & pre-emption triggered otherwise bearer is rejected
Low Prioriy bearer admission - Pre-emption allowed
If number of bearers > TH1
If enough eRAB(s) to pre-empt to reduce #bearers below TH1 then
bearer accepted & pre-emption triggered otherwise bearer is rejected
High Priority bearer admission - Pre-emption not allowed
If number of bearers > TH2 then the bearer is rejected
Low Priority bearer admission - Pre-emption not allowed
If number of bearers > TH1 then the bearer is rejected
Radio Resources Management

[LA4] Admission of bearers - DL/UL PRBs usage in the cell criterion

High Priority bearer admission - Pre-emption allowed
If PRBs usage (current + new bearer*) < TH2 then the bearer is accepted
If PRBs usage (current + new bearer*) > TH2
If enough eRAB(s) to pre-empt to reduce PRBs usage below TH2 then
bearer accepted & pre-emption triggered, otherwise bearer is rejected
Low Priority bearer admission - Pre-emption allowed
If PRBs usage (current + new bearer*) > TH1
If enough eRAB(s) to pre-empt to reduce PRBs usage below TH1 then
bearer accepted & pre-emption triggered, otherwise bearer is rejected
High Priority bearer admission - Pre-emption not allowed
If PRBs usage (current + new bearer*) > TH2 then the bearer is rejected
Low Priority bearer admission - Pre-emption not allowed
If PRBs usage (current + new bearer*) > TH1 then the bearer is rejected
* non-GBR bearers can be considered as zero PRB consumption (by configuration)
Pool of contexts reserved for EC #ue in the cell criterion
If IMS VoIP EC [LA4] or CSFB [LA3] are enabled, a certain number of users may be
reserved for emergency call in cell
(RadioCacCell::nbOfContextsReservedForEmergencyCalls).
Radio/PRB RESOURCE Usage - different steps through releases:

In LA2: static PRB CAC (allocation based on MIM config)
In LA3: dynamic PRB CAC - new L1/L2 measurements. Real-time PRB consumption
is used to adjust periodically the radio resource consumption, according to the real
cell load, and to estimate the radio resource consumption on new incoming
services.
In LA4: dynamic PRB CAC - L1/L2 measurements evolves per service count + new
CCH dynamic consumption.
Self-tuned PRB consumption: modem meas Reservations Extra PRB that can be used
CCH SRB VoIP GBR Non-GBR available for CAC
PRB really needed
Total PRB that can be used available on the cell
[LA4] Radio/PRB RESOURCE

Usage DL/UL Total PRBs available on the cell - computed based on cell bw
DL/UL Threshold for HIGH Prio bearer
Two global pools of PRB

(dl/ulAdmissionThresholdOnPRB + deltaAdmissionThresholdOnPRBForHighPrioReq
resources DL/UL Threshold for LOW Prio bearer (dl/ulAdmissionThresholdOnPRB)
- one pool for DL, PRBs

consumed by
PRBs
consumed
PRBs
consumed
PRBs consumed
by non-VoIP GBR
PRBs
reserved Available for CAC
control by SRBs by VoIP bearers for non-
- one pool for UL
channels bearers GBR
Common Non- For For

Channel SRB VoIP GBR GBR HIGH & HIGH
LOW
CCH PRB Consumption for CCH reported by modem
SRB == [dl/ul]NbPRBRequiredPerSRB x [dl/ul]NbSrb Free PRB

pool
for CAC
VoIP pool == [dl/ul]AggregatedGBR x
[dl/ul]AveragePRBRequiredPerKbps
GBR pool == [dl/ul]AggregatedGBR x
[dl/ul]AveragePRBRequiredPerKbps
non- == MinBitRateForBestEffort x
GBR NbNonGbrBearer
pool [dl/ul]AveragePRBRequiredP
erKbps
[LA3] 3 new measurements are configured after cell setup:

2 measurements to report the PRB consumption: 1 in DL, 1 in UL
1 measurement to report the UE radio condition
[LA3] At C-Plane level, these measurements are used for the CAC algorithm
to admit or not new incoming users or bearers:
The current PRB consumption on the cell is periodically adjusted by CallP based on
real-time PRB consumption reported by UL & DL schedulers
The resource consumption estimation for a new request (triggered at Bearer Setup
/ Modify / Delete request) is derived.
from real-time PRB consumption in UL and DL
from UE radio condition
from service characteristics (GBR requested by MME for VoIP and GBR
bearers, MIM parameters for non-GBR bearers)
[LA3] Estimation of consumption of (DL/UL) resources for a bearer (SRB, VoIP, GBR or
non-GBR)
[dl/ul]NbPRBrequiredByOneSRB & [dl/ul]AveragePRBrequiredPerKbps values are computed in

CallP based on modem measurement reports
SRB case:
(DL/UL) consumed resources = [dl/ul]NbPRBrequiredByOneSRB
VoIP case:
(DL/UL) consumed resources = [dl/ul]AveragePRBrequiredPerKbps *
[dl/ul]_GBR * PRBReservationFactor[QCI]
GBR case:
(DL/UL) consumed resources = [dl/ul]AveragePRBrequiredKbps *
[dl/ul]_GBR * PRBReservationFactor[QCI]
Non GBR case:
(DL/UL) consumed resources = [dl/ul]AveragePRBrequiredPerKbps *
RadioCacCell[dl/ul]MinBitRateForBE
1b Transport Call Admission Control LA5
LA5
Transport Call Admission Control:
Transport CAC -> performed at bearer admission / control transport resources

available for the new incoming eRAB:
Transport CAC is performed on S1-U only. S1c, X2, OAM, 1588 bandwidths are
statically reserved from MIM. No transport CAC is performed on X2.
Transport CAC applies on per port or per VLAN basis.
If Transport CAC is based on VLAN, Transport resources are defined on a per VLAN
basis. A given VLAN is not shared between operators: even if serving gateways are
shared between different operators (eUTRAN Sharing feature), In this case one
VLAN is entirely managed by one single operator.
If Transport CAC is based on Port, Transport resources are defined on a per Port. In
this case L114383 transport eUTRAN sharing cannot be enabled. A WIPS check is
be added to control that both features are not activated simultaneously.
Transport CAC limitations:

Transport CAC is only based on static configuration (no measurement) -> feature
activation flag activationService::isTransportCacAllowed
No offload/pre-emption on transport resource congestion detection during CAC.
LA5
The bandwidth of a transport link is segmented in transport classes of service (transport CoS):
Number of transport CoS is configurable
Size (i.e. reserved bandwidth) of each transport CoS is configurable
Affectation of the QCI inside the different CoS pools is configurable
Extra bandwidth can be managed for priority calls (EC & HPA)
The size of each pool corresponds to the maximum bandwidth that can be allocated for
E-RABs associated to QCI affected in the pool COS.
The sum of the bandwidths of all COS pools for a VLAN and for a direction (up or down)
must be less than the ingress CIR static reserved Bandwidth (S1C + X2 +OAM
+1588,MBMS..).
Transport CAC application is performed during the following procedures:
-> S1AP Initial Context Setup
-> S1AP eRAB Setup
-> S1AP eRAB Modify
-> Incoming Inter-eNodeB HO (S1AP or X2AP)
Update of the transport resources consumption also applies on bearer/context release.
Transport resource estimation & computation (VoIP, GBR, Non-GBR)
Transport Load & X2 load exchange per E-RAB ( Voip, GBR, NGBR)
LA5
Transport CAC - Ingress Sharing
SlaConf::ingressCir
Part of the SlaConf::ingressCir for the user-plane over S1
DL_COS_STANDARD_RESER
Bandwidth configured in VED DL_COS_STANDARD_RESERVED DL_COS_STANDARD_RESERVED
SlaConf::StaticBandwidth _BANDWIDTH(0) _BANDWIDTH(1) _BANDWIDTH(2)
dl1588Bandwidth
dlOamBandwidth
dlX2cBandwidth
dlS1cBandwidth
dlM1Bandwidth
DL_COS_CONSUME DL_COS_CONSUMED_BAND DL_COS_CONSUMED_BAND

D_BANDWIDTH(0) WIDTH(1) WIDTH(2)
TransportCacCosConf:: TransportCacCosConf:: TransportCacCosConf::

transportCoS=0 transportCoS=1 transportCoS=2
Voice QCI=1 GBR, Real-Time Non-GBR, Non-Real-Time,
QCI=2,3,4 Best-Effort QCI=5,6,7,8
DL_COS_EXTRA__RESERVED
_BANDWIDTH(0)
2 Congestion Management LA4
LA4
Congestion Management:
Determine the existing bearer(s) that could be pre-empted depending of

its ARP value - Pre-emption Vulnerability
only bearers with Pre-emption Vulnerability ON can be pre-empted
its ARP value Priority Level
only bearers with priority lower than the priority of the incoming bearer
can be pre-empted
bearers are selected in ascending priority order starting with the lowest
priority
its QCI value
only GBR bearers are pre-empted when the limiting criterion is the PRB
usage (case MinBitRateForBestEffort set to 0)
GBR and non-GBR can be pre-empted when the limiting criterion is the
number of bearers
restricted to a set of QCIs when the limiting criterion is the number of
bearers per group of QCIs
its average PRB consumption
only in case the limiting criterion is the PRB usage
determine the amount of resources that can be freed
LA4
Determine the appropriate action to take due to admission failure
Depending on QCI value of existing bearers

Depending of ARP value (Pre-emption Capability) of the incoming bearer
Pre-emption is triggered only if Pre-emption Capability is set to ON
Decision is taken by using an operator configurable decision table
On a per QCI basis, a table indicates the preferred actions to take

EXAMPLE Configuration
QCI value
Pre-emption action 1 2 3 4 5 6 7 8 9
Release - - x x - x x x x
Offload (eMCTA) x x - - x - - - -
From the above example:

QCI 1: Offload (eMCTA) of the UE (selected bearer + all other UEs bearers)
QCI 3: eRAB released (other UEs bearers are kept in the cell)
LA4
How are taking into account the other UEs bearers when the action of the selected
bearer is offload ?
UE can be pre-empted only if:

all its bearers have ARP - Pre-emption Vulnerability set to ON
all its bearers have ARP - Priority Level lower than the one of the incoming bearer
Pre-emption efficiency depends on operators strategy for ARP setting:
UE oriented: all bearers of the UE have the same ARP value
Service/bearer oriented: ARP value set on a per QCI basis only (not UE dependent)
Default bearers with High Priority (or not vulnerable) will reduce the possibility to find
UE to pre-empt
Mix of UE and Service/bearer oriented: ARP value set on a per QCI and UE basis
LA4
What happen to the selected UEs bearers when offloading is not possible ?
The selected bearer identified for pre-emption is released
Resources have to be released since incoming bearer has been admitted

The other UEs bearers are kept in the source cell
LA4
Pre-emption may also be triggered to accept an incoming emergency call when the
maximum number of UEs is reached
An existing UE connection shall then be pre-empted

The UE to pre-empt is selected with the following rules
UE Priority aggregate from the Prority Level of all UEs bearers
UE Priority = highest (UEs bearers Priority Level)
UEs are selected in ascending UE Priority starting with the lowest priority
all UEs bearers have a ARP - Pre-emption Vunerability set to ON
How to determine the pre-emption action ?

UE connection release or offload (eMCTA) ?
Operator choice
What happen to the selected UE when offloading is not possible ?
The selected UEs connection is released
LA4
Nb of Users PRB + Nb of Bearers

Triggering Event per cell && per eNB per cell && per eNB
Congestion Pre-emption Congestion Pre-emption

detection detection
Any RrcEstabCause
Cell + eNB No SRB No
except EC
EC
RRC CX ESTAB RrcEstabCause Cell + eNB
Spare ctx usage Yes (*)
(only if L103897
ACTIVATED) for check /cell
NON EC-ARP Cell + eNB No TRB Yes

INTER-ENB HO EC-ARP Cell + eNB
(Target Cell) -
(only if L103897 Spare ctx usage Yes (*) TRB Yes
S1 or X2
NON EC-ARP Cell only No TRB Yes
INTRA-ENB HO EC-ARP Cell only

(Target Cell) (only if L103897 Spare ctx usage Yes (*) TRB Yes
NON EC-ARP Cell only No TRB Yes
RE-ESTAB non- EC-ARP Cell only
serving (New
(only if L103897 Spare ctx usage Yes (*) TRB Yes
Cell)
INITIAL CTX TRB Yes

All ARP
SETUP
eRAB SETUP All ARP TRB Yes
TRB: case
eRAB MODIFY All ARP GBR_new > Yes
GBR_old
(*) if spare ctx are exhausted, pre-emption does not apply and EC are rejected
3 Preventive Load Control for load
balancing LA5
LA5
Congestion Management for Preventive Load control:
100% Reactive Offloading upon admission
Congestion management estimates if PRB of low or high priority bearers
consumption level (TH0) needs to trigger preventive TH2 = <xx>AdmissionThreshold +

deltaAdmissionThresholdForHighPrioAdmission
Offload, on selected UEs. Reactive Offloading upon admission

of low priority bearers
TH1 = <xx>AdmissionThreshold
Preventive Offloading of low

priority bearers / Load balancing
It is evaluated at:
CAC Context Update - Meas Report from Modem TH0 = <xx>LoadBalancingThresholdOnPrb
PRB Consumption UL Report Where <xx> stands for

PRB Consumption DL Report respectively = ul, dl, ul band,
dl band
CAC Commitment (after successful admission)
RRC CONNECTION REQUEST
RRC CONNECTION RE-EST (new cell)
Intra-Enb HO (target cell)
Inter-Enb HO (target cell)
S1AP INITIAL CONTEXT SETUP
S1AP E-RAB Setup
LA5
A UE Candidates list is maintained for Preventive offload purpose:
> The criteria to make a UE part (or not) of the list are:
UEs whose ARP (numerical) aggregated priority is lower than new MIM parameter:
RadioCacEnB::arpThresholdForPreventiveLoadControl will never be candidate for preventive offloading;
UEs that do not support Inter-frequency handover and event A4 can not be selected; (fgi bits #13 & #14)
If MinBitRateForBE is 0 (UL or DL, depending on which criteria is hit for load balancing), UEs with only non-GBR
bearers shall not be selected;
UEs that do not support any LTE neighboring carrier (numOfSupportedLteNeighboringCarriers == 0) can not be
selected
> Also, the list is sorted according to the following criteria:
-1st criterion: highest aggPriorityLevel
- 2nd criterion: UE supporting most LTE neighboring bands with same aggPriorityLevel (see 6.4.6.6)
- 3rd criterion: highest aggDlCost or aggUlCost, depending on the congestion trigger direction
LA5
When preventive Load Control is triggered and some UEs must be offloaded, due to at
least one of the four PRB consumption (Dl Cell, Ul Cell, Dl Band and Ul Band) exceeded
the related TH0, the UEs selected for offload are picked from the UE Candidates list:
The UE selection stops when:

There is no more UE listed in candidatePreventiveUeList
OR
The number of UEs selected is reaching Actual PRB Consumption (CAC

view)
MIM:: RadioCacEnb::maxNbrOfUsersImpactedByPreventiveLoadControl
OR UE 1
Overall offload gain expected

enough PRB resources are found TH0 => UE 2
Target: being below after UE 3
offload
(assuming that the offload of selected UEs will succeed)
Provisonal contribution of
Candidates UEs to offload
LA5
Triggering Offload Management For Preventive Load Control:
Please refer to the slide package eMCTA-Phase 2, Offload management for Reactive
and Preventive triggers, Intra-LTE Cell Load Exchange.
In case of Offload failure, UE stays in the cell (no congestion decision to release, as
for Reactive)
4 Conclusion
Admission Control/Congestion Mgt Framework Overview
New UE connection
New incoming bearer
Multi-bearer Connection in mobility
Bearer modification [POST LA5] Scheduler
Nb of connections Admission Control Scheduling
Nb of bearers
Av. PRBs consumption RAC Transport
transport BW
(Radio Adm. Control) CAC
Congestion
Admission (GBR/PDB not served)
No Yes No (Could be also for high-prio

non-GBR)
Yes
Congestion Mgt
(@ Admission)
Pre-emption Cell Load Monitoring

possible LA5 [Post LA5] Congestion
No Mgt (During Calls)
Yes
Cell Load
Accept new bearer and take above Take appropriate action based
appropriate action based on QCI & threshold No
on QCI & ARP parameters
PRBs consumption
ARP parameters
Yes
Offload
Reject eRAB Release eMCTA Congestion eRAB Release

(of incoming (of existing bearers) (redirection of existing multi-bearer Indication (of existing bearers)
connection/bearer) connections to other layer or RAT)
(UL& DL ECN-CE for Target RAT cell load
VoIP calls) Target eNB cel load
Input criterion

LA50 ENB CallP CAC and Congestion MNGT v0102

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LA50 ENB CallP CAC and Congestion MNGT v0102

Загружено:

Авторское право:

Доступные форматы

ALU solution for eNodeB / C-Plane

Admission Control & Congestion Mgt

Nb of connections Admission Control

Priority Level - ARP based

[LA2] - In case of multiple E-RABs the CAC is performed according to the

[LA4] - Each bearer is classified as a HIGH Priority or LOW Priority bearer

Admission Thresholds Two thresholds approach: PRB (1)

[LA3] TH1/TH2 differentiation between new & existing calls

Admission Thresholds Two thresholds approach: PRB & #bearers (2)

[LA4] TH1/TH2 differentiation between HIGH & LOW Priority bearers

[LA4] Admission of bearers - #bearers in the cell criterion

Radio Resources Management

[LA4] Admission of bearers - DL/UL PRBs usage in the cell criterion

* non-GBR bearers can be considered as zero PRB consumption (by configuration)

Pool of contexts reserved for EC #ue in the cell criterion

Radio/PRB RESOURCE Usage - different steps through releases:

CCH SRB VoIP GBR Non-GBR available for CAC

PRB really needed

Total PRB that can be used available on the cell

[LA4] Radio/PRB RESOURCE

DL/UL Threshold for HIGH Prio bearer

Two global pools of PRB

resources DL/UL Threshold for LOW Prio bearer (dl/ulAdmissionThresholdOnPRB)

- one pool for DL, PRBs

Common Non- For For

CCH PRB Consumption for CCH reported by modem

SRB == [dl/ul]NbPRBRequiredPerSRB x [dl/ul]NbSrb Free PRB

[LA3] 3 new measurements are configured after cell setup:

[dl/ul]NbPRBrequiredByOneSRB & [dl/ul]AveragePRBrequiredPerKbps values are computed in

Transport CAC -> performed at bearer admission / control transport resources

Transport CAC limitations:

Transport CAC - Ingress Sharing

Part of the SlaConf::ingressCir for the user-plane over S1

DL_COS_CONSUME DL_COS_CONSUMED_BAND DL_COS_CONSUMED_BAND

TransportCacCosConf:: TransportCacCosConf:: TransportCacCosConf::

Determine the existing bearer(s) that could be pre-empted depending of

Determine the appropriate action to take due to admission failure

Depending on QCI value of existing bearers

Decision is taken by using an operator configurable decision table

On a per QCI basis, a table indicates the preferred actions to take

From the above example:

UE can be pre-empted only if:

The selected bearer identified for pre-emption is released

Resources have to be released since incoming bearer has been admitted

An existing UE connection shall then be pre-empted

How to determine the pre-emption action ?

Nb of Users PRB + Nb of Bearers

Congestion Pre-emption Congestion Pre-emption

NON EC-ARP Cell + eNB No TRB Yes

INTRA-ENB HO EC-ARP Cell only

INITIAL CTX TRB Yes

eRAB SETUP All ARP TRB Yes

consumption level (TH0) needs to trigger preventive TH2 = <xx>AdmissionThreshold +

Offload, on selected UEs. Reactive Offloading upon admission

Preventive Offloading of low

CAC Context Update - Meas Report from Modem TH0 = <xx>LoadBalancingThresholdOnPrb

PRB Consumption UL Report Where <xx> stands for

A UE Candidates list is maintained for Preventive offload purpose:

> Also, the list is sorted according to the following criteria:

-1st criterion: highest aggPriorityLevel

The UE selection stops when:

The number of UEs selected is reaching Actual PRB Consumption (CAC

Overall offload gain expected