MLB in LTE

0
System Engineering
LTE MLB - Design
Document
Author: Unknown User (cwilliams)

Version: 148
Date: 2014.06.26
LTE MLB - Design Document v148
TABLE OF CONTENTS
1 References .........................................8
2 LTE Load balancing Algorithm Overview ..............9
3 LTE Load balancing Flow Chart .....................10
4 LTE Loading Algorithm Metrics (1.1) ...............12

4.1 Nokia Networks ............................................................................................................. 12
4.2 Ericsson ......................................................................................................................... 14
4.3 Huawei............................................................................................................................ 14
4.4 Alcatel Lucent ................................................................................................................ 15
5 Uplink Noise Measurements (2.1) ...................18

5.1 Nokia Networks ............................................................................................................. 18
5.2 Ericsson Networks ........................................................................................................ 19
5.3 Huawei Networks ........................................................................................................... 19
5.4 Alcatel Lucent Networks ............................................................................................... 19
6 Performance Metrics (2.9, 2.10) ...................21

6.1 Nokia Networks ............................................................................................................. 21
6.3 Huawei Networks ........................................................................................................... 23
6.4 Alcatel Lucent ................................................................................................................ 24
7 Neighbor Cells Measurements (1.5, 1.6) ............27
REFERENCES - NOKIA NETWORKS 1

7.1 Nokia Networks............................................................................................................. 27
7.2 Ericsson ......................................................................................................................... 27
7.3 Huawei............................................................................................................................ 27
7.4 Alcatel Lucent ................................................................................................................ 28
8 Default Eden-Net Criteria for Cell Overload (1.2) .29

8.1 Source ............................................................................................................................ 29
8.1.1 Nokia Networks ............................................................................................................... 29
8.1.2 Ericsson Networks ........................................................................................................... 29
8.1.3 Huawei Networks............................................................................................................. 29
8.2 Target ............................................................................................................................. 30

8.2.1 Nokia Networks ............................................................................................................... 30
8.2.3 Huawei Networks............................................................................................................. 30
9 Criteria for Cell Underload (1.21) ................31

9.1 Source ............................................................................................................................ 31
9.1.1 Nokia Networks ............................................................................................................... 31
9.1.3 Huawei Networks............................................................................................................. 31
9.2 User Defined Thresholds .............................................................................................. 32
10 T-Mobile Criteria for Cell Overload (1.3) .........34

10.2 Nokia Networks ............................................................................................................. 34
10.3 Target ............................................................................................................................. 35

10.3.1 Nokia Networks ............................................................................................................... 35
10.4 User Defined Thresholds .............................................................................................. 35
11 Neighbor Cell Weighting (1.7, 2.5) ................37

11.1 Cell Weighting Calculation: .......................................................................................... 38
11.1.1 Nokia ............................................................................................................................... 38
11.1.2 Ericsson .......................................................................................................................... 38

11.1.3 Huawei ............................................................................................................................ 38

11.1.4 ALU ................................................................................................................................. 39
12 Dedicated Mode Parameter Settings for Offloading

(1.8) 40
12.1 Adjusted CIO Parameters ............................................................................................. 40
12.1.1 Nokia Network ................................................................................................................. 40
12.1.2 Ericsson Network............................................................................................................. 40
12.1.3 Huawei Network .............................................................................................................. 41
12.1.4 Alcatel Lucent Network .................................................................................................... 41
12.2 Adjusted Trigger Threshold Parameters...................................................................... 41

12.2.1 Nokia Networks ............................................................................................................... 41
12.2.2 Ericsson .......................................................................................................................... 41
12.2.3 Huawei Networks............................................................................................................. 42
12.2.4 Alcatel Lucent Networks .................................................................................................. 42
13 Idle Mode Parameter Settings for Offloading (1.8) .43

13.1 Offset Parameters Adjusted.......................................................................................... 43
13.1.1 Nokia Networks ............................................................................................................... 43
13.1.3 Huawei Networks............................................................................................................. 44
13.2 sIntrasearch Thresholds Adjusted ............................................................................... 44

13.2.1 Nokia Networks ............................................................................................................... 44
13.2.3 Huawei Networks............................................................................................................. 45
14 Uplink Noise Threshold Calculation (2.2) ..........46
15 Reducing Offsets (2.3) ............................47
16 Increase Offsets (2.6) ............................48
17 Performance Triggers (2.10) .......................49

17.1 Nokia Networks ............................................................................................................. 49

17.3 Huawei Networks ........................................................................................................... 49
18 Reporting .........................................51
19 System Delay (2.11) ...............................52
20 PM Counter Requirements ...........................55
21 Load Balancing Flow Diagram .......................64
22 PM scanners enabled in T Mobile's Ericsson ........65
23 Test Plans ........................................68

23.1 Current test plans, Aug 15, 2014 .................................................................................. 68

 References
 LTE Load balancing Algorithm Overview
 LTE Load balancing Flow Chart
 LTE Loading Algorithm Metrics (1.1)
o Nokia Networks
o Ericsson
o Huawei
o Alcatel Lucent
 Uplink Noise Measurements (2.1)
o Nokia Networks
o Ericsson Networks
o Huawei Networks
o Alcatel Lucent Networks
 Performance Metrics (2.9, 2.10)
o Nokia Networks
o Ericsson Networks
o Huawei Networks
o Alcatel Lucent
 Neighbor Cells Measurements (1.5, 1.6)
o Nokia Networks
o Ericsson
o Huawei
o Alcatel Lucent
 Default Eden-Net Criteria for Cell Overload (1.2)
o Source
 Nokia Networks
 Ericsson Networks
 Huawei Networks
o Target
 Nokia Networks
 Huawei Networks

 Criteria for Cell Underload (1.21)

o Source
 Nokia Networks
 Huawei Networks
o User Defined Thresholds
 T-Mobile Criteria for Cell Overload (1.3)
o Ericsson Networks
o Nokia Networks
 Target
o Nokia Networks
 User Defined Thresholds
 Neighbor Cell Weighting (1.7, 2.5)

o Cell Weighting Calculation:
 Nokia
 Ericsson
 Huawei
 ALU
 Dedicated Mode Parameter Settings for Offloading (1.8)
o Adjusted CIO Parameters
 Nokia Network
 Ericsson Network
 Huawei Network
 Alcatel Lucent Network
o Adjusted Trigger Threshold Parameters
 Nokia Networks
 Ericsson
 Huawei Networks
 Alcatel Lucent Networks

 Idle Mode Parameter Settings for Offloading (1.8)

o Offset Parameters Adjusted

 Nokia Networks
 Huawei Networks
o sIntrasearch Thresholds Adjusted
 Nokia Networks
 Huawei Networks
 Uplink Noise Threshold Calculation (2.2)
 Reducing Offsets (2.3)
 Increase Offsets (2.6)
 Performance Triggers (2.10)
o Nokia Networks
o Ericsson Networks
o Huawei Networks
 Reporting
 System Delay (2.11)
 PM Counter Requirements

1 REFERENCES
Eden-NET 4G Metrics - ALU - Initial Formulas

2 LTE LOAD BALANCING

ALGORITHM OVERVIEW
The LTE load balancing module detects cells within the LTE network that exceed the loading
threshold triggers for accessibility failures and cell loading. When congested cells are detected, the
module attempts to reduce congestion by moving idle mode users on the congested cell and
dedicated users in the congested cell to neighbor cells within the same frequency layer.
The LTE load balancing module does this through:
- Making adjustments to neighbor cell offset parameters used in both dedicated and idle mode.
- Making adjustments to handover thresholds.
- TBD: Decreasing total power used in the cell. (This part of the algorithm will not be
implemented yet. Currently for all RAN vendors object locking is required before the cell power can
be adjusted. This causes a temporary outage)
The module examines the loading on neighbor cells and attempts to distribute load among target
neighbor cells. Based on handover metrics the module will continually measure the load on the top
filtered neighbors and will adjust individual offsets per neighbor pair to allow priority selection in UE
offload to these neighbor cells.
The module will monitor the handover success rate for each handover pair to ensure that the most
suitable neighbors are selected as target cells for sharing the excess load on the source cell. The
module will ensure that corrective actions do not cause the neighbors cells themselves to become
congested.
The module continually monitors the load of the neighbor cells to ensure that the UE offloading
(particularly for dedicated mode UEs) does not cause the target neighbor cells to become
congested. If this occurs, other neighbor cells will be made more attractive (through offset
adjustments), so that offloading decreases to the loaded target cell.
Once loading consistently decreases over a set number of periods, the module returns all
parameters to the original operator defined settings.
LTE LOAD BALANCING ALGORITHM OVERVIEW - NOKIA NETWORKS 9

3 LTE LOAD BALANCING F LOW

CHART
LTE LOAD BALANCING FLOW CHART - NOKIA NETWORKS 10

LTE LOAD BALANCING FLOW CHART - NOKIA NETWORKS 11

4 LTE LOADING ALGORITHM

METRICS (1.1)
Load detection in LTE utilizes the following metrics:
 Average Physical Resource Block (PRB) usage over the measurement period
 eNB Buffer Delay per QCI
 Uplink interference
 Traffic DL Volume
 Average active UEs with data in the eNB buffer.
 DRB access success rate
 RRC setup failure due to Radio Access Control
 E-Rab failure due to resource failure
4.1 Nokia Networks
Metric Calculation
Average avg(PDCP_RET_DL_DEL_MEAN_QCI_1)
Latency
Downlink for
QCI1 DRBs
(msec)
[Avg_Lat_Q
C1]
Average ( LNCEL.PDCP_RET_DL_DEL_MEAN_NON_GBR)
Latency
Downlink for
non GBR
DRBs
(msec)
[Avg_lat_All
_QCI ]
LTE LOADING ALGORITHM METRICS (1.1) - NOKIA NETWORKS 12

Metric Calculation
% DL PRB ( LNCEL.DL_PRB_UTIL_TTI_MEAN)/10
Utilization
[%_DL_PR
B_Util]
RRC 100*(SIGN_CONN_ESTAB_FAIL_RRMRAC
Connection /(SIGN_CONN_ESTAB_ATT_MO_S+SIGN_CONN_ESTAB_ATT_MT+SIGN_CON
Setup N_ESTAB_ATT_MO_D+SIGN_CONN_ESTAB_ATT_OTHERS+SIGN_CONN_EST
Failure Rate AB_ATT_EMG))
- Radio
Access
Control
[RRC_Conn
_Stp_Fail_R
AC]
E-RAB 100*(EPS_BEARER_SETUP_FAIL_RESOUR)
Failure Rate /(EPS_BEARER_SETUP_ATTEMPTS)
- Resource
Failure
[ERAB_Fail
_Resource]
DL Traffic (PDCP_SDU_VOL_DL)
Volume
(byte)
Average ( LNCEL.DL_UE_DATA_BUFF_AVG)/100
Active UEs
with data in
the DL
buffer
[Avg_Act_U
ser]
"lncel.rrc_conn_ue_avg": "LTE_Cell_Load.M8001C199"
Average
RRC
 Not to be used now.It is valid for upcoming features
Connected
Users
[RRC_Conn
ected_UE]
LTE LOADING ALGORITHM METRICS (1.1) - NOKIA NETWORKS 13

4.2 Ericsson
Metric Calculation
Average Latency for All QCI (Summation of i from 0 to 255 of (pmPdcpLatTimeDlQci_[i]) /

(msec) (Summation of i from 0 to 255 of (pmPdcpLatPktTransDlQci_[i])
[Avg_Lat_All_QCI]
Average Downlink Latency for pmPdcpLatTimeDlQci_1 / pmPdcpLatPktTransDlQci_1

QCI 1 (msec)
[Avg_Lat_QCI1]
% DL PRB Utilization 100 * ((pmPrbUsedDlDtch) / (nvl(pmPrbAvailDl) -

nvl(pmPrbUsedDlBcch) - nvl(pmPrbUsedDlPcch) -
[%_DL_PRB_Util]
nvl(pmPrbUsedDlSrbFirstTrans))))
RRC Connection Setup Failure 100* (nvl(pmRrcConnEstabFailBearerAdmissionRej) /

Rate nvl(pmRrcConnEstabAtt))
- Load Admission Control
[RRC_Conn_Stp_Fail_RAC]
Average Active users per TTI pmActiveUeDlSum

in DL
[Avg_Act_User]
DL Traffic Volume (MB) (pmPdcpVolDlDrbTrans)/(8*1024)

[DL_Traffic_Vol]
E-RAB Failure Rate - Resource (nvl(pmErabEstabFailGbrDlEnb) +

Failure nvl(pmErabEstabFailGbrUlEnb)) / nvl(pmErabEstabSuccInit)
[ERAB_Fail_Resource]
Average RRC Connected safe_divide(pmRrcConnLevSum, pmRrcConnLevSamp)

Users
*Not to be used now.It is valid for upcoming features
[RRC_Connected_UE]
4.3 Huawei
Metric Description Calculation
LTE LOADING ALGORITHM METRICS (1.1) - ERICSSON 14

[Avg_Lat_QC1] Average Latency (L.Traffic.DL.PktDelay.Time.QCI.1) /

Downlink for (L.Traffic.DL.PktDelay.Num.QCI.1)
QCI1 DRBs
(msec)
[Avg_Lat_Non_GBR] Average Latency Maximum of (L.Traffic.DL.PktDelay.Time.QCI.6

Downlink for non / L.Traffic.DL.PktDelay.Num.QCI.6,
GBR DRBs
L.Traffic.DL.PktDelay.Time.QCI.7 /
(msec)
L.Traffic.DL.PktDelay.Num.QCI.7,
L.Traffic.DL.PktDelay.Num.QCI.8,
L.Traffic.DL.PktDelay.Num.QCI.9)
[%_DL_PRB_Util] % DL PRB 1526726740_L.ChMeas.PRB.DL.Used.Avg

Utilization
[RRC_Conn_Stp_Fail_RAC] RRC Connection 100 * (1526727083.L.RRC.SetupFail.ResFail) /

Setup Failure (1526728216.L.RRC.ConnSetup)
Rate - Radio
Access Control
[ERAB_Fail_Resource] E-RAB Failure 100 * (1526728279.L.E-

Rate - Resource RAB.FailEst.NoRadioRes) / (1526727545.L.E-
Failure RAB.AttEst)
[Avg_Act_User] Average Active 1526727384.L.Traffic.User.DLData.Avg

UEs with data in
the DL buffer
[DL_Traffic_Vol] DL Traffic Volume 1526728261.L.Thrp.bits.DL

(MB)
4.4 Alcatel Lucent
Metric Descriptio Calculation

n
LTE LOADING ALGORITHM METRICS (1.1) - ALCATEL LUCENT 15


n
[Avg_Lat_QC1] Average (VS.DLPdcpPduDelay.QCI1.Cum /

Latency VS.DLPdcpPduDelay.QCI1.NbEvt)
Downlink
for QCI1
DRBs
(msec)
[Avg_Lat_Non_GBR] Average Max( (VS.DLPdcpPduDelay.QCI6.Cum /

Latency VS.DLPdcpPduDelay.QCI6.NbEvt),
Downlink (VS.DLPdcpPduDelay.QCI7.Cum /
for non VS.DLPdcpPduDelay.QCI7.NbEvt),
GBR DRBs
(VS.DLPdcpPduDelay.QCI8.Cum /
(msec)
VS.DLPdcpPduDelay.QCI8.NbEvt),
(VS.DLPdcpPduDelay.QCI9.Cum /
VS.DLPdcpPduDelay.QCI9.NbEvt) )
[%_DL_PRB_Util] % DL PRB (VS.DLPRBUsed.Cum / VS.DLPRBUsed.NbEvt)

Utilization
[RRC_Conn_Stp_Fail_RA RRC 100 * (RRC.ConnEstabFail.CACFailure +

C] Connection RRC.ConnEstabFail.UnexpectedResourceDepletion) /
Setup (RRC.ConnEstabSucc.Sum + RRC.ConnEstabFail.Sum)
Failure
Rate -
Radio
Access
Control
[ERAB_Fail_Resource] E-RAB 100 * (VS.ERABSetupFailed.CACFailure +

Setup VA.ERABSetupFailued.OveroadCondition) /
Failure ($LTE_eRAB_Setup_Attempts$)
Rate -
Resource
Failure
[Avg_Act_User] Average (VS.NbSimultaneousTransmittingUEInDL.GBR.Cum

Active UEs +
with data in VS.NbSimultaneousTransmittingUEInDL.NonGBR.C
the DL um) /
buffer
(VS.NbSimultaneousTransmittingUEInDL.GBR.NbEvt
+
VS.NbSimultaneousTransmittingUEInDL.NonGBR.N
bEvt)


n
[DL_Traffic_Vol] DL Traffic (VS.DLPdcpPduSentByPdcp.QCI1 +

Volume VS.DLPdcpPduSentByPdcp.QCI2 +
(MB) VS.DLPdcpPduSentByPdcp.QCI3 +
VS.DLPdcpPduSentByPdcp.QCI4 +
VS.DLPdcpPduSentByPdcp.QCI9) Not in Bytes...
(VS.DLRlcPduKbytes.VoIP +
VS.DLRlcPduKbytes.OtherGBR +
VS.DLRlcPduKbytes.NonGBR) * 1024/1000000
1. "Converted from KiBytes to MByte"
2. "Pdcp bytes does not appear to be available, so
replacing with Rlc bytes"

5 UPLINK NOISE
MEASUREMENTS (2.1)
Changing cell individual offsets will artificially shrink the source cell footprint and cause the UEs that
should be connected to the source cell to be connected to the neighbor cell although being closer
(in terms of RF) to the source cell. This
will result in a rise in UL interference. The algorithm will require that the uplink is monitored. If the
rise in uplink interference rises above a user defined threshold then the offsets shown in table for
dedicated and idle mode will be reduced by 1dB.
The counter used are as follows:
5.1 Nokia Networks
Metric Calculation
% Bad PUSCH SINR 100*((SINR_PUSCH_LEVEL_1 + SINR_PUSCH_LEVEL_2 +

SINR_PUSCH_LEVEL_3 + SINR_PUSCH_LEVEL_4 +
[%_B_PUSCH_SNR]
SINR_PUSCH_LEVEL_7 )/( SINR_PUSCH_LEVEL_1 +
SINR_PUSCH_LEVEL_22))
UPLINK NOISE MEASUREMENTS (2.1) - NOKIA NETWORKS 18

5.2 Ericsson Networks
Metric Calculation
% Bad PUSCH SINR 100*((pmSinrPuschDistr_0 + pmSinrPuschDistr_1 +

pmSinrPuschDistr_2)/(pmSinrPuschDistr_0 + pmSinrPuschDistr_1 +
[%_B_PUSCH_SNR]
pmSinrPuschDistr_2 + pmSinrPuschDistr_3 + pmSinrPuschDistr_4 +
pmSinrPuschDistr_5 + pmSinrPuschDistr_6 + pmSinrPuschDistr_7))
5.3 Huawei Networks
[%_B_PUSCH_SNR] Interference and Noise L.UL.Interference.Avg

Received by Each
1. No distribution counters counters available,
PRB in a Cell
need to develop workaround for current design
2. Go ahead and implement as is, and we can
play with the thresholding and see how it looks.
This may require an algorithm change.
5.4 Alcatel Lucent Networks
[%_B_PUSCH_SNR] Interference and 100 * (VS.ULNoiseAllPRBs.LeRg1) /

Noise Received (VS.ULNoiseAllPRBs.LeRg1 +
by Each PRB in a VS.ULNoiseAllPRBs.GtRg1LeRg2 +
Cell VS.ULNoiseAllPRBs.GtRg2LeRg3 +
VS.ULNoiseAllPRBs.GtRg3LeRg4 +
VS.ULNoiseAllPRBs.GtRg4),
1.
a. Different bin definitions from other vendor.
Will need calibrated for default thresholds.
UPLINK NOISE MEASUREMENTS (2.1) - ERICSSON NETWORKS 19


b. What is the reference for the bins? mW?
dBm? something else?
c. Need real data to analyze effectiveness of UL
Noise all PRB vs avg of UL Noise on PUSCH
PRBs
UPLINK NOISE MEASUREMENTS (2.1) - ALCATEL LUCENT NETWORKS 20

6 PERFORMANCE METRICS
(2.9, 2.10)
The performance metrics are used to assess performance degradation on the target cells only. This
will allow the algorithm to reduce the offsets to mitigate any negative impacts if needed.
6.1 Nokia Networks
Metric Calculation
Intra eNB 100-(100*(INTRA_F_HO_SUCC_NB)/(INTRA_F_HO_ATT_NB)))

HO
For the Target to Source pairs only. If the Target to Source attempts are Zero, treat
Execution
the failure rate as Zero.
Failure Rate
[Intra_F_HO
_FR]
RRC 100*(SIGN_CONN_ESTAB_FAIL_RRMRAC
Connection /(SIGN_CONN_ESTAB_ATT_MO_S+SIGN_CONN_ESTAB_ATT_MT+SIGN_CON
Setup N_ESTAB_ATT_MO_D+SIGN_CONN_ESTAB_ATT_OTHERS+SIGN_CONN_EST
Failure Rate AB_ATT_EMG))
- Radio
Access
Control
[RRC_Conn
_Stp_Fail_R
AC]
E-RAB Drop 100*([EPC_EPS_BEARER_REL_REQ_RNL])

Rate /([EPC_EPS_BEARER_REL_REQ_NORM]+[EPC_EPS_BEARER_REL_REQ_DE
Initiated TACH]+[EPC_EPS_BEARER_REL_REQ_RNL]+
EPC Radio
[EPC_EPS_BEARER_REL_REQ_OTH]
Network
+[ENB_EPSBEAR_REL_REQ_RNL_REDIR]+[ENB_EPS_BEARER_REL_REQ_N
[ERAB_DR ORM] +[ENB_EPS_BEARER_REL_REQ_RNL]+
OPRATE]
[ENB_EPS_BEARER_REL_REQ_TNL]+[ENB_EPS_BEARER_REL_REQ_OTH])
($eRAB_Voice_Drops$) / ($eRAB_Voice_Call_Initiated$)
[eRAB_Voic
PERFORMANCE METRICS (2.9, 2.10) - NOKIA NETWORKS 21

Metric Calculation
e_Drop_Rat
e]
Average $Avg_Lat_QC1$
Latency
Downlink for
QCI1 DRBs
(msec)
[Avg_Lat_Q
C1]
Average $Avg_Lat_Non_GBR$
Latency
Downlink for
non GBR
DRBs
(msec)
[Avg_Lat_N
on_GBR]
Metric Calculation
LTE Mobility Success Rate 100 * [ ( pmHoPrepSuccLteIntraF) / ( pmHoPrepAttLteIntraF )] *

[ ( pmHoExeSuccLteIntraF ) / ( pmHoExeAttLteIntraF )]
[Intra_HO_FR]
For the Target to Source pairs only. If the Target to Source
attempts are Zero, treat the failure rate as Zero.
eRAB_Drop_Rate = ($eRAB_Drops$) /
ERAB Drop Rate - All QCI (%)
($eRAB_Disconnections$)
[ERAB_DROPRATE]
[eRAB_Voice_Drop_Rate] ($eRAB_Voice_Drops$) / ($eRAB_Voice_Call_Initiated$)

RRC Connection Setup Failure 100* (nvl(pmRrcConnEstabFailBearerAdmissionRej) /
Rate nvl(pmRrcConnEstabAtt))
- Load Admission Control
[RRC_Conn_Stp_Fail_RAC]
Average Latency for All QCI $Avg_Lat_All_QC1$
(msec)
[Avg_Lat_All_QCI]
Average Downlink Latency for $Avg_Lat_QC1$
PERFORMANCE METRICS (2.9, 2.10) - ERICSSON NETWORKS 22

Metric Calculation
QCI 1 (msec)
[Avg_Lat_QCI1]
6.3 Huawei Networks

n
[Intra_F_HO_FR] Intra eNB 100-

HO (100*(INTRA_F_HO_SUCC_NB)/(INTRA_F_HO_ATT_
Execution NB)))
Failure
For the Target to Source pairs only. If the Target to
Rate
Source attempts are Zero, treat the failure rate as Zero.
[RRC_Conn_Stp_Fail_RA RRC 100 * (1526727083.L.RRC.SetupFail.ResFail) /

C] Connection (1526728216.L.RRC.ConnSetup)
Setup
Failure
Rate -
Radio
Access
Control
[ERAB_DROPRATE] E-RAB 100*(1526727546.L.E-

Drop Rate RAB.AbnormRel+1526728292.L.E-
Initiated RAB.AbnormRel.MME ) / (1526727546.L.E-
EPC Radio RAB.AbnormRel+1526728292.L.E-
Network RAB.AbnormRel.MME +1526727547.L.E-RAB.NormRel
))
[Avg_Lat_QC1] Average $Avg_Lat_QC1$

Latency
Downlink
for QCI1
DRBs
(msec)
[Avg_Lat_Non_GBR] Average $Avg_Lat_Non_GBR$

Latency
Downlink
for non
PERFORMANCE METRICS (2.9, 2.10) - HUAWEI NETWORKS 23


n
GBR DRBs
(msec)
6.4 Alcatel Lucent

n
[Intra_F_HO_FR] Intra eNB 100 - (100 * ($INTRA_F_HO_SUCC_NB$) /

HO ($INTRA_F_HO_ATT_NB$)))
Execution
For the Target to Source pairs only. If the Target to Source
Failure
attempts are Zero, treat the failure rate as Zero.
Rate
[RRC_Conn_Failure_R RRC 100 * (RRC.ConnEstabFail.Sum) /

ate] Connectio (RRC.ConnEstabSucc.Sum + RRC.ConnEstabFail.Sum)
n Setup
Failure
Rate
LTE_eRAB_Drops LTE E- VS.AbnormalERABReleasePerQCI.QCI1

RAB + VS.AbnormalERABReleasePerQCI.QCI2
Drops + VS.AbnormalERABReleasePerQCI.QCI3
+ VS.AbnormalERABReleasePerQCI.QCI4
+ VS.AbnormalERABReleasePerQCI.CustomerQCIs
+ VS.OtherAbnormalERABReleasePerQCI.QCI1
+ VS.OtherAbnormalERABReleasePerQCI.CustomerQCIs
+ VS.ERABReleasedDueToRadioLinkFailurePerQCI.QCI1
PERFORMANCE METRICS (2.9, 2.10) - ALCATEL LUCENT 24


n
+
VS.ERABReleasedDueToRadioLinkFailurePerQCI.Custom
erQCIs
LTE_eRAB_NormalRel LTE E- VS.NormalERABRelease.QCI1

RAB + VS.NormalERABRelease.QCI2
Normal + VS.NormalERABRelease.QCI3
Releases + VS.NormalERABRelease.QCI4
+ VS.NormalERABRelease.QCI5
+ VS.NormalERABRelease.CustomerQCI
[ERAB_DROPRATE] E-RAB 100 * (LTE_eRAB_Drops /. (LTE_eRAB_Drops +

Drop Rate LTE_eRAB_NormalRel))
Initiated
EPC
Radio
Network
[ERAB_DROPRATE] E-RAB 100 * (VS.OtherAbnormalERABReleasePerQCI +

Drop Rate VS.AbnormalERABReleasePerQCI +
Initiated VS.ERABReleasedDueToRadioLinkFailurePerQCI) /
EPC
(VS.OtherAbnormalERABReleasePerQCI +
Radio
VS.AbnormalERABReleasePerQCI +
Network
VS.ERABReleasedDueToRadioLinkFailurePerQCI +
VS.NormalERABRelease.QCI +
VS.ERABReleaseResponseERABReleaseSuccess)
Are these distinct categories, or are we double counting
some? Is this complete with including UTRAN initiated and
MME initiated releases?
[Avg_Lat_QC1] Average $Avg_Lat_QC1$

Latency
Downlink


n
for QCI1
DRBs
(msec)
[Avg_Lat_Non_GBR] Average $Avg_Lat_Non_GBR$

Latency
Downlink
for non
GBR
DRBs
(msec)

7 NEIGHBOR CELLS
MEASUREMENTS (1.5, 1 .6)
The following counters are used to determine the number of handover attempts per neighbor cell
pair, at least one weeks worth of data will need to be collected:
7.1 Nokia Networks
Description Metric Name KPI Equation
Handover attempts per INTRA_F_HO_ATT_NB INTRA_HO_ATT_NB (M8015C1) +

neighbor cell INTER_HO_ATT_NB (M8015C8)
Handover successes INTRA_F_HO_SUCC_NB INTRA_HO_SUCC_NB (M8015C2) +

per neighbor cell INTER_HO_SUCC_NB (M8015C9)
7.2 Ericsson
Metric Metric Name KPI Equation
Intra frequency Handover attempts per INTRA_F_HO_ATT_NB pmHoExeAttLteIntraF

neighbor cell
Intra frequency Handover successes per INTRA_F_HO_SUCC_NB pmHoExeSuccLteIntraF

neighbor cell
7.3 Huawei
NEIGHBOR CELLS MEASUREMENTS (1.5, 1.6) - NOKIA NETWORKS 27

Intra frequency Handover INTRA_F_HO_ATT_NB 1526727294_L.HHO.NCell.ExecAttOut

attempts per neighbor cell
Intra frequency Handover INTRA_F_HO_SUCC_NB 1526727295_L.HHONCell.ExecSuccOut

successes per neighbor cell
7.4 Alcatel Lucent
Intra INTRA_F_HO_ATT_NB VS.OutgoingIntraFrequencyHOMobilityEventPerRelation

frequency
Handover
attempts
per
neighbor
cell
Intra INTRA_F_HO_SUCC_NB VS.OutgoingIntraFrequencyHOMobilityEventPerRelation

frequency - (HO.IntraFreqOutFail.TooEarly +
Handover HO.IntraFreqOutFail.TooLate +
successes HO.IntraFreqOutFail.ToWrongCell)
per
neighbor
cell
For Nokia and ALU the success rate is calculated as:

Intra_F_HO_SR = Handover Success Rate = 100*($INTRA_F_HO_SUCC_NB$/
$INTRA_F_HO_ATT_NB$)
similarly Ericsson is calculated as follows:
similarly Huawei is calculated as follows:
NEIGHBOR CELLS MEASUREMENTS (1.5, 1.6) - ALCATEL LUCENT 28

8 DEFAULT EDEN-NET
CRITERIA FOR CELL
OVERLOAD (1.2)
8.1 Source
A Source cell is considered overloaded if the following criteria is fulfilled:
8.1.1 Nokia Networks

if (((%_DL_PRB_Util > PRB_Userdefinedthreshold) and ((Avg_Lat_QC1 > BufferDelay_QCI1) or
(Avg_Lat_Non_GBR > BufferDelay_NonGBR))) or (RRC_Conn_Stp_Fail_RAC >
Userdefined_L_RAC) or ( ERAB_Fail_Resource > Userdefined_Erab))
{ Cell_Overload = true; }
Except any cell with Avg_Act_User < Low_Users
Low_Users default = 4
8.1.2 Ericsson Networks

(Avg_Lat_All_QCI) > BufferDelay_NonGBR)) or (RRC_Conn_Stp_Fail_RAC >
Userdefined_L_RAC) or ( ERAB_Fail_Resource > Userdefined_Erab ))
Note: Ericsson buffer delay counters to not work correctly for measuring user latency, as the
measurement only trigger when the buffer is empty.
8.1.3 Huawei Networks

(Avg_Lat_Non_GBR > BufferDelay_NonGBR))) or (RRC_Conn_Stp_Fail_RAC >
Userdefined_L_RAC) or ( ERAB_Fail_Resource > Userdefined_Erab))
DEFAULT EDEN-NET CRITERIA FOR CELL OVERLOAD (1.2) - SOURCE 29


8.2 Target
A Target cell is considered overloaded if the following criteria is fulfilled:

if (((%_DL_PRB_Util > PRB_Userdefinedthreshold) OR ((Avg_Lat_Non_GBR >
BufferDelay_NonGBR) or (RRC_Conn_Stp_Fail_RAC > Userdefined_L_RAC) or (
ERAB_Fail_Resource > Userdefined_Erab))

if (((%_DL_PRB_Util > PRB_Userdefinedthreshold) OR ((Avg_Lat_All_QCI >
BufferDelay_NonGBR) or (RRC_Conn_Stp_Fail_LAC > Userdefined_L_RAC) or (
ERAB_Fail_Resource > Userdefined_Erab ))

if (((%_DL_PRB_Util > PRB_Userdefinedthreshold) OR ((Avg_Lat_All_QCI >
BufferDelay_NonGBR) or (RRC_Conn_Stp_Fail_LAC > Userdefined_L_RAC) or (
ERAB_Fail_Resource > Userdefined_Erab ))
DEFAULT EDEN-NET CRITERIA FOR CELL OVERLOAD (1.2) - TARGET 30

9 CRITERIA FOR CELL

UNDERLOAD (1.21)
9.1 Source
A Source cell is considered underloaded if the following criteria is fulfilled:
if (((%_DL_PRB_Util < PRB_exit_threshold) and ((Avg_Lat_QC1 > BufferDelay_QCI1_exit) or

(Avg_Lat_Non_GBR > BufferDelay_NonGBR_exit)))
{ Cell_Underload = true; }
if (((%_DL_PRB_Util > PRB_exit_threshold)
CRITERIA FOR CELL UNDERLOAD (1.21) - SOURCE 31

if (((%_DL_PRB_Util < PRB_exit_threshold) and ((Avg_Lat_QC1 > BufferDelay_QCI1_exit) or

(Avg_Lat_Non_GBR > BufferDelay_NonGBR_exit)))
9.2 User Defined Thresholds

PRB_threshold - This parameter allows the user to define a trigger threshold for setting of PRB
occupancy over a measurement period.
Range : 0 to 100%
Steps size : 1%
Default: 80%
BufferDelay_QCI1 - This parameter defines the maximum amount of time data scheduled for a user
is allowed to be delayed within the eNB. As the eNB loads per cell the delays for transmission of
data will increase and eventual exceed the this threshold indicating overload.
Range: 10 to 100 ms
Step size : 5ms
Default : 20 ms
BufferDelay_NonGBR - This parameter defines the maximum amount of time data scheduled for a
user is allowed to be delayed within the eNB. As the eNB loads per cell the delays for transmission
of data will increase and eventual exceed the this threshold indicating overload.
Range: 100 to 1000 ms
Step size : 50ms
Default : 200 ms
Userdefined_L_RAC - This parameter allows the user to define a threshold for the percentage of
blocking due to Load and Admission Control before load balancing is activated
Range: 0 to 100%
Step size : 1%
Default : 5%
CRITERIA FOR CELL UNDERLOAD (1.21) - USER DEFINED THRESHOLDS 32

Userdefined_Erab - This parameter allows the user to set a threshold for ERAB failures due eNB
resource blocking before load balancing is activated
Range: 0 to 100%
Step size : 1%
Default : 5%
Userdefined_Time_No_Res - This parameter allows the users to set a percentage of time threshold
for blocking due to lack of eNodeB resources over the measurement period, before load balancing
is activated.
Range: 0 to 100%
Step size : 1%
Default : 5%
PRB_exit_threshold - This parameter allows the users to set a threshold for beginning to reduce
offsets over a measurement period
Range: 0% to (less than or equal to PRB_threshold)
Step size: 1%
Default 75 (or 5% below entry criteria)
Buffer_Delay_QC1_exit - This parameter defines the maximum amount of time data can be
buffered before the offset are allowed to be reduced on the source call
Range: 0% to (less than or equal to BufferDelay_QCI1)
Step size : 1 ms
Default: 20
Buffer_Delay_nonGBR_exit - This parameter defines the maximum amount of time non-GBR data
can be buffered before the offset are allowed to be reduced on the source call
Range: 0% to (less than or equal to BufferDelay_nonGBR)
Step size : 5 ms
Default : 175 (or 25 ms below entry criteria)
CRITERIA FOR CELL UNDERLOAD (1.21) - USER DEFINED THRESHOLDS 33

10 T-MOBILE CRITERIA FO R
CELL OVERLOAD (1.3)
Add a new optional section to the config called, "Operator Criteria". If this module config file section
contains: "Triggers = TMUS", then this sections trigger criteria applies. If module config file
contains: "Triggers = edennet" or contains no "Triggers" entry, then use the default criteria in
section 1.2
There is a longer term need to make operator in use be visible to the module through the
framework, in order to make a Default vs Operator selection available in GUI Parameters list.
Currently an operator flag is available and used at "install" time, and this is not retained or stored in
redis or otherwise. If this was retained for the framework to access, then the GUI parameters could
become variable and change as a function of the operator(s) in use. We do not recommend
hardcoding a default/operator selection into the GUI parameters as is, as this may deliver one
operators custom capability to all other customers, which is not desired.
Source
A Source cell is considered overloaded if the following criteria is fulfilled:

Configuration Parameters:
 dlChannelBandwidth; Value{10,5}
If (DL_PRB_Util > TMO_PRB_threshold and (RRC_Connected_UE / (dlChannelBandwidth / 5)) >
TMO_RRC_Users_threshold)
Then { Cell_Overload = true; }
10.2 Nokia Networks

Configuration Parameters:
 inactivityTimer, Value{10,5}
 dlChBw, Value {10,5}
T-MOBILE CRITERIA FOR CELL OVERLOAD (1.3) - ERICSSON NETWORKS 34

If (InactivityTimer = 5), Then (DL_PRB_UTIL > TMO_PRB_threshold AND (RRC_Connected_UE /

(dlChBw / 5)) > TMO_RRC_Users_eq5_threshold))
Else if (InactivityTimer <> 5), Then (DL_PRB_UTIL > TMO_PRB_threshold AND
(RRC_Connected_UE / (dlCHBw / 5)) > TMO_RRC_Users_threshold))
10.3 Target
A Target cell is considered overloaded if the following criteria is fulfilled:

If (InactivityTimer = 5), Then (DL_PRB_UTIL > TMO_PRB_threshold OR (RRC_Connected_UE /
(dlChBw / 5)) > TMO_RRC_Users_eq5_threshold))
Else if (InactivityTimer <> 5), Then (DL_PRB_UTIL > TMO_PRB_threshold OR
(RRC_Connected_UE / (dlCHBw / 5)) > TMO_RRC_Users_threshold))
Ericsson Networks
If (DL_PRB_Util > TMO_PRB_threshold OR (RRC_Connected_UE / (dlChannelBandwidth / 5)) >
TMO_RRC_Users_threshold)
10.4 User Defined Thresholds

These should be added as optional entries to the config file section for "Operator Criteria". If
missing and Triggers=TMUS, then the defaults apply
TMO_PRB_threshold - This parameter allows the user to define a trigger threshold for setting of DL
PRB occupancy over a measurement period.
 Range : 0 to 100%
 Steps size : 1%
 Default: 70%
T-MOBILE CRITERIA FOR CELL OVERLOAD (1.3) - TARGET 35

TMO_RRC_Users_threshold - This parameter allows the user to define a trigger threshold for
setting of RRC Connected UEs over a measurement period.
 Range : 0 to 100
 Steps size : 1
 Default: 65
TMO_RRC_Users_eq5_threshold - This parameter allows the user to define a trigger threshold for
setting of RRC Connected UEs over a measurement period, when inactivityTimer=5 for Nokia
 Range : 0 to 100
 Steps size : 1
 Default: 50
T-MOBILE CRITERIA FOR CELL OVERLOAD (1.3) - USER DEFINED THRESHOLDS 36

11 NEIGHBOR CELL WEIGHT ING

(1.7, 2.5)
By categorizing the top N neighbor cells according to load through the use of a weighting value, will
ensure that a cell does not offload too much of it's traffic to a cell that is close to overload itself.
The weighting mechanism will allow individual cell offsets to be implemented to make one cell more
attractive than the other, the loaded cell should offload more traffic to the low traffic cells than the
higher traffic cells. This concept is shown in the figure below:
It should be noted that in the diagram the individual cell offset from the neighbor cells to loaded cell
is set so that only a minimum amount of handovers take place back to to loaded cells. Also, a
target candidate that is already under mitigation with always be excluded from a source cell
selection list.
To determine the top 5 suitable cells to offload load to; arrange the cells with greater than 1% of the
total handover attempts, in a list from highest to lowest based on handover attempts where the
success rate is greater 95% and apply the following pseudo code:
NEIGHBOR CELL WEIGHTING (1.7, 2.5) - USER DEFINED THRESHOLDS 37

For number of target neighbors on offset neighbor list less than 5 do

For each neighbor not overloaded
add to target offset neighbor list
end
end
11.1 Cell Weighting Calculation:

The cell weighting calculation is based on the number of active users being served per TTI and the
average DL PRB usage over the measurement period.
The higher the calculated cell weighting value the more loaded the cell.
The source cell %_DL_PRB_Util should be greater than target cell CellWeight by
Loading_Threshold
Loading_Threshold default = 10
11.1.1 Nokia
Buffer_Slope = 2
Buffer_Weight = 30
CellWeight = %_DL_PRB_Util + (Avg_Lat_Non_GBR -
Buffer_Slope*%_DL_PRB_Util)/Buffer_Weight
11.1.2 Ericsson
Buffer_Slope = 5
Buffer_Weight = 20
CellWeight = %_DL_PRB_UTIL + (Avg_Lat_All_QCI - (Buffer_Slope)) / Buffer_Weight
11.1.3 Huawei
Buffer_Slope = 2
Buffer_Weight = 60
NEIGHBOR CELL WEIGHTING (1.7, 2.5) - CELL WEIGHTING CALCULATION: 38

11.1.4 ALU
Buffer_Slope = 2
Buffer_Weight = 60

NEIGHBOR CELL WEIGHTING (1.7, 2.5) - CELL WEIGHTING CALCULATION: 39

12 DEDICATED MODE
PARAMETER SETTINGS F OR
OFFLOADING (1.8)
The cell weighting that has been calculated in step 1.7 for the top 5 neighbor cells which are not
overloaded and the following initial offset applied, relative to the defaults network setting, from the
source cell to the target neighbor cell and from the target cell to the source cell:
Number of Targets Offset Applied (source to targets) Offset Applied (targets to source)
Min 5, Max 15 3 dB -3 dB
Maximum offset - Maximum offset allowable for any cell

Range: 3 to 12 dB
Steps: 1 dB
Default: 6 dB
12.1 Adjusted CIO Parameters
12.1.1 Nokia Network

Managed Object Parameter
LNREL cellIndOffNeigh
12.1.2 Ericsson Network

EUtranCellRelation cellIndividualOffsetEUtran
DEDICATED MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - ADJUSTED CIO

PARAMETERS 40
12.1.3 Huawei Network

EutranIntraFreqNCell CellIndividualOffset
12.1.4 Alcatel Lucent Network

LteNeighboringCellRelation cellIndividualOffset
12.2 Adjusted Trigger Threshold

Parameters
Measurement trigger thresholds are also adjusted and these are set to a value 6dB better than that
of the default network settings. This will require that parameter is read from the network before
being modified. The amount of adjustment applied is configurable in the config file.

LNCEL threshold1
threshold1(new) = threshold1(old) + 6
12.2.2 Ericsson
UeMeasControlsMeasure sMeasure
If sMeasure = 0, the Ignore sMeasure

Else, sMeasure(new) = sMeasure(old) + 6
DEDICATED MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - ADJUSTED TRIGGER

THRESHOLD PARAMETERS 41

HoMeasComm SMeasureInd
HoMeasComm SMeasure
If SMeasureInd = 0, then ignore SMeasure

Else, if SMeasureInd = 1, then SMeasure(new) = SMeasure(old) + 6
12.2.4 Alcatel Lucent Networks

RrcMeasurementConf sMeasure
12.2.5
sMeasure(new) = sMeasure(old) + 6
DEDICATED MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - ADJUSTED TRIGGER

THRESHOLD PARAMETERS 42
13 IDLE MODE PARAMETER

SETTINGS FOR OFFLOAD ING
(1.8)
For idle mode the following offsets are applied per neighbor relation.
Number of Targets Offset Applied (source to targets) Offset Applied (targets to source)
Min 5, Max 15 3 dB -3 dB
Maximum offset - Maximum absolute offset allowable for any cell

Range: 3 to 12 dB
Steps: 1 dB
Default: 6 dB
13.1 Offset Parameters Adjusted

IAFIM physCellIdNcl
IAFIM qOffsetCell
Nokia requires that under the IAFIM managed object a "list name="intrFrNCList" is created if one is
not present and then the above parameters are to be added .
The physCellIdNcl is the neighbor cell physical cell identity (PCI) that will be used by the UE to
apply the offset to the power measurements.
qOffsetCell is the parameter that the offset in the above table is applied to.
IDLE MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - OFFSET PARAMETERS

ADJUSTED 43
An extract for the xml that illustrates the structure is shown as follows:

EUtranCellRelation qOffsetCellEUtran

EutranIntraFreqNCell CellQOffset

LteNeighboringCellRelation qOffsetCell
13.2 sIntrasearch Thresholds Adjusted

The setting which sets the threshold for triggering neighbor cell reselection is Sintrasearch .
Changing this value to 10dB above the operator defined value will ensure that the UE starts
searching for an alternate cell for reselection earlier.
The value will need to be read first for each cell before it is modified by 10dB.

IDLE MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - SINTRASEARCH

THRESHOLDS ADJUSTED 44
LNCEL sIntrasearch
sIntraseach(new) = sIntraseach (old) + 10

EUTRANCELLFDD/SIB3 sIntraSearch
EUTRANCELLFDD/SIB3 sIntraSearchP
sIntraSearchP(new) = sIntraSearch(new) = sIntraSearchP (old) + 10

CellResel SIntraSearch
SIntraSearch(new) = SIntraSearch (old) + 10 dB

CellSelectionReselectionConf sIntraSearch
Do we need to include P and/or Q here?
SIntraSearch(new) = SIntraSearch (old) + 10 dB
IDLE MODE PARAMETER SETTINGS FOR OFFLOADING (1.8) - SINTRASEARCH

THRESHOLDS ADJUSTED 45
14 UPLINK NOISE THRESHO LD

CALCULATION (2.2)
This equation is to be used for both Nokia Networks and Ericsson:
if (%_B_PUSCH_SNR > SNRThreshold)
{
reduceoffsets = true
}
This equation is to be used for Huawei Networks
if (%_B_PUSCH_SNR > SNRThreshold)
{
reduceoffsets = true
}
SNRThreshold - This parameter allows the user to set a threshold to allow high levels of
interference for a percentage of all SINR measurements before reducing the cell weighting for all
neighbor cells.
Range: 0 to 100%
Step size : 1%
Default : 20%
UPLINK NOISE THRESHOLD CALCULATION (2.2) - SINTRASEARCH THRESHOLDS

ADJUSTED 46
15 REDUCING OFFSETS (2. 3)
If the uplink noise threshold has been triggered or the loaded cell is no longer overloaded then the
algorithm will reduce the offsets for both dedicated and idle mode.
Do not reduce any of the offsets below that of the network operator values.
For source to target neighbor cell, the offsets should be adjusted as follows:
new Offset = Offset - RedOffset
For target to source cell the offsets are adjusted as follows:
new Offset = Offset + RedOffset
RedOffset - Value that sets the amount by which the CIO offsets can be increased or decreased
Range: 0,1,2
Step Size : 1
Default : 1
REDUCING OFFSETS (2.3) - SINTRASEARCH THRESHOLDS ADJUSTED 47

16 INCREASE OFFSETS (2. 6)
If the cell is still overloaded then the offsets can be increased to offload more traffic as follows:
For source to target neighbor cell, the offsets should be adjusted as follows for dedicated and idle
parameters:
new Offset = Offset +IncOffset
For target to source cell, the offsets should be adjusted as follows for dedicated and idle
parameters:
new Offset = Offset -IncOffset
The maximum absolute offset that can be applied per cell should be configurable by a configuration
file threshold and should be relative to the cells starting offset values. The default max absolute
offset is 6 dB over the current offset value
For example, if CIO in the cells is set to 0, then the max allowable offset is 0 + 6 = 6. If CIO, in the
cell is set to 2, then the max allowable offset is 2 + 6 = 8 dB
IncOffset - Value that sets the amount by which the CIO and qOffset parameters can be increased
or decreased
Range: 0,1,2
Step Size : 1
Default : 1
INCREASE OFFSETS (2.6) - SINTRASEARCH THRESHOLDS ADJUSTED 48

17 PERFORMANCE TRIGGERS
(2.10)
17.1 Nokia Networks

if ((Intra_HO_FR(current) > Intra_HO_FR(old)(1+HOHysteresis)) or ((ERAB_DROPRATE(current)
> ERAB_DROPRATE(old)(1+ERABHysteresis)) or (RRC_Conn_Stp_Fail_RAC(current) >
RRC_Conn_Stp_Fail_RAC(old)(1+RACHysteresis)) or (Avg_Lat_QC1 or Avg_Lat_Non_GBR) >
BufferDelay))
{
OffsetReduction = true; // Offset reduction required for individual cell.
}

RRC_Conn_Stp_Fail_RAC(old)(1+RACHysteresis)) or (Avg_Lat_QC1 or Avg_Lat_All_QCI) >
BufferDelay))
{
}
17.3 Huawei Networks

RRC_Conn_Stp_Fail_RAC(old)(1+RACHysteresis)) or (Avg_Lat_QC1 or Avg_Lat_Non_GBR) >
BufferDelay))
{
}
PERFORMANCE TRIGGERS (2.10) - NOKIA NETWORKS 49

BufferDelay has been defined in above and is reused in this assessment.

HOHysteresis - This parameter sets the threshold for the increase in HO failure rate between the
target and source cell before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
ERABHysteresis - This parameter sets the threshold for the increase in drop rate for the target cell
before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
RACHysteresis - This parameter sets the threshold for the increase in eNB resource failure on the
target cell before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
LACHysteresis - This parameter sets the threshold for the increase in eNB resource failure on the
target cell before the algorithm attempts to reduce the offsets applied.
Range : 0 .. 100%
Step: 1%
Default: 10%
PERFORMANCE TRIGGERS (2.10) - HUAWEI NETWORKS 50

18 REPORTING
The following reports are to be generate per module instance:

 Cell detected as overloaded, and the 5 cells selected to offload traffic to.
 The offsets applied to each cell relation.
 For each overloaded cell and the targeted neighbor cells, all the metrics used to determine cell
loading and the performance metrics should be used in the report.
REPORTING - HUAWEI NETWORKS 51

19 SYSTEM DELAY (2.11)

In consideration of PM File Delay and System Feedback Cycle Length, the module should not
make a response action if the current available PM Period is not older than the last OSS Push
Time. This means the system will take steps at least every 3 PM file periods for 15 mins data. See
diagram below:
SYSTEM DELAY (2.11) - HUAWEI NETWORKS 52



20 PM COUNTER REQUIREMENTS
Nokia Ericsson Huawei Alcatel Lucent
kpiNa pegNames kpiNa pegNames kpiNam pegNames

me me e
%_B_ ["LTE_Pwr %_B_ ["EUtranCell [Avg_L L.Traffic.DL. [Avg_L VS.DLPdcpPduD

PUSC _and_Qual PUSC FDD.pmSinr at_QC1 PktDelay.Ti at_QC1 elay.QCI1.Cum,
H_SN _UL.M800 H_SN PuschDistr"] ] me.QCI.1, ]
VS.DLPdcpPduD
R 5C131", R
L.Traffic.DL. elay.QCI1.NbEvt
"LTE_Pwr_
PktDelay.N
and_Qual_
um.QCI.1
UL.M8005
C130",
"LTE_Pwr_
and_Qual_
UL.M8005
C133",
"LTE_Pwr_
and_Qual_
UL.M8005
C132",
"LTE_Pwr_
and_Qual_
UL.M8005
C135",
"LTE_Pwr_
and_Qual_
UL.M8005
C134",
"LTE_Pwr_
and_Qual_
UL.M8005
C137",
"LTE_Pwr_
and_Qual_
UL.M8005
C136",
"LTE_Pwr_
and_Qual_
UL.M8005
C139",
"LTE_Pwr_
and_Qual_
PM COUNTER REQUIREMENTS - HUAWEI NETWORKS 55


UL.M8005
C138",
"LTE_Pwr_
and_Qual_
UL.M8005
C128",
"LTE_Pwr_
and_Qual_
UL.M8005
C129",
"LTE_Pwr_
and_Qual_
UL.M8005
C120",
"LTE_Pwr_
and_Qual_
UL.M8005
C123",
"LTE_Pwr_
and_Qual_
UL.M8005
C121",
"LTE_Pwr_
and_Qual_
UL.M8005
C119",
"LTE_Pwr_
and_Qual_
UL.M8005
C118",
"LTE_Pwr_
and_Qual_
UL.M8005
C126",
"LTE_Pwr_
and_Qual_
UL.M8005
C127",
"LTE_Pwr_
and_Qual_
UL.M8005
C124",
"LTE_Pwr_
and_Qual_
UL.M8005
C125",


"LTE_Pwr_
and_Qual_
UL.M8005
C122"]
%_DL_ ["LTE_Cell %_DL_ ["EUtranCell [Avg_L L.Traffic.DL. [Avg_L VS.DLPdcpPduD

PRB_ _Resource PRB_ FDD.pmPrbU at_Non PktDelay.Ti at_Non elay.QCI6.Cum,
Util .M8011C3 Util sedDlSrbFirst _GBR] me.QCI.6, _GBR]
VS.DLPdcpPduD
7"] Trans", L.Traffic.DL.
elay.QCI6.NbEvt
"EUtranCellF PktDelay.Ti
DD.pmPrbUs me.QCI.7, VS.DLPdcpPduD
edDlBcch", L.Traffic.DL. elay.QCI7.Cum
"EUtranCellF PktDelay.Ti VS.DLPdcpPduD
DD.pmPrbUs me.QCI.8, elay.QCI7.NbEvt
edDlDtch", L.Traffic.DL.
"EUtranCellF PktDelay.Ti VS.DLPdcpPduD
DD.pmPrbUs me.QCI.9, elay.QCI8.Cum
edDlPcch", VS.DLPdcpPduD
L.Traffic.DL.
"EUtranCellF elay.QCI8.NbEvt
PktDelay.N
DD.pmPrbAv
um.QCI.6, VS.DLPdcpPduD
ailDl"]
L.Traffic.DL. elay.QCI9.Cum
PktDelay.N
um.QCI.7, VS.DLPdcpPduD
L.Traffic.DL. elay.QCI9.NbEvt
PktDelay.N
um.QCI.8,
L.Traffic.DL.
PktDelay.N
um.QCI.9
Avg_A ["LTE_Cell Avg_A ["EUtranCell [%_DL 152672674 [%_DL VS.DLPRBUsed.

ct_Use _Load.M80 ct_Use FDD.pmActiv _PRB_ 0_L.ChMea _PRB_ Cum,
r 01C147"] r eUeDrbSamp Util] s.PRB.DL.U Util] VS.DLPRBUsed.
", sed.Avg NbEvt
"EUtranCellF
DD.pmActive
UeDlSum"]
Avg_L ["LTE_Cell Avg_A ["EUtranCell [RRC_ 152672708 [RRC_ 100 *

at_All_ _Load.M80 ct_Use FDD.pmActiv Conn_ 3.L.RRC.Se Conn_ (RRC.ConnEstab
QCI 01C270"] r_Sam eUeDrbSamp Stp_Fai tupFail.Res Stp_Fai Fail.CACFailure
p "] l_RAC] Fail, l_RAC] +
152672821 RRC.ConnEstab
6.L.RRC.Co Fail.Unexpected
nnSetup ResourceDepleti
on) /


(RRC.ConnEstab
Succ.Sum +
RRC.ConnEstab
Fail.Sum)
Avg_L ["LTE_Cell Avg_A ["EUtranCell [ERAB 152672827 [ERAB 100 *

at_QC _Load.M80 ct_Use FDD.pmActiv _Fail_R 9.L.E- _Fail_R (VS.ERABSetup
1 01C271", r_Sum eUeDlSum"] esourc RAB.FailEst esourc Failed.CACFailur
"LTE_Cell_ e] .NoRadioRe e] e+
Load.M800 s, VA.ERABSetupF
1C269", ailued.OveroadC
152672754
"LTE_Cell_ ondition) /
5.L.E-
Load.M800 (VS.SAEB.EstabI
RAB.AttEst
1C273", nitSuccNbrPerR
"LTE_Cell_ RH,
Load.M800 SAEB.EstabAdd
1C272"] AttNbr.QCI1..9)
DL_Tr ["LTE_Cell Avg_L ["EUtranCell [Avg_A 152672738 [Avg_A

affic_V _Throughp at_All_ FDD.pmPdcp ct_User 4.L.Traffic.U ct_User
VS.NbSimultane
ol ut.M8012C QCI LatTimeDl", ] ser.DLData. ]
ousTransmittin
20"] "EUtranCellF Avg
gUEInDL.GBR.C
DD.pmPdcpL
um,
atPktTransDl
VS.NbSimultane
"]
ousTransmittin
gUEInDL.NonG
BR.Cum,
VS.NbSimultane
ousTransmittin
gUEInDL.GBR.N
bEvt,
VS.NbSimultane
ousTransmittin
gUEInDL.NonG
BR.NbEvt
ERAB_ ["LTE_EPS Avg_L ["EUtranCell [DL_Tr 152672826 [DL_Tr (VS.DLPdcpPdu

DROP _Bearer.M at_QC FDD.pmPdcp affic_V 1.L.Thrp.bit affic_V SentByPdcp.QCI
RATE 8006C6", 1 LatTimeDl", ol] s.DL ol] 1+
"LTE_EPS "EUtranCellF VS.DLPdcpPduS
_Bearer.M DD.pmPdcpL entByPdcp.QCI2
8006C7", atPktTransDl +
"LTE_EPS "] VS.DLPdcpPduS
_Bearer.M entByPdcp.QCI3


8006C12", +
"LTE_EPS VS.DLPdcpPduS
8006C13", +
8006C10", +
8006C14", +
8006C15", +
8006C8", +
_Bearer.M entByPdcp.QCI9)
8006C9"] Not in Bytes...
(VS.DLRlcPduKb
ytes.VoIP +
VS.DLRlcPduKb
ytes.OtherGBR +
VS.DLRlcPduKb
ytes.NonGBR) *
1024/1000000
1. "Converted
from KiBytes
to MByte"
2. "Pdcp bytes
are not
available, so
replacing with
Rlc bytes"
ERAB_ ["LTE_EPS DL_Tr ["EUtranCell [Intra_F INTRA_F_H [%_B_ Average of

Fail_R _Bearer.M affic_V FDD.pmPdcp _HO_F O_SUCC_N PUSC (VS.ULNoiseOnP
esourc 8006C0", ol VolDlDrb"] R] B, H_SNR USCHPRBs,)
e "LTE_EPS INTRA_F_H ]
100 *
_Bearer.M O_ATT_NB
(VS.ULNoiseAllP
8006C4"]
RBs.LeRg1) /
(VS.ULNoiseAllP
RBs.LeRg1 +


VS.ULNoiseAllP
RBs.GtRg1LeRg
2+
VS.ULNoiseAllP
RBs.GtRg2LeRg
3+
VS.ULNoiseAllP
RBs.GtRg3LeRg
4+
VS.ULNoiseAllP
RBs.GtRg4)
INTRA ["LTE_Nei eRAB_ ["EUtranCell [RRC_ 152672708 INTRA VS.OutgoingIntra

_F_HO ghb_Cell_ Drop_ FDD.pmErab Conn_ 3.L.RRC.Se _F_HO FrequencyHOMo
_ATT_ HO.M8015 Rate RelNormalEn Stp_Fai tupFail.Res _ATT_ bilityEventPerRel
NB C8", b", l_RAC] Fail, NB ation
"LTE_Neig "EUtranCellF 152672821
hb_Cell_H DD.pmErabR 6.L.RRC.Co
O.M8015C elAbnormalE nnSetup
1"] nbAct",
"EUtranCellF
DD.pmErabR
elAbnormalE
nb",
"EUtranCellF
DD.pmErabR
elMme",
"EUtranCellF
DD.pmErabR
elAbnormalM
meAct"]
eRAB_ pmErabRelA eRAB_
eRAB_ M8006C10
Voice_ bnormalEnbA Voice_
Voice_ 7,
Drop_ ctQci, Drop_R
Drop_ M8006C11
Rate pmErabRelA ate
Rate 6,
bnormalMme
M8006C13
ActQci,
4,
pmErabRelN
M8006C26
ormalEnbQci,
8,
pmErabRelM
M8006C14
meQci
3,
M8006C26
6,
M8006C26
7,
M8006C26


8,
M8006C26
9,
M8006C27
0,
M8006C27
1,
M8006C27
2,
M8006C15
2,
M8006C27
8,
M8006C28
0,
M8006C89
,
M8006C98
,
M8006C12
5,
M8006C16
1)
Intra_F ["LTE_Nei ERAB_ pmErabEstab [ERAB 152672754 INTRA VS.IncomingIntra
_HO_F ghb_Cell_ Fail_R FailGbrDlEnb _DROP 6.L.E- _F_HO ENodeBHOSucc
R HO.M8015 esourc , RATE] RAB.Abnor _SUCC ess
C2", e pmErabEstab mRel, _NB 1. Required per
"LTE_Neig FailGbrUlEnb 152672829 cell counters
hb_Cell_H , 2.L.E- not available.
O.M8015C pmErabEstab RAB.Abnor Investigation
8", SuccInit mRel.MME, required if call
"LTE_Neig 152672754 trace can be
hb_Cell_H 6.L.E- used to
O.M8015C RAB.Abnor workaround
9", mRel,
"LTE_Neig 152672829
hb_Cell_H 2.L.E-
O.M8015C RAB.Abnor
1"] mRel.MME,
152672754
7.L.E-
RAB.Norm
Rel
Intra_F ["LTE_Nei INTRA ["EUtranNeig [Avg_L L.Traffic.DL. [Intra_F 100 - (100 *
_HO_S ghb_Cell_ _F_HO hbor.pmHoE at_QC1 PktDelay.Ti _HO_F (INTRA_F_HO_S


R HO.M8015 _ATT_ xeAttLteIntra ] me.QCI.1 R] UCC_NB) /
C2", NB F"] (INTRA_F_HO_A
"LTE_Neig TT_NB))) #Not
hb_Cell_H per cell pair
O.M8015C
8",
"LTE_Neig
hb_Cell_H
O.M8015C
9",
"LTE_Neig
hb_Cell_H
O.M8015C
1"]
INTRA ["LTE_Nei Intra_F ["EUtranNeig [Avg_L L.Traffic.DL. [RRC_ 100 *

_F_HO ghb_Cell_ _HO_F hbor.pmHoE at_Non PktDelay.Ti Conn_ (RRC.ConnEstab
_SUC HO.M8015 R xeAttLteIntra _GBR] me.QCI.6, Failure Fail.Sum) /
C_NB C2", F", L.Traffic.DL. _Rate] (RRC.ConnEstab
"LTE_Neig "EUtranNeig PktDelay.Ti Succ.Sum +
hb_Cell_H hbor.pmHoE me.QCI.7, RRC.ConnEstab
O.M8015C xeSuccLteInt L.Traffic.DL. Fail.Sum)
9"] raF"] PktDelay.Ti
me.QCI.8,
L.Traffic.DL.
PktDelay.Ti
me.QCI.9
RRC_ ["LTE_UE_ Intra_F ["EUtranNeig [%_B_ L.UL.Interfe [ERAB 100 *

Conn_ State.M80 _HO_S hbor.pmHoE PUSC rence.Avg _DROP (VS.OtherAbnor
Stp_Fa 13C21", R xeAttLteIntra H_SNR RATE] malERABReleas
il_RAC "LTE_UE_ F", ] ePerQCI +
State.M80 "EUtranNeig VS.AbnormalER
13C20", hbor.pmHoE ABReleasePerQ
"LTE_UE_ xeSuccLteInt CI +
State.M80 raF"] VS.ERABReleas
13C17", edDueToRadioLi
"LTE_UE_ nkFailurePerQCI)
State.M80 /
13C18",
(VS.OtherAbnor
"LTE_UE_
malERABReleas
State.M80
ePerQCI +
13C19",
VS.AbnormalER
"LTE_UE_
ABReleasePerQ
State.M80
CI +
13C8"]
VS.ERABReleas


edDueToRadioLi
nkFailurePerQCI
+
VS.NormalERAB
Release.QCI +
VS.ERABReleas
eResponseERAB
ReleaseSuccess)
INTRA ["EUtranNeig INTRA 152672729 [Avg_L Average of

_F_HO hbor.pmHoE _F_HO 4_L.HHO.N at_QC1 (VS.DLPdcpPdu
_SUC xeSuccLteInt _ATT_ Cell.ExecAtt ] Delay.QCI1)
C_NB raF"] NB Out
RRC_ ["pmRrcConn INTRA 152672729 [Avg_L Average of

Conn_ EstabFailBea _F_HO 5_L.HHON at_Non Maximum of
Stp_Fa rerAdmission _SUCC Cell.ExecSu _GBR] (VS.DLPdcpPdu
il_RAC Rej, _NB ccOut Delay.QCI6 +
pmRrcConnE VS.DLPdcpPduD
stabAtt"] elay.QCI7 +
VS.DLPdcpPduD
elay.QCI8 +
VS.DLPdcpPduD
elay.QCI9)

21 LOAD BALANCING FLOW

DIAGRAM(SƠ ĐỒ CÂN BẰNG
TẢI)
LOAD BALANCING FLOW DIAGRAM(SƠ ĐỒ CÂN BẰNG TẢI) - HUAWEI NETWORKS 64

22 PM SCANNERS ENABLED IN
T MOBILE'S ERICSSON
Currently, T Mobile LTE Ericsson RAN is L14B
verifiable via AMOS in any eNb with command
LBX03130A> invh
150521-19:55:02 11.162.122.84 11.0b ERBS_NODE_MODEL_E_1_236 stopfile=/tmp/9813
Node: RBS6131L CXP102051/22_R45DM L14B (C15.0-EP2-5)
===========================================================================
==========================================================
SMN APN BOARD SWALLOCATION S FAULT OPER MAINT c/p d PRODUCTNUMBER REV
SERIAL DATE MO
===========================================================================
==========================================================
0 1 DUL2001 main 1 OFF ON OFF 27% 33% KDU137533/4 R1F D160962507 20120619 1,Slot=1
------------------------------------------------------------------------------------------------------------------------------------
-
===========================================================================
==========================================================
XPBOARD ST FAULT OPER MAINT PRODUCTNUMBER REV SERIAL/NAME DATE MO
===========================================================================
==========================================================
S-RET 1 16910526 V_A02 KA035871201843_A1 AntennaUnitGroup=1,AntennaNearUnit=1
RRUS0ZB4 1 OFF ON OFF KRC118034/1 R1C D162180635 20120826 AuxPlugInUnit=RRU-1-1
AIR21B4AB2P KRC118046/1 R2A CQ30031500 20120906 000100/BXP_1 000100/BXP_1_1
------------------------------------------------------------------------------------------------------------------------------------
-
===========================================================================
==========================================================
MO SMN PRODUCT PRODUCTNUMBER REV SERIAL/NAME DATE transmissionType maxPwr
PM SCANNERS ENABLED IN T MOBILE'S ERICSSON - HUAWEI NETWORKS 65

fanConfiguration position
===========================================================================
==========================================================
Subrack=1 0 Subrack ROJ999999 * ETHERNET_CABLE 2000W NO_CPP_FAN
As per Ericsson T2 support, the T Mobile pm scanners are:

(updated with the scanners from poloss30, as per T Mobile's e-mail, 5/28/15)
LSF70072M> pst
150528-12:50:38 11.226.74.244 11.0b ERBS_NODE_MODEL_E_1_236 stopfile=/tmp/26936
Connecting to 11.226.74.244:56834 (CorbaSecurity=OFF, corba_class=2, java=1.6.0_71,
jacoms=R80L10, jacorb=R80L01)
Trying file=/var/opt/ericsson/amos/moshell_logfiles/rflore75/logs_moshell/tempfiles/20150528-
125011_26877/ior26877
**** Bootstrapping OK
****
$pmtester_pid = 27196
===========================================================================
=====
PROXY SCANNER-NAME STATE
===========================================================================
=====
40 PREDEF.STATS ACTIVE
41 PREDEF.10000.CELLTRACE SUSPENDED
42 PREDEF.10001.CELLTRACE ACTIVE
44 PREDEF.10003.CELLTRACE ACTIVE
69 USERDEF.TMO_LTE_Default_All.Profile=10000266.Continuous=Y.STATS ACTIVE
===========================================================================
=====
>>> Total: 8 Scanners
the attached pm.txt has the contents of scanners 40 (predefined) & 69 (T Mobile's default)

the enclosed lic.txt has the license status of LTE features (via AMOS invr
Ideally, this information needs to be provided by any operator, for each provider, and updated prior
to any RAN release.

23 TEST PLANS
FOA for LTE LBO_v0.2.docx
TP-Lab for LTE LBO v0.1.docx
23.1 Current test plans, Aug 15, 2014

Current test plans
Name Version Date
FOA for LTE LBO_v0.3.docx 1 2014-08-15 14:53
TP FOA for 3G_SC_Retune_v1_0.docx 1 2014-08-15 16:19
TP Lab for 3G_SC_Retune_v1_0.docx 1 2014-08-15 16:18
TP-Lab for LTE LBO v0.2.docx 1 2014-08-15 14:53
TEST PLANS - CURRENT TEST PLANS, AUG 15, 2014 68

MLB in LTE

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MLB in LTE

Hochgeladen von

Copyright:

Verfügbare Formate

0

Author: Unknown User (cwilliams)

2 LTE Load balancing Algorithm Overview ..............9

3 LTE Load balancing Flow Chart .....................10

4 LTE Loading Algorithm Metrics (1.1) ...............12

4.2 Ericsson ......................................................................................................................... 14

4.4 Alcatel Lucent ................................................................................................................ 15

5 Uplink Noise Measurements (2.1) ...................18

5.2 Ericsson Networks ........................................................................................................ 19

5.3 Huawei Networks ........................................................................................................... 19

5.4 Alcatel Lucent Networks ............................................................................................... 19

6 Performance Metrics (2.9, 2.10) ...................21

6.2 Ericsson Networks ........................................................................................................ 22

6.3 Huawei Networks ........................................................................................................... 23

6.4 Alcatel Lucent ................................................................................................................ 24

7 Neighbor Cells Measurements (1.5, 1.6) ............27

REFERENCES - NOKIA NETWORKS 1

7.1 Nokia Networks............................................................................................................. 27

7.2 Ericsson ......................................................................................................................... 27

7.4 Alcatel Lucent ................................................................................................................ 28

8 Default Eden-Net Criteria for Cell Overload (1.2) .29

8.2 Target ............................................................................................................................. 30

9 Criteria for Cell Underload (1.21) ................31

9.2 User Defined Thresholds .............................................................................................. 32

10 T-Mobile Criteria for Cell Overload (1.3) .........34

10.2 Nokia Networks ............................................................................................................. 34

10.3 Target ............................................................................................................................. 35

10.4 User Defined Thresholds .............................................................................................. 35

11 Neighbor Cell Weighting (1.7, 2.5) ................37

REFERENCES - NOKIA NETWORKS 2

11.1.3 Huawei ............................................................................................................................ 38

12 Dedicated Mode Parameter Settings for Offloading

12.2 Adjusted Trigger Threshold Parameters...................................................................... 41

13 Idle Mode Parameter Settings for Offloading (1.8) .43

13.2 sIntrasearch Thresholds Adjusted ............................................................................... 44

14 Uplink Noise Threshold Calculation (2.2) ..........46

15 Reducing Offsets (2.3) ............................47

16 Increase Offsets (2.6) ............................48

17 Performance Triggers (2.10) .......................49

REFERENCES - NOKIA NETWORKS 3

17.2 Ericsson Networks ........................................................................................................ 49

17.3 Huawei Networks ........................................................................................................... 49

19 System Delay (2.11) ...............................52

20 PM Counter Requirements ...........................55

21 Load Balancing Flow Diagram .......................64

22 PM scanners enabled in T Mobile's Ericsson ........65

23 Test Plans ........................................68

REFERENCES - NOKIA NETWORKS 4

REFERENCES - NOKIA NETWORKS 5

 Criteria for Cell Underload (1.21)

 Neighbor Cell Weighting (1.7, 2.5)

REFERENCES - NOKIA NETWORKS 6

o Offset Parameters Adjusted

REFERENCES - NOKIA NETWORKS 7

REFERENCES - NOKIA NETWORKS 8

2 LTE LOAD BALANCING

LTE LOAD BALANCING ALGORITHM OVERVIEW - NOKIA NETWORKS 9

3 LTE LOAD BALANCING F LOW

LTE LOAD BALANCING FLOW CHART - NOKIA NETWORKS 10

LTE LOAD BALANCING FLOW CHART - NOKIA NETWORKS 11

4 LTE LOADING ALGORITHM

4.1 Nokia Networks

LTE LOADING ALGORITHM METRICS (1.1) - NOKIA NETWORKS 12

LTE LOADING ALGORITHM METRICS (1.1) - NOKIA NETWORKS 13