You are on page 1of 15

LTE INTER-FREQUENCY

HANDOVER Trouble shooting


case study-Missing
measurement gaps

LTE L12A
Shawn zhang
Mar 1, 2012
Issue

Measurement Based Inter-frequency handover in sprint LTE


network is failing due to no A5 event received from UE. (Blind
inter-frequency handover works)
Inter-Freq Handover OVERVIEW

Handover between two cells with different center frequency (earfcn).


Two events are triggered:
A2 Event: Serving becomes worse than threshold
A5 Event: serving becomes worse than threshold1 and neighbor becomes
better than threshold2
Two Inter-Frequency Handover preparation methods:
blind inter-frequency handover: . eNodeB configures event A2 based on UE
report. after A2 measurement report from UE, RBS identifies coverage of
selected cell, and start a Blind IFHO handover process, if prerequisites are
followed.
measurement based inter-frequency handover: If no cell available for blind
handover, A5 measurement will be assigned on the UE, UE starts
measurements on reported cells and triggers A5 event. Once UE triggers the
event, RBS will start IFHO if prerequisites are followed.
Inter-Freq Handover OVERVIEW
S-GW S-GW MME MME
Source
Source eNB
eNB Target
Target eNB
eNB Source Target Source Target
RRC 1. RRC CONNECTION RECONFIGURATION
CONNECTED (Bearer Setup,Measurement conf))

2. RRC Measurement Report


(Event A5)
3. HO
S1 Handover

Decision

4. S1 HANDOVER REQIRED
(Source to Target Transparent Container ) 5. S10 FORWARD RELOCATION
TS1RELOCprep REQUEST
6. S11 CREATE BEARER REQ/RES
7. S1 HANDOVER REQUEST

8. Admission
Control
9. S1 HANDOVER REQUEST ACKNOWLEDGE
10. S10 FORWARD RELOCATION
RESPONSE
11. S11 CREATE BEARER REQ/RES
UP Forwarding
12. S1 HANDOVER COMMAND
T304 12. RRC CONNECTION RECONFIGURATION
(Handover Command,Measurement conf)
13 MAC: CFRA Random Access Preamble
Regenerate 14. MAC Random Access Response (UL allocation + TA)
Security Keys
15. RRC CONNECTION RECONFIGURATION COMPLETE
(Handover Confirm) 16. S1 HANDOVER NOTIFY

17.Data Transfer in Target

18.S10 FORWARD RELOCATION


RRC COMPLETE/ ACK
CONNECTED 19. S1 UE CONTEXT RELEASE COMMAND
(Cause: Successful Handover)
REQUIREMENTS
1. General requirement:
licenseStateInterFrequencyLTEHandover is Enabled.
featureStateInterFrequencyLTEHandover is Active.
EUtranFreqRelation and EUtranCellRelation should be created
the UE capability supports inter-frequency handover. This is indicated in bit 13 of the featureGroupIndicators which is part of
the Information Element UE-EUTRA-Capability as described in TS 36.331

2. For Blind Handover:


covTriggerdBlindHoAllowed set to true on Serving cell
mobilityAction on EUtranFreqRelation MO must be HANDOVER
coverageIndicator on EUtranCellRelation MO should be set to 1 ( Cover)
isHoAllowed on EUtranCellRelation MO should be set to 1

3. For Measurement Based Handover:


ueMeasurementActive set to true.
mobilityAction on EUtranFreqRelation MO must be HANDOVER
isHoAllowed on EUtranCellRelation MO should be set to 1
OTHER PARAMETERS

The following parameters allows to fine tune the behavior of the UE to trigger the HO events.
triggerQuantityA2Prim/ triggerQuantityA2Sec attributes on ReportConfigEUtraBadCovPrim
MO: The quantity that triggers the eventA2 for the primary/secondary eventA2
measurement. Primary and secondary measurement parameters refer to the option to use
different settings for two simultaneous measurements for eventA2. set to 0 for RSRP and 1
for RSRQ
triggerQuantityA5 on ReportConfigA5 MO: The quantity that triggers the eventA5 for the
eventA5 measurement. set to 0 for RSRP and 1 for RSRQ
a2ThresholdRsrpPrim
a5ThresholdXRsrp: where X can be 1 or 2
a2ThresholdRsrqSec
a2ThresholdRsrqPrim
a5ThresholdXRsrq: where X can be 1 or 2
Trouble shooting-ENB TRACE SIGNAL FLOW
measObjectToAddModList {
UE eNB TeNB MME
|====>| | | (RRC) rrcConnectionRequest eCause:mo-Signalling measObjectId 1,
:|:::: :|: ::::|: ::: ::| ::::::
|<====| | | UE:388 (RRC) ueCapabilityEnquiry measObject
|====>| | | UE:388 (RRC) ueCapabilityInformation measObjectEUTRA : {
|========== ====>| UE:388 (NAS) AttachComplete carrierFreq 8665,
| |=========>| UE:388 (S1AP) UECapabilityInfoIndication
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration ...........
|<==============| UE:388 (NAS) AttachAccept:ParsingFailure (ciphered) reportConfigToAddModList {
|====>| | UE:388 (RRC) rrcConnectionReconfigurationComplete
:|:::: :|: ::::|::: :::| :::::: reportConfigId 2,
|==============>| UE:388 (NAS) AttachComplete
:|:::: :|: ::::|::: :::| :::::: reportConfig reportConfigEUTRA :
{
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 triggerType event : {
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration
eventId eventA2 : {a2-Threshold
|====>| | | UE:388 (RRC) rrcConnectionReconfigurationComplete
threshold-RSRP:30},
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113
hysteresis 2,
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 timeToTrigger ms640},
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114 triggerQuantity rsrp,
:|:: :::|:::: :| ::::| ::::::
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-121 reportQuantity both,

maxReportCells 4,
eNB sends A2 config. info correctly to UE, UE triggers A2 event at condition meet-> No
problem at this point reportInterval ms480,
Trouble shooting-ENB TRACE SIGNAL FLOW

UE eNB TeNB MME measObjectToAddModList {


|====>| | | (RRC) rrcConnectionRequest eCause:mo-Signalling {
:|:::: :|: ::::|: ::: ::| :::::: measObjectId 2,
measObject measObjectEUTRA : {
|<====| | | UE:388 (RRC) ueCapabilityEnquiry
|====>| | | UE:388 (RRC) ueCapabilityInformation carrierFreq 8040,
|========== ====>| UE:388 (NAS) AttachComplete
{ Inter_freq
| |=========>| UE:388 (S1AP) UECapabilityInfoIndication
measObjectId 3,
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration measObject measObjectEUTRA : {
|<==============| UE:388 (NAS) AttachAccept:ParsingFailure (ciphered)
|====>| | UE:388 (RRC) rrcConnectionReconfigurationComplete carrierFreq 8340,
{
:|:::: :|: ::::|::: :::| :::::: reportConfigId 7, A5 condition:
|==============>| UE:388 (NAS) AttachComplete reportConfig reportConfigEUTRA : {
Serv
:|:::: :|: ::::|::: :::| :::::: triggerType event : {
RSRP<-120
eventId eventA5 : {
a5-Threshold1 threshold-RSRP : 20, Nerb RSRP
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 a5-Threshold2 threshold-RSRP : 4 >-136
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration },
|====>| | | UE:388 (RRC) rrcConnectionReconfigurationComplete hysteresis 2,
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 timeToTrigger ms640
},
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 triggerQuantity rsrp,
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 }
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114
measIdToAddModList {
:|:: :::|:::: :| ::::| :::::: {
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-121 measId 7,
measObjectId 3,

eNB seems correctly send A5 config info to UE after eventreportConfigId


A2, UE doesnt7 trigger A5 at
condition meet -> UEs problem ???
Comparing with other good enb trace

Good HO Failed HO
measIdToAddModList { measIdToAddModList {
{
measId 5, {
measObjectId 1, measId 5,
reportConfigId 5 measObjectId 1,
}, reportConfigId 5
{ },
measId 6, {
measObjectId 1, measId 6,
reportConfigId 6 measObjectId 2,
}, reportConfigId 6
{ },
measId 7, {
measObjectId 2, measId 7,
reportConfigId 7 Comapring measObjectId 3,
}, rrcConnectionReconfiguration reportConfigId 7
{ },
measId 8,
after event A2, {
measObjectId 3, measId 8,
reportConfigId 8
NO measGapConfig on measObjectId 4,
} customers site eNB tracing reportConfigId 8
}, },
measGapConfig setup : { {
gapOffset gp0 : 26
What is measurement GaPS and how to let enb
send it?
3GPP 36.331

Measurement gaps: Periods that the UE may use to perform measurements, i.e. no (UL, DL)
transmissions are scheduled.

Value gapOffset of gp0 corresponds to gap offset of Gap Pattern Id 0 with MGRP = 40ms,
gapOffset of gp1 corresponds to gap offset of Gap Pattern Id 1 with MGRP = 80ms. Also used to
specify the measurement gap pattern to be applied, as defined in TS 36.133 [16].

3GPP 36.300

-Intra-frequency neighbour (cell) measurements: The UE shall be able to carry out such
measurements without measurement gaps.

-Inter-frequency neighbour (cell) measurements: compared to the current cell. The UE should not be
assumed to be able to carry out such measurements without measurement gaps.

Whether a measurement is non gap assisted or gap assisted depends on the UE's capability and
current operating frequency. The UE determines whether a particular cell measurement needs to be
performed in a transmission/reception gap and the scheduler needs to know whether gaps are
needed:

Conclusion: There is no parameter in eNB to set if measurement gap sends or not, eNB makes
decision based on UEs capability information ( eNB can change UE measurement gaps either 40ms
or 80 ms by systemconstant).
Measurement GaP
Does UE capability require measurement Gaps?

UE eNB TeNB MME measParameters {


|====>| | | (RRC) rrcConnectionRequest eCause:mo-Signalling
:|:::: :|: ::::|: ::: ::| :::::: bandListEUTRA {
|<====| | | UE:388 (RRC) ueCapabilityEnquiry
|====>| | | UE:388 (RRC) ueCapabilityInformation {
|========== ====>| UE:388 (NAS) AttachComplete interFreqBandList {
| |=========>| UE:388 (S1AP) UECapabilityInfoIndication
{
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration
interFreqNeedForGaps TRUE
|<==============| UE:388 (NAS) AttachAccept:ParsingFailure (ciphered)
|====>| | UE:388 (RRC) rrcConnectionReconfigurationComplete
}
:|:::: :|: ::::|::: :::| :::::: },
|==============>| UE:388 (NAS) AttachComplete interRAT-BandList {
:|:::: :|: ::::|::: :::| ::::::
{
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 interRAT-NeedForGaps FALSE
|<====| | | UE:388 (RRC) rrcConnectionReconfiguration
|====>| | | UE:388 (RRC) rrcConnectionReconfigurationComplete },
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 {
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-113 ,
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114 Bit13&25:UE
featureGroupIndicators '01100110
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-114 support
00001101 11011000 Inter-
10011000'B
:|:: :::|:::: :| ::::| :::::: frequency
|====>| | | UE:388 (RRC) measurementReport measId:2 rsrp:-121 handover

UE does require measurement Gaps, so it seems eNB who should be blamed!


Further analysis and fix
Further more, we found below error from te log read
000100/LmCellPT6 UehMeasDataCapabilityHandlerD.cpp:273 ERROR:!<0xa92>! No valid
sourceBand or targetBand found in the supportedBandListEUTRA IE

The mobile phone we were testing was working in Band 25. Band 25 is only used in sprint network.
We suspect eNB doesnt interpret band 25 information correctly at handling assembling
measurement gap IE. TR HP26018 was raised at this point. Designer quickly confirmed our analysis
and fix was delivered in L12A CP1 in TR answer:

CAUSE OF FAULT
-------------------------------
UehMeasDataCapabilityHandlerD contains a list to be able to map frequencies against frequency-bands. This list was
not updated when CR1134 was implemented. Therefore only parts of the system handled the new frequency-bands
defined in later 3GPP specifications. The result of the fault is that the eNodeB can not determine the capability of the
UE on this frequency-band. So the result is that meas-gap is not activated, because we do not know if the UE
supports meas-gap.

SYSTEM IMPACT
------------------------
Inter-frequency measurements is not started. So measurement based handovers is not triggered.

SOLUTION
-----------------
The list in UehMeasDataCapabilityHandlerD to map frequency against frequency-bands is updated.