Beruflich Dokumente
Kultur Dokumente
0
Document number: LTE/IRC/APP/032105
Document issue: V05.03 / EN
Document status: Approved-Standard
Data classification: Confidential
Date: 30/Mar/2012
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
UNCONTROLLED COPY: The master of this document is stored on an electronic database and is write
protected; it may be altered only by authorized persons. While copies may be printed, it is not recommended.
Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be
regarded as uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-
Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information
contained herein confidential, shall disclose the information only to its employees with a need to know, and
shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized
in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you
have received this document in error, please notify the sender and destroy it immediately.
Without notice. Networks assumes no responsibility for errors that might appear in it .All other brand and
product names are trademarks or registered
1 INTRODUCTION
The document is the optimization handbook for the main RF features and related parameters
per domain of Alcatel-Lucent LTE release LA4.0
The procedures detailed in this document can be used to improve the network performance
so that it meets contractual and technical objectives prior to a commercial launch. It can also
be used in a continuous process as the network evolves due to addition of new cells, increase
in traffic load or introduction of new features.
1.1 SCOPE
Main purpose of the document consists of proposing parameter tuning that shall mitigate
observed performance degradations.
Coverage
Throughput
Latency
Capacity
The parameters described in this document are related to the Alcatel-Lucent LTE
LA4.0 release.
First-Off Trials
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
2 PUBLICATION HISTORY
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
TABLE OF CONTENTS
1 INTRODUCTION .....................................................................................................................................2
1.1 SCOPE ..............................................................................................................................................2
1.2 AUDIENCE FOR THIS DOCUMENT .............................................................................................................2
2 PUBLICATION HISTORY.........................................................................................................................3
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
LIST OF FIGURES
Figure 8.2-1: Throughput for single UE vs. Path loss (Lab environment) .......................................................30
Figure 8.2-2: Throughput vs. RSRP 700 (Field Results VzW) .........................................................................34
Figure 8.2-3: Throughput vs. RSRP AWS (Field Results VzW) ........................................................................35
Figure 8.2-4: qRxLevMin Selection ...................................................................................................................35
Figure 8.2-5: Po_pusch_Nominal Impact .........................................................................................................38
Figure 8.2-6: Slope - PuschPowerControl vs. uplinkSIRtargetValueForDynamicPUSCHscheduling .................39
Figure 9.1-1: preambleTransMax vs. preambleInitialRceivedTargetPower vs.
preambleTransmitPowerStepSize .............................................................................................................41
Figure 9.1-2: Po_preamble impact on UE Tx Power vs. PL(RA) (TRY1) ..........................................................41
Figure 9.1-3: Po_preamble impact on UE Tx Power vs. PL (RA) .....................................................................42
Figure 9.1-4: preambleTransMax vs. preambleInitialRceivedTargetPower vs.
preambleTransmitPowerStepSize (example of values) ............................................................................42
Figure 9.1-5: Parameters dependency and relations ......................................................................................45
Figure 10.1-1: Radio link Quality vs. MCS Robustness vs. Throughput ............................................................48
Figure 10.1-2: Radio link Quality vs. dlMCSTransition Table vs. Throughput .................................................48
Figure 10.1-3: Dl Sinr Threshold Example........................................................................................................51
Figure 10.1-4: CL 2Layer-1Layer SNR Switch Threshold: 10 dB (purple) vs. 12 dB (blue) AWGN (Lab
results VzW) ..............................................................................................................................................52
Figure 10.1-5: CL 2Layer-1Layer SNR Switch Threshold: 10 dB (purple) vs. 12 dB (blue) EPA 5Hz,
Medium Correlation (Lab Results VzW) ....................................................................................................52
Figure 10.1-6: Dl Sinr Threshold Example........................................................................................................53
Figure 10.1-7: alphaFairnessFactor Change Impact ........................................................................................54
Figure 11.1-1: Impact of the pUSCHPowerControlAlphaFactor =1.0 in MCS usage. .......................................59
Figure 11.1-2: Impact of the pUSCHPowerControlAlphaFactor =0.8 in Throughput per RB ...........................59
Figure 11.1-3: Impact of the pUSCHPowerControlAlphaFactor =0.7 in Throughput per RB. ..........................60
Figure 11.1-4: Set 1 Result ...............................................................................................................................61
Figure 11.1-5: Set 1UL Throughput & UE TX Power vs. Path loss ...................................................................62
Figure 11.1-6: SIR Target for theoretical assumptions with different alpha factor values ............................63
Figure 11.1-7: UL SIR Target for theoretical assumptions with different alpha factor values ......................63
Figure 11.1-8: Different alpha factor comparison (Throughput, PRBs, SINR & PUSCH SINR Target) ............64
Figure 11.1-9: UL Throughput & UE TX Power vs. Path loss alpha factor 0.7 & 1 with set 3.........................65
Figure 11.1-10: UL Throughput & UE TX Power vs. Path loss for alpha factor 0.7 for all sets ......................66
Figure 11.1-11: UL Throughput vs. Path loss for set1 & set3 with alpha factor 0.7 and 1 ............................67
Figure 11.1-12: UE TX Power vs. Path loss for set1 & set3 with alpha factor 0.7 and 1 ................................67
Figure 11.1-13: Fractional Power Control Slope vs. Sets ................................................................................68
Figure 11.1-14: Impact of the ulSchedPropFairAlphaFactor ...........................................................................70
Figure 12.1-1: Example for IMSI attach procedure (with authentication) ......................................................73
Figure 12.1-2: Example for GUTI attach procedure (no authentication) ........................................................73
Figure 12.1-3: Idle to active message chart ....................................................................................................76
Figure 12.1-4: Example of total Idle to active latency ...................................................................................77
Figure 14.1-1: Intra HO Neighbour list .............................................................................................................84
Figure 14.1-2: Coverage analysis AMX trial done by ARFCC team ................................................................85
Figure 14.1-3: X2-Link creation by ANR ...........................................................................................................86
Figure 14.1-4: HO ping pong area ....................................................................................................................87
Figure 14.1-5: LTE to LTE Mobility Measurement phase (RSRP vs. Time) ....................................................88
Figure 14.1-6: LTE to LTE Mobility Ranking Phase ........................................................................................89
Figure 14.1-7: LTE to LTE Mobility Decision Phase (RSRP vs. Time) .............................................................89
Figure 14.1-8: LTE to LTE Mobility Handover cases ......................................................................................97
Figure 14.1-9: Theoretical view .......................................................................................................................98
Figure 14.1-10: filterCoefficientRSRP - Theoretical comparison (Simulation Analysis) .................................98
Figure 14.1-11: Call flow for Inter-eNB mobility, X2 HO UE in RRC Connected (1) ...................................104
Figure 14.1-12: Call flow for Inter-eNB mobility, X2 HO UE in RRC Connected (2) ...................................105
Figure 14.1-13: Call flow for Inter-eNB mobility, S1 HO UE in RRC Connected (1)....................................106
Figure 14.1-14: Call flow for Inter-eNB mobility, S1 HO UE in RRC Connected (2)....................................107
Figure 14.1-15: LTE to LTE Mobility Cell Reselection .................................................................................109
Figure 14.1-16: Idle Mode Algorithm B4B13 ...............................................................................................109
Figure 14.1-17: Idle Mode Algorithm B13B4 ...............................................................................................110
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
LIST OF TABLES
Table 6-1: Parameters impacting UL coverage................................................................................................15
Table 6-2: Parameters impacting DL coverage ................................................................................................16
Table 6-3: Parameters impacting attach/detach procedures .........................................................................16
Table 6-4: Parameters impacting DL throughput ............................................................................................17
Table 6-5: Parameters impacting UL throughput ............................................................................................17
Table 6-6: Parameters impacting control plane latency .................................................................................17
Table 6-7: Parameters impacting eNB Capacity ..............................................................................................17
Table 6-8: Parameters impacting measurements for intra-LTE mobility........................................................18
Table 6-9: Parameters impacting measurements for inter-frequency (idle mode) ........................................19
Table 6-10: Parameters impacting measurements for inter-frequency (active mode) ..................................19
Table 6-11: Parameters impacting LTE UMTS Inter-Frequency (Idle Mode) .................................................20
Table 6-12: Parameters impacting LTE UMTS Inter-Frequency (Active Mode) .............................................20
Table 6-13: Parameters impacting LTE GSM (Idle Mode) ..............................................................................21
Table 6-14: Parameters impacting LTE GSM (Active Mode) ..........................................................................21
Table 6-15: Parameters impacting LTE HRPD (Idle Mode) ............................................................................21
Table 6-16: Parameters impacting LTE HRPD (Active Mode) ........................................................................22
Table 7-1: LA4.0 Features ................................................................................................................................23
Table 8-1: Default setting for parameter referenceSignalPower....................................................................25
Table 8-2: UL 2.6GHz .......................................................................................................................................29
Table 8-3: Path Loss & UL Cell Range in Dense Urban Indoor .........................................................................29
Table 8-4: Path Loss & UL Cell Range Suburban in Car ...................................................................................29
Table 8-5: DL Cell Range in Dense Urban ........................................................................................................29
Table 10-1: Examples of threshold tuning for a 10MHz band (academic only, not applied in any trial
/project). ..................................................................................................................................................49
Table 10-2: Theory Assumption on CFI Tuning ................................................................................................55
Table 11-1: uplinkSIRtargetValueForDynamicPUSCHscheduling vs. PUSCHPowerControlAlphaFactor ...........57
Table 11-2: Different Sets Combinations .......................................................................................................60
Table 11-3: Different Sets Combinations Used...............................................................................................68
Table 12-1: Attach Latency for LA4.0.1...........................................................................................................74
Table 12-2: SW Reference ................................................................................................................................75
Table 12-3: Idle to Active Latency ...................................................................................................................77
Table 12-4: SW Reference ................................................................................................................................78
Table 12-5: Ping Latency for 32 Bytes with and without Extended SR grant for U-plane latency .................79
Table 13-1: LA4.0.1 Capacity figures ...............................................................................................................80
Table 14-1: Mobility parameters ......................................................................................................................87
Table 14-2: Intra-eNB HO Interruption time ..................................................................................................107
Table 14-3: SW Reference ..............................................................................................................................108
Table 14-4: Parameters Tuning for Active Mode ...........................................................................................124
Table 14-5: Connected Mode Test cases executed........................................................................................124
Table 14-6: A5 through S1 with 50% DL OCNS ................................................................................................124
Table 14-7: A5 through X2 with 100% DL OCNS .............................................................................................124
Table 14-8: A5 through X2 with 50% DL OCNS ...............................................................................................124
Table 14-9: A3 through X2 with 50% DL OCNS ...............................................................................................124
Table 14-10: A3 through X2 with 100% DL OCNS ...........................................................................................125
Table 14-11: A5 through X2 with 100% DL OCNS (thresholdEutraRSRP & threshold2EutraRSRP =-111) .......125
Table 14-12: A5 through X2 with 50% DL OCNS (thresholdEutraRSRP & threshold2EutraRSRP =-111) .........125
Table 14-13: Parameters Tuning for Idle Mode .............................................................................................126
Table 14-14: Idle Mode Test cases executed .................................................................................................126
Table 14-15: Idle Mode Test B4B13 with 50% OCNS ...................................................................................126
Table 14-16: Idle Mode Test B13B4 with 50% OCNS ...................................................................................126
Table 14-17: Idle Mode Test B4B13 with 100% OCNS .................................................................................127
Table 14-18: Idle Mode Test B13B4 with 100% OCNS .................................................................................127
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
3 REFERENCE DOCUMENTS
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Simulation Tool for RF design: Alcatel-Lucent uses A9955. Used for antenna change validation and
RF analysis. There must be consistency with the methods used by the customer so it is possible to
use their solution if it has been validated by Alcatel-Lucent teams.
Data Acquisition Platform (DAP): currently Nixt Platform composed of JSDU Nixt E6474A, W1314A
receiver and 1 to 4 test mobiles.
Tests Mobiles: typically LGE, Motorola, Samsung and Bandrich. Also IPW or Sequans UEs for TDD
systems.
Post processing platform (PPP): Gladiator or eDAT (ALU internal), which allow automatic and
customized KPI generation, built-in failure characterization, as well as UE and Call Trace
synchronization capabilities (for a deeper and accurate analysis).
For enhanced troubleshooting, the usage of a protocol analyzer (Agilent DNA) may be required, in
particular to monitor the S1 and X2 interfaces.
Project Database: For a correct follow-up of all the optimization activities it is mandatory to have a
common and unique project information system (Project Database) which contains the following
information:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
This chapter is intended to present various parameters existing in ALU RAN, grouped per main area
of interest in trials and network deployments. Grouping was made such that it reflects various types
of tests that are being performed during trials and KPIs tests that might as well be addressed during
trials and network deployment.
Parameters have been split by following domains:
Coverage
Attach /Detach
Throughput
Latency
Capacity
Mobility
Due to the wide scope of mobility, the parameters impacting mobility have been further divided in:
Inside each group, parameters are ordered by the most important and relevant for optimization
activities. They should be optimized in case of strong constraints for performance (very demanding
KPI, strong competition).
To each parameter is associated a recommended value that can be obtained from [1] for
parameters that have not been yet optimized in field activities. The parameters for which a
different, optimized, value have been obtained in various field tests, have recommended values
specified in the corresponding paragraphs along with some precisions about the conditions in which
the optimized value have been obtained (cluster, load).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
uplinkSIRtargetValueForDynamicPUSCHsche
EnbRadioConf Check Recommendation
duling
Check Recommendation
EnbRadioConf sEcorrInit
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
PowerOffsetConfiguration phichResource 1
ULPowerControlConf deltaPreambleMsg3 0
DownlinkMimo dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer 12
CellL2DLConf dlSinrThresholdBetweenOLMimoAndTxDiv 15
CellL1L2ControlChannelsConf AlphaFairnessfactor 1
Check
CellL1L2ControlChannelsConf CFI
recommendation
Check
CellL1L2ControlChannelsConf cfi1allowed
recommendation
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
CellRachConf preambleTransMax n3
EnbRadioConf aUGtriggerDelayforRACHmsg4 10
CellRachConf alphaFairnessFactor 1
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Note: Measurement Gap feature parameters can impact the mobility parameters considered through
the quality of measurement performed.
Because measurements are somehow a common part of various types of mobility, in the table below
are listed the parameters impacting measurement process for intra-LTE mobility.
Object Name Recommended Value
CellSelectionReselectionConf sIntraSearch 62
CellSelectionReselectionConf qRxlevminoffset 8
CellReselectionConfLte tReselectionEUTRAN 2
SpeedStateEvalConf nCellChangeHigh 12
SpeedStateEvalConf nCellChangeMedium 4
ReportConfigEUTRA Hysteresis 2
ReportConfigEUTRA eventA3Offset 0
ReportConfigEUTRA reportAmount r8
CellSelectionReselectionConf sNonIntraSearch 16
CellSelectionReselectionConf threshServingLow 10
LteNeighboringCellRelation threshXLow 0
CellReselectionConfLte tReselectionEUTRAN 2
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
SpeedStateEvalConf nCellChangeHigh 12
SpeedStateEvalConf nCellChangeMedium 4
ReportConfigEUTRA Hysteresis 2
ReportConfigEUTRA reportAmount r8
Coexistence of various technologies requires the possibility of performing mobility between various
types of RAN. Indeed, such mobility requires multi-standard UEs.
Parameters impacting LTE UMTS mobility are presented in the table below.
Object Name Recommended Value
CellSelectionReselectionConf sNonIntraSearch 16
CellSelectionReselectionConf threshServingLow 16
CellReselectionConfUtraFdd threshXLow 0
UtraNeighboring tReselectionUtra 2
SpeedStateEvalConf nCellChangeHigh 12
SpeedStateEvalConf nCellChangeMedium 4
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
ReportConfigUTRA hysteresis 4
ReportConfigUTRA maxReportCells 1
ReportConfigUTRA reportAmount r8
MeasObjectUTRA offsetFreqUTRA 0
Parameters impacting LTE GSM mobility are presented in the table below.
Object Name Recommended Value
CellSelectionReselectionConf sNonIntraSearch 16
CellSelectionReselectionConf threshServingLow 16
CellReselectionConfGERAN threshXLow 0
GeranNeighboring tReselectionGERAN 2
SpeedStateEvalConf nCellChangeHigh 12
SpeedStateEvalConf nCellChangeMedium 4
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
ReportConfigGERAN hysteresis 3
ReportConfigGERAN maxReportCells 1
ReportConfigGERAN reportAmount r8
MeasObjectGERAN offsetFreqGERAN 0
Mobility implying CDMA ecosystem can be realized in idle mode as cell reselection and in connected
mode as cell redirection. Both features are used when LTE coverage ends and there is a larger CDMA
coverage. Parameters impacting LTE CDMA mobility are presented in the table below.
Object Name Recommended Value
CellSelectionReselectionConf sNonIntraSearch 16
CellReselectionConfHrpd threshXLow -2
HrpdNeighboring tReselectionCDMAHRPD 2
SpeedStateEvalConf nCellChangeHigh 12
SpeedStateEvalConf nCellChangeMedium 4
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
ReportConfigCDMA2000 thresholdCDMA2000 -9
MeasObjectCDMA2000 OffSetFreq 1
ReportConfigCDMA2000 hysteresis 3
ReportConfigCDMA2000 maxReportCells 2
ReportConfigCDMA2000 reportAmount r8
In the table below is presented all the new features belonging to LA4.0 and it is identified all the
domains impacted by each feature.
For more information regarding the features the following link should be checked: LA4.x FTS
Documents for Review
Feature name Optimization Capacity Throughput Coverage Latency Mobility Attach MOS
LA4.0 KPI Targets KPI x x x x x x x
LA4.0 eNB SW Capacity Targets KPI x x x x
Commercial Mobile Alert
E2E
System (CMAS) support
Support Fiber delay (or any
delay between modem and RF KPI
head) in LTE
Single antenna transmit scheme Optim x x x x x
VoLTE Solution for Field Trial
E2E
Applications
VoLTE Friendly User Trial
E2E
solution
RoHC v1 Support for VoIP E2E
ECID and LPP protocol support
E2E
(trial)
eNB Synchronization support
E2E
for OTDOA (Trial)
eNB IMS VoIP emergency call
E2E
support (trial)
eNB support of OTDOA
Hearability Enhancement (Trial E2E
)
CSFB enhancement to
UTRAN/GERAN-- enhanced KPI x x
Redirection and PSHO
ANR Support for Inter RAT
Optim x
Neighbours (UTRAN)
LTE RRH Antenna Cross Connect
KPI
Capability Support in LA4.0.1
Transport UL Traffic Shaping E2E/Optim x
Congestion Management at Call
E2E
Admission
Service, and load based
KPI x x
handover behaviour support
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
(eMCTA -Phase 2)
LTE and 1xRTT cell reselection Optim x
CS Fallback to 1XRTT for Voice
Calls-- Dual
E2E/Optim x x
transceiver/receiver UE
Standard based solution
Transport eUTRAN Sharing E2E
eUTRAN Sharing basics: MOCN
KPI
with shared LTE spectrum
eUTRAN Sharing - Mobility KPI
Tuneable Antenna Path Delay
KPI
between RF head and DAS
LTE Support for 5MHz 4Rx
KPI x x x
Receive Diversity
Inter LTE Service Provider
E2E
Roaming (using Home PGW)
CSFB to UTRAN/GERAN
enhancements with enhanced E2E
Redirection
GSMA VoLTE IMS Profile
E2E
Compliance Phase1
LTE Local Breakout with S9 E2E
Online Charging between ALU
E2E
PGW and 8610 ICC over Ro/Gy
LTE Offline Charging Support
with ALU PGW/SGW and IeCCF E2E
on Ga Interface
Public Safety E2E Solution
E2E
Testing for LE4.0
Basic EUTRAN Sharing with
E2E
MOCN
Priority Access With Pre-
E2E
Emption (for all bearers)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is coverage in LTE.
In this chapter it will be beaked in two sub-domains; Downlink Coverage and Uplink Coverage.
Normally some questions arise, such as:
Mainly the Coverage optimization can occur when the Link Budget is below expectations
(Theoretical calculation).
Before starting playing with the parameterization; usually is part of best practice rules for in Near
Cell /Mid Cell & Cell Edge test to follow up simple steps as:
If we could guarantee that these values are normal, the chances to have performance issues are
much less difficult to occur.
If regardless of the correct values, still facing some performance issues, the below parameters can
be used in order to correct the situation.
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
As note; please remember that this can be a static test in each position, or can be a moving test
the same principles can be applied in both situations.
8.1.1 REFERENCESIGNALPOWER
ATTENTION! When modifying this parameter, all other signal power setting will be automatically
adjusted in accordance to a power offset relative to the referenceSignalPower.
This parameter is expressed in dBm. It is converted into linear scale (miliwatts) according to the
following formula:
P [mW] = 100.1referenceSignalPower
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Note: The following table translates the expected behaviour in terms of cellDLTotalPower when
changing the reference Signal Power; some difference may occur if other sets of parameters are
used also.
8.1.2 PHICHRESOURCE
PHICH channels are grouped in PHICH groups. Each PHICH group consists of 8
PHICH channels (hence conveys 8 ACK/NACKs) that use the same resources,
PHICH channels of a same group being separated by orthogonal sequences.
Where:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
A PHICH group consists of 3 REGs over either 1 or 3 OFDM symbols, depending on the value of
parameter phich-Duration (normal or extended). This parameter can only be set to extended
if the CFI is equal to 3.
Setting the value low will result in lower number of PHICH groups in a subframe, so the higher the
number of ACK/NACKs that need to be sent out the longer the buffer, eventually leading to failing
to transmit the messages.
Setting value high will impact in having a higher number of PHICH groups in a subframe, so the
fewer ACK/NACKs needed to be transmitted, OFDM symbols are not used and the allocated
resources for this process go to waste.
8.2.1 SIRTARGETFORREFERENCEPUCCHFORMAT
The PUCCH power control procedure is used to guarantee the required error rate. For this purpose,
it aims at achieving a target SIR the value of which guarantees the required error rate. The SIR
target is set to sIRTargetforReferencePUCCHFormat for PUCCH Format 1A and to
sIRTargetforReferencePUCCHFormat + deltaFPUCCHFormat1b for PUCCH format 1B.
Note that the PUCCH power control procedure assumes shortened PUCCH Format to account for the
SRS configuration.
This parameter is a key RF optimization parameter. Higher settings of this parameter will improve
PUCCH reception, but will also drive higher UE TX power leading to interference to neighbouring
cells, and vice-versa.
Note:Recent results coming from VzW FSA, are pointing for a different value main justification
is that in order to support dynamic change of the number of receiving antennas (and 4x
receive), in LA4 to have the same effect /influence they need to be adjusted.
The eNB starts Spectrum Efficiency Correction when the call setup is completed using these two
parameters and sEcorrMin, sEcorrMax.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
This parameter controls the initial value (in dB) of correction metric SEcorr managed by the link
adaptation function to maintain the PUSCH initial HARQ BLER around its target value.
The lower the sEcorrInit value, the more conservative is the PUSCH link adaptation starting point
and, consequently, the lower the PUSCH MCS. In other words, the lower the sEcorrInit values, the
lower is the initial PUSCH MCS value, and the lower are the risks of observing high BLER value at call
setup or on the target cell just after handover.
Note however that the lower the sEcorrInit value, the longer the link adaptation will take to
converge to its setpoint. This may impact the maximum achievable throughput for a brief period
(exact time depends on traffic activity) after call setup or handover.
Note:Recent results coming from VzW FSA, are pointing for a different value main justification
is that in order to support dynamic change of the number of receiving antennas (and 4x
receive), in LA4 to have the same effect /influence they need to be adjusted.
The other values in the SE_corr tables are set in order to allow fast convergence around that set
point.
&
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The uplink synchronization detection mechanism is based on the SIR metric derived from the
Sounding Reference Signal observations. Upon processing of an SRS measurement report from L1
related to user k, the UL scheduler evaluates the UL synchronization status of that user by
comparing the SRS synchronization metric computed to threshold levels as follows:
The threshold for the transition from In sync state to out of sync state is configured by
parameter ulSyncSINRsyncToOOSTreshold, i.e.
If the UE is assumed in In Sync state and the following condition is met:
SINRsync(userk)<ulSyncSINRsyncToOOSTreshold
Then the user is considered in Out Of Sync state.
The threshold for the transition from out of sync state to in sync state is configured by
parameter ulSyncSINROOStoSyncTreshold i.e. If the UE is assumed in out of sync state and
SINRsync(userk) > ulSyncSINROOStoSyncThreshold
Then the user is considered in In Sync state by the MAC scheduler.
Concerning the deltaFPUCCHFormat1; the setting of the UE Transmit Power PPUCCH for PUCCH in
{
subframe i is defined by PPUCCH (i) = min Pmax, P0 _ PUCCH + PL + F _ PUCCH + g(i) [dBm] }
Where F _ PUCCH denotes the (PUCCH) format specific power offset; the format dependent power
offset TF_PUCCH (TF) is defined on a per cell basis and configured by parameter
deltaFPUCCHFormat1 for format 1.
Note:
Recent results coming from VzW FSA, are pointing for a different value main justification is
that in order to support dynamic change of the number of receiving antennas (and 4x receive),
in LA4 to have the same effect /influence they need to be adjusted.
VzW FSA LA4 Value= -14 for ulSyncSINRsyncToOOSThreshold & -13 for
ulSyncSINROOStoSyncThreshold
8.2.4 DELTAFPUCCHFORMAT1
This parameter is used for setting the transmit power of SR over PUCCH by the UE. LA3.0 eNodeB
relies on Scheduling Request on PUCCH from UE for scheduling uplink grants. If the SR is not
received by the eNodeB, it will trigger the UE to declare SRmax failure, which in turn will trigger
eNodeBs OOS condition. Under certain conditions the SR power may not be sufficient to ensure
detection. By boosting the SR transmit power, it increases the SR detection likelihood at the
eNodeB.
Concerning the deltaFPUCCHFormat1; the setting of the UE Transmit Power PPUCCH for PUCCH in
{
subframe i is defined by PPUCCH (i) = min Pmax, P0 _ PUCCH + PL + F _ PUCCH + g(i) [dBm] }
Where F _ PUCCH denotes the (PUCCH) format specific power offset; the format dependent power
offset TF_PUCCH (TF) is defined on a per cell basis and configured by parameter
deltaFPUCCHFormat1 for format 1.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The Uplink cell coverage is defined as a target service that UE must satisfy at cell edge conditions.
The worst case is 14.5 kbps which was selected for this case. The cell coverage is independent of
channel bandwidth and is strictly dependent of UE TX power which is 23dBm maximum for the UEs
supplied by third parties and tested by ALU.
UL 2.6GHz
Target Service at cell edge PS14.5
Table 8-2: UL 2.6GHz
Suburban In-Car
Path loss 144.3
cell range 2.95
Table 8-4: Path Loss & UL Cell Range Suburban in Car
As expected, for the two environmental models the dense urban cell coverage is much lower but it
gives a rough understanding for the UL coverage and where to aim as a low and high value expected
in field tests.
In Downlink the eNBs ReferenceSignalPpower is influencing the cell range. Two cases were selected
for ReferenceSignalPower. The coverage computation is independent of channel bandwidth.
Almost every time the DL cell coverage will be higher than UL cell coverage. Not always selecting a
high ReferenceSignalPower will mean better coverage: Hearing the Sync signals and MIB isnt
enough to obtain an RRC connected state.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The so called total cell coverage is expressed as a minimum between UL and DL. The thorough cell
range is expressed by the following formula:
Total cell coverage [m] = Min (UL cell range, DL cell range)
The total cell range will almost every time be the UL one. In a dense site area where the cells are
close to one another, and effects of shadowing, multipath propagation are very accentuated, cell
coverage is limited and a high UE Tx Power will create interference in neighbouring cells when UE is
inside its serving cell edge. The phenomenon is very common and needs to be analyzed carefully
from the network planning stages. The Fractional Power control algorithm is a good way to improve
conditions at cell edge by lowering the SIR target level so the interference in neighbouring cell is
kept at a minimum.
Fractional Power control is used in order to limit the interference that cell edge-users create to the
neighbouring cells.
In fractional power control, the transmit power adjustment pUSCHPowerControlAlphaFactor PL
compensates for only a fraction of the estimated path loss PL. The result is that the SINR achieved
by the UE at the eNB varies linearly with the path loss. Higher levels of path loss are associated with
lower SINR and vice versa.
When the UE is close to the cell centre, the path loss decreases and hence the target SINR is
increased. When the UE is at the cell edge, the path loss increases and hence the target SINR is
decreased.
Figure 8.2-1: Throughput for single UE vs. Path loss (Lab environment)
In high path loss conditions, the throughput with a lower SIR target becomes better because eNB
will grant a lower MCS but with more PRBs than for high SIR Target.
For the Fractional power control tests, was used the following values /configuration expressed in
the two examples given below. In the first example given the SIR target = 0 between Path loss 110
to 140dB. In the 2nd below the SIR target = 0 between Path loss 135 to 140dB.
maxSIRtargetForFractionalPowerCtrl = 15.0dB
minSIRtargetForFractionalPowerCtrl = 0.0dB
uplinkSIRtargetValueForDynamicPUSCHscheduling = 15.0dB
pathLossNominal = 60dB
p0NominalPUSCH = -79 dBm
Path loss where SIRtarget reaches 0dB: 110dB
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
maxSIRtargetForFractionalPowerCtrl = 15.0dB
minSIRtargetForFractionalPowerCtrl = 0.0dB
uplinkSIRtargetValueForDynamicPUSCHscheduling = 11.0dB
pathLossNominal = 80dB
p0NominalPUSCH = -84 dBm
Path loss where SIRtarget reaches 0dB: 135dB
8.2.6 PUSCHPOWERCONTROLALPHAFACTOR
Part of PUSCH power control and is intended to allow partial compensation of the path loss or
otherwise stated it allows controlling, by decreasing, the PUSCH for users in cell edge conditions.
If set to 1; an increase in path loss will determine the same increase in PUSCH. If this parameter is
not set to 1, the increase in PUSCH power can be lower than the increase in path loss. It is thus a
means of controlling the UL interference created in the neighbour cell by the UEs found near the
cell edge.
Because the value of this parameter represents a trade-off between minimizing interference and
maximizing throughput, its value must be set according to the clients desired network behaviour.
If Fractional Power Control is used, the recommended value of this parameter is 0.8. If Fractional
Power Control is not to be used, the parameter must have the value 1.
Take care that this recommendation is only for commercial usage.
KPI Impact:
Coverage higher values improve coverage
Throughput higher values will improve throughput, while lower values will decrease it.
Capacity - higher values might reduce capacity, while lower values might increase it.
The optimization process of this parameter should include the customer definition of the optimum
trade-off between cell throughput and interference towards the neighbour cells. The choice can be
different if cell wise optimization is to be performed or if a network wide setting is being aimed.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
8.2.7 QRXLEVMIN
A parameter with this name appear in several objects and is then transmitted to UE inside several
system information block types i.e.SIBs:
The one that is object of this paragraph is transmitted in SIB1 which contains information relevant
when evaluating if a UE is allowed to access a cell and defines the scheduling of other system
information.
This parameter impacts the cell size in terms of re-selection area i.e. mobility in idle mode.
It configures the serving cell min required RSRP level used by the UE in cell reselection. The value
sent over the RRC interface is half the value configured.
Changing the value of this parameter will have an effect on the cell the UE is camped on during its
idle mode. One way of optimizing it is to find the value that best superposes the cell size in idle
with the cell size in active mode such that an idle-to-active transition would not result in an
immediate handover decision.
The exact selection criterion, S relev , is based on several values related to measured signal and power
compensation level as below:
As long as the above relation is being satisfied the measured cell is selected. Increasing this value
will lead the mobile to start cell-selection/re-selection procedure sooner because the inequality
will be satisfied for a narrower range of measured values and then will artificially decrease cell size
in idle mode. Indeed, for avoiding too many measurements to be performed for too long a time,
there is a decision for starting inter-cell measurements based only on the received field level.
The variation of the cell size when various RSRP targets are set is given in the figure below. The
information in this picture is only informative since the cell size variation strongly depends on the
clutter.
Recommended & Default Value = -120 for 10MHz BW or -124 in case of 5MHz BW
Will lead the mobile to start cell-selection/re-selection procedure sooner because the inequality
will be satisfied for a narrower range of measured values and then will artificially decrease cell size
in idle mode. Indeed, for avoiding too many measurements to be performed for too long a time,
there is a decision for starting inter-cell measurements based only on the received field level.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Attach/Detach - low values might negatively impact (delay or make impossible) the attach
operation.
Coverage - lower value means larger cells.
Mobility - high values might create coverage discontinuity in idle, as seen by mobile.
When trying to match the idle mode cell size and active mode cell size, i.e. optimize the value of
this parameter, drive tests must be performed in the cell. The testing procedure should comprise
the following steps:
Step 1: With UE in active mode, perform a drive test back and forth between the two cells on
various routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 2: Post process the logged data and determine the cell edge, as being the positions at which
the UE switched to the neighbour cell and the measured SINR at those locations.
Step 3: Set the value of qRxLevMin to one of the following values {- 124, -122, -120, -118, -116}.
Step 4: With UE in idle mode, perform a drive test back and forth between the two cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 5: Choose another qRxLevMin and repeat Step 4.
Step 6: Post process the logged data and determine the positions at which the UE started searching
for another cell and the positions at which UE switched to the neighbour cell along with the
measured SINR.
Step 7: Based on the cell size in active mode and cell sizes in idle mode, choose the optimized value
in order to compensate if you have a smaller or lager cell than you wish.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
qRxLevMin
selection if:
Inter-Cells Gaps
Inter-Cells
Overlapping
Cell load
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
8.2.8 P0NOMINALPUSCH
This parameter is, somehow indirectly, impacting the power the UE transmits, before any power
control commands is being received from the eNodeB. This parameter is a key RF optimization
parameter.
Higher settings will improve PUSCH reception, but will also drive higher UE Tx power leading to
interference to neighbouring cells, and vice-versa. Its current default value is -108dBm.
Indeed, the power of the UE will be adapted once the transmission is being started and the impact
this parameter has on the UE power decreases with time.
Optimization would mean finding the best value that, at the same time, for which the PUSCH
reception is good enough, even at the beginning of the PUSCH transmission, and the interference
created towards the neighbour cells is kept to an acceptable level. For more details on the PUSCH
power control see the end of this paragraph.
KPI Impact:
Coverage higher value will temporarily increase the UL interference
Access lower values might increase the access time
For optimizing the value of this parameter for minimizing the interference in neighbour cells, two
cells and several UEs are needed (in the interfering cell). The following steps must be performed
(this recommendation is only for the UL Fractional Power Control Disabled):
Step 1: In victim sell, use the default p0NominalPUSCH value. In the interfering cell, set
p0NominalPUSCH to one of the values {-112, -110, -108, -106, -104}.
Step 3: In interfered cell perform an UL data transfer and log data related to PC command (TPC
command field or F value) and PUSCH BLER and PUSCH DM RS SINR.
Step 4: In the interfering cell, with UEs located near the cell edge, perform UL data transfer with
several UEs, in synchronous manner.
Step 5: In the interfering cell choose another value for p0NominalPUSCH and repeat Step 3 and Step
4.
Step 6: Post process the logged data and provide results in terms PUSCH BLER of the average PUSCH
DM RS SINR for each value p0NominalPUSCH in the interfering cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The setting of the UE Transmit power PPUSCH for the physical uplink shared channel (PUSCH)
transmission in the subframe is defined by:
Where:
PMAX is the maximum allowed power that depends on the UE power class
MPUSCH (i) is the bandwidth of the PUSCH transmission expressed in number of resource blocks taken
from the resource allocation valid for uplink subframe i from scheduling grant received on subframe
i-KPUSCH.
P0_PUSCH is a parameter obtained as a sum of a cell specific nominal component p0NominalPUSCH
signalled from higher layers and a UE specific component p0UePUSCH.
pUSCHPowerControlAlphaFactor is a cell specific parameter signalled from higher layers in order to
support fractional power control.
PL is the downlink path loss estimate calculated in the UE.
TF(TF (i)) denotes the power offset depending on PUSCH transport format TF(i).
Both accumulated and non accumulated power control rules are used this is set by means of
parameter accumulation Enabled. The current PUSCH power control adjustment state in subframe i
is given by f (i):
where:
PUSCH is a UE specific correction value in dB, also referred to as a TPC command and is included in
PDCCH with DCI format 0 on subframe i-KPUSCH.
f(0) = 0.
For case when enabling Fractional Power control use following formula for applying the correct
value to the parameter:
Example 1:
for pUSCHPowerControlAlphaFactor =1, and SINR_target_nominal = 1 dB,
p0NominalPUSCH = 1 + 0 -112 = -111 dBm
Example 2:
for pUSCHPowerControlAlphaFactor =0.7, and SINR_target_nominal = 15 dB,
p0NominalPUSCH = 15 + (1-0.7)*140 112 = -55 dBm
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
8.2.9 UPLINKSIRTARGETVALUEFORDYNAMICPUSCHSCHEDULING
This parameter is used inside PUSCH power control algorithm as outer loop power control for non-
semi-static. It is used as an initial target for the SINR values. During transmission, the SINR targets
are changing based on the measured path loss.
The input of the UL outer-loop power control function is the path loss along with some other
parameters.
In the commercial mode, and on a network level, the higher the SINR target (i.e. the higher the
setting of uplinkSIRtargetValueForDynamicPUSCHscheduling) the higher the near-cell throughput but
the higher the interference generated in the different cells of the network (and thus the lower the
cell-edge throughput and at some point the lower overall cell throughput too). In this case, the
default setting of this parameter (for a target IoT of 5.5 dB and a nominal path loss of 60 dB) should
be as follows:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Throughput: high values increase the throughput for near cell and mid-cell conditions.
Capacity - high values allow reaching the capacity for a wider range of propagation
conditions.
Coverage - high values might reduce the coverage if the target is not dynamically adjusted
based on propagation conditions.
Mobility - might negatively impact the throughput during handover if the threshold is set too
high.
For optimizing the value of this parameter for minimizing the interference in neighbour cells while
maximizing the throughput in the analyzed cell, two cells and several UEs are needed (in the
interfering cell). The following steps must be performed:
Step 1: In victim cell, use the default parameters. In the interfering cell, set
uplinkSIRtargetValueForDynamicPUSCHscheduling to one of the values {15, 14, 10, 8, and 6}.
Step 2: In victim cell perform an UL data transfer and log data related to PC command (TPC
command field or F value) and PUSCH BLER and PUSCH DM RS SINR.
Step 3: In the interfering cell, with UEs located near the cell edge, perform UL data transfer with
several UEs, in synchronous manner and log the value of the throughput.
Step 4: In the interfering cell choose another value for
uplinkSIRtargetValueForDynamicPUSCHscheduling and repeat Step 2 and Step 3.
Step 5: Post process the data and choose the value of
uplinkSIRtargetValueForDynamicPUSCHscheduling that provides an acceptable trade-off between
the throughput in the interfering cell and the throughput in the victim cell.
s lo
pe
Target SINR
=
-(
1-
PU
SC
maxSIRtargetForFractionalPowerCtrl
HP
ow
uplinkSIRtargetValueForDynamicPUSCHscheduling
er
Co
n
tro
lA
lp
ha
Fa
minSIRtargetForFractionalPowerCtrl
cto
r)
pathLossNominal
PL
Figure 8.2-6: Slope - PuschPowerControl vs. uplinkSIRtargetValueForDynamicPUSCHscheduling
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is access in LTE.
Normally some questions arise, such as:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Mainly the Access optimization can occur when the attach success rate is below the ALU KPI
As main indicator to evaluate the performance several tests to access the network should be
performed; although before starting playing with the parameterization; usually is part of best
practice rules for in Near Cell /Mid Cell & Cell Edge test to follow up simple steps as:
If we could guarantee that these values are normal, the chances to have performance issues are
much less difficult to occur.
If regardless of the correct values, still facing some performance issues, the below parameters can
be used in order to correct the situation.
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
As note; please remember that this can be a static test in each position, or can be a moving test
the same principles can be applied in both situations.
9.1.1 PREAMBLEINITIALRECEIVEDTARGETPOWER
Open-loop power control is applied for initial transmission of RACH (i.e. message1). The transmit
power is determined by taking into account the total UL interference level and the required SINR
operating point.
At each new transmission of the preamble, the power is ramped up by RAMP_UP dB until we reach the
maximum number of transmissions preambleTransMax. If the mobile still does not receive any
Random Access response from the eNodeB, the UE MAC layer then declares the Random Access
procedure as failed.
30
20
10
PRACH TxPower
0
Try1#-104
Try1#-96
-10
-20
-30
-40
PL
70 75 80 85 90 95 100 105 110 115 120 125 130 135 140 145 150
-37.5 -42.5 -47.5 -52.5 -57.5 -62.5 -67.5 -72.5 -77.5 -82.5 -87.5 -92.5 -97.5 -102.5 -107.5 -112.5 -117.5 Estim.
RSRP
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Minimize the repetitions i.e. RACH attempts and hence expedite call setup, but will cause higher
interference to other cells during the attach procedure. Thus there will be higher interference
during a shorter period of time.
KPI Impact:
Attach/Detach: low values of this parameter can delay the success of the attach operation.
Very low values might even make the attach operation impossible.
A good optimization criterion for this parameter would be to set it to the lowest limit that ensures
that the required RACH preamble success rate at 1st attempt is achieved.
The optimization of this parameter should consider the steps below:
Step 1: In the database, check that the default value dBm-104 is set.
Step 2: Perform drive tests while connecting and disconnecting the UE in various parts of the cell
while logging the data and the GPS position.
Step 3: Change the value of the parameter to the following {dBm-108, dBm-106, dBm-102, dBm-100}
and repeat Step 2 on the similar route.
Step 4: Provide results in form of three graphs representing:
9.1.2 PREAMBLETRANSMITPOWERSTEPSIZE
This parameter is a key RF optimization parameter that impacts connection setup performance and
uplink interference to neighbouring cells. Higher values will minimize the repetitions/ RACH
attempts and hence expedite connection setup, but will cause higher interference to other cells.
Lower values will tend to increase RACH repetition/ connection setup delay.
The current default value for this parameter is dB6.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Attach/Detach: low values of this parameter can delay the success of the attach operation.
Very low values might even make the attach operation impossible.
Mobility: low values might lengthen the interruption time.
A good optimization criterion for this parameter would be to set it to the value that minimizes the
number of preamble transmissions.
The optimization of this parameter must be performed in conjunction with the optimization of the
previous parameter. It is best to start optimization by first considering the highest value of this
parameter i.e. dB6
The optimization of this parameter should consider the steps below:
The Nominal transmit power for RACH msg3, denoted as PO_ NOMINAL _ PUSCH is computed at the UE as:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Attach/Detach: low values of this parameter(s) can slightly delay the success of the attach
operation.
9.1.4 DELTAPREAMBLEMSG3
A good optimization criterion for this parameter (deltapreamblemsg3) would be to set it to the value
that minimizes the number of HARQ retransmissions of Msg3.
9.1.5 TPCRACHMSG3
A good optimization criterion for this parameter (tPCRACHMsg3) would be to set it to the value that
minimizes the number of HARQ retransmissions of Msg3.
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is Downlink Throughput in LTE.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Mainly the DL t-put optimization can occur when the average throughput value for a specific
location is not matching the ALU product specification for a determined Bandwidth target.
Before starting playing with the parameterization; usually is part of best practice rules for in Near
Cell /Mid Cell & Cell Edge test to follow up simple steps as:
If we could guarantee that these values are normal, the chances for having performance issues
are much less difficult to occur.
If regardless of the correct values, still facing some performance issues, they below parameters can
be used in order to correct the situation.
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
As note; please remember that this can be a static test in each position, or can be a moving test
the same principles can be applied in both situations.
10.1.1 DLMCSTRANSITIONTABLE
This table contains 28 float values representing the thresholds of SINRs values for which the DL
modulation is being changed and it is part of an intricate algorithm inside DL scheduler.
Optimization of this table would imply changing the values of the thresholds either by decreasing
them or by increasing them. Indeed, it is not necessary to have them all increased or all decreased.
Both uniform and non-uniform modifications of these values are possible. Below, several suggestions
are presented, two of them implying uniform modifications of threshold values and four of them
considering non-uniform modifications.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 10.1-1: Radio link Quality vs. MCS Robustness vs. Throughput
In the above Figure 10.1-1 it can be observed that both Radio Link Quality, MCSs Robustness and
Throughput are closely related meaning that for a better Radio Link, this would imply a less robust
MCS, but in other hand, the final result is a higher Throughput!
Figure 10.1-2: Radio link Quality vs. dlMCSTransition Table vs. Throughput
In the table below there are several (academic) examples of threshold tuning for a 10MHz band.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Increase all threshold values (up-shift) will result in lower data rates because higher MCS will only
be selected for higher values of SINRs. Indeed, due to improved SINRs when a given MCS is selected,
there will be a lower percentage of transmission errors over air interface.
Decrease all values of the thresholds (down - shift) will lead to more optimistic MCS assignments
and hence, higher bitrates and possibly more HARQ retransmissions and higher BLERs.
Keep the lower values unchanged and gradually increase/decrease the higher values. Such a
modification will only force less/more robust MCSs (i.e. higher/lower data rates) for good
propagation conditions.
Keep the higher values unchanged and gradually increase/decrease the lower values. Such
modifications will only force less/more robust MCSs (i.e. higher/lower data rates) for bad
propagation conditions.
Increase the lower values and decrease the higher values while keeping the middle values
unchanged. Such a modification will force more robust MCSs (i.e. lower data rates) for bad
propagation conditions and will force less robust MCSs (i.e. higher data rates) for good propagation
conditions.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Decrease the lower values and increase the higher values while keeping the middle values
unchanged. Such modifications will force less robust modulations (i.e. higher data rates but possible
higher BLER) for bad propagation conditions and more robust MCSs (i.e. lower data rates) for good
propagation conditions.
All types of thresholds tuning specified above can indeed be performed by changing the thresholds
by various amounts. Finding the best type of modification and the amount by which the changes are
made is part of the optimization process.
KPI Impact:
Throughput - proper tuning increases the throughput
Capacity - proper tuning can increase the capacity (capacity reached over a slightly wider
range of propagation conditions).
For finding the optimum set of SINR thresholds among the sets proposed in the table above, a drive
test is needed in the cell to be optimized. The flowing steps need to be performed and the optimum
set of thresholds shall be chosen based on the observed performance.
Step 1: In the eNodeB database, choose the default set of values for dlMCSTransitionTable, the
values in the Default column in the table above.
Step 2: While performing DL UDP transfer, perform a drive tests through the cell for covering
various morphologies and positions relative to the transmitting antennas (near-cell, mid-cell, cell
edge) and log the instantaneous throughput.
Step 3: Chose another set of values from the table above and repeat Step 2.
10.1.2 DLSINRTHRESHOLDBETWEENCLMIMOONELAYERANDTXDIV
Force TX Div instead of 1-Layer Closed Loop which will be reflected in lower throughputs and
performance for the same radio condition.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
10.1.3 DLSINRTHRESHOLDBETWEENCLMIMOTWOLAYERSANDONELAYER
Force 2-Layer CL-MIMO for bad propagation condition. This will be reflected in lower throughput at
least for SINRs values situated between the actual value of the threshold and the optimized value of
the threshold. Higher BLER and increased HARQ retransmissions might as well be observed.
KPI Impact:
Throughput - values both higher and lower than the optimal value decrease the throughput.
For finding an optimized value of this parameter (i.e. the one that maximizes the throughput) for a
given environment, a procedure containing the steps below can be used:
Step 1: In the database, set transmission mode = tm4 and check that default value of
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer (i.e. 15) is also correctly set.
Step 2: While performing DL FTP/UDP transfer, perform a drive tests through the cell and log the
instantaneous throughput.
Step 3: Repeat Step 1 & 2 for the following set of values of
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer: {9, 11, 13, and 17}
Step 4: Provide results in form of a graph representing average throughput versus
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer values
Step 5: Provide recommendations for choosing
dlSinrThresholdBetweenCLMimoTwoLayersAndOneLayer
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
10.1.4 DLSINRTHRESHOLDBETWEENOLMIMOANDTXDIV
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Force TxDiv in good transmission conditions which will be reflected in lower throughputs for good
radio condition.
Decreasing the value of this parameter would:
Force OL MIMO for bad propagation condition for which the MIMO algorithms are not anymore
performing well. This will be reflected in lower throughput at least for SINRs values situated
between the actual value of the threshold and the optimized value of the threshold. Higher BLER
and increased HARQ retransmissions might as well be observed.
KPI Impact:
Throughput - values both higher and lower than the optimal value decrease the throughput.
For finding an optimized value of this parameter (i.e. the one that maximizes the throughput) for a
given environment, a procedure containing the steps below can be used:
Step 1: In the database, set the transmission mode to tm3 and check that the default value of
dlSinrThresholdBetweenOLMimoAndTxDiv (i.e. 15) is also correctly set.
Step 2: While performing DL FTP/UDP transfer, perform a drive test and log the instantaneous
throughput.
Step 3: Repeat Step 1 and step 2 the following set of values of
dlSinrThresholdBetweenOLMimoAndTxDiv: {i.e. 9, 11, 13 and 17}
Step 4: Provide results in form of a graph representing average throughput versus
dlSinrThresholdBetweenOLMimoAndTxDiv values
Step 5: Provide recommendations for choosing dlSinrThresholdBetweenOLMimoAndTxDiv.
10.1.5 ALPHAFAIRNESSFACTOR
alphaFairnessFactor = 0 yields a maximum C/I scheduler. The scheduler provides more resources to
UEs in better conditions
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
alphaFairnessFactor = 1 yields a fair scheduler. The scheduler attempts to provide the same number
of RBs to all the UEs
alphaFairnessFactor = 2 yields an increased fairness scheduler. The scheduler attempts to allocate
the resources in such a way that all the UEs eventually get the same data rate.
In the Figure 10.1-7 it is presented the impact of using the different values for alphaFairnessFactor;
such as 0 or 2.
The test in Figure 10.1-7 was performed with the usual configuration; 2NC; 4MC; 2CE, and having
the different alphafairnessFactor will make the scheduler to adjust more or less fair the resources
to all the ue's; resulting in a lower sector t-put for the more fair distribution of resources.
KPI Impact:
Throughput Low values increase the throughput in the near&mid-cell condition at expense of
cell edge users.
Capacity - Low values increase the cell overall throughput at expense of cell edge users.
10.1.6 DYNAMICCFIENABLED
This parameter when set to True allows the CFI to be dynamically adjusted to use the lowest
value needed for PDCCH usage. This makes more OFDM symbols available to PDSCH when PDCCH
usage is low (fewer users), resulting in higher throughputs. In this case (dynamicCFIEnabled set to
True), parameter cFI is ignored.
When set to False, the CFI is static and derived from parameter cFI. The latter should be set
keeping in mind that value 1 is only supported in 20 MHz and knowing that higher values of CFI
allow for more PDCCH robustness and/or more users served per TTI, but at the expense of
throughput (fewer resources for PDSCH).
In the Table 10-2 it is illustrated the theory impact on the PDSCH channel when disabling the
DynamicCFI and forcing the usage of different values for CFI (1, 2 or 3).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
OFDM symbol per 1ms CFI PDSCH [symbol] PDSCH usage[%] PDSCH decrease [%]
14 1 13 92,86% n/a
14 2 12 85,71% 7,14%
14 3 11 78,57% 7,14%
Table 10-2: Theory Assumption on CFI Tuning
10.1.7 CFI
This parameter Control Format Indicator is limited to the value 1, 2 or 3. For bandwidths greater
than ten resource blocks, the number of OFDM symbols used to contain the downlink control
information is the same as the actual CFI value. Otherwise span of the downlink control information
is CFI+1 symbol. It will be only taken into consideration if the dynamicCFIEnabled is set to False.
Higher values of CFI allow for more PDCCH robustness and/or more users served per TTI, but at the
expense of throughput (fewer resources for PDSCH).
In the Table 10-2 we have the expected value when playing with the value of CFI.
Recommended Value & Default= "5 & 10 MHz =3 for 20MHz = 2"
KPI Impact:
Throughput Low values increase the cell overall throughput.
Note: for a demo case & if you are in 20MHz and the goal is to show max troughput you can
use the CFI set to 1; but to be sure that also dynamicCFIEnabled is set to false; plus
CFI1Llowed should set to "True".
Using this set of parameters configuration and in near cell radio condition (optimum
conditions); you can boost the Downlink Throughput, since his makes more OFDM symbols
available to PDSCH when PDCCH usage is low (fewer users), resulting in higher throughputs.
10.1.8 CFI1ALLOWED
Like the name indicates this parameter allows the usage or not of the value 1 for CFI.
Only possible to use CFI =1 in 20MHz.
Recommended Value & Default= "5 & 10 MHz = False for 20MHz = True"
10.1.9 CFI2ALLOWED
Like the name indicates this parameter allows the usage or not of the value 2 for CFI.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
10.1.10 CFI3ALLOWED
Like the name indicates this parameter allows the usage or not of the value 3 for CFI.
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is Uplink Throughput in LTE.
Normally some questions arise, such as:
Mainly the UL t-put optimization can occur when the average throughput value for a specific
location is not matching the ALU product specification for a determined Bandwidth target.
Before starting playing with the parameterization; usually is part of best practice rules for in Near
Cell /Mid Cell & Cell Edge test to follow up simple steps as:
If we could guarantee that these values are normal, the chances to have performance issues are
much less difficult to occur.
If regardless of the correct values, still facing some performance issues, they below parameters can
be used in order to correct the situation.
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
As note; please remember that this can be a static test in each position, or can be a moving test
the same principles can be applied in both situations.
11.1.1 UPLINKSIRTARGETVALUEFORDYNAMICPUSCHSCHEDULING
This parameter used inside PUSCH power control algorithm as outer loop power control. It is initial
target for the SINR values.
During transmission, the SINR targets are changing based on the measured PL. The input of the UL
outer-loop power control function is the PL along with some other parameters.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The default value of this parameter is 10, but higher values, as high as 15, could be used for
maximum throughput tests, especially outdoor for forcing higher power and thus allowing the
compensation of higher PL for preserving the throughput.
It is not recommended to consider high values in a loaded network due to increased interference
even if the throughput for one user could be higher for higher values of this parameter.
In high path loss conditions, the throughput with a lower SIR target becomes better because eNB
will grant a lower MCS but with more PRBs than for high SIR Target.
PUSCHPowerControlAlphaFactor uplinkSIRtargetValueForDynamicPUSCHscheduling
1.0 1.0
0.8 19.0
Table 11-1: uplinkSIRtargetValueForDynamicPUSCHscheduling vs. PUSCHPowerControlAlphaFactor
Increase interference in the neighbour cells due to higher transmitting power. This would result in
lower throughputs in the neighbour cells.
Decrease the power of the UE which would result in lower MCSs and lower throughputs.
Decreasing this parameter will decrease the overall level of interference and hence improve the
throughput of cell-edge users at the expense of cell-centre UEs, i.e. the peak throughputs will be
lower.
KPI Impact:
Throughput: high values increase the throughput for near cell and mid-cell conditions.
Capacity - high values allow reaching the capacity for a wider range of propagation
conditions.
For optimizing the value of this parameter for minimizing the interference in neighbour cells while
maximizing the throughput in the analyzed cell, two cells and several UEs are needed (in the
interfering cell). The following steps must be performed:
Step 1: In victim sell, use the default parameters. In the interfering cell, set
uplinkSIRtargetValueForDynamicPUSCHschedulingto one of the values {15, 14, 10, 8, and 6}.
Step 2: In victim cell perform an UL data transfer and log data related to PC command (TPC
command field or F value) and PUSCH BLER and PUSCH DM RS SINR.
Step 3: In the interfering cell, with UEs located near the cell edge, perform UL data transfer with
several UEs, in synchronous manner and log the value of the throughput.
Step 4: In the interfering cell choose another value for
uplinkSIRtargetValueForDynamicPUSCHscheduling and repeat Step 2 and Step 3.
Step 5: Post process the data and choose the value of
uplinkSIRtargetValueForDynamicPUSCHscheduling that provides an acceptable trade-off between
the throughput in the interfering cell and the throughput in the victim cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
11.1.2 PUSCHPOWERCONTROLALPHAFACTOR
Part of PUSCH power control and is intended to allow partial compensation of the path loss or
otherwise stated it allows controlling, by decreasing, the PUSCH power for users in cell edge
conditions.
If set to 1, an increase in path loss will determine the same increase in PUSCH power. If this
parameter is not set to 1, the increase in PUSCH power can be lower than the increase in path loss.
It is thus a means of controlling the UL interference created in the neighbour cell by the UEs found
near the cell edge.
Because the value of this parameter represents a trade-off between minimizing interference and
maximizing throughput, its value must be set according to the clients desired network behaviour.
If Fractional Power Control is used, the recommended value of this parameter is 0.8. If Fractional
Power Control is not to be used, the parameter must have the value 1.
Increase the throughput for the users experiencing cell edge propagation conditions.
Increase the interference toward the neighbouring cells which might lower the throughput of users
being in cell edge propagation conditions in neighbour cells.
Decreasing the value of this parameter would:
Decrease the throughput for the users experiencing cell edge propagation conditions.
Decrease the interference toward the neighbouring cells which might increase the throughput of
users being in cell edge propagation conditions in neighbour cells.
KPI Impact:
Throughput high values increase the throughput in the near&mid-cell condition. The Edge
cell performances depend on PL & MonoUE vs. MultiUE.
High values may lead to a decrease in the overall system capacity in Uplink, due to increased
UL interference.
The optimization process of this parameter should include the customer definition of the optimum
trade-off between cell throughput and interference towards the neighbour cells. The choice can be
different if cell wise optimization is to be performed or if a network wide setting is being aimed
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Our initial assumption was to demonstrate other parameter presents in the power control algorithm
performance impact, besides pUSCHPowerControlAlphaFactor parameter. So far we have considered
set of values for related test cases, they can be seen in the Table 11-2
uplinkSIRtargetValueForDynamicPUSCHscheduling 15 15 15 15 15 15 15
pUSCHPowerControlAlphaFactor 1 1 1 1 1 1 1
pUSCHPowerControlAlphaFactor 0,8 0,8 0,8 0,8 0,8 0,8 0,8
pUSCHPowerControlAlphaFactor 0,7 0,7 0,7 0,7 0,7 0,7 0,7
pUSCHPowerControlAlphaFactor 0,6 0,6 0,6 0,6 0,6 0,6 0,6
pUSCHPowerControlAlphaFactor 0,5 0,5 0,5 0,5 0,5 0,5 0,5
p0NominalPUSCH 60 60 60 85 70 20 40
minSIRtargetForFractionalPowerCtrl 0 0 0 0 0 0 0
maxSIRtargetForFractionalPowerCtrl 15 20 19 20 19 19 19
Table 11-2: Different Sets Combinations
We have considered a low IoT value=3dB in an UL&DL balanced cabled tests lab environment. We
have used an automatic mechanism to increase the attenuation over the same amount of time for
all the tests we have performed, 10MHz and 2.6GHz network.
Based on Network Engineering for Optimization teams tests the below results were obtained:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Based on the above results in Figure 11.1-4 we can conclude that having a non fractional power
control mechanism will lead to best throughput (compared to FPC ON cases) in near & mid cell.
Starting path loss 110dB we have observed an UL throughput degradation which corresponds to
number of PRB decrease, which explains the product reaction to UL TxPower saturation (number of
PRB are decreased when the TxPower is maximum and the number of PRB-es is still high).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-5: Set 1UL Throughput & UE TX Power vs. Path loss
NOTE: PL de-synch(~4dB) is due to the fact that in Figure 11.1-5 displays UL PL and Figure 11.1-8
displays DL PL.
Please use the UL throughput curves to align the TxPower it effect.
Comparing the plots above we can conclude that for pUSCHPowerControlAlphaFactor=0.7 number of
PRB is not degraded, UE TxPower at near&edge cell environment has an acceptable value and also
the uplink throughput still is satisfactory for most of the services an operator might offer.
Below in Figure 11.1-6 is the theoretical analysis for SIR target calculation in case of SET2&4.
Results confirm the theory and the fact that having Max_SIR_targetForFPC greater than
SIR_Target_Nominal will not help (if Path loss nominal is equal 60dB). There are no commercial
networks in which the less than 60dB is found.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-6: SIR Target for theoretical assumptions with different alpha factor values
Looking to theoretical assumptions we have found that SET3 of values as something that could
produce a similar UL throughput in Near cell environment compared to non-FPC case. As well as PL
increases the UL throughput will smoothly decrease (around 93dB UL PL, compared to 110dB
SET1&Alphafactor=1)
Figure 11.1-7: UL SIR Target for theoretical assumptions with different alpha factor values
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-8: Different alpha factor comparison (Throughput, PRBs, SINR & PUSCH SINR Target)
NOTE: Comparing the SIR target collected with SIR target estimated in the theoretical approach.
This proves that Alcatel-Lucent power control mechanism works as expected.
The below comparison shows the UL throughput and TxPower comparison between the
AlphaFactor=1 and AlphaFactor=0.7 for SET3. Out of this we can conclude that a
SET3(AlphaFactor=0.7) could be used when customers are requesting an high UL throughput in Near
cell with a UL throughput decrease in late-mid cell and edge cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-9: UL Throughput & UE TX Power vs. Path loss alpha factor 0.7 & 1 with set 3
Notes:
Alpha Factor=0.7 is a good compromise between UL Throughput and the TxPower used. Never the
less, bigger the AlphaFactor, bigger the UL throughput for near&mid cells. Bigger the AlphaFactor,
lower the UL throughput for edge cells (below ~110dB UL PL).
Nominal path loss impacts the UL throughput performances. Bigger the value, later the UL
throughput decrease effect, but high the TxPower.
Having Max_SIR_targetForFPC greater than SIR_Target_Nominal will not help(if for e.g. Path loss
nominal is equal 60dB, will not help to have max 20dB when target is 15dB).
Path loss nominal with value less than 60dB is not useful. There are no commercial networks in
which the less than 60dB is found.
SET 1 &AlphaFactor=1 is the template. It is a good setting combination for non-FPC and best
performances in Near&Mid-Cell radio condition. We recommend this to be used for best
performances.
SET1 & AlphaFactor=0.7 is a good trend between the UL throughput and UL interference. It is more
suitable for commercials networks were customer vision needs a near&mid-cell not targeting the
maximum or what Alcatel-Lucent product can offer to respect of lower interference.
SET3 & AlphaFactor=0.7&PathLossNominal = 85 looks a better UL throughput approach having as
well the FPC on. So high throughput in near&mid-cell radio conditions, but as well higher
throughput in edge cell (compared to non-fractional power control). TxPower is a compromise
between the SET1&AlphaFactor=1 and SET1&AlphaFactor=0.7.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-10: UL Throughput & UE TX Power vs. Path loss for alpha factor 0.7 for all sets
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 11.1-11: UL Throughput vs. Path loss for set1 & set3 with alpha factor 0.7 and 1
Figure 11.1-12: UE TX Power vs. Path loss for set1 & set3 with alpha factor 0.7 and 1
Baseline configuration - Fixed UL SINR target and hence comparable average UL throughput
across cell until UE begins to hit max Tx power
o Offers good balance between achieving high throughputs near the cell and mitigating IoT
impact to neighboring cells from users at cell edge
o Cell adjusts UL SINR target for a given user based on estimated UL pathloss
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
o Fractional power compensation at the cell: High SINR target close to cell, and then linear
adjustment beyond certain pathloss
o Fractional power compensation at the UE: Cell communicates pathloss component Alpha and
Po_pusch_nominal via SIBx to manage PUSCH Tx power at the start of a call as well as
throughout the call as pathloss changes
While in the Temp Market the results were compiled from Drive tests, in the Boston Market they
were base both in Drive test and simulation.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Comparing the median values, the normalized UL Throughput is around 60% -70% higher using set4
compared to the baseline configuration.
Comparing the results from all the sets, the median for the normalized UL throughput is around 40%
higher for Set4 relative to Baseline.
Main conclusions:
FPC gains demonstrated via drive tests 40-70% improvement in median normalized PUSCH
throughput with Set4 relative to fixed and 4dB UL SIR target
11.1.3 ULSCHEDPROPFAIRALPHAFACTOR
In the Figure 11.1-14 it is presented the impact of using the different values for 8.3
ULSCHEDPROPFAIRALPHAFACTOR; such as 0 or 1.
The test represented in the Figure 11.1-14was made with the typical configuration; 2NC; 4MC; 2CE,
and having the different UlschedpropfairAlphaFactor will make the scheduler to adjust more or less
fair the resources to all the ue's...
KPI Impact:
Throughput Low values increase the throughput in the near&mid-cell condition at expense of
cell edge users.
Capacity - Low values increase the cell overall throughput at expense of cell edge users.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is Latency in LTE.
Normally some questions arise, such as:
Mainly the Latency optimization can occur when the average value for a specific location is not
matching the ALU product specification in terms of KPI.
Before starting playing with the parameterization; usually is part of best practice rules for in Near
Cell /Mid Cell & Cell Edge test to follow up simple steps as:
If we could guarantee that these values are normal, the chances to have performance issues are
much less difficult to occur.
If regardless of the correct values, still facing some performance issues, they below parameters can
be used in order to correct the situation.
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
As note; please remember that this can be a static test in each position, or can be a moving test
the same principles can be applied in both situations.
This chapter contains optimization guidelines for some parameters that have the highest impact on
latency.
LTE latency test cases include air latency and end-to-end latency as shown in Figure below.
RAN / air latency in this document is defined in terms of the round trip time between UE and eNB.
RAN / air latency is measured in loaded and unloaded conditions. Unloaded condition implies that a
valid scheduling grant is available; i.e. no random access procedure needs to be performed. End to
end latency is the elapsed round trip time from UE to a certain application server in the network.
The EPC latency is the round trip time between UE and PDN GW.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The Idle to Active Transition Time is defined as the time required for the UE to transition from RRC
idle state to RRC Active state. In particular this KPI is defined at the UE side as the latency (RTT) of
the first ping sent by the UE to trigger the idle-to-active transition
Transition time (excluding downlink paging delay and NAS signalling delay) of less than 100 ms
from a camped-state i.e. Idle Mode, to an active state, in such a way that the user plane is
established
Additionally the latency between RA Preamble (followed by RRC Connection Request message NAS
Service Request as shown in figure below) and RRC Connection Reconfiguration Complete message
(Control Plane Latency)
Ping is being used for discovering the User plane latency. Typically 32, 1000 and 1500 bytes payload
sizes are set for the unloaded scenario, 32 and 1500 bytes for the loaded scenario
Result will be the round trip delay between the eNodeB and the FTP server
An estimation of the RTD between the eNodeB and the FTP server was performed by pinging the
FTP.
For a successful attach attempt to happen the needed the RACH preamble must be correctly
decoded by eNB. Setting preambleInitialReceivedTargetPower >= -104dB will speed attach time
but may result in interference to the other cells. Also making sure the following parameter
preambleTransmitPowerStepSize= dB6 is important for reducing number of RACH preambles sent
for RACH msg 1, and implicitly the attach time.
The attach time latency is mainly dependent on the authentication procedure which has the highest
proportion of total attach time. The IMSI attach time as an example is 600ms out of a total time of
677ms.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The examples are suggestive and clear that the RRC UE Capability procedure is time consuming. In
conclusion attach time latency is mainly dependent on the authentication time.
The table below one can have an idea about the comparison between LA3.0.2 and LA4.0.1. The
attach time is worse in LA4.0.1 but the table shows that the worsening on LA4.0.1 vs. LA3.0.2 is
mainly in the ePC part.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Although, the target for this KPI on LE4 in the LTE KPI database is 290 ms.
LLDM LLDM Attach
LLDM
attach S1 S1 Time ePC ePC UE + eNB
attach
Test n request attach attach attach request part part part
accept Cell
Cell request accept <-> attach (ms) (%) (ms)
time (ms)
Time(ms) accept (ms)
1 9328 9626 902407 1053357 298 151 51% 147
2 2256 2567 567019 734066 311 167 54% 144
CONFIGURATION USED
eNB sw is ENB_LA0400_D10_E02026
The database is customized:
No mobility (isIntraFreqMobilityAllowed = false)
No ciphering
Measurements are done without authentication
PCRF-1 DSC_2_0-I133
DSC_3_0_R1
PCRF-2
(DSC_3_0_I377)
S-GW R3.0_R1
P-GW R3.0_R1
MME02 R21.80.12.07
MME03 R22.31.01
LLDM R4.0.4
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
With G13 LGE device in very good RF (Near Cell) the average Attach time of 225ms and UE
activation time of 90-92ms have been achieved..
With load: D11_E00041
The UL Scheduler may receive requests for Anticipated Uplink Grants (AUG) from the DL
Scheduler.
Note that in LA4.0, AUG is only used for connection setup scenarios (i.e. it is not used for
bearer setup or during handover).
1. Reception of an ACK for the transmission of a RACH message 4. The AUG request is
processed by the UL scheduler with a configurable delay aUGtriggerDelayforRACHmsg4 in
order to avoid sending an UL grant before the UE has finished processing the RRC
Connection Setup message.
Upon receipt of an AUG request triggered by the reception of an ACK for the transmission of
a RACH message 4, the UL scheduler transitions the UE into sync state.
2. Detection of an ACK for the transmission of the last DL RLC PDU of a DL RRC
message on SRB1 within a time window of duration configurable by parameter
aUGprocessDuration starting at the trigger of the first AUG request for the UE context.
Fixed bugs:
AUG Feature that was introduced in LE3.0 was broken in the beginning of LE4.0 and thanks
to Lams work with dev team it has been fixed now.
Initially a new LE4.0.1 feature Processor-Overload Control also impacted negatively this
KPI and has been fixed from E00030 onwards.
The Idle to active latency is defined as the time needed for UE to enter active state. Starting point
is the moment when UE initiates RACH Procedure with RACH message 1 for entering active mode
until the UE sends RRC Connection Reconfiguration Complete message.
For Idle to active the RACH procedure is included for this test.
NOTE! The Idle to active transition is a process that needs less time than the normal attach
procedure because the UE doesnt need to initiate the authentication procedure anymore.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
If the RACH Preamble is not decoded by eNB then the UE will resend up to maximum
preambleTransMax preambles before restarting RACH Procedure. The parameters:
preambleInitialReceivedTargetPower, preambleTransmitPowerStepSize both should be set
according to cell conditions for fast RACH procedure and hence a good Idle to active latency.
The example listed below shows a total Idle to active latency of 153ms.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The table below one can have an idea about the idle to active time latency.
LLDM cell time
Average 106,07
Min 101,00
Max 110,00
Table 12-3: Idle to Active Latency
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
PCRF-1 DSC_2_0-I133
DSC_3_0_R1
PCRF-2
(DSC_3_0_I377)
S-GW R3.0_R1
P-GW R3.0_R1
MME02 R21.80.12.07
MME03 R22.31.01
LLDM R4.0.4
When initializing a detach procedure the UE sends Detach Request after which eNB responds with
Detach Accept.
The detach latency is mainly clear context dependent and parties communication latencies.
The Detach Latency should be around 200ms.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
In the table below, one can find the preliminary results for latency tests with a 32 Bytes ping.
The Qualcomm UE has been tested with and without Extended SR grant for U-plane latency feature.
Qualcomm Activated 17 ms 27 ms
Deactivated --- 35 ms
Table 12-5: Ping Latency for 32 Bytes with and without Extended SR grant for U-plane latency
CONFIGURATION USED
UE version is M9600B-SCAQWAFD-3.0.361109
eNB version is LA4.0 ENB_LA0400_D10_E02070
MIM 10.6.4 delivery 11W32
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is Capacity in LTE.
Normally some questions arise, such as:
By default, there is not much chance to make an improvement of the connected users normally
what can be worked is split of the performance (resource block allocation), for users in different
radio conditions.
This means that we can have fair or unfair resource distribution; for more details you can check the
parameters described below.
Features and configuration elements impacting the eNB capacity figures are:
UL/DL Bandwidth configured through parameters dlBandwidth and ulBandwidth. Different capacity
figures are available depending on the LTE bandwidth used.
Parameter maxNbrOfUsers controls the number of users that can be admitted in a cell (users per
modem).
Parameter maxNumberOfCallPerEnodeB controls the number of users that can be admitted on the
eNB (users per Controller board)
The usage of 700 MHz Upper C band (US specific) controlled through
ul700MHzUpperCBlockEnabled activation flag.
The following table is summarizing the different eNB capacity figures that can be obtained for du/ul
Bandwidth parameters.
dl/ul Capacity in terms of max. number of users per Capacity in terms of max. number of users per
Bandwidth cell eNB
n25-5MHz 167 (at the publication date) 500 (at the publication date)
DR5 target: 167 (current view) DR5 target: 500 (current view)
n50-10MHz 167 (at the publication date) 500 (at the publication date)
DR5 target: 167 (current view) DR5 target: 500 (current view)
n100-20MHz 167(at the publication date) 500 (at the publication date)
DR5 target: 167 (current view) DR5 target: 500 (current view)
Table 13-1: LA4.0.1 Capacity figures
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
13.1.2 ALPHAFAIRNESSFACTOR
Parameter alphaFairnessFactor tunes the alpha fairness factor (thus the behaviour) of the DL
scheduler.
The scheduler is the processing entity that allocates resources to user plane and control plane
traffic. Different factors such as channel quality, data pending in buffers, relative priorities in terms
of QoS traffic are some key factors that are used by the scheduler to pick specific users from the
active pool and allocate air-link resources to them. The overall goal is to ensure that users do get a
chance to share the available bandwidth in the system, and the resources are allocated in an
efficient manner while maintaining good system utilization.
alphaFairnessFactor = 0
Aggressive mode ( = 0) the scheduler provides more resources to UEs in better conditions. The
better the radio conditions of the UE, the more resources (and hence the higher the data rate) it
gets.
Using the follow results in 10MHz with 20UEs when apply the aggressive mode you should expect:
UE in Cell Edge are allocated the less PRB in average to favour UE with better radio conditions
Average UE Throughput per radio group => differences increased compared to proportional Fair
mode
alphaFairnessFactor = 1
Proportional Fairness ( = 1), the scheduler attempts to provide the same number of RBs to all the
UEs (despite their different conditions).
Using the follow results in 10MHz when apply the conservative mode you should expect:
alphaFairnessFactor = 2
Conservative mode ( = 2) shows the more Ue move away, the more PRB they are allocated,
decreasing gaps between Ue Throughput but decreasing the cell Throughput as well. The scheduler
attempts to allocate the resources in such a way that all the UEs eventually get the same data rate
(which is not the case of the fair scheduler since different radio conditions result in different data
rates even when the number of resources is the same, hence the increased fairness of the
scheduler, as compared to the regular fair scheduler).
Using the follow results in 10MHz when apply the conservative mode you should expect:
When the UEs is in bad radio conditions, more PRB are allocated in average to decrease throughput
gaps
Average UE DL throughput per radio group (Good, Medium, Bad radio conditions), decrease
compared to proportionalfair mode
In overall the final 20 UE throughput decrease compared with proportionalfair mode
alphaFairnessFactor conclusions:
Conservative mode ( = 2), shows the more UE move away, the more PRB they are allocated,
decreasing gaps between UE Throughput but decreasing the cell Throughput as well.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Aggressive mode ( = 0), shows the more UE come closer, the more PRB they are allocated,
increasing gaps between UE Throughput but also the cell Throughput.
Proportional Fair mode ( = 1), shows the better fairness distribution between the different radio
conditions. All UEs will have the same resources even in bad radio conditions, appropriate for
commercial networks.
KPI Impact:
Throughput Low values increase the throughput in the near&mid-cell condition at expense of
cell edge users.
Capacity - Low values increase the cell overall throughput at expense of cell edge users.
13.1.3 ULSCHEDPROPFAIRALPHAFACTOR
Parameter ulSchedPropFairAlphaFactor tunes the alpha fairness factor (thus the behaviour) of the
UL Scheduler.
ulSchedPropFairAlphaFactor = 1
Aggressive mode ( = 1), Yields a maximum C/I scheduler. The scheduler provides more resources
to UEs in better conditions. The better the radio conditions of the UE, the more resources (and
hence the higher the data rate) it gets.
Using the follow results in 10MHz when apply the aggressive mode you should expect:
ULS choice only depends on spectrum efficiency => unpredictable fairness behaviour
TCP flow control increases BO of favoured Ues and decrease BO of others
ulSchedPropFairAlphaFactor = 0.5
Proportional Fair ( = 0.5), Yields a fair scheduler. The scheduler attempts to provide the same
number of RBs to all the UEs (despite their different conditions).
Using the follow results in 10MHz when apply the aggressive mode you should expect:
70,6 % PRB BW used in UL => decreased in degraded radio when Ue reach maximum path loss (PH
limitation)
fairness no more significant between Cell edge group and the others since Ue at maximum path loss
BLER with Sol3 issue on Ue in Mid Cell only when mixed with UE in Near Cell (CR 312408)
UL BLER in Cell Edge converge to almost 10%
ulSchedPropFairAlphaFactor = 0
Conservative mode ( = 0), yields an increased fairness scheduler. The scheduler attempts to
allocate the resources in such a way that all the UEs eventually get the same data rate (which is not
the case of the fair scheduler since different radio conditions result in different data rates even
when the number of resources is the same, hence the increased fairness of the scheduler, as
compared to the regular fair scheduler).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Using the follow results in 10MHz when apply the aggressive mode you should expect:
Average Ue Throughput per radio group => differences decreased compared to proportional Fair
mode
Cell Throughput decreased compared to proportional Fair mode
The more UE are in bad radio, the more PRB they are allocated in average to decrease Throughput
gaps.
ulSchedPropFairAlphaFactor conclusions:
Conservative mode ( = 0), does not show any improvement compared to proportionalfair results,
as shown in simulations results as well.
Proportionalfair mode ( = 0.5), fairness no more significant between Cell edge and the other
radio conditions, since UE is at maximum path loss. More PRB bandwidth used in this configuration
compared with the other. Better configuration for commercial networks.
Aggressive mode ( = 1), is not a significant test since throughput between users are not
predictable. This mode is not recommended for customer deployment.
KPI Impact:
Throughput: high values increase the throughput for near cell and mid-cell conditions.
Capacity - high values allow reaching the capacity for a wider range of propagation
conditions.
In this chapter it will be highlighted the main focus of testing and the primary steps that will allow
to optimize a specific domain and the most important /priority parameters; in this case the domain
addressed is Mobility in LTE.
Normally some questions arise, such as:
Mainly the Mobility optimization can occur when the average success rate or average interruption
time value is not matching the ALU product specification for a determined Bandwidth target.
Before starting playing with the parameterization; usually is part of best practice rules cell Edge
test to follow up simple steps as:
If we could guarantee that these values are normal, the chances to have performance issues are
much less difficult to occur.
If regardless of the correct values, still facing some performance issues, they below parameters can
be used in order to correct the situation.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
When changing parameters; you can adopt a more error-free approach, meaning that a parameter is
changed at each time. If three or four parameters are changed same time it could be difficult to
understand which one is bringing the improvement in performance.
In the beginning when network is deployed, inside CIQ is necessary to fulfil the information relative
to the Intra Neighbouring cells of each sector.
After network deployment a first check in the neighbour list should be done, to ensure the intra HO
neighbours are created.
Example bellow in Figure 14.1-1 shows the sector PU1084L2100_0 have Intra neighbour with sector
PU1084L2100_1 and PU1084L2100_2
One of the ways to declare the best neighbour relation is working with the information done by
ARFCC team previously. With Cell ID coverage we can check the cell IDs neighbours for each sector
as showing bellow.
After should be done drive test and post processing the measurements to confirm the neighbour list
and the HO success rate between sites.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Other possible way to perform the neighbour list is run ANR feature in the network. The feature will
create the X2 links that would be need for each sector. Maximum of 32 X2 visible links could be
created. Be aware the feature should be activated after the first neighbour optimization performed
and after the users start to perform data traffic.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Here the X2-Link is created but the name of the neighbour comes in Binary.
For the case above site NE0054 create X2 link with site NE0034, but in the Wips appear
X2Access/0_330_110_NE0054_11.
To avoid ping pong effect between different cells IDs as show in the Figure 14.1-4, a balance
between the following parameters should be done:
filterCoefficientRSRP - The higher the value of filterCoefficientRSRP the smoother the reported
measurement will be and consequently the less likely ping-ponging occurs between sectors
during handover
Hysteresis - Increasing the value of this parameter would delay the HO due to the more
important difference that must exist between the serving cell and neighbour cell.
CellIdividualoffset Low values decrease the number of ping pongs between the 2 cells and
delay the HO.
These three parameters if setup correctly will help to avoid ping pong effect and improve
throughput, during HO attempts.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Some parameters are the base to optimize the mobility. In some of then we are able to change and
get better results, for example in terms of performance (HO Success Rate).
Note for different networks and environments the recommended values could not be the best to
apply. Always run a first drive and after with recommended parameters try to setup the best for
your network.
CellSelectionReselectionConf qRxlevminoffset 8
LteNeighboringCellRelation threshXLow 0
ReportConfigEUTRA Hysteresis 2
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Cell Reselection is a procedure triggered by the UE in Idle Mode to determine which LTE cell to
camp on. The trigger can be internal (e.g. periodic trigger to ensure that UE is still on the best cell)
or external (e.g. upon change of Cell Reselection parameters broadcast on the selected cells BCH).
The cell selection and reselection is controlled by the System Information parameters provided in
SIB1, SIB3 and SIB4.
Cell Reselection is a procedure triggered by UEs in Idle Mode to determine which LTE cell to camp
on. When a UE, camps on a cell it monitors its broadcast and paging channels. The procedure is
internal to the UE and there is therefore no EUTRA level use case for it.
3GPP rules:
SservingCell > 0 where
SservingCell = Qrxlevmeas (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Lets consider:
IF SServingCell > Sintrasearch -> UE choose to not perform intra-frequency measurements
If SServingCell Sintrasearch -> UE shall perform intra-frequency measurements
As soon as possible neighbours are measured, the UE should rank them using:
UE will reselect the new first cell on the ranked list if both below conditions are met:
The new cell is better ranked than the serving-cell during a time interval tReselectionEUTRAN
More than 1 second(s) has elapsed since the UE camped on the current serving-cell
Measurement phase
RSRP
Measurement phase
Figure 14.1-5: LTE to LTE Mobility Measurement phase (RSRP vs. Time)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Ranking phase
Decision phase
RSRPn2
RSRPs
QoffSet
qHyst
Rn2 reselection
tReselectionEUTRAN
Figure 14.1-7: LTE to LTE Mobility Decision Phase (RSRP vs. Time)
14.1.5.1 QRXLEVMIN
KPI Impact:
Mobility - low values might create coverage discontinuity in idle, as seen by UE.
Step 1: Set the value of qRxLevMin to one of the following values {- 124, -122, -120, -118, -116}.
Step 2: With UE in idle mode, perform a drive test back and forth on various routes and log the
control messages exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another qRxLevMin and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.2 SINTRASEARCH
This parameter specifies the threshold for the serving cell reception level, below which the UE
triggers intra-frequency measurements for cell reselection.
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
The optimization process: test results indicate sIntraSearch should be set to the highest allowed
value to minimize SINR degradation in reselection boundaries.
Although as an experiment process; values such as 30 or 40 for the sIntraSearch might be used.
14.1.5.3 QHYST
This parameter configures the hysteresis value of the serving cell used by the UE for ranking
criteria in cell reselection.
Broadcast in SystemInformationBlockType3.
KPI Impact:
Mobility - can improve mobility by determining timely reselection.
Step 1: Set the value of qHyst to one of the following values {dB1, dB2, dB3, dB4, dB5}.
Step 2: With UE in idle mode, perform a drive test back and forth on various routes and log the
control messages exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another qHyst and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.4 QOFFSETCELL
This parameter defines the offset between the current LteCell and the LteNeighboringCell.
KPI Impact:
Mobility - higher the value later the cell reselection. Lower the value, earlier the cell
reselection.
Step 1: Set the value of qOffsetCell to one of the following values {dB1, dB2, dB3, dB4, dB5, dB6,
dB7}.
Step 2: With UE in idle mode, perform a drive test back and forth on various routes and log the
control messages exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another qOffsetCell and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
14.1.5.5 QRXLEVMINOFFSET
This parameter defines an offset to be applied in cell selection criteria by the UE when it is engaged
in a periodic search for a higher priority PLMN.
KPI Impact:
Mobility - low values might create coverage discontinuity during selection operation due to
shrinking target cell as seen by the UE.
14.1.5.6 TRESELECTIONEUTRAN
This parameter specifies the value of the cell reselection UE timer in the serving cell. Broadcast in
SystemInformationBlockType3.
It imposes a condition on the reselection. UE will actually reselect the new cell, only if the new cell
is better ranked than the serving cell during a time interval tReselectionEUTRAN.
KPI Impact:
Mobility - low values of this parameter might allow ping-pong behaviour during reselection
operation. High values of this parameter might delay the reselection and possible lead to lost
connection to the serving cell.
Optimization of this parameter should find a trade-off between delayed reselection and ping pong
behaviour. Most probably, if the UEs are not moving fast, the delayed reselection would not be an
issue. For optimization, a procedure containing the following steps can be used:
Step 1: Set the value of tReselectionEUTRAN to one of the following values {1, 2, 3, and 4}.
Step 2: With the UE in idle mode, perform a drive back and forth between the cells on various
routes and log the reselection - related messages and the position of the UE. Perform this test 10
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
times in each direction. Make sure that the driving speed is nominal and the same for all the test
samples.
Step 3: Repeat Step 2 for another value of tReselectionEUTRAN.
Step 4: Post-process the logs and analyze them as reselection position vs. tReselectionEUTRAN
values and ping pong behaviour vs. tReselectionEUTRAN values and choose the optimized value to
obtain smallest interruption time and highest success rate.
Step 5: Calculate the HO success rate in each direction.
14.1.5.7 TRESELECTIONEUTRASFMEDIUM
This parameter avoids ping pong radio phenomena during the RA-Update & idle mobility.
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionEutraSfMedium to one of the following values {0.25, 0.5, 0.75,
and 1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the cells on various
routes and log the reselection - related messages and the position of the UE. Perform this test 10
times in each direction. Make sure that the driving speed is nominal and the same for all the test
samples.
Step 3: Repeat Step 2 for another value of tReselectionEutraSfMedium.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.8 TRESELECTIONEUTRASFHIGH
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
This parameter avoids ping pong radio phenomena during the RA-Update & idle mobility.
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionEutraSfHigh to one of the following values {0.25, 0.5, 0.75, and
1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the cells on various
routes and log the reselection - related messages and the position of the UE. Perform this test 10
times in each direction. Make sure that the driving speed is nominal and the same for all the test
samples.
Step 3: Repeat Step 2 for another value of tReselectionEutraSfHigh.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.9 TEVALUATION
This parameter configures the duration for evaluating criteria to enter mobility states
KPI Impact:
Mobility - low values of this parameter will determine the UE to spend less time evaluating
criteria for enter mobilityr. This results in a speed up of the handover process.
Higher values of this parameter will determine the UE to spend more time evaluating criteria
for enter mobilityr. This results in a delay of the handover process
Step 1: Set the value of tEvaluation to one of the following values {s30, s60, s120, s180, and s240}.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 2: Perform a drive test back and forth on various routes and log the control messages
exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another tEvaluation and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.10 NCELLCHANGEHIGH
This parameter configures the number of cell changes to enter high mobility state
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of nCellChangeHigh to one of the following values {10, 11, 12, 13, and 14}.
Step 2: Perform a drive test back and forth on various routes and log the control messages
exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.11 NCELLCHANGEMEDIUM
This parameter configures the number of cell changes to enter medium mobility state
KPI Impact:
Mobility low values of this parameter might allow the UE to start cell reselection earlier.
High values of this parameter might allow the UE to start cell reselection later.
Step 1: Set the value of nCellChangeMedium to one of the following values {1, 2, 3, 4, 5, and 6}.
Step 2: Perform a drive test back and forth on various routes and log the control messages
exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.12 QHYSTSFHIGH
KPI Impact:
Mobility low values of this parameter might allow the UE to start cell reselection earlier.
High values of this parameter might allow the UE to start cell reselection later.
Step 1: Set the value of qHystSfHigh to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive test back and forth on various routes and log the
control messages exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another qHystSfHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.5.13 QHYSTSFMEDIUM
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter might allow the UE to start cell reselection earlier.
High values of this parameter might allow the UE to start cell reselection later.
A
procedure that optimizes qHystSfMedium would contain the following steps:
Step 1: Set the value of qHystSfMedium to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive test back and forth on various routes and log the
control messages exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another qHystSfMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.6.1 FILTERCOEFFICIENTRSRP
-70
1 106 211 316 421 526 631 736 841 946 1051 1156 1261 1366 1471 1576 1681 1786 1891
-80
-90
RSRP_instant
-100 RSRP_FC(K=4)
RSRP_FC(K=11)
-110
-120
-130
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Step 1: Set the values of filterCoefficientRSRP and to hysteresis and to timeToTrigger to one of the
following {(fc6,2,80), (fc8,3,40), (fc8,4,20), (fc5,1,100)}, in both current cell and neighbour cell. It
was proven that the time to trigger below 100 ms have the same impact on performance as LGE UE
measures RSRP every 100ms.
Step 2: Perform a drive test while performing a download and log the throughput values and the
position of the UE. Drive in and out of the current cell to the neighbour cell.
Step 3: Repeat Step 2 for another pair of values of the three tested parameters.
Step 4: Represent throughput vs. position (distance) (Service continuity), #HO-attempts, Success
Rate/Failure Rate, #of Ping-pongs, HO interruption time for all pairs of tested values.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.6.2 HYSTERESIS
This parameter configures the RRC IE hysteresis included in the IE reportConfigEUTRA in the
MeasurementConfiguration IE. This parameter defines the hysteresis used by the UE to trigger an
intra-frequency event-triggered measurement report.
It is used in several processes: Event A1 (Serving becomes better than threshold); Event A2 (Serving
becomes worse than threshold); Event A3 (Neighbour becomes offset better than serving); Event A4
(Neighbour becomes better than threshold); Event A5 (Serving becomes worse than threshold1 and
neighbour becomes better than threshold2.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Drop the call if the value is too large i.e. connection to the serving cell is lost before having
reached the neighbour cell level that satisfies the HO condition.
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Throughput - low values of this parameter can generate a ping pong behaviour which can
result in interruption times and low throughput during HO operation.
14.1.6.3 TIMETOTRIGGER
This parameter sets the time duration time during which the conditions to trigger an event report
have to be satisfied before sending a RRC measurement report in event triggered mode.
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
This parameter should be carefully optimized, best in conjunction with filterCoefficientRSRP and
hysteresis as presented in paragraph 12.1.1.2.1. Indeed, the optimized value can be impacted by
the load of the surrounding cells.
Note: LGE UE RSRP filtering is every 100ms, which means that any time-to-trigger value equal or
above 100ms is indeed significant. The only reason to have ms40 is to be sure that we will take the
first RSRP reporting into consideration in case it is before the 100ms.
14.1.6.4 CELLINDIVIDUALOFFSET
This parameter defines the cell individual offset between the current LteCell and the neighbour cell
provided to the UE in RRC Connected mode for measurement.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Increase the number of ping pongs between the 2 cells and speed up the HO.
Decrease the number of ping pongs between the 2 cells and delay the HO.
KPI Impact:
Mobility low values of this parameter will delay the HO, and high values will generate ping-
pong behaviour.
The following steps could be used if you plan to optimize this parameter:
Step 1: If you detect a consist dropping from a specific cell, you can think to tune the
cellIndividualOffset in steps of dB2 units.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of cellIndividualOffset.
Step 4: Post process the measurement and analyze them as HO success rate vs. cellIndividualOffset
values and ping pong behaviour vs. cellIndividualOffset values and choose the optimized value to
obtain smallest interruption time and highest success rate.
14.1.6.5 EVENTA3OFFSET
This parameter is used to indicate an event (A3) specific offset of the serving frequency to be
applied when evaluating triggering conditions for measurement reporting.
KPI Impact:
Mobility low values of this parameter might allow the UE to handover earlier; while high
values might delay the handover
The following steps could be used if you plan to optimize this parameter:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 1: Set the values of eventA3offset to one of the following values {-3,-2,-1, 0, 1, 2, 3}.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of eventA3Offset
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
14.1.6.6 OFFSETFREQ
This parameter is used to indicate a frequency specific offset to be applied when evaluating
triggering conditions for measurement reporting.
KPI Impact:
Mobility low values of this parameter might allow the UE to determine the strongest cell
later. High values of this parameter might allow the UE to determine the strongest cell
earlier.
The following steps could be used if you plan to optimize this parameter:
Step 1: Set the values of offsetFreq to one of the following values {-3,-2,-1, 0, 1, 2, 3}.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of offsetFreq.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
14.1.6.7 REPORTINTERVAL
This parameter configures the RRC IE reportInterval included in the IE reportConfigEUTRA in the
MeasurementConfiguration IE.
The ReportInterval indicates the interval between periodical reports. The ReportInterval is
applicable if the UE performs periodical reporting (i.e. when reportAmount exceeds 1), for
triggerType event as well as for triggerType periodical.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility No specific issues using higher or lower values; a compromise needs to be found.
Step 1: Set the value of reportInterval to one of the following values {120, 240, 480, 640, 1024, and
2048}.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of reportInterval.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
14.1.6.8 MAXREPORTCELLS
This parameter defines the maximum number of cells to be reported in a measurement report.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells.
High values of this parameter allow the UE to report more neighbour cells..
Step 1: Set the value of maxReportCells to one of the following values {1, 2, 3, 4, 5, 6, 7, and 8}.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of maxReportCells.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
14.1.6.9 REPORTAMOUNT
This parameter configures the number of periodical reports the UE has to transmit after the event
was triggered.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells.
High values of this parameter allow the UE to report more neighbour cells..
Step 1: Set the value of reportAmount to one of the following values {r1, r2, r4, r8, r16, r32, r64}.
Step 2: Perform a drive test in and out of the cell and log the HO - related messages and the
position of the UE.
Step 3: Repeat Step 2 for another value of reportAmount.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
Figure 14.1-11: Call flow for Inter-eNB mobility, X2 HO UE in RRC Connected (1)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 14.1-12: Call flow for Inter-eNB mobility, X2 HO UE in RRC Connected (2)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 14.1-13: Call flow for Inter-eNB mobility, S1 HO UE in RRC Connected (1)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 14.1-14: Call flow for Inter-eNB mobility, S1 HO UE in RRC Connected (2)
u-plane
delta
test DL grant1 DL grant2
(ms)
1 7827 7884 57
2 7222 7281 59
3 1077 1124 47
4 9922 9971 49
5 5202 5254 52
average 52,8
Table 14-2: Intra-eNB HO Interruption time
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
DSC_3_0_R1
PCRF
(DSC_3_0_I377)
S-GW R3.0_R1
P-GW R3.0_R1
MME02 R21.80.12.07
MME03 R22.31.01
LLDM R4.0.4
Lets consider:
IF SServingCell > Snonintrasearch -> UE choose to not perform inter-frequency measurements
If SServingCell Snonintrasearch -> UE shall perform inter-frequency measurements
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
3
Qrxlevmin+Qrxlevminoffset
Qrxlevmin(SIB3)+ +Pcompensation
threshServingLow +threshXLow
2
3
Time
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
sNonIntraSearch = 62 UE will start measuring for lower or equal priority cells when RSRP falls
below -120 + 62 = -58 dBm
threshServingLow = 8 UE will reselect the neighbor cell when B4 becomes worse than -120 + 8 =
-112 dBm and B13 is better than -120 + 0 = -120 dBm (threshXLow = 0)
threshXHigh = 12 UE will reselect the higher priority cell when B4 is better than -120 + 12 = -108
dBm
14.1.7.1 QRXLEVMIN
This parameter configures the minimum required RSRP level in the cell, used by the UE in cell
reselection.
KPI Impact:
Mobility - high values might create coverage discontinuity in idle, as seen by UE.
Step 1: Set the value of qRxLevMin to one of the following values {- 124, -122, -120, -118, -116}.
Step 2: With UE in idle mode, perform a drive test back and forth between the cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 3: Choose another qRxLevMin and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.7.2 SNONINTRASEARCH
This parameter is used for setting a threshold for the selection criterion, threshold that would
determine when, based in serving cell field level, the UE starts performing measurements for inter-
frequency and inter-RAT measurements. It is used for cell reselection.
Note: The reasoning for the use of a different value was only not to limit the performance in terms
of Handover due to late measurements
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Step 1: Set the value of sNonIntraSearch to one of the following values {12, 13, 14, 15, and 16}.
Step 2: With UE in idle mode, perform a drive test back and forth between the cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 3: Choose another sNonIntraSearch and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
14.1.7.3 THRESHSERVINGLOW
Threshold for serving cell reception level used in reselection evaluation towards lower priority E-
UTRAN frequency or RAT. The value sent over the RRC interface is half the value configured (the
UE then multiplies the received value by 2) Defined in TS 36.331 Broadcast in
SystemInformationBlockType3
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionEUTRAN.
The parameter discussed here only impacts the part related to the serving cell.
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
Note: To get the option to reselect as soon as possible, with serving cell reception level below
sNonIntraSearch, we can set threshServingLow at the same level than sNonIntraSearch. I.e. set
threshServingLow to 16 dB.
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Coverage high values might create coverage discontinuity during reselection operation.
Optimization of this parameter, in conjunction with threshXLow should aim at obtaining the cell
sizes for both target cell and serving cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshServingLow should be decoupled from the optimization for
threshXLow. For this, the value of threshXLow should be the minimum allowed such that the first
inequality of the selection criteria is satisfied for the largest surface of the cell. Once this is
realized, the selection will always be triggered by the value of threshServingLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshServingLow to one of the following values {6, 8, 10, 12, and 14}.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 2: With UE in idle mode, perform a drive test back and forth between the cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 3: Choose another threshServingLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.7.4 THRESHXLOW
This parameter sets the threshold of the selection criteria in case of inter-frequency.
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionEUTRAN.
The parameter discussed here only impacts the part related to the serving cell.
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
KPI Impact:
Mobility - high values might create coverage discontinuity during reselection operation due to
shrinking GSM cell as seen by the UE.
Optimization of this parameter, in conjunction with threshServingLow should aim at obtaining the
cell sizes for both target cell and serving cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshXLow should be decoupled from the optimization for
threshServingLow. For this, the value of threshServingLow should be the minimum allowed such
that the first inequality of the selection criteria is satisfied for the largest surface of the cell. Once
this is realized, the selection will always be triggered by the value of threshXLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshXLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
14.1.7.5 THRESHXHIGH
In terms of reselection we fullfil the criteria when the SnonServingCell,x > threshXHigh
during tReselectionEUTRAN
KPI Impact:
Mobility - high values might create coverage discontinuity during reselection operation due to
shrinking GSM cell as seen by the UE.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshXHigh to one of the following values for example {8, 10, 12, and 14}.
Step 2: With UE in idle mode, perform a drive test back and forth between the cells on various
routes and log the control messages exchanged between eNodeB and UE along with the GPS
coordinates of the UE.
Step 3: Choose another threshXHigh and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
target cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.7.6 TRESELECTIONEUTRAN
14.1.7.7 TRESELECTIONEUTRASFMEDIUM
14.1.7.8 TRESELECTIONEUTRASFHIGH
14.1.7.9 NCELLCHANGEHIGH
14.1.7.10 NCELLCHANGEMEDIUM
14.1.7.11 QHYSTSFHIGH
14.1.7.12 QHYSTSFMEDIUM
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Information about various events is provided by eNB to UE in a timely manner and the parameters
related are transmitted in RRCConnectionReconfig message:
For the Inter-Frequency the following state machine should be considered in terms of priorities
/steps:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Event A5: when the serving cell becomes worse than a given threshold and the neighbour cell
becomes better than a given absolute threshold2
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
14.1.8.1 THRESHOLDEUTRARSRP
This parameter configures the first threshold to be used for event A5 measurement reporting.
KPI Impact:
Mobility - Low values might create coverage discontinuity during selection operation due to
shrinking target cell as seen by the UE.
Throughput - Low values will have negative impact in user experience, dragging the call to
level were throughput will be quite low.
Step 1: Set the value of thresholdEutraRsrp to one of the following values {-112, -110, -109, -108, -
106}.
Step 2: Perform a drive test back and forth on various routes and log the control messages
exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another thresholdEutraRsrp and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the new
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate;
but also take care about the throughput degradation never forget the user experience impact.
14.1.8.2 THRESHOLD2EUTRARSRP
This parameter configures the second threshold to be used for event A5 measurement reporting.
This parameter configures the RRC IE Threshold EUTRA RSRP included in the IE reportConfigEUTRA
in the MeasurementConfiguration IE. This IE should be present if the parameter triggerTypeEUTRA
is set to eventA1, eventA2, eventA4 or eventA5 and triggerQuantity is set to RSRP. Otherwise it
should be absent.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - Low values might create coverage discontinuity during selection operation due to
shrinking target cell as seen by the UE.
Throughput - Low values will have negative impact in user experience, dragging the call to
level were throughput will be quite low.
Step 1: Set the value of threshold2EutraRsrp to one of the following values {-104, -102, -100, -98, -
96}.
Step 2: Perform a drive test back and forth on various routes and log the control messages
exchanged between eNodeB and UE along with the GPS coordinates of the UE.
Step 3: Choose another threshold2EutraRsrp and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the new
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
14.1.8.3 FILTERCOEFFICIENTRSRP
14.1.8.4 HYSTERESIS
14.1.8.5 TIMETOTRIGGER
14.1.8.6 OFFSETFREQ
14.1.8.7 REPORTINTERVAL
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
14.1.8.8 MAXREPORTCELLS
14.1.8.9 REPORTAMOUNT
During a recent trial for Verizon Market, it was performed a quite complex Multi-Band Handover
campaign, for this porpoise it was used event A5 and A3 as triggers for the Handover between the
different bands considered (for information Band 13 and Band 4).
The main objective for this trial was to determine the optimal network settings to maximize the B4
coverage while limiting the amount of drop calls or losing data throughput. This objective should
also meet the deployment scenario criteria set by Verizon.
These test were performed in both connected and idle states (A5 and A3) respectively), to ensure
we optimize the different conditions of a data call.
Other scenarios were also completed in connected mode (A5 settings):
The scenario match closest to a network deployment configuration (A5 with 50% OCNS through X2),
was tested more extensively with a big focus on the tuning of the parameters A5 Event Source
Threshold and A5 Event Target Threshold.
These are the two main triggers for the A5 event for Inter-frequency mobility.
Important note, the results were obtained in LA3.0.2 release but due to the important topic and
not so many information about Inter-Frequency, it is still interesting to post the results achieved in
order to have an idea about the performance that could be expected and the main tunings around
the parameters.
In the next chapters will be highlighted some of the test cases executed and the outcome and
feedback collected.
In the below box the main considerations for the usage of both bands:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The UE considered was a LG Gyro (Multi-Band) Mobile; please find more details on the UE in the
link: Gyro Info
The network was composed of 6 main site locations, and some of them had different configurations;
to be known (Multi-Band, Dual-Band or Single Band).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
As per costumer demand, the main idea was to extend to the maximum the coverage in each band,
without taking the risk of dropping the connection; meaning that we should not waist valuable
resources, both on the Network side or on the UE side.
The tests were splited between Idle and Connected Mode (A5 and A3 event).
CONNECTED MODE:
For connected mode and for the event A5, it was also performed a more detailed test per customer
requirement; three main scenarios were tested (X2 with 50% and 100% OCNS, plus S1 with 50%
OCNS).
To be noted that for a specific scenario, more similar to a network deployment configuration (A5
with 50% and 100% DL OCNS through X2), it was tested more extensively with a big focus on the
tuning of two main parameters thresholdEutraRsrp and threshold2EutraRsrp; since these are the
main triggers for the event A5 for Inter-frequency mobility.
ReportConfigEUTRA Hysteresis 2 dB
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
thresholdEutraRsrp Threshold2EutraRsrp
Test Event DL OCNS (%) Interface Hysteresis
(dBm) (dBm)
Connected A5 50 X2 2 -109 -109
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Table 14-11: A5 through X2 with 100% DL OCNS (thresholdEutraRSRP & threshold2EutraRSRP =-111)
Table 14-12: A5 through X2 with 50% DL OCNS (thresholdEutraRSRP & threshold2EutraRSRP =-111)
A5 event presents better coverage, 3.85% more compared with Event A3.In average we are able to
reach 1.08miles coverage on Band 4
Using A5 event on source target,
For 50% OCNS, we get 20.83% more UL throughput compared with Event A3
For 100% OCNS UL throughput is better 9.83% compared with Event A3
Overall we are capable to reach better UL throughput using Event A5 until we perform the Inter
Frequency HO
Inter Frequency interruption time is similar in both cases A5 and A3 event. In both cases we reach
49ms for C-plane and around 70ms for U-plane.
Using alternate parameters (more aggressive), we have better coverage on band 4 using A5 event.
Using 50% OCNS we reach 11.11% more coverage on band 4
Using 100% OCNS we reach10.28% more coverage on band 4
Coverage on band 4 using A5 event we reach 1.20miles
Performing Inter Frequency HO with S1 the U-plane Interruption Time takes more time than using
X2.
IDLE MODE
The focus of the idle mode tests was to verify that the UE was respecting the thresholds defined and
also the priorities set.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Basically, in the test, the main objective was to extend to the maximum the idle session in the
source cell before the mobile perform the reselection to the target. Other configuration was
regarding the priority, using for that porpoise the CellReselectionConfLte::cellReselectionPriority
parameter. It was on the interest of Verizon to keep the mobile in the Band 4 most of the time, and
perform Band 13 reselection only if Band 4 not available So, by defining this parameter with a
different value /priority it was possible to prioritize the Band 4 instead Band 13.
CellSelectionReselectionConf sNonIntraSearch 62 dB
CellSelectionReselectionConfLTE threshXLow 0 dB
CellSelectionReselectionConfLTE threshXHigh 12 dB
CellSelectionReselectionConf threshServingLow 8 dB
CellSelectionReselectionConfLTE tReselectionEutra 2s
Idle 50 0 62 12 8 2
Idle 100 0 62 12 8 2
Distance to Site
Before Reselection, Source Cell After Reselection, Target Cell
IF reselection take place (Miles)
RSRP Source Cell RSRP Target SNR Target Cell
SNR Source Cell (dB) Distance
(dBm) Cell (dBm) (dB)
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 14.1-22: Time spent in each Band vs. Number of Reselection Attempts for 50% OCNS
Distance to Site
Before Reselection, Source Cell After Reselection, Target Cell
IF reselection take place (Miles)
RSRP Source Cell RSRP Target SNR Target Cell
SNR Source Cell (dB) Distance
(dBm) Cell (dBm) (dB)
Figure 14.1-23: Time spent in each Band vs. Number of Reselection Attempts for 100% OCNS
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Mobility
Cell reselection from EUTRAN to UTRAN includes the support of additional information elements of
SIB3 and SIB6 by the eNB. Redirection (including RRC connection release) includes the support of
configuration of UE measurement and RRCConnectionRelease message with the IE
redirectedCarrierInfo.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
In LA2.0 and for the UE in RRC idle mode, the inter-RAT mobility to UTRA-FDD is supported with the
cell reselection from E-UTRA-FDD to UTRA-FDD. Cell reselection inter-RAT (E-UTRA-FDD to UTRA-
FDD) is internal to the UE and controlled by system information parameters provided in
SystemInformationBlockType6 SIB6 and SystemInformationBlockType3 SIB3. Cell reselection to
UTRA-FDD is supported with SystemInformationBlockType6 SIB6. Cell reselection to UTRA-FDD is
enhanced with SystemInformationBlockType3 SIB3 (IE speedStateReselectionPars).
In LA2.0 and for the UE in RRC connected mode, the inter-RAT mobility to UTRA-FDD is supported
with the RRC connection release and redirection from E-UTRA-FDD to UTRA-FDD. The redirection
is driven by the eNodeB based on radio criteria.
When the EUTRA serving cell becomes worse than a threshold and the UTRA-FDD neighbouring cell
becomes better than another threshold, the eNodeB receives a Measurement Report message with
Event-B2 from the mobile. If the UE capability or the network cannot support EUTRA-to-UTRA-FDD
PS handover, the Algorithm for Control Procedures for Mobility decides to trigger a redirection
EUTRA-to-UTRA-FDD.
When the eNodeB does not receive any Measurement Report message from the mobile and, if the UE
capability or the network cannot support EUTRA-to-UTRA-FDD PS handover, the selection of mobility
mechanism decides to trigger a blind EUTRA-to-UTRA-FDD redirection (i.e. without measurements).
The function of EUTRA-to-UTRA-FDD redirection, the eNodeB provides the following functions; (1)
EUTRA-to-UTRA-FDD redirection execution phase; (2) EUTRA-to-UTRA-FDD redirection completion
phase.
During the previous phase of section Mobility Trigger Management (Control Procedures for Mobility),
the source ENB has decided to initiate a EUTRA-to-UTRA-FDD redirection to the target access
network (UTRA-FDD). The source ENB will give a command to the UE to re-select a cell in the target
access network via the RRC CONNECTION RELEASE. The RRCConnectionRelease message is used to
command the release of an RRC connection.
Done by the UE under control from EUTRAN via System Information Broadcast
Cell selection: the UE seeks to identify a suitable cell i.e. cell for which the measured cell
attributes satisfy the cell selection criteria; if found it camps on that cell and starts the cell
reselection procedure
Cell reselection: UE performs measurements of the serving and neighbour cells:
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
SIB6 contains information about UTRA frequencies and UTRA neighbouring cells relevant for cell re-
selection (including cell re-selection parameters common for a frequency as well as cell specific re-
selection parameters)
In RRC_IDLE mode, the cell reselection is internal to UE and is controlled by the System Information
Parameters provided in SIB6 if the reselection to UTRA FDD is enabled (isMobilityToUtraAllowed =
TRUE). Any modification of SIB6 parameters triggers a dynamic system information modification
procedure
In order to limit the amount of inter-RAT measurements an additional criterion broadcasted in SIB3
is used:
Snonintrasearch: threshold for serving cell reception under which the UE may trigger inter-RAT
measurements for cell reselection.
Configurable under : CellSelectionReselectionConf::sNonIntraSearch
The UE applies rules as follows, where CRP = Cell Reselection Priority and IRAT=UTRAN, GERAN, S =
selection criterion:
3GPP rules:
SservingCell > 0 where
SservingCell = Qrxlevmeas (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Lets consider:
IF SServingCell > Snonintrasearch -> UE choose to not perform inter-RAT measurements
If SServingCell Snonintrasearch -> UE shall perform inter-RAT measurements
UE will reselect the new cell if the conditions below are met:
Sservingcell < threshServingLow and SnonServingCell > threshXLow during tReselectionUtra
No cell with higher priority than the serving will fulfil the condition: SnonServingCell >
threshXHigh during tReselectionUtra
More than 1 second(s) has elapsed since the UE camped on the current serving cell.
Figure 15.1-4: LTE to UTRAN Mobility (RSRP vs. Time) measurement phase
Several database parameters are used for handling this kind of mobility. Some of them are tuneable
and most important are the following: qRxLevMin, pMaxUTRA, qQualMin, sNonIntraSearch,
trhreshServingLow, threshXLow.
A summary of the selection procedure is presented in the figure below.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 15.1-5: LTE to UTRAN Mobility Algorithm Cell Reselection toward lower priority UTRAN Cell
Figure 15.1-6: LTE to UTRAN Mobility (RSRP vs. Time) Decision Phase
15.1.1.1 QRXLEVMIN
A parameter with the same name appears in several objects and is then transmitted to UE inside
several system information block types i.e. Sibs:
CellSelectionReselectionConf transmitted in SIB1 and SIB3
CellReselectionConfUtraFdd transmitted in SIB6
CellReselectionConfUtraTdd transmitted in SIB6
CellReselectionConfGERAN transmitted in SIB7
The LTE UTRAN mobility is using two of them, the one sent in SIB3 and the one sent in SIB6.
This parameter configures the minimum required RSCP level in the UTRAN cell, used by the UE in
cell reselection.
Determine a delayed selection of UTRAN cell, i.e. a shrinking of the UTRAN cell in idle mode.
KPI Impact:
Mobility - high values might create coverage discontinuity in idle, as seen by mobile.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 1: Set the value of qRxLevMin to one of the following values {- 124,-122,-120,-118,-116}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qRxLevMin and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.2 SNONINTRASEARCH
This parameter is used for setting a threshold for the selection criterion, threshold that would
determine when, based in serving cell field level, the UE starts performing measurements for inter-
frequency and inter-RAT measurements. It is used for cell reselection.
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Step 1: Set the value of sNonIntraSearch to one of the following values {12, 14, 16, 18, and 20}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another sNonIntraSearch and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.3 THRESHSERVINGLOW
This threshold is used when the mobility towards lower priority frequency is taken in consideration.
The default priority for UTRAN frequency is lower than for EUTRAN frequency which implies that
this parameter is used each time mobility towards UTRAN happens.
This parameter sets the threshold of the selection criteria in case of mobility towards lower priority
RAT.
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionRAT.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The parameter discussed here only impacts the part related to the serving cell.
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Coverage - high values might create coverage discontinuity during reselection operation.
Optimization of this parameter, in conjunction with threshXLow should aim at obtaining the cell
sizes for both UTRAN cell and EUTRAN cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshServingLow should be decoupled from the optimization for
threshXLow. For this, the value of threshXLow should be the minimum allowed such that the first
inequality of the selection criteria is satisfied for the largest surface of the cell. Once this is
realized, the selection will always be triggered by the value of threshServingLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshServingLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another threshServingLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value.
15.1.1.4 THRESHXLOW
This threshold is used when the mobility towards lower priority frequency is taken in consideration.
The default priority for UTRAN frequency is lower than for EUTRAN frequency which implies that
this parameter is used each time mobility towards UTRAN happens.
This parameter sets the threshold of the selection criteria in case of mobility towards lower priority
RAT.
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionRAT.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The parameter discussed here only impacts the part related to the serving cell.
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
Determine an earlier selection of UTRAN cell, i.e. a shrinking of the EUTRAN cell in idle mode.
Indeed, it is possible that modifying the value of this parameter in a given range does not in fact
impact the selection due to possibly stronger condition on the EUTRAN cell.
KPI Impact:
Mobility - high values might create coverage discontinuity during reselection operation due to
shrinking UMTS cell as seen by the UE.
Optimization of this parameter, in conjunction with threshServingLow should aim at obtaining the
cell sizes for both UTRAN cell and EUTRAN cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshXLow should be decoupled from the optimization for
threshServingLow. For this, the value of threshServingLow should be the minimum allowed such
that the first inequality of the selection criteria is satisfied for the largest surface of the cell. Once
this is realized, the selection will always be triggered by the value of threshXLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshXLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another threshXLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Step 5: Choose the optimized value.
15.1.1.5 TRESELECTIONUTRA
This parameter concerns the cell reselection timer tReselectionRAT for UTRAN. Broadcast in
SystemInformationBlockType6.
It imposes a condition on the reselection. UE will actually reselect the new cell, only if the new cell
is better ranked than the serving cell during a time interval tReselectionUtra.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Optimization of this parameter should find a trade-off between delayed reselection and ping pong
behaviour. Most probably, if the UEs are not moving fast, the delayed reselection would not be an
issue.
Step 1: Set the value of tReselectionUtra to one of the following values {1, 2, 3, and 4}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionUtra.
Step 4: Post-process the logs and analyze them as reselection position vs. tReselectionUtra values
and ping pong behaviour vs. tReselectionUtra values and choose the optimized value to obtain
smallest interruption time and highest success rate.
Step 5: Calculate the HO success rate in each direction.
15.1.1.6 TRESELECTIONUTRASFMEDIUM
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionUtraSfMedium to one of the following values {0.25, 0.5, 0.75,
and 1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionUtraSfMedium.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.7 TRESELECTIONUTRASFHIGH
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionUtraSfHigh to one of the following values {0.25, 0.5, 0.75, and
1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionUtraSfHigh.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.8 NCELLCHANGEHIGH
This parameter configures the number of cell changes to enter high mobility state
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
Step 1: Set the value of nCellChangeHigh to one of the following values {10, 11, 12, 13, and 14}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.9 NCELLCHANGEMEDIUM
This parameter configures the number of cell changes to enter medium mobility state
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
Step 1: Set the value of nCellChangeMedium to one of the following values {1, 2, 3, 4, 5, and 6}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.1.1.10 QHYSTSFHIGH
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
Step 1: Set the value of qHystSfHigh to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.1.11 QHYSTSFMEDIUM
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
Step 1: Set the value of qHystSfMedium to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
UTRAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The eNodeB configures an event A2 (A2_CA for Coverage Alarm) that is configured at cell entry (call
set-up, incoming handover, RRC re-establishment) with purpose in MiM set to Entering-Coverage-
Alarm (serving worse than mobility threshold)
Inter-RAT measurements for PS HO to UTRA
The eNodeB configures an event B2 (Serving worse than Threshold1 and neighbour better than
Threshold2) that is configured after reception of an event A2_CA i.e. when the radio enter the
coverage alarm conditions
An event B1 (Neighbour better than Threshold) can also be configured for CS fallback as explained
by LA3.0 CSFB feature presentation
Measurement Gaps may be needed with respect to UE capabilities (per RAT and carrier)
The eNodeB checks conditions before configuring inter-RAT measurements to UTRA-FDD
the mobility to UTRAN is activated in MiM (isMobilityToUtranAllowed TRUE) although PS HO may be
deactivated (isPsHoToUtranAllowed FALSE) since redirection may be used
At least one inter-RAT neighbour carrier is configured in MiM for the serving LTE cell
UE can perform inter-RAT measurements, reporting and measurement reporting event B2 in eUTRA
RRC_connected
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
this message includes the transmission of the radio container that is the target-RNC to source-RNC
radio container previously received in the S1AP HANDOVER COMMAND message. Indeed the eNodeB
has ensured the S1AP-to-RRC mediation in a transparent fashion.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Inter-RAT Mobility to UMTS in RRC Connected Mode: RRC Connection Release and Redirection to
UTRAN.
Redirection from LTE to a UTRAN target cell relies on radio measurements to trigger the redirection
procedure.
A redirection results in a RRC Connection Release from the source eNB, instructing the UE to leave
the LTE eUTRAN and start access on a new target cell in the UTRAN RAT.
Only blind redirection was implemented in LA2.0. Blind redirection means redirection without
measurements on a target RAT. Blind redirection is triggered by detection of serving cell
degradation (eventA2) when intra-frequency LTE radio conditions fall below a configured threshold.
Figure 15.1-11: RAT frequency with highest cellReselectionPriority is chosen for redirection
In RRC_Connected mode, the eNB may trigger a procedure of RRC Release with
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 15.1-12: RRC Connection Release with Redirection Info from EUTRAN to UTRAN
Event B2 Serving becomes worse than threshold1 and inter-RAT neighbour becomes better than
threshold2.
&
Ms = measurement result of the serving cell [dBm]
Hys = reportConfigUTRA::hysteresis [dB]
Thresh1 = ReportConfigUTRA::thresholdEutraRsrpB2 [dBm]
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.1.2.4 THRESHOLDEUTRARSRPB2
This parameter sets the RSRP threshold for the serving cell of the selection criteria in case of
mobility towards UTRAN.
KPI Impact:
Mobility - low values of this parameter might create coverage discontinuity during selection
operation due to shrinking UMTS cell as seen by the UE.
Step 1: Set the value of thresholdEutraRsrpB2 to one of the following values {-104,-102,-100,-98,-
96}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and UTRAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdEutraRsrpB2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.1.2.5 THRESHOLDUTRARSCP
This parameter sets the RSRP threshold for the target cell of the selection criteria in case of
mobility towards UTRAN.
KPI Impact:
Mobility - low values of this parameter might create coverage discontinuity during selection
operation due to shrinking UMTS cell as seen by the UE.
Step 1: Set the value of thresholdUtraRscp to one of the following values {-118,-116,-114,-112, -
110}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and UTRAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdUtraRscp.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.2.6 OFFSETFREQUTRA
This parameter is used to indicate a frequency specific offset to be applied when evaluating
triggering conditions for measurement reporting.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might allow the UE to determine the strongest cell
later. High values of this parameter might allow the UE to determine the strongest cell
earlier.
Step 1: Set the value of offsetFreqUtra to one of the following values {-3,-2,-1, 0, 1, 2, 3}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and UTRAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of offsetFreqUtra.
Step 4: Post process the logged data and determine the positions at which the UE selected the
UTRAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.1.2.7 FILTERCOEFFICIENTOFQUANTITYCONFIGUTRA
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.1.2.8 HYSTERESIS
This IE is a parameter used within the entry and leave condition of an event triggered reporting
condition. This is used to provision IE Hysteresis in IE ReportConfigInterRAT, in IE MeasConfig . This
parameter defines the hysteresis used by the UE to trigger an inter-RAT event-triggered
measurement report.
It is used in several processes: Event B2 (Serving becomes worse than threshold1 and inter RAT
neighbour becomes better than threshold2); Event B1 (Inter RAT neighbour becomes better than
threshold); Event A1 (Serving becomes better than threshold); Event A2 (Serving becomes worse
than threshold); Event A3 (Neighbour becomes offset better than serving); Event A4 (Neighbour
becomes better than threshold); Event A5 (Serving becomes worse than threshold1 and neighbour
becomes better than threshold2).
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Throughput - low values of this parameter can generate a ping pong behaviour which can
result in interruption times and low throughput during HO operation.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.1.2.9 TIMETOTRIGGER
This parameter sets the time duration time during which the conditions to trigger an event report
have to be satisfied before sending a RRC measurement report in event triggered mode.
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Note: LGE UE RSRP filtering is every 100ms, which means that any time-to-trigger value equal or
above 100ms is indeed significant. The only reason to have ms40 is to be sure that we will take the
first RSRP reporting into consideration in case it is before the 100ms.
15.1.2.10 REPORTINTERVAL
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter will decrease the HO success rate. High values of this
parameter will increase the Ho success rate.
Step 1: Set the value of reportInterval to one of the following values {120, 240, 480, 640, 1024, and
2048}.
Step 2: perform a drive test back and forth between the EUTRAN cell and UTRAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportInterval.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.1.2.11 MAXREPORTCELLS
This parameter defines the maximum number of cells to be reported in a measurement report.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of maxReportCells to one of the following values {1, 2, 3, 4, 5, 6, 7, and 8}.
Step 2: perform a drive test back and forth between the EUTRAN cell and UTRAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of maxReportCells.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.1.2.12 REPORTAMOUNT
This parameter configures the number of periodical reports the UE has to transmit after the event
was triggered.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of reportAmount to one of the following values {r1, r2, r4, r8, r16, r32, r64}.
Step 2: Perform a drive test back and forth between the EUTRAN cell and UTRAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportAmount.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Triggers:
- an A2 measurement report is received
- a B2 measurement report is received
- a CS Fallback is triggered
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
This feature supports basic mobility for UE moving from LTE radio coverage to GSM radio coverage.
The capability provided by this feature enables the LTE-to-GSM mobility of a dual-mode UE in
RRC_IDLE mode, which allows a UE leaving LTE coverage to recover service in GSM coverage, as
soon as it gets available, i.e. radio conditions are sufficiently good.
It also enables LTE-to-GSM mobility in RRC_CONNECTED with packet data session that is the leaving
of an LTE coverage island, while the user is moving this done via PS Handover procedure. The
triggering condition is because of radio conditions on LTE being degraded. Release/Redirect
mechanism is supported to accommodate the scenarios where the optimized HO procedures.
CCO with or without Network Assisted Cell Change (NACC) mechanism is supported. CCO mechanism
is supported to accommodate the scenarios where the optimized PS-HO procedure is not supported
in the UE, or the ePC Core, or the GERAN network during early deployment.
For cell reselection the UE must be in RRC-IDLE mode and to be GERAN capable. It shall receive the
information about GERAN coverage through SIB7 message. Then the UE applies inter-RAT cell
reselection criteria.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
3GPP rules:
SservingCell > 0 where
SservingCell = Qrxlevmeas (Qrxlevmin + Qrxlevminoffset) - Pcompensation
Lets consider:
IF SServingCell > Snonintrasearch -> UE choose to not perform inter-RAT measurements
If SServingCell Snonintrasearch -> UE shall perform inter-RAT measurements
Measurement phase
RSRP
> Qrxlevmin + Qrxlevminoffset + Snonintrasearch
Qrxlevmin + Qrxlevminoffset + Snonintrasearch
Measurement phase
Figure 15.2-3: LTE to GERAN Mobility (RSRP vs. Time) Cell Reselection Measurement phase
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
UE will reselect the new cell if the conditions below are met:
Sservingcell < threshServingLow and SnonServingCell > threshXLow during tReselectionGeran
No cell with higher priority than the serving will fulfil the condition: SnonServingCell >
threshXHigh during tReselectionGeran
More than 1 second(s) has elapsed since the UE camped on the current serving cell.
Figure 15.2-4: LTE to GERAN Mobility Cell Reselection toward lower priority GERAN cell
Step 1: Serving cell become less good and the RSRP level decrease under
[Qrxlevmin(SIB3)+sNonIntraSearch]. Then Measurement GAP is activated and the UE can detect and
measure lower priority cells than the serving.
Step 2: Serving cell becomes worse and the RSRP level decrease under
[Qrxlevmin(SIB3)+threshServingLow]. Cell reselection would be possible, but not yet candidate cell,
reaching [Qrxlevmin+Qrxlevminoffset +Pcompensation+threshXLow]. In this user case, 1 and 2 occur
at the same time because we have chosen to implement sNonIntraSearch= threshServingLow.
Step 3: The situation just above is still reached and also, in the target cell, threshold
[Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXLow] is reached. tReselectionGeran is started.
During tReselectionGeran, NO higher cell priority reaches
[Qrxlevmin+Qrxlevminoffset+Pcompensation+threshXHigh]
Step 4: tReselectionGeran is achieved, reselection is triggered.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Figure 15.2-3: LTE to GERAN Mobility (RSRP vs. Time) Cell Reselection Decision phase
15.2.1.1 QRXLEVMIN
This parameter configures the minimum required RSRP level in the GERAN cell, used by the UE in
cell reselection.
KPI Impact:
Mobility - high values might create coverage discontinuity in idle, as seen by UE.
Step 1: Set the value of qRxLevMin to one of the following values {- 105, -103, -101, -99, -97}.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qRxLevMin and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.2 SNONINTRASEARCH
This parameter is used for setting a threshold for the selection criterion, threshold that would
determine when, based in serving cell field level, the UE starts performing measurements for inter-
frequency and inter-RAT measurements. It is used for cell reselection.
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Step 1: Set the value of sNonIntraSearch to one of the following values {12, 14, 16, 18, and 20}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another sNonIntraSearch and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.3 THRESHSERVINGLOW
This threshold is used when the mobility towards lower priority frequency is taken in consideration.
The default priority for GERAN frequency is lower than for EUTRAN frequency which implies that
this parameter is used each time mobility towards GERAN happens.
This parameter sets the threshold of the selection criteria in case of mobility towards lower priority
RAT.
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionRAT.
The parameter discussed here only impacts the part related to the serving cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
Optimization of this parameter, in conjunction with threshXLow should aim at obtaining the cell
sizes for both GERAN cell and EUTRAN cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshServingLow should be decoupled from the optimization for
threshXLow. For this, the value of threshXLow should be the minimum allowed such that the first
inequality of the selection criteria is satisfied for the largest surface of the cell. Once this is
realized, the selection will always be triggered by the value of threshServingLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshServingLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another threshServingLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.4 THRESHXLOW
This threshold is used when the mobility towards lower priority frequency is taken in consideration.
The default priority for GERAN frequency is lower than for EUTRAN frequency which implies that
this parameter is used each time mobility towards GERAN happens.
This parameter sets the threshold of the selection criteria in case of mobility towards lower priority
RAT.
The reselection criterion is quite a complex one which means that the optimization of this
parameter would need some decoupling to be performed and the optimization to be made one
parameter at a time. There is a condition on the serving cell through threshServingLow, another
one on target cell through threshXLow and another one on time through tReselectionRAT.
The parameter discussed here only impacts the part related to the serving cell.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
The condition on the serving cell can be rewritten as a condition on the measured level in the
serving cell as follows:
KPI Impact:
Mobility - high values might create coverage discontinuity during reselection operation due to
shrinking GSM cell as seen by the UE.
Optimization of this parameter, in conjunction with threshServingLow should aim at obtaining the
cell sizes for both GERAN cell and EUTRAN cell both in active and in idle mode. Once the cells are
correctly dimensioned for active mode, the optimization for idle mode parameters can be
performed. The optimization of threshXLow should be decoupled from the optimization for
threshServingLow. For this, the value of threshServingLow should be the minimum allowed such
that the first inequality of the selection criteria is satisfied for the largest surface of the cell. Once
this is realized, the selection will always be triggered by the value of threshXLow.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshXLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another threshXLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.5 TRESELECTIONGERAN
This parameter concerns the cell reselection timer tReselectionRAT for GERAN. Broadcast in
SystemInformationBlockType7.
It imposes a condition on the reselection. UE will actually reselect the new cell, only if the new cell
is better ranked than the serving cell during a time interval tReselectionGERAN.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might allow ping-pong behaviour during reselection
operation. High values of this parameter might delay the reselection and possible lead to lost
connection to the serving cell.
Optimization of this parameter should find a trade-off between delayed reselection and ping pong
behaviour. Most probably, if the UEs are not moving fast, the delayed reselection would not be an
issue. For optimization, a procedure containing the following steps can be used:
Step 1: Set the value of tReselectionGERAN to one of the following values {1, 2, 3, and 4}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionGERAN.
Step 4: Post-process the logs and analyze them as reselection position vs. tReselectionGERAN values
and ping pong behaviour vs. tReselectionGERAN values and choose the optimized value to obtain
smallest interruption time and highest success rate.
Step 5: Calculate the HO success rate in each direction.
15.2.1.6 TRESELECTIONGERANSFMEDIUM
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionGERANSfMedium to one of the following values {0.25, 0.5, 0.75,
and 1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the reselection - related messages and the position of the UE.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionGERANSfMedium.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.7 TRESELECTIONGERANSFHIGH
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionGERANSfHigh to one of the following values {0.25, 0.5, 0.75,
and 1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionGERANSfHigh.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.8 NCELLCHANGEHIGH
This parameter configures the number of cell changes to enter high mobility state
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of nCellChangeHigh to one of the following values {10,11,12,13,and 14}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.9 NCELLCHANGEMEDIUM
This parameter configures the number of cell changes to enter medium mobility state
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of nCellChangeMedium to one of the following values {1, 2, 3, 4, 5, and 6}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.10 QHYSTSFHIGH
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might allow the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
Step 1: Set the value of qHystSfHigh to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.1.11 QHYSTSFMEDIUM
KPI Impact:
Mobility - low values of this parameter might allow the UE to start reselection earlier. High
values of this parameter might allow the UE to start reselection later.
A
procedure that optimizes qHystSfMedium would contain the following steps:
Step 1: Set the value of qHystSfMedium to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
GERAN cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Event B2 Serving becomes worse than threshold1 and inter-RAT neighbour becomes better than
threshold2.
&
Ms = measurement result of the serving cell [dBm]
Hys = reportConfigGERAN::hysteresis [dB]
Thresh1 = ReportConfigGERAN::thresholdEutraRsrpB2 [dBm]
15.2.2.1 THRESHOLDEUTRARSRPB2
This parameter sets the RSRP threshold for the serving cell of the selection criteria in case of CCO
with NACC towards GERAN.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might create coverage discontinuity during selection
operation due to shrinking GSM cell as seen by the UE.
Step 1: Set the value of thresholdEutraRsrpB2 to one of the following values {-104,-102,-100,-98,-
96}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and GERAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdEutraRsrpB2.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.2.2 THRESHOLDGERAN
This parameter sets the RSRP threshold for the target cell of the selection criteria in case of CCO
with NACC towards GERAN.
KPI Impact:
Mobility - low values of this parameter might create coverage discontinuity during selection
operation due to shrinking GSM cell as seen by the UE.
Step 1: Set the value of thresholdGeran to one of the following values {-114,-112,-110,-108, -106,-
104}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and GERAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdGeran.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.2.3 OFFSETFREQGERAN
This parameter is used to indicate a frequency specific offset to be applied when evaluating
triggering conditions for measurement reporting.
KPI Impact:
Mobility - low values of this parameter might allow the UE to determine the strongest cell
later. High values of this parameter might allow the UE to determine the strongest cell
earlier.
Step 1: Set the value of offsetFreqGERAN to one of the following values {-3,-2,-1, 0, 1, 2, 3}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and GERAN cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of offsetFreqGERAN.
Step 4: Post process the logged data and determine the positions at which the UE selected the
GERAN cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.2.2.4 FILTERCOEFFICIENTOFQUANTITYCONFIGGERAN
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
15.2.2.5 HYSTERESIS
This IE is a parameter used within the entry and leave condition of an event triggered reporting
condition. This is used to provision IE Hysteresis in IE ReportConfigInterRAT, in IE MeasConfig . This
parameter defines the hysteresis used by the UE to trigger an inter-RAT event-triggered
measurement report.
It is used in several processes: Event B2 (Serving becomes worse than threshold1 and inter RAT
neighbour becomes better than threshold2); Event B1 (Inter RAT neighbour becomes better than
threshold); Event A1 (Serving becomes better than threshold); Event A2 (Serving becomes worse
than threshold); Event A3 (Neighbour becomes offset better than serving); Event A4 (Neighbour
becomes better than threshold); Event A5 (Serving becomes worse than threshold1 and neighbour
becomes better than threshold2).
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Throughput - low values of this parameter can generate a ping pong behaviour which can
result in interruption times and low throughput during HO operation.
15.2.2.6 TIMETOTRIGGER
This parameter sets the time duration time during which the conditions to trigger an event report
have to be satisfied before sending a RRC measurement report in event triggered mode.
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during HO operation.
High values of this parameter might delay the HO and possible lead to lost connection to the
serving cell.
Note: LGE UE RSRP filtering is every 100ms, which means that any time-to-trigger value equal or
above 100ms is indeed significant. The only reason to have ms40 is to be sure that we will take the
first RSRP reporting into consideration in case it is before the 100ms.
15.2.2.7 REPORTINTERVAL
KPI Impact:
Mobility low values of this parameter will decrease the HO success rate. High values of this
parameter will increase the Ho success rate.
Step 1: Set the value of reportInterval to one of the following values {120, 240, 480, 640, 1024, and
2048}.
Step 2: perform a drive test back and forth between the EUTRAN cell and GERAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportInterval.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.2.2.8 MAXREPORTCELLS
This parameter defines the maximum number of cells to be reported in a measurement report.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of maxReportCells to one of the following values {1, 2, 3, 4, 5, 6, 7, and 8}.
Step 2: Perform a drive test back and forth between the EUTRAN cell and GERAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of maxReportCells.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.2.2.9 REPORTAMOUNT
This parameter configures the number of periodical reports the UE has to transmit after the event
was triggered.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of reportAmount to one of the following values {r1, r2, r4, r8, r16, r32, r64}.
Step 2: Perform a drive test back and forth between the EUTRAN cell and GERAN cell on various
routes and log the HO - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportAmount.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
Figure 15.2-4: Call Flow for Cell Change Order with /Without NACC
In RRC_Idle mode the UE performs inter-RAT cell reselection based on cell signal quality
measurements.
Done by the UE under control from EUTRAN via System Information Broadcast 8.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Cell selection: the UE seeks to identify a suitable cell i.e. cell for which the measured cell
attributes satisfy the cell selection criteria ; if found it camps on that cell and starts the cell
reselection procedure.
Cell reselection: UE performs measurements of the serving and neighbour cells.
The cell selection and reselection algorithms are controlled by setting of parameters (thresholds
and hysteresis values) that define the best cell and/or determine when the UE should select a new
cell.
If a LTE cell is in the border area of the HRPD system, SystemInformationBlockType8 (SIB8) should
be broadcasted in additional to SIB3 for UE to perform LTE to HRPD reselection.
SIB8 contains the following three optional information blocks:
systemTimeInfo
searchWindowSize
parametersHRPD
In RRC_IDLE mode, the cell reselection is internal to UE and is controlled by the System
Information Parameters provided in SIB8 if the reselection to HRPD is enabled
(isMobilityToHrpdAllowed = TRUE). Any modification of SIB8 parameters triggers a dynamic
system information modification procedure.
Measurement phase
RSRP
SServingCell Snonintrasearch
SServingCell > Snonintrasearch
Measurement phase
Figure 15.3-1: LTE to CDMA Mobility (RSRP vs. Time) Cell Reselection Measurement Phase
Decision phase
eHRPD Pilot Strength
RSRPs
tReselectionCdmaHrpd
Figure 15.3-2: LTE to CDMA Mobility (RSRP vs. Time) Cell Reselection Decision Phase
UE will reselect the new LowPriority cell if the conditions below are met:
Sservingcell < CellReselectionConfLte::threshXLow and SnonServingCell >
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.3.1.1 SNONINTRASEARCH
This parameter is used for setting a threshold for the selection criterion, threshold that would
determine when, based in serving cell field level, the UE starts performing measurements for inter-
frequency and inter-RAT measurements. It is used for cell reselection.
KPI Impact:
Mobility - low values delay the start of measurements performed by the UE which can be
reflected in delayed reselection.
Step 1: Set the value of sNonIntraSearch to one of the following values {12, 14, 16, 18, and 20}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another sNonIntraSearch and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the HRPD
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.2 THRESHXLOW
This threshold is used when the mobility towards lower priority frequency is taken in consideration.
The default priority for HRPD frequency is lower than for EUTRAN frequency which implies that this
parameter is used each time mobility towards HRPD happens.
This parameter sets the threshold of the selection criteria in case of mobility towards lower priority
RAT.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - high values might create coverage discontinuity during reselection operation due to
shrinking HRPD cell as seen by the UE.
The optimization process should contain the following steps (it is supposed that the sizes of cells in
active mode are known):
Step 1: Set the value of threshXLow to one of the following values {0, 6, 12, 18, and 24}.
Step 2: With UE in idle mode, perform a drive test back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another threshXLow and repeat Step 2.
Step 4: Post process the logged data and determine the positions at which the UE selected the HRPD
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.3 TRESELECTIONCDMAHRPD
This parameter concerns the cell reselection timer tReselectionRAT for HRPD. Broadcast in
SystemInformationBlockType8.
It imposes a condition on the reselection. UE will actually reselect the new cell, only if the new cell
is better ranked than the serving cell during a time interval tReselectionCdmaHrpd.
KPI Impact:
Mobility - low values of this parameter might allow ping-pong behaviour during reselection
operation. High values of this parameter might delay the reselection and possible lead to lost
connection to the serving cell.
Optimization of this parameter should find a trade-off between delayed reselection and ping pong
behaviour. Most probably, if the UEs are not moving fast, the delayed reselection would not be an
issue. For optimization, a procedure containing the following steps can be used:
Step 1: Set the value of tReselectionCdmaHrpd to one of the following values {1, 2, 3, and 4}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the reselection - related messages and the position of the UE.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionCdmaHrpd.
Step 4: Post-process the logs and analyze them as reselection position vs. tReselectionCdmaHrpd
values and ping pong behaviour vs. tReselectionCdmaHrpd values and choose the optimized value to
obtain smallest interruption time and highest success rate.
Step 5: Calculate the HO success rate in each direction.
15.3.1.4 TRESELECTIONHRPDSFMEDIUM
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionHRPDSfMedium to one of the following values {0.25, 0.5, 0.75,
and 1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionHRPDSfMedium.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.5 TRESELECTIONHRPDSFHIGH
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of tReselectionHRPDSfHigh to one of the following values {0.25, 0.5, 0.75, and
1}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the reselection - related messages and the position of the UE.
Perform this test 10 times in each direction. Make sure that the driving speed is nominal and the
same for all the test samples.
Step 3: Repeat Step 2 for another value of tReselectionHRPDSfHigh.
Step 4: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.6 NCELLCHANGEHIGH
This parameter configures the number of cell changes to enter high mobility state
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of nCellChangeHigh to one of the following values {10, 11, 12, 13, and 14}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.7 NCELLCHANGEMEDIUM
This parameter configures the number of cell changes to enter medium mobility state
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of nCellChangeMedium to one of the following values {1, 2, 3, 4, 5, and 6}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another nCellChangeMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.1.8 QHYSTSFHIGH
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
Step 1: Set the value of qHystSfHigh to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfHigh and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.3.1.9 QHYSTSFMEDIUM
KPI Impact:
Mobility - low values of this parameter will determine the UE to start reselection earlier. High
values of this parameter will determine the UE to start reselection later.
A
procedure that optimizes qHystSfMedium would contain the following steps:
Step 1: Set the value of qHystSfMedium to one of the following values {dB-6, dB-4, dB-2, dB0}.
Step 2: With the UE in idle mode, perform a drive back and forth between the EUTRAN cell and
HRPD cell on various routes and log the control messages exchanged between eNodeB and UE along
with the GPS coordinates of the UE.
Step 3: Choose another qHystSfMedium and repeat Step 2.
Step 4: Post process the logged data.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
In RRC_Connected mode the UE sends to the eNB a measurement report associated with a
configured inter-RAT measurement that was setup when it moved to an LTE border cell.
When eNB receives a UE event B2 measurement report with measurementPurpose = Mobility-
Inter-RAT-to HRPD, LTE to HRPD measurement based redirection procedure will be performed.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Event B2 Serving becomes worse than threshold1 and inter-RAT neighbour becomes better than
threshold2.
&
15.3.2.1 THRESHOLDEUTRARSRPB2
This parameter sets the RSRP threshold for the serving cell of the selection criteria in case of
mobility towards CDMA2000.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might create coverage discontinuity during selection
operation due to shrinking CDMA2000 cell as seen by the UE.
Step 1: Set the value of thresholdEutraRsrpB2 to one of the following values {-104,-102,-100,-98,-
96}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and HRPD cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdEutraRsrpB2.
Step 4: Post process the logged data and determine the positions at which the UE selected the HRPD
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.2.2 THRESHOLDCDMA2000
This parameter sets the RSRP threshold for the target cell of the selection criteria in case of
mobility towards HRPD.
KPI Impact:
Mobility - high values might create coverage discontinuity during selection operation due to
shrinking HRPD cell as seen by the UE
Step 1: Set the value of thresholdCDMA2000 to one of the following values {-13,-11,-9,-7,-5}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and HRPD cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of thresholdCDMA2000.
Step 4: Post process the logged data and determine the positions at which the UE selected the HRPD
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.2.3 OFFSETFREQ
This parameter is used to indicate a frequency specific offset to be applied when evaluating
triggering conditions for measurement reporting.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility - low values of this parameter might allow the UE to determine the strongest cell
later. High values of this parameter might allow the UE to determine the strongest cell
earlier.
Step 1: Set the value of offsetFreq to one of the following values {-3,-2,-1, 0, 1, 2, 3}.
Step 2: While performing a download with the UE, perform a drive test back and forth between the
EUTRAN cell and HRPD cell on various routes and log the control messages exchanged between
eNodeB and UE along with the GPS coordinates of the UE
Step 3: Repeat Step 2 for another value of offsetFreq.
Step 4: Post process the logged data and determine the positions at which the UE selected the HRPD
cell.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.2.4 HYSTERESIS
This IE is a parameter used within the entry and leave condition of an event triggered reporting
condition. This is used to provision IE Hysteresis in IE ReportConfigInterRAT, in IE MeasConfig . This
parameter defines the hysteresis used by the UE to trigger an inter-RAT event-triggered
measurement report.
It is used in several processes: Event B2 (Serving becomes worse than threshold1 and inter RAT
neighbour becomes better than threshold2); Event B1 (Inter RAT neighbour becomes better than
threshold); Event A1 (Serving becomes better than threshold); Event A2 (Serving becomes worse
than threshold); Event A3 (Neighbour becomes offset better than serving); Event A4 (Neighbour
becomes better than threshold); Event A5 (Serving becomes worse than threshold1 and neighbour
becomes better than threshold2).
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during redirection
operation. High values of this parameter might delay the redirection and possible lead to lost
connection to the serving cell.
Throughput - low values of this parameter can generate a ping pong behaviour which can
result in interruption times and low throughput during redirection operation..
Step 1: Set the values of hysteresis and to timeToTrigger to one of the following {(2,100), (3, 80),
(4,200), (1, 40)}, in both current cell and neighbour cell.
Step 2: Perform a drive test while performing a download and log the throughput values and the
position of the UE. Drive in and out of the current cell to the neighbour cell.
Step 3: Repeat Step 2 for another pair of values of the three tested parameters.
Step 4: Represent throughput vs. position (distance) (Service continuity), #redirection-attempts,
Success Rate/Failure Rate, #of Ping-pongs, redirection interruption time for all pairs of tested
values.
Step 5: Choose the optimized value to obtain smallest interruption time and highest success rate.
15.3.2.5 TIMETOTRIGGER
This parameter sets the time duration time during which the conditions to trigger an event report
have to be satisfied before sending a RRC measurement report in event triggered mode.
KPI Impact:
Mobility low values of this parameter might allow ping-pong behaviour during redirection
operation. High values of this parameter might delay the redirection and possible lead to lost
connection to the serving cell.
This parameter should be carefully optimized, best in conjunction with hysteresis as presented in
the previous paragraph. Indeed, the optimized value can be impacted by the load of the
surrounding cells.
Note: LGE UE RSRP filtering is every 100ms, which means that any time-to-trigger value equal or
above 100ms is indeed significant. The only reason to have ms40 is to be sure that we will take the
first RSRP reporting into consideration in case it is before the 100ms.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
15.3.2.6 REPORTINTERVAL
KPI Impact:
Mobility low values of this parameter will decrease the HO success rate. High values of this
parameter will increase the Ho success rate.
Step 1: Set the value of reportInterval to one of the following values {120, 240, 480, 640, 1024, and
2048}.
Step 2: perform a drive test back and forth between the EUTRAN cell and HRPD cell on various
routes and log the redirection - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportInterval.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.3.2.7 MAXREPORTCELLS
This parameter defines the maximum number of cells to be reported in a measurement report.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of maxReportCells to one of the following values {1, 2, 3, 4, 5, 6, 7, and 8}.
Step 2: perform a drive test back and forth between the EUTRAN cell and HRPD cell on various
routes and log the redirection - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of maxReportCells.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
15.3.2.8 REPORTAMOUNT
This parameter configures the number of periodical reports the UE has to transmit after the event
was triggered.
KPI Impact:
Mobility low values of this parameter allow the UE to report fewer neighbour cells. High
values of this parameter allow the UE to report more neighbour cells.
Step 1: Set the value of reportAmount to one of the following values {r1, r2, r4, r8, r16, r32, r64}.
Step 2: Perform a drive test back and forth between the EUTRAN cell and HRPD cell on various
routes and log the redirection - related messages and the position of the UE.
Step 3: Repeat Step 2 for another value of reportAmount.
Step 4: Post process the measurement and choose the optimized value to obtain smallest
interruption time and highest success rate.
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
16.1 ABBREVIATIONS
Acronym Description
3G 3rd Generation Mobile Telecommunications
3GPP 3rd Generation Partnership Project
3GPP2 EV-DO standards
AMBR Aggregate Maximum Bit Rate
AMR Adaptive Multi Rate codec
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction
TDD Time Division Duplex (UE operates on one frequency with different time slots for UL
and DL)
TEID Tunnel Endpoint Identifier (GTP)
TEID-C Tunnel Endpoint Identifier, Control Plane
TEID-U Tunnel Endpoint Identifier, User Plane
TI Transaction Identifier
TIL Terminal dInstallation Locale (Local I&C terminal)
TM Transparent Mode
TMSI Temporary Mobile Station Identifier
TMU Traffic Management Unit
TRB Traffic Radio Bearer
TS Technical Specification
UBM Upper Bearer Management
UDP User Datagram Protocol
UE User Equipment (similar to Access Terminal in EV-DO)
UEA UMTS Encryption Algorithm
UICC Universal Integrated Circuit Card
UIIV UMTS Interoperability Integration and Verification
UL Uplink (equivalent to EV-DO Reverse Channel) LTE supports peak data rate of 80
Mbps UL
ULI User Location Info
UL-SCH Uplink Shared Channel
UMTS Universal Mobile Telecommunication System
UTRAN Universal Terrestrial Radio Access Network
VAL Value counter
VLR Visitor Location Register
VoA Visited IP Address
VoIP Voice over Internet Protocol
VSNCP Vendor Specific Network Control Protocol
WCDMA Wideband CDMA
WPS or WiPS 9452 Wireless Provisioning System (also sometimes referred to as WIPS)
END OF DOCUMENT
Alcatel-Lucent - Confidential - Solely for authorized persons having a need to know Proprietary - Use pursuant to Company instruction