LTE Parameter - Knowledge Sharing

LTE Parameters
Ankur Prasad
Senior Engineer
GSC India
LTE Cell selection:
UE MEASURMENTS AND EVALUATION
EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 2

Intra Frequency Cell Reselection:
Vendor
MOC Parameter AT&T Gold Standard Range Unit
Recommended
EUtranCellFDD systemInformationBlock3.sIntraSearch 62 62 0..62 dB

LTE Intra Frequency Handover:
AT&T Gold Vendor

MOC Parameter Range Unit
Standard Recommended
UeMeasControl sMeasure 0 0 -140..-44,0 dBm


Intra Frequency Cell Reselection:
The parameter reportIntervalA3 determines the time interval between measurement reports. The
parameter reportAmountA3 indicates how many reports to send; a value of 0 indicates that the
reports are sent indefinitely while the EventA3 condition is fullfilled.

AT&T Gold Vendor

MOC Parameter Range Unit
Standard Recommended
ReportConfigEUtraBestCell a3offset 30 30 -150..150 0.1 dB
ReportConfigEUtraBestCell hysteresisA3 10,30 10 0..150 0.1 dB
0,40,64,80,100,128,160
ReportConfigEUtraBestCell timeToTriggerA3 40 ,256,320,480,512,640,1 ms
024,1280,2560,5120
80,320,512
RSRP
ReportConfigEUtraBestCell triggerQuantityA3 0 RSRP RSRQ
ReportConfigEUtraBestCellAnr a3offsetAnrDelta 3 1 -10..10 1 dBm
ReportConfigEUtraBestCellAnr hysteresisA3 10 0..150 0.1 dB

10,30
0,40,64,80,100,128,160
ReportConfigEUtraBestCellAnr timeToTriggerA3 640 ,256,320,480,512,640,1
024,1280,2560,5120
80,320,512
cellIndividualOffsetEUtran = 0 { -24, -22, -20, -18, -16, -14, -12, -10, -8, -6, -5, -4, -3, -2, -1, 0,
1, 2, 3, 4, 5, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24 }
Offset value of the neighbor cell. Used when the UE is in connected mode.
Takes effects: New connection.
Unit: dB
LTE to WCDMA Idle Mode Cell Reselection
› WCDMA carrier frequencies must be defined as UtranFrequency managed objects in the
eNode-B, each with the LTE parameter UtranFrequency. arfcnValueUtranDl set to the
downlink UARFCN of the WCDMA carrier.
The order of priority between the LTE and WCDMA network is determined by the absolute
priority of the LTE carrier frequency, which is set by the LTE parameter
EUtranFreqRelation . cellReselectionPriority, and the absolute priority of the WCDMA
carrier frequency, which is set by the LTE parameter UtranFrequencyRelation
.cellReselectionPriority.
RAN Managed Object Parameter Value Comment

LTE EUtranFreqRelation cellReselectionPriority 5
LTE UtranFrequencyRelation cellReselectionPriority 2

LTE to WCDMA Idle Mode Cell Reselection(IRAT)
Given the existence of SIB6 and the higher priority of LTE over WCDMA for cell reselection ,
an LTE device starts measuring IRAT cells when :
SServingCell ≤ Snonintrasearch (6,10)
Snonintrasearch = Threshold for inter-frequency and inter-RAT measurements on frequencies of equal or

lower priority, i.e. LTE parameter EUtranCellFDD. systemInformationBlock3.sNonIntraSearch
SServingCell = QRxLevMeas - (QRxLevMin + QRxLevMinOffset) – Pcompensation
Qrxlevmeas = Measured RSRP value in the cell (dBm)

Qrxlevmin = Required minimum RSRP level in the cell (dBm), i.e. LTE parameter EUtranCellFDD .
qRxLevMin ( -120 dbm)
qRxLevMinOffset = 1000 { 2..16, 1000 } The offset applied to the signalled Qrxlevmin. Corresponds to
parameter Qrxlevminoffset in 3GPP TS 36.304. Value 1000 means it is not sent and the UE sets
Qrxlevminoffset=0dB.
Qrxlevminoffset is not configurable in L11B and the default value is 0 dBm
Pcompensation = Compensation [max (PEMAX - PUMAX, 0)] if the maximum power according to the UE
capability (PUMAX) is less than the maximum UE power to be used in the cell (PEMAX), i.e. LTE parameter
EUtranCellFDD.pMaxServingCell. Value 1000 means the parameter is not included in system information.

When the measurement of IRAT cells is active, cell reselection to a cell on a lower priority
WCDMA frequency is performed when
• No LTE intra-frequency neighbor meets the intra-frequency cell reselection criteria and
• LTE SServingCell < Threshserving, low (4 -116 dbm) , and
• WCDMA SnonServingCell,x > Threshx, low (0  -120 dbm) during a time interval
TreselectionRAT ( 2 sec) , and
• More than 1 second has elapsed since the UE camped on the current LTE serving cell
Where for LTE serving cells, SServingCell is as defined above in last slide.
Threshserving,low = Threshold for the signal strength of the serving cell, below which the UE
performs cell reselection towards a lower priority inter-frequency or inter-RAT frequency, i.e. LTE
parameter EUtranCellFDD. systemInformationBlock3.threshServingLow
And for the WCDMA target cells,
SnonServingCell,x = Qrxlevmeas - qRxLevMin – Pcompensation

Qrxlevmeas = Received signal strength measured by the UE and expressed in CPICH RSCP
(dBm).
qRxLevMin = Minimum required RX level in the cell expressed in dBm, i.e. LTE parameter
UtranFrequencyRelation.qRxLevMin
Threshx, low is The threshold used in reselection towards frequency X priority from a higher
priority frequency. Each frequency of UTRAN might have a specific threshold.
The relevant LTE parameter is UtranFrequencyRelation.threshXLow
TreselectionRAT = Cell reselection timer, i.e. LTE parameter EUtranCellFDD.
systemInformationBlock6.tReselectionUtra
Pcompensation = Compensation [max(maxTxPowerUl – P_MAX, 0) (dB)] where maxTxPowerUl
is the maximum TX power level a UE may use when accessing the cell on RACH (dBm) which is
sent in SIB6 and set with the LTE parameter
UtranFrequencyRelation.pMaxUtra and P_MAX is the maximum RF output power of the UE in
dBm. Value 1000 means the parameter is not included in system information.

› RAN Managed Object Parameter Value Comment
› LTE EUtranCellFDD qRxLevMin -120
› LTE EUtranCellFDD sNonIntraSearch 6 /10 -114 /-110 dBm
› LTE EUtranCellFDD pMaxServingCell 23
› LTE EUtranCellFDD threshServingLow 6 /10 -114 /-110 dBm
› LTE UtranFrequencyRelation qRxLevMin -120
› LTE UtranFrequencyRelation threshXLow 0 -120dBm
› LTE EUtranCellFDD tReselectionUtra 2
› LTE UtranFrequencyRelation pMaxUtra 24
Trail case:

2 .WCDMA to LTE Cell Reselection:
Configuration Requirements
Cell reselection to LTE is supported by E-UTRA capable UEs in Idle mode and in state URA_PCH.
If the device detects a neighboring LTE cell with higher priority than the serving WCDMA cell it will
attempt a cell reselection even if the measured signal strength is lower for the LTE cell compared to
the WCDMA cell. The signal strength must however be above a minimum threshold. This will ensure
that an LTE-capable device maximizes the time spent in the LTE network.
SIB19 specifies the LTE frequencies (downlink EARFCN) and the parameters used for priority
based cell reselection.
The WCDMA parameter EutranFrequency.earfcnDl must be set to the downlink EARFCN of the
LTE network.
The UE shall always perform measurements on LTE frequencies with higher priority than the
serving WCDMA cell, which is the recommended configuration.
WCDMA parameter UtranCell.absPrioCellRes.cellReselectionPriority (2)determines absolute
priority of Utran serving cell.
WCDMA parameter EutranFreqRelation.cellReselectionPriority (5)determines the absolute
priority of the LTE neighbors.

WCDMA to LTE Cell Reselection
The intensity of these measurements may vary depending on whether Srxlev and Squal of the serving cell are
above or below the thresholds defined by the parameters:
UtranCell.absPrioCellRes.sPrioritySearch1 (0  -120 dbm) and
UtranCell.absPrioCellRes.sPrioritySearch2 (0  -24 db) .
If SrxlevServingCell > Sprioritysearch1 AND SqualServingCell > Sprioritysearch2 then LTE-capable
devices shall search for LTE cells at least every Thigher_priority_search = 60 s. This seems to be consistent
with the behavior of most device that being tested.
If SrxlevServingCell ≤ Sprioritysearch1 OR SqualServingCell ≤ Sprioritysearch2 then LTE-capable devices
shall search for and measure E-UTRA frequency layers of higher or lower priority in preparation for possible
reselection.
Set as -120 dbm

WCDMA to LTE Cell Reselection
When the measurement of IRAT cells is active, cell reselection to an LTE cell on a higher
priority LTE frequency is subject to priority based criteria.
• Criterion 1 for higher priority layers: LTE SrxlevnonServingCell,x > Threshx,high
(4-116 dbm) during a time interval Treselection
• If more than one cell meets the above criteria, the UE shall reselect the cell with the highest
SrxlevnonServingCell,x among the cells meeting the criteria on the highest absolute priority
layer.
• The UE shall not perform cell reselection to cells for which the cell selection criterion S is
not fulfilled. Only LTE cells with Srxlev > 0, are considered as candidates for cell reselection.
• The UE shall not perform cell reselection until more than 1 second has elapsed since the
UE camped on the current serving cell.

WCDMA to LTE Cell Reselection----Trail Value

3.Return Back to E-UTRAN in WCDMA Active Mode
› Currently there are no specific mechanisms to steer the UE back to LTE while the UE is active in
WCDMA. Once the UE is moved to WCDMA, it is up to WCDMA Network to release the UE back to
LTE. When the UE becomes idle it will perform a cell reselection and reconnect to LTE. If additional
PS services have been acquired in the WCDMA network after a terminated CS session (in case of
CSFB), the UE does not transit into idle state. In this scenario, it is unclear as to when the UE will be
returned to LTE. Basically, if the UE has an active PS connection in Cell_ DCH or Cell_ FACH in
WCDMA it will stay there as long as there is an ongoing communication.
› When the PS connection becomes inactive the UE goes to URA_PCH or Idle and returns to LTE by
Idle Mode Cell Reselection, given that LTE has been set as the preferred RAT in the broadcast
information in WCDMA (SIB19).
› Inactivity timers are regulating the UE states when the PS connection becomes inactive.
› These are operator configurable and typical values seen today are 2 seconds for down switch to
Cell_ FACH and 10-30 seconds for down switch from Cell_ FACH to URA_PCH. This could mean
that it could take 12-32 seconds of PS inactivity before the UE can return to LTE.

4. Coverage Triggered WCDMA Session continuity
The Coverage Triggered WCDMA Session Continuity feature uses the Event A2 (serving cell becomes worse
than threshold) measurement process as defined in 3GPP documents TS 36.300 and TS 36.331.
The measurement process used by the UE to evaluate the serving cell uses parameters sent by the serving RBS
to the UE. These parameters, sent to the UE in RRCConnectionReconfiguration messages,
Types of measurements used in the handover evaluation process include the following:
• Reference Signal Received Power (RSRP), representing the mean measured power per reference signal
• RSRQ
The RBS determines whether to release the UE with a redirection to a WCDMA network, depending on the UE
capabilities, RBS licenses, and redirection priority. If the UE is released with a redirection to a WCDMA network,
the release message contains the UMTS Absolute Radio Frequency Channel Number (UARFCN), to help the UE
find a suitable WCDMA cell.

Network Architecture Configuration
The Coverage Triggered WCDMA Session Continuity feature requires no direct connections between the LTE
network and the WCDMA network. Information about the WCDMA network carrier frequencies must be entered in
the LTE RBS during network configuration. The carrier frequency information is sent to the UE during the
redirection process to assist the UE in finding the WCDMA network.
The redirection priorities set per cell include the following:
• redirectionInfoRefPrio1
The priorities can be set for each of the following Managed Objects (MO)s:
• GeranFreqGroup
• UtranFrequency
• Cdma2000Freq
The redirection information with the highest priority (where priority 1 is highest) and supported by the UE is
included in the release message.
License Configurations
A license key needs to be activated to operate the Coverage Triggered WCDMA Session Continuity feature . The
license is called WcdmaSessionContinuity. The parameter featureStateWcdmaSessionContinuity must be
enabled.

Coverage Triggered WCDMA Session continuity :Feature Operation Details
The LTE parameters EUtranFreqRelation.connectedModeMobilityPrio (5) and

UtranFreqRelation.connectedModeMobilityPrio (0.1.2.3) set the absolute priorities for LTE and
WCDMA in connected mode, with 0 being the lowest priority and 7 being the highest.
When an Event A2 measurement report is received by the serving eNode-B there are two options
for redirecting the LTE device to WCDMA:
• The device performs a blind redirection to the pre-configured UtranFrequency; or
• The device waits for a maximum of 12 seconds while evaluating WCDMA coverage until a
WCDMA neighbor of sufficient coverage strength is detected (Event B2- Serving becomes worse
than threshold1 and inter RAT neighbour becomes better than threshold2 ), in which case the
device is redirected to the carrier frequency of the detected neighbor. However, if the B2 timer
expires after 12 seconds and LTE coverage doesn’t recover, i.e. the criteria for Event A1 isn’t
met, then the device performs a blind redirection to the pre-configured UtranFrequency.

Parameter Used in RBS to Control Poor Coverage Evaluation
badCoverageMeasSelection : Specifies whether primary, secondary, both primary and secondary,

or no EventA2 measurement thresholds should be used.
The UE enters Event A2 “Serving becomes worse than absolute threshold” when:
Ms – hysteresisA2prim < a2ThresholdPrimary or
Ms – hysteresisA2sec < a2ThresholdSecondary
where
Ms = Measured RSRP or RSRQ of serving cell
badCoverageMeasSelection = BOTH
Deprecated: Since L11B. Has no functional behaviour. Planned to be removed.
Indicates if primary, secondary or both A2 measurement thresholds are used. The option to
use two measurements for eventA2 is needed since the UE is not always able to use both
RSRP and RSRQ measurement quantities when moving in a cell. The primary measurements
default to RSRP and secondary measurements default to RSRQ. Both primary and secondary
measurements can use the same measurement quantity.
Takes effects: New connection.

Coverage Triggered WCDMA Session continuity
After the UE has entered Event A2, it will check if A2 condition is fulfilled during timeToTriggerA2Prim(1280 mS)
or timeToTriggerA2Sec (640 mS) and if fulfilled then starts sending measurement reports to the serving cell.
While Event A2 is fulfilled, the reports are sent with a periodicity specified by parameter reportIntervalA2Prim(1)
or reportIntervalA2Sec(1) and the total
number of reports that can be sent (while Event A2 is fulfilled) is defined by
parameter reportAmountA2Prim(1) or reportAmountA2Sec(1).
The reported measurement quantity can be either RSRP, or RSRQ or both
RSRP and RSRQ, and is specified by parameter reportQuantityA2Prim(1) or reportQuantityA2Sec(1).
When the serving cell receives Event A2, it send a release with redirect to the UE to release the connection on
the current LTE frequency and re-establish a connection on another LTE carrier or on a IRAT carrier.
It is possible to specify the following three (3) priority targets:
redirectionInfoRefPrio1, redirectionInfoRefPrio2, redirectionInfoRefPrio3

Initial Value
(Only to be
AT&T Gold used by
MOC Parameter Vendor Recommended Range Unit
Standard Ericsson
when
building a
new site)
-116, -112,
ReportConfigEUtraBadCovPrim a2ThresholdRsrpPrim -116 -140 -140..-44 dBm
-110, -112
ReportConfigEUtraBadCovPrim a2ThresholdRsrqPrim -195 -195 -195 -195 0.1 dB
ReportConfigEUtraBadCovPrim hysteresisA2Prim 10 10 0..150 0.1 dB
-140
ReportConfigEUtraBadCovSec a2ThresholdRsrpSec -140 -140..-44 dBm
ReportConfigEUtraBadCovSec a2ThresholdRsrqSec -195..-50 -195 -195 -195..-30 0.1 dB

ReportConfigEUtraBadCovSec hysteresisA2Sec 10 10 0..150 0.1 dB
0,40,64,80,100,128,160
ReportConfigEUtraBadCovPrim timeToTriggerA2Prim 1280 640 ,256,320,480,512,640,1 ms
024,1280,2560,5120
0,40,64,80,100,128,160
ReportConfigEUtraBadCovSec timeToTriggerA2Sec 640 640 ,256,320,480,512,640,1 ms
024,1280,2560,5120
RSRP
ReportConfigEUtraBadCovPrim triggerQuantityA2Prim 0 RSRP RSRQ
RSRP
ReportConfigEUtraBadCovSec triggerQuantityA2Sec 1 RSRQ RSRQ
MeasReportConfigParams.a2ThresholdR
0 0 -24..24 1 dBm
QciProfilePredefined srpPrimOffset
0 0 -24..24 1 dBm
QciProfilePredefined srpSecOffset
0 0 -240..240 0.1 dB
QciProfilePredefined srqPrimOffset
EANRPRD / Ankur prasad | MeasReportConfigParams.a2ThresholdR
Ericsson Internal | 2012-28-03 | Page 24 0 0 -240..240 0.1 dB
QciProfilePredefined srqSecOffset
Overview of Measurements and Triggering of Event A2

Problem /Trail cases
Case 1.Accessibility: S1 Failure / MME issue
Problem
Analysis
Cell trace was activated on suspect sites

Continue…
Probably the MME is not getting the message from eNB and that’s due to S1 link losing the message
before it gets to MME. As long failure happens few times only then MME is not suspected of
having wrong configuration.
Action : Need S1 link investigation and a confirmation from MME team.
Case 2. Accessibility issues in ERAB Phase
› Accessibility in ERAB phase can happen due to an UE issue or due to
hanging resources in the eNb or an RRU issue.
› With regards to hanging resources in eNb – a restart normally helps.

› With regards to faulty RRU’s – if restarting the RRU doesn’t help, replacing the
RRU is the option (All DL carrier HW resources on port B are not functional
BXP_0_1: R XALM_ALARM_1 BXP_0_1: R
PD_B_STATE_MACHINE_FAULT_IND )
› NEO is a very powerful tool to identify UE related issues. You will need cell traces
and EBM traces to narrow down the UE.
› Cell Traces are Active in the OSS for cells you want to investigate.
› MME Traces are Active and readily available

Continue
– CCL00703 Gamma sector has a high number of ERAB failures.

RRC rate and S1 success rate is good.

CCL00703_7C_1: Access Failures
All Access failures in the Gamma sector are due to one UE with the IMSI
310410426878445.
Table_Results

Case 3. numberOfAssociations
Attribute Recommended Value Recommended Value Comment

in eNodeB in eNodeB Considering
Legacy WCDMA
Network
numberOfAssociations 320 320 Assuming an MME(2) pool size of 64 (maximum
size) for S1 connectivity and up to 256 RBS
neighbors that require X2 connectivity.
Problem:
HO KPIs are bad and Following alarms are present
Alarm :
m ExternalLinkFailure ENodeBFunction=1 (X2 link problem to one or several neighbouring
eNodeBs.)
m Remote IP Address Unreachable
Action :check the status of termpointtoENB on between sites. If they are disabled then unlock them both
ways. numberofassociations set to 48 . Chang3 to 320.

Case 4:
allowedMeasBandwidth = 6 { 6, 15, 25, 50, 75, 100 } The maximum allowed measurement
bandwidth on a carrier frequency.
Takes effects: Immediately

› For 5MHz market the 'allowedmeasbandwidth' should be 25 and not 50.
› For 10MHz market the 'allowedmeasbandwidth' should be 50 and not 25.
vsDataEUtranFreqRelation (ERTT name )defined in the MO EUtranFreqRelation should

ideally have only one value as most of the markets have only have one LTE frequency been
used.
The MO is based on a per sector basis

Case 5 : Ret Offender: ILL01204_7A_1
E drops are also very high during Poor RET. Need to investigate at MME end.
Case 6. pZeroNominalPucch and pZeroNominalPusch
High UL RSSI on Cell.
pZeroNominalPucch and pZeroNominalPusch were increased
to mitigate impact of high RSSI on the sector:
New
AT&T Gold
Parameter Recommendatio
Standard
n
pZeroNominalPu
-117 -114
cch
pZeroNominalPu
-103 -96
sch
MO Class Name Parameter Name Parameter Description

EUtranCellFDD pZeroNominalPucch The nominal component of the UE transmit power for
Physical Uplink Control Channel (PUCCH).
EUtranCellFDD pZeroNominalPusch The nominal component of the UE transmit power for
Physical Uplink Shared Channel (PUSCH).

pZeroNominalPucch and pZeroNominalPusch
KPI for Cell CCL04145

Continue..
Adobe Acrobat
Document

Case 7 :IRAT Rate PRL00123_7A_1,PRL00253_7A_1
are worst cell having high IRAT rate IRAT Rate Reduces significantly after trail
at 15th Feb (outage issue at
neighbors)
02/14/2012: a2ThresholdRsrpPrim changed from -110 to -112 dbm
IRAT parameter trail Implemented at 8.00 am -14th Feb 2012

Case 8 :IRAT Rate Indy Border Cell Changes
1) Change of a2ThresholdRsrpPrim to -114 on 5th September

2) Change of a2ThresholdRsrpPrim to -116 & hysteresisA2Prim from 10 to 20 on 12th
September
IRAT & MO Signaling has improved if compared to Previous state (before 5 th September) after
the second set of changes on 12th September.
Case study: HO Success Rate

1.HO Preparation failures : Due to Disabled feature
Date EUtranCellFDD EUtranCellRelation pmHoPrepSuccLteIntraF pmHoPrepAttLteIntraF HOPrepFails
DXL00221
DXL20221 5/27/2011 DXL23040_2C DXL23040_2B 3 367 364
Date EUtranCellFDD EUtranCellRelation pmHoPrepSuccLteIntraF pmHoPrepAttLteIntraF HOPrepFails

DXL23162
DXL03162
5/27/2011 DXL23002_2A DXL23040_2B 5 168 163
DXL00567
DXL20567
DXL03040
DXL23040
DXL23002
DXL03002 Date UTC Hour EUtranCellFDD EUtranCellRelation pmHoPrepSuccLteIntraF pmHoPrepAttLteIntraF HOPrepFailures
5/27/2011 19:00 DXL23040_2C DXL23040_2B 1 365 364
› HO Prep failures occurred to DXL23040 as the

IntraLTEHandover feature had been disabled

2 .ILL04322_7H_1_D -> 310410-210286-15
There is only one way relation from

ILL04322_7H_1_D to ILL0286_7A_1
and all executions are failed . This is
not valid relation.
Need to set "isHOAllowed"=false

Between relation
ILL04322_7H_1_D -> 310410-
210286-15

3 .MAL02247_7B_1 Worst HO Success Rate
Worst EUTRAN relations Problem at Execution stage not in Preparation phase
pmHoExeAttL pmHoExeSuccL pmHoPrepAt pmHoPrepS

time object Source Cell Target Cell
teIntraF teIntraF tLteIntraF uccLteIntraF
2011W47 MAL02247_7B_1_310410-62261-17 MAL02247_7B_1 MAL02261_7C_1 3174 3067 3174 3174

2011W46 MAL02247_7B_1_310410-62261-17 MAL02247_7B_1 MAL02261_7C_1 2045 1960 2046 2045
2011W46 MAL02247_7B_1_310410-62226-15 MAL02247_7B_1 MAL02226_7A_1 25 20 25 25
2011W46 MAL02247_7B_1_310410-62224-16 MAL02247_7B_1 MAL02224_7B_1 4 0 4 4
Source Cell
Target Cell MAL02261_7C_1 is not declared on air
and has very High UL RSSI . Most of the HO drops
with this cell.
MAL02261 is not on air

3 .HO Preparation Failures: Disabled termpointtoMME
BEFORE
AFTER

4 .ILL01235_7C_1 -> 310410-210967-16
Target cell has poor cell Avail and also is

not a good candidate of Handover.
Need to set "isHOAllowed"=false Between
relation ILL01235_7C_1 ->ILL00967_7B_1
5 .HO Preparation Failures: Missing
termpointtoMME
HO Prep Failure -
Test Case

X2 HO Execution Failure Study
Oklahoma Market
Preamble
› We have recently came across several cases of HO Execution Failures in Oklahoma
Market. While the HO Preparation Failures were zero in those cells.
› Since the HO Preparation Success Rate was ok so it ruled out any issues related to
ipAddress on the Term Points.
› The point of troubleshooting was when the source and target eNB communicate without
any issues then why HO is not executed on X2 interface.
› MME was not considered in the troubleshooting because the HO Preparation is Ok if
there is some problem on S1 interface it will affect all the relations not just only few of
them and will have affect on accessibility KPI. But here it shows that particular handover
pairs are failing to execute HO on X2.

The X2 Handover (Different Stages)
UE Source eNB Target eNB MME Serving Gateway
0. Area Restriction Provided

1. Measurement Control
packet data packet data
UL allocation Legend
L3 signalling
2. Measurement Reports
L1/L2 signalling
3. HO decision
User Data
4. Handover Request
Handover Preparation
5. Admission Control
6. Handover Request Ack
DL allocation
RRC Conn. Reconf. incl.
7.
mobilityControlinformation
Detach from old cell
and
Deliver buffered and in transit
packets to target eNB
HO Execution Part
synchronize to new cell
Handover Execution
8. SN Status Transfer
Data Forwarding
Buffer packets from

Source eNB
9. Synchronisation
10. UL allocation + TA for UE
11. RRC Conn. Reconf. Complete
packet data
packet data
12. Path Switch Request
13. User Plane update
request
End Marker
14. Switch DL path
Handover Completion
packet data
End Marker
15.User Plane update
response
16.Path Switch Request Ack
17. UE Context Release
18. Release
Resources

The X2 HO Execution Part
X2 HO Execution Fails when UE doesn’t send RRC Connection Reconfiguration
Message to the target eNB.
There are two possible reasons for it:
1. Data forwarding fails: Might be X2 UP bandwidth issue, X2 UP link down.
2. Synchronization to target fails: Might be due to weak coverage, high UL RSSI on the
source / target sites.

Troubleshooting / Findings
› What we found: This execution failures were found high due to synchronization
failures during HO execution part.
› Why Not Data Forwarding:

– We found that when HO fails on particular X2, this phenomena is quite abrupt.
Sometimes HOs are high but they succeed while sometimes HOs are less but they
fail. So if it’s a bandwidth or link down issue we wont have success in case of high
attempts else had 100% failures.
› Why Its Synchronization Issue:

– Most of the X2 HO Pairs failing belong to the border sites or where target site is in the
third tier and > 5 miles apart. These sites have big coverage gaps in between due to
locked sectors or no LTE sites nearby.
– Remaining of the X2 HO Pairs failing belong to the core area where there is high UL
RSSI on either source or target sites. We have seen that when the RSSI goes high
the X2 HO Exec failures increase decrease sharply.
› Next slides will show both cases in detail.

Troubleshooting / Interference Issues
Interference Related
Execution Failures
Cells With High X2 HO Exec
Failures Due to Interference
The first category of X2 HO Execution Failures

belong to the synchronization issues due to high UL
RSSI in the sites. The failures were high on the day
when the RSSI was high. It also shows that the target
was very far when the HO was attempted therefore
these cases are more sensitive to RSSI increase
since they already have a weak link balance.
Troubleshooting / Coverage Issues
IRAT Attempts are High in the

Cells with Weak Coverage
Cells With High X2 HO Exec

Failures Due to Coverage
The second category of X2 HO Execution Failures belong to

the synchronization issues due to weak coverage areas. The
failures are always high in the areas where either few sectors
are locked due to other operator frequency issues OR the
sectors are at border AND again they are trying to make a
HO with the target very far. Since they already have a weak
link balance therefore its hard to maintain synchronization
EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 53 during HO execution.
Geographical Location of Exec Failures
Solid Lines: Interference Related Failures
Dotted Lines: Coverage Related Failures
More Severe Cases: Red, Orange, Yellow
HO Execution Failures
Due to Interference Issues
HO Execution Failures
Due to Coverage Issues

Conclusion
› The X2 HO Execution Failures seem to occur because of either X2 (user plane) link
issues or UE Synchronization failures to the target cell during HO.
› We have found UE Synchronization issues as a dominant reason of X2 HO Execution
Failures in OKC market. This is mostly due to bad coverage & UL RSSI issues.
› What We Are Doing To Fix:
– Resolve UL RSSI Issues in the sites

– Reduce overshooting through tilt optimization
– Audit the power parameters in order to make sure that no sector is set to lower power
than its actual value.
– Reduce outages so that far neighbors don’t get added through ANR automatically
when the first tier site is down.
– Black list those relations which have less counts and always show failures due to
coverage issues so that ANR don’t add them again and again.
– Check X2 UP link utilization if it’s a bottleneck.
– Detect UP link failure issues through trace route.

Questions and Answer


LTE Parameter - Knowledge Sharing

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LTE Parameter - Knowledge Sharing

Caricato da

Copyright:

Formati disponibili

LTE Parameters

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 2

EUtranCellFDD systemInformationBlock3.sIntraSearch 62 62 0..62 dB

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 3

AT&T Gold Vendor

UeMeasControl sMeasure 0 0 -140..-44,0 dBm

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 4

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 5

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 6

AT&T Gold Vendor

ReportConfigEUtraBestCellAnr a3offsetAnrDelta 3 1 -10..10 1 dBm

ReportConfigEUtraBestCellAnr hysteresisA3 10 0..150 0.1 dB

RAN Managed Object Parameter Value Comment

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 8

SServingCell ≤ Snonintrasearch (6,10)

Snonintrasearch = Threshold for inter-frequency and inter-RAT measurements on frequencies of equal or

SServingCell = QRxLevMeas - (QRxLevMin + QRxLevMinOffset) – Pcompensation

Qrxlevmeas = Measured RSRP value in the cell (dBm)

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 10

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 11

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 12

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 13

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 14

Set as -120 dbm

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 15

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 16

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 17

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 18

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 19

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 20

The LTE parameters EUtranFreqRelation.connectedModeMobilityPrio (5) and

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 21

badCoverageMeasSelection : Specifies whether primary, secondary, both primary and secondary,

Takes effects: New connection.

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 22

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 23

ReportConfigEUtraBadCovSec a2ThresholdRsrqSec -195..-50 -195 -195 -195..-30 0.1 dB

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 25

Cell trace was activated on suspect sites

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 27

› With regards to hanging resources in eNb – a restart normally helps.

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 29

– CCL00703 Gamma sector has a high number of ERAB failures.

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 30

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 31

Attribute Recommended Value Recommended Value Comment

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 32

Takes effects: Immediately

vsDataEUtranFreqRelation (ERTT name )defined in the MO EUtranFreqRelation should

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 33

MO Class Name Parameter Name Parameter Description

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 35

KPI for Cell CCL04145

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 36

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 37

IRAT parameter trail Implemented at 8.00 am -14th Feb 2012

1) Change of a2ThresholdRsrpPrim to -114 on 5th September

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 40

Date EUtranCellFDD EUtranCellRelation pmHoPrepSuccLteIntraF pmHoPrepAttLteIntraF HOPrepFails

› HO Prep failures occurred to DXL23040 as the

EANRPRD / Ankur prasad | Ericsson Internal | 2012-28-03 | Page 41

There is only one way relation from