ALU LTE LB Workshop

ALCATEL-LUCENT
LTE EMCTA & LOAD BALANCING WORKSHOP
AINMT
COPYRIGHT © 2014 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

ALCATEL-LUCENT — CONFIDENTIAL — SOLELY FOR AUTHORIZED PERSONS HAVING A NEED TO KNOW — PROPRIETARY — USE PURSUANT TO COMPANY INSTRUCTION
AGENDA
1. eMCTA
2. LA5 –> LR14.1 load balancing features

• LA5 L115203 Load Base Idle Mode mobility
• LA5 L115223 Inter-Freq Load Balancing
• LR13.1 L114538 Enhanced Load Balancing criteria (Load Equalization)
• LR13.3 L171232 nGBR QoS Based Load Balancing
• LR13.3 L163172 Traffic Management Evolution
• LR14.1 171193 Network accessibility improvements with Redirection/de-
prioritization at Call Admission
3. Annex
LR15.1 load balancing features
3
EMCTA OVERVIEW
• eMCTA(evolved Multi-Carrier Traffic Allocation) is a proprietary feature located in
the eNB
• eMCTA aims at providing a sorted list of RAT/carriers for measurements or for
blind handover based on a flexible operator’s configuration. Following mobility is
supported by eMCTA:
 inter-frequency LTE neighboring carriers
 inter RAT GERAN neighboring carriers
 inter-RAT UTRAN neighboring carriers
• eMCTA can be invoked either by following events:
 serving radio monitoring via RRC Measurement
 CSFB indicator from the MME
 eNB Reactive Load Control
 eNB Preventive Load Control
 eNB ANR function
• eMCTA is invoked only in the RRC-connected mode
4
EMCTA ROLE AMONG OTHER ENB PROCESSES
Preventive Load Control Configured neighbor RAT/carriers
for LTE or GERAN or UTRAN
ANR inter RAT/carriers (Fdd or Tdd) or HRPD
Reactive Load Control
Measurement Based Mobility
Meas. report for A2_CA
RRC Measured candidate RAT/
CS Fallback indicator
Measurement Carriers sorted list eMTCA
Meas. report for Blind mobility
A2_floor process Framework
Blind candidate RAT/carrier
Inter-freq/RAT Sorted list
Measurement configuration
Only one single best carrier is

Meas. Report for
selected for blind redirection
events A3,A4,A5, UE Capabilities
B1,B2 Mobility
procedures
Cell Change Order (LTE > GERAN)
Redirection
output
PS Handover (LTE > UTRAN)
Inter-Frequency HO intput
5
FOCUS ON EMCTA PROCESS
Preventive Load Control
ANR inter RAT/carriers
Reactive Load Control
Meas. report for A2_CA
Meas. report for A2_floor
CF Fallback Indicator
1
UE Capabilities
Filter 2 UE Capability
3 Network Capability
4 Service-based Policy
Neighbor RAT/Carrier List 5 QCI-based Policy
6 Frequency Load
- Candidate1 RAT/carrier Candidate RAT/carrier sorted list with for each candidate:
- Candidate2 RAT/carrier
- Candidate3 RAT/carrier
Target Measurement Configuration (B2/B1, A5/A3, A4 or none)
Priority (0-lowest to 7-highest)
Whether a Measurement Gap needs to be configured (yes/no)
6
OBJECT MODEL FOR EMCTA
LteCell
[0..1] [0..1] [0..1] [0..1]
LteNeighboring UtraNeighboring GeranNeighboring HrpdNeighboring
[1..2]
HrpdBandClassConf
[1..9] [0..16] [0..16] [0..3]

LteNeighboring UtraFddNeighboring GeranNeighboring HrpdNeighboring
FreqConf FreqConf FreqConf FreqConf
MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable
7
MOBILITY PRIORITY TABLE
Only for RAT supporting CSFB.
Applicable to Service-Based Policy MobilityPriorityTable Applicable to QCI-Based Policy
(CSFB) when (non-CSFB) when
isServiceBasedTrafficSegmentation isServiceBasedTrafficSegmentationAllowed =
Allowed = True True
defaultConnectedPriorityOfFreq
[0..4] [0..32]
Possible values:
ServiceTypePriorityConf qci1 to qci255 qciPriorityConf
serviceType qciHierarchyForMultiQciCallList
eMctaPriority qci
eMctaPriority
Possible values: Possible Values: Lists the QCIs in order of importance for
csfbByIdleUE, emergencyCsfbByIdleUE, serviceOrQci-not-allowed-in-RAT- carrier, mobility purpose. Up to 32 entries
csfbByConnectedUE, 0-lowest, 1, 2, 3, 4, 5, 6, 7
emergencyCsfbByConnectedUE
8
AGENDA
1. eMCTA

3. Annex
9
LOAD BALANCING FEATURES
Load balancing and overload handling strategies at various cell load levels
10
11
Functionalities and triggering criteria involved in load control
12
AGENDA
1. eMCTA

3. Annex
13
LA5 L115203 LOAD BASE IDLE MODE MOBILITY
Feature Description
• Provides the capability for the eNB to automatically adapt some of the cell reselection
parameters advertised in SIB3 depending upon the serving cell’s loading
• Can be used to trigger some idle UEs to reselect when the serving is heavily loaded, to reduce
the future load
• Can be used to impact intra-frequency, inter-frequency and/or IRAT reselection
• Load criteria is the cell’s PRB consumption,
• Independently for DL and UL
• Configurable Weight factors for DL and UL
• Operator can specify the value to use at up to 4 different load levels for the following
parameters:
• q-Hyst (for intra-frequency or inter-frequency equal priority reselection)
• threshServingLow (for inter-frequency lower/higher priority reselection)
• threshServingLowQ-R9 (for inter-frequency lower/higher priority reselection, Rel-9 UEs)
• s-nonIntraSearch (for inter-frequency lower/higher priority reselection)
• s-nonIntraSearchP-r9 (for inter-frequency lower/higher priority reselection, Rel-9 UEs)
• s-nonIntraSearchQ-r9 (for inter-frequency lower/higher priority reselection, Rel-9 UEs)
• The neighbor load is not considered in this feature and there is no communication to inform the
neighbor of a parameter adjustment
• This feature provides the capability to automatically adjust broadcasted cell reselection
parameters based on the loading condition of the serving cell
• This can reduce the load in the serving cell by causing some idle UEs to reselect to neighbor
cells, and thus some future connection requests will be handled by the
neighbors
14
PRB consumption for NGBR is based on dlMinBitRateForBE and ulMinBitRateForBE.
The following provides examples for calculation of Minimum Bit Rate For Best Effort:
Assumptions:
Only NonGBR bearers, No GBR bearer
Average PRB consumption per SRB = 0.25 PRB/s
Average PRB consumption for 1kbps = 10 PRB/s/kbps (eNB calculates this based on real traffic, and it can vary)
Average Number of NonGBR bearers per UE = 1 bearer/UE
Overhead PRB consumption = 4000 PRB/s (dlOverheadConsumption = 2200 & ulOverheadConsumption = 5600)
PRB consumption is 70% of total bandwidth
Filtering of averagePRBperkbps:
filterCoeff: Current number of connected UEs in cell / maxNbrOfUsers

The filtering is currently performed as:
New averagePRBperkbps = (1 – filterCoeff) * Old averagePRBperkbps + filterCoeff * current averagePRBperkbps
15
Parameters adaptation
• Several controls are available to the operator to determine the adaptation behavior.
• In order to perform any adaptation the feature must be enabled via the
isSIB3ReselectionAutomationAllowed parameter
• Up to 3 loading levels can be defined by creating a object for each level
• Each object contains parameters that define the delta between the existing SIB3
parameters listed above and the SIB3 value to use at a loading level
that is defined by an (lowerBound, upperBound)
• If the cell loading is not within the range defined by any object then the SIB3 parameter value is
unchanged. Thus it is possible to construct 4 loading
levels if desired, for example when 3 objects are defined as follows:
• object 1 has bounds of 80 and 100%
When the loading level is from 20 to 59% the normal parameters apply
• The operator will be able to configure how often the automated adjustment can be made
Loading level
• The loading level is derived from the recent UL / DL PRB consumption
• An individual weighting factor can be applied for each of the 4 components of PRB
consumption
• At the automated ajustment interval the system will apply the weighting factors as following:
•weightDlPrbCell * (% of cell DL PRB consumed)
•weightUlPrbCell * (% of cell UL PRB consumed)
•weightDlPrbEnb * (% of total PRB consumption of the band in DL)
•weightUlPrbEnb * (% of total PRB consumption of the band in UL)
16
AGENDA
1. eMCTA

3. Annex
17
LA5 L115223 Inter-Freq Load Balancing
18
INTER-FREQ LOAD BALANCING
Triggering conditions
• Average PRB consumption (LA5 L115223 Inter-Freq Load Balancing)
• Based on average cost for non-GBR bearers (minBitRateForBE parameter) and S1AP
GBR value for GBR bearers
• When PRB consumption reaches a configurable threshold in either UL or DL, trigger load
balancing
• Real PRB consumption and cell DL non-GBR throughput (LR13.3 L171232 nGBR QoS Based Load Balancing)
• Level of QoS Degradation at which load balancing should be triggered is decided by the
operator and is based on average cell DL throughput for non-GBR bearers (per QCI)
• If real PRB consumption is high, but no presence of QoS degradation -> no need to
offload
• If real PRB consumption is high, and there are signs of QoS degradation -> Trigger load
balancing
• If real PRB consumption is low -> no need to offload
• Number of UEs (LR13.3 L163172 Traffic Management Evolution)
• Number of connected mode users per cell
• Number of connected mode users per eNB
• Number of active users per cell
Each criterion can be activated independently
19
UE selection 1/2:
•For Load Balancing and Load Equalization multiple UEs may be selected depending on current load,
capped by parameter: maxNbrOfUsersImpactedByPreventiveLoadControl
• For Load Balancing triggered by either number of connected UEs per cell or per eNB:
• enough UEs are selected such that the remaining number of connected UEs is below both
thresholds for number of UEs per cell and number of UEs per eNB.
• For UE Reclaiming multiple UEs are selected defined by parameter:
maxNbrOfUsersImpactedByUeReclaiming
• UEs are ranked from lowest to highest aggregate priority to avoid impact on service
• Aggregate priority is defined as the highest ARP priority (lowest ARP value) amongst all of the
UE’s radio bearers
• For UEs with same priority:
• UEs supporting more configured LTE neighbor carriers are selected ahead of ones
supporting less LTE neighbor carriers
• For UEs supporting the same number of LTE neighbor carriers
• UEs with higher aggregate DL+UL PRB cost are selected ahead of ones with lower
aggregate DL+UL PRB cost
• Either UEs that are at cell edge or the ones that are at cell center can be favored
• Based on UE DL SINR in serving cell
• Capability activable/de-activable on a per cell basis: uESelectionPriorityForOffload
20
UE selection 2/2:
• UEs with high priority can be out of the selection

• Priority higher than a configurable ARP priority threshold: arpThresholdForPreventiveLoadControl
• UEs with a VoLTE call can be preferred to offload last

• Capability activable/de-activable on a per cell basis: isVoipOffloadEnabled
• UE Carrier Aggredation CA capable in the serving cell can be preferred to offload last if there is no other cell
of the sector which allows CA configuration.
• Capability activable/de-activable on a per eNB basis: isCaPcellCapabilityMobilityEnabled
• UE that can’t be configured CA in the sector due to maximum aggregated bandwidth limitation can be
preferred to offload last if there is no nother cell with an equivalent or higher bandwidth
• Capability activable/de-activable on a per eNB basis: isCaBandwidthMobilityEnabled
• UEs cannot be selected if It doesn’t support inter-frequency HO and inter-frequency measurements (event
A4)
21
Execution 1/3:
The following steps are performed in order to select the target carrier and cell:
1. Preventive offload trigger will invoke eMCTA;
2. eMCTA will perform selection of the most appropriate carrier(s) after applying different
frequency filters (Service, UE capabilities, eNB capabilities, target cell load…) on the list of
neighbor carriers of the serving cell.
3. UE measurements are configured with candidate frequency(ies), using event A4 (neighbor

better than a configurable threshold)
• There is a timer to control the maximum time the UE will be making offload
measurements:ueTimerNoOffload. Upon expiry, measurements are de-configured and
offloading process is stopped.
4. Upon reception of UE measurement report, target cell is NOT considered if it is loaded.
5. If target cell is identified as not loaded, inter-frequency handover is attempted.
22
Execution 2/3:
Load Comparison with Target Carrier/Cell
• When receiving a UE A4 measurement report for preventive offload, the eNB will compare the load of
the target cell with the load of the serving cell in order to ensure there is a minimum configurable delta
between the two cells (i.e. serving cell load needs to be higher than target cell by a delta).
• For semi-static PRB per cell usage trigger, this is done by comparing semi-static PRB usage
between serving and target cell:
- Target cells (intra-eNB or inter-eNB) for which the semi-static PRB usage per cell is within a
pre-determined threshold of the serving cell’s PRB usage will be filtered out;
- For existing preventive offload, this threshold will be hard-coded;
-For early preventive offload / load equalization, this threshold is configurable (based on
thresholdRelativePreventiveOffload, LR13.1 L114538) ;
• Intra-eNB target cells for which preventive offload is being triggered (based on any of the possible
criteria) are filtered out.
• If a neighbor cell’s load is unknown, then preventive offload is not triggered, unless
isBlindPreventiveOffloadEnabled is set to true (LR13.1 L114538)
23
Execution 3/3:
Neighbor cell filtering – How neighbor cell load info is used
Upon reception of a UE measurement report for load balancing, the eNB will apply the following logic:
• If the target cell is considered ‘loaded’, the target cell is not considered for offload;
• If the target cell is considered ‘not loaded’,

• If load balancing trigger is based on PRB consumption
•If PRB consumption of neighbor cell is below the serving cell’s PRB
consumption by a pre-determined Load Balancing delta (default is 10%), then
offload is triggered
• Else, the target cell is not considered for offload
• Else (load balancing is triggered by other criteria)

• If Available Capacity of neighbor cell is Above the serving cell’s Available
Capacity by a predetermined delta (default is 10%), then offload is triggered
24
Execution 3/3:
Neighbor cell filtering – How neighbor cell load info is used
Upon reception of a UE measurement report for load balancing, the eNB will apply the following logic:
• If the target cell is considered ‘loaded’, the target cell is not considered for offload;
• If the target cell is considered ‘not loaded’,

• If load balancing trigger is based on PRB consumption
•If PRB consumption of neighbor cell is below the serving cell’s PRB
consumption by a pre-determined Load Balancing delta (default is 10%), then
offload is triggered
• Else (load balancing is triggered by other criteria)

• If Available Capacity of neighbor cell is Above the serving cell’s Available
Capacity by a predetermined delta (default is 10%), then offload is triggered
25
AGENDA
1. eMCTA

3. Annex
26
LR13.1 L114538 ENHANCED LOAD BALANCING CRITERIA (LOAD EQUALIZATION)
Blind Inter-Frequency Preventive Offload:
• Blind load balancing allows the option of performing offload without any load information from the
neighbor cell
• Examples: if X2 link is not available or X2 link is down
• When a UE A4 Measurement report is received for preventive offload, if:

• Blind offload is activated: Allow handover towards best cell even if neighbor cell load is
unknown;
• Blind offload is deactivated: Ignore UE measurement report if neighbor cell load is unknown;
27
Load Equalization:
• Load equalization is an early form of preventive offload, allowing to provide consistent user QoS in
different LTE carriers by correcting load imbalances possibly early
- LR13.1 introduces Load Equalization step 1
- Load Equalization is trigger when the serving cell load hits a configurable threshold (in terms of
PRB usage), AND when there is sufficient delta (configurable) between serving and target cell
loading
- If a target cell does not satisfy this criterion, preventive load balancing will not be
triggered towards this cell;
-Done by comparing load levels at the moment of UE A4 measurement report reception;
• Can be switched ON/OFF on a per LTE neighbor carrier basis, so the operator can decide between
which carriers load equalization is applicable
- Works intra-band and inter-band
28
29
AGENDA
1. eMCTA

3. Annex
30
LR13.3 L171232 NGBR QOS BASED LOAD BALANCING
In addition to looking at “static” PRB consumption based on minBitRateForBE and GBR, the feature
looks at real PRB consumption & average cell-level QoS to determine if there is radio
congestion
- It wouldn’t be enough to look only at real PRB consumption since a few UEs can take the whole
band – the implementation relies on QoS evaluation to confirm radio congestion (or early signs of
congestion) :
- If real PRB consumption is high, but no presence of QoS degradation -> no need to trigger
Load balancing
- If real PRB consumption is high, and there are signs of QoS degradation -> Trigger Load
balancing
-If real PRB consumption is low -> no need to trigger Load balancing
-Level of QoS Degradation at which load balancing should be triggered is decided by the operator and
is based on average cell DL throughput for non-GBR bearers
- One configurable average DL throughput threshold per non-GBR QCI
31
LR13.3 L171232 NGBR QOS BASED LOAD BALANCING
The eNB will trigger load balancing when the following two conditions are met:
1) Real PRB consumption is above a configurable threshold

- Real PRB consumption is measured across control channels, SRBs and Traffic channels
-PRB consumption is filtered in time using a configurable filter coefficient
2) Average bursty DL throughput is below a configurable threshold for any non-GBR QCI
- DL throughput is based on total RLC burst size and RLC burst time for each non-GBR QCI
(this is the throughput across all active users)
32
AGENDA
1. eMCTA

3. Annex
33
LR13.3 L163172 TRAFFIC MANAGEMENT EVOLUTION
This feature provides more controls for the service provider for load balancing and call admission and
increased flexibility of managing traffic across layers.
• Multiple load balancing thresholds per LTE neighbor carrier allows the operator to prioritize neighbor
carriers for preventive offload.
• This feature adds the option for load balancing to be triggered based on number of connected UEs
per cell or number of connected UEs per eNB.
• The eNB can avoid selecting UE's with VoIP bearer for preventive offload and load equalization. For
example configuring this on the layer with the best coverage in a network with multiple carriers may
improve VoIP user experience.
• This feature allows configuring up to 4 ARP priority classes for call admission to differentiate different
priorities of traffic radio bearers.
34
Per neighbor carrier Preventive Load balancing:
• Prior to this feature, all neighbor carriers use the same set of preventive offload thresholds. With
this feature, the operator can define up to 4 different sets of preventive offload thresholds, where
each set of per carrier load thresholds can include one or more of the following:
• uplink estimated (semi-static) PRB consumption
• downlink estimated (semi-static) PRB consumption
• uplink real PRB consumption and average QoS degradation
• downlink real PRB consumption and average QoS degradation
• number of connected UEs per cell
• number of connected UEs per eNB (same threshold value for all neighbor carriers).
35
Each LTE neighbor carrier is assigned to one of up to 3 sets of thresholds

- Thresholds are based on serving cell loading
36
Number of UE as criterion for Load balancing
• Prior to LR13.3, preventive load balancing was only based on estimated PRB consumption. This feature
adds ability to trigger load balancing based on number Ues:
• Number of connected mode users per cell

• Number of connected mode users per eNB
• Number of active users per cell
37
• Multiple priority levels for Call Admission
- Separate pairs of UL/DL thresholds for new call or bearer admission can be defined for up to 4 ARP
priority classes, where a priority class is defined as a range of ARPs and the PRB threshold is the
maximum percentage of PRBs consumed.
- A separate UL/DL threshold pair is used for call re-establishment and incoming mobility.
38
Avoid selecting UE's with VoIP bearer for preventive offload
• Enables the operator to improve VoIP user experience by selecting non-VoIP (that is, non-QCI1)
bearers/UEs before selecting QCI1 bearers/UEs for preventive offload and load equalization. For
example, this may be activated on the layer with the best coverage in a network with multiple
carriers.
• PRB usage counter improvements

• The feature also improves some existing PM counters so that PRB usage is monitored not only after
the PRB CAC is hit, but all the time.
39
40
AGENDA
1. eMCTA

3. Annex
41
• LR14.1 171193 NETWORK ACCESSIBILITY IMPROVEMENTS WITH REDIRECTION/DE-
PRIORITIZATION AT CALL ADMISSION
• Redirection at Call Admission:
• When the cell/eNB cannot accept a call, redirect it to another carrier/RAT using eMCTA
• De-prioritization IE in RRC Connection Reject
• Support of Rel-11 IE Deprioritization Req in RRC Connection Reject message, for either current LTE
carrier, or LTE altogether
42
Item#1: Redirection upon CAC failure
In our current implementation, when an incoming RRC connection request cannot be accepted due to
resource exhaustion in the cell, the attempt is simply rejected (RRCConnectionReject message is sent to
the UE with waitTime IE set). This makes UE most of the time try to connect again to the same cell after
waitTime seconds.
Redirection on CAC failure will allow to redirect the UE to another RAT/frequency if it cannot be admitted.
Blind redirection is performed in order to speed up the procedure and limit the duration of the RRC
connection in the eNB. If no suitable RAT frequency can be found, RRC connection is released.
43
Item#2: RRC Reject with de-prioritization
3GPP has introduced in release 11 an additional IE in RRCConnectionReject message,being

deprioritisationReq-r11. This IE forces the UE to set lowest reselection priority for either the frequency
selected by the UE or for all E-UTRAN frequencies. This applies for a given duration provided in the IE.
Reselection of another frequency or RAT by the UE will then be favored during this time.
De-prioritization is triggered by the eNB in two different use cases:

1. When an incoming RRC connection request is rejected due to CAC failure
2. When the eNB is in overload
Dedicated parameters allows to configure the type of de-prioritization applied (the serving frequency or all
LTE ones de-prioritized), and the duration of the deprioritization for both use cases.
RRC De-prioritization and Redirection at CAC are mutually exclusive
44
AGENDA
1. eMCTA

3. Annex
45
ANNEX
46

ALU LTE LB Workshop

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ALU LTE LB Workshop

Caricato da

Copyright:

Formati disponibili

ALCATEL-LUCENT

LTE EMCTA & LOAD BALANCING WORKSHOP

COPYRIGHT © 2014 ALCATEL-LUCENT. ALL RIGHTS RESERVED.

2. LA5 –> LR14.1 load balancing features

Only one single best carrier is

Priority (0-lowest to 7-highest)

Whether a Measurement Gap needs to be configured (yes/no)

[0..1] [0..1] [0..1] [0..1]

LteNeighboring UtraNeighboring GeranNeighboring HrpdNeighboring

[1..9] [0..16] [0..16] [0..3]

MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable MobilityPriorityTable

2. LA5 –> LR14.1 load balancing features

2. LA5 –> LR14.1 load balancing features

filterCoeff: Current number of connected UEs in cell / maxNbrOfUsers

2. LA5 –> LR14.1 load balancing features

Each criterion can be activated independently

• UEs with high priority can be out of the selection

• UEs with a VoLTE call can be preferred to offload last

1. Preventive offload trigger will invoke eMCTA;

3. UE measurements are configured with candidate frequency(ies), using event A4 (neighbor

4. Upon reception of UE measurement report, target cell is NOT considered if it is loaded.

5. If target cell is identified as not loaded, inter-frequency handover is attempted.

Load Comparison with Target Carrier/Cell

Neighbor cell filtering – How neighbor cell load info is used

• If the target cell is considered ‘not loaded’,

• Else (load balancing is triggered by other criteria)

Neighbor cell filtering – How neighbor cell load info is used

• If the target cell is considered ‘not loaded’,

• Else (load balancing is triggered by other criteria)

2. LA5 –> LR14.1 load balancing features

Blind Inter-Frequency Preventive Offload:

• When a UE A4 Measurement report is received for preventive offload, if:

- Works intra-band and inter-band

2. LA5 –> LR14.1 load balancing features

- One configurable average DL throughput threshold per non-GBR QCI

1) Real PRB consumption is above a configurable threshold

2. LA5 –> LR14.1 load balancing features

Per neighbor carrier Preventive Load balancing:

Each LTE neighbor carrier is assigned to one of up to 3 sets of thresholds

Number of UE as criterion for Load balancing

• Number of connected mode users per cell

• Multiple priority levels for Call Admission

Avoid selecting UE's with VoIP bearer for preventive offload

• PRB usage counter improvements

2. LA5 –> LR14.1 load balancing features

• Redirection at Call Admission:

• De-prioritization IE in RRC Connection Reject

Item#1: Redirection upon CAC failure

Item#2: RRC Reject with de-prioritization

3GPP has introduced in release 11 an additional IE in RRCConnectionReject message,being

De-prioritization is triggered by the eNB in two different use cases:

RRC De-prioritization and Redirection at CAC are mutually exclusive

2. LA5 –> LR14.1 load balancing features

Potrebbero piacerti anche