12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

LTE KNOWLEDGE Searchthissite...

4GLTE

CATEGORIES

LTE FDD Network Planning & Optimization System-LTE

system TAU reject issue analysis
Budi Prasetyo CS NPO 18:08

OneFDDLTEnetwork,theresomeTAUrejectduringuseAppleUEtestCSFBfunctioninsome
eNodeB,needtocheckthefailureandsolved.TheAppleUEtestlogasfollowing:
-> UE releases the call in UMTS
-> moves to LTE
-> Sends TAU
-> Gets TAU Accept
-> The Next TAU is rejected with cause 10
AndanotherTAUrejectlogasfollowing:
1> Service Reject for Extended Service REQ from UE for CSFB call
PCI 408 & PCI 317
[00] 0xB0EC LTE NAS EMM Plain OTA Incoming Message -- Service reject Msg
pkt_version = 1 (0x1)
rel_number = 9 (0x9)
rel_version_major = 5 (0x5)
rel_version_minor = 0 (0x0)
security_header_or_skip_ind = 0 (0x0)
prot_disc = 7 (0x7) (EPS mobility management messages)
msg_type = 78 (0x4e) (Service reject)
lte_emm_msg
emm_service_rej
emm_cause
cause_value = 10 (0xa) (Implicitly detached)
T3442_incl = 0 (0x0)
t3346_incl = 0 (0x0)
2> PCI 406 : device sent ESR went to UE and got RAU REJ 10
GMM_ROUTING_AREA_UPDATE_REJECT
gmm_cause
http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 1/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

gmm_cause_val = 10 (0xa) (Implicitly detached)

force_stby
force_standby_value = 0 (0x0)
t3302_value_incl = 0 (0x0)
t3346_value_incl = 0 (0x0)
3> [58] 0x713A UMTS UE OTA
Message Direction = To UE
NAS OTA Message Contents:
chan_type = 0 (0x0)
prot_disc_check = 8 (0x8)
trans_id_or_skip_ind = 0 (0x0)
prot_disc = 8 (0x8) (GSM_GMM_MESSAGES)
msg_type = 11 (0xb)
prot
gprs_mob_man_prot
GMM_ROUTING_AREA_UPDATE_REJECT
gmm_cause
gmm_cause_val = 9 (0x9) (MS identity cannot be derived by the network)
force_stby
force_standby_value = 0 (0x0)
t3302_value_incl = 0 (0x0)
t3346_value_incl = 0 (0x0

AnalysistheUElog,wefindUEreleasesthecallinUMTSisnormal,reelectiontoLTE,after
handoveriscompleted,sendtheTAUrequest,therewasaTAUrejectwhenreceiveandcomplete,
Its3GCSfallbackto4G,theissuereasoncause#10.
FirstweneedkonwUEintheendaftertheCSfallbacktoLTE,thenTAUupdateprocedure,as
following:

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 2/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

Setp20signal
explain:
TheMMEsendsaTAUAccept(GUTI,TAIlist,EPSbearerstatus,NASsequencenumber,NAS
MAC,IMSVoiceoverPSsessionsupportedIndication)messagetotheUE.Iftheactiveflagisset
theMMEmayprovidetheeNodeBwithHandoverRestrictionList.GUTIisincludediftheMME
allocatesanewGUTI.Ifthe"activeflag"issetintheTAURequestmessagetheuserplanesetup
procedurecanbeactivatedinconjunctionwiththeTAUAcceptmessage.
Setp21signalexplain:
IfGUTIwasincludedintheTAUAccept,theUEacknowledgesthereceivedmessagebyreturning
aTAUCompletemessagetotheMME.Whenthe"Activeflag"isnotsetintheTAURequest
messageandtheTrackingAreaUpdatewasnotinitiatedinECMCONNECTEDstate,thenew
MMEreleasesthesignallingconnectionwithUE.
AccordingtheaboveTAUupdatesignaling,UEcallendandmovetoLTEnetwork,thenormal
TAUupdateprocessshouldbelikethis:UEsendTAURequesttoSGSN,SGSNfeedbackTAU
Accept,afterUEsendNASsignalingTAUComplete,itsmeaningtheTAUprocedureisfinish.But
checktheAppleUEtestlog,whileTheSGSNfeedbackTAUAccept,doesnotcontainGUTI
information,leadtonocompletemessagefromUE,shownasTheNextTAUisrejectedwith
cause10.
TAUnormalorabnormalprocedureasfollow:

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 3/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

ChecktheTAUrejectedreason,thereasonfromEMM,rejectedNASmessagetoEMM.

Checkthecause10from3GPP.24301by5.5.3.2.5,thereasonexplainasfollow:
Ifthetrackingareaupdatingcannotbeacceptedbythenetwork,theMMEsendsaTRACKING
AREAUPDATEREJECTmessagetotheUEincludinganappropriateEMMcausevalue.
IftheMMElocallydeactivatesEPSbearercontextsfortheUE(seesubclause5.5.3.2.4)andnoactive
EPSbearercontextsremainfortheUE,theMMEshallsendtheTRACKINGAREAUPDATEREJECT
messageincludingtheEMMcausevalue#10"Implicitlydetached".

AfterTAUrejectedtheUEaction:
#10 (Implicitly detached);

The UE shall delete the list of equivalent PLMNs and shall enter the state EMM-DEREGISTERED.NORMAL-SERVICE. If the

rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall delete any mapped

EPS security context or partial native EPS security context and perform a new attach procedure.

User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

IfA/GbmodeorIumodeissupportedbytheUE,theUEshallhandletheGMMstateasspecifiedin3GPPTS24.008[13]for
thecasewhenthenormalroutingareaupdatingprocedureisrejectedwiththeGMMcausewiththesamevalue.

Accordingtotheaboveexplaination,therejectedcausebyMMEfrom3G,needcheckMMEset.
Becausethe3Gand4GsMME,EPCequipmentfromanothercompany,soneedthecustomto
pushtheissuesolvedandtest.
IftherejectedfromBS,themainreasonasfollow:
1.RRCestablishmentfailure
2.CNrejected
3.eNBcannotgetInitialcontextsetuprequestmessageandtimeout
4.RRCReconfigurationlostorUEconfigurerrorsecurityparameterornotconnecttheNGBR

bear.

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 4/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

5.eNBsetupbearingfailure
6.eNBsetupthedefaultbearingfailure

AnotherAppleUEtestloganalysisandexplainasfollow:
1UEtestCSFBfunction,UEsendExtendedServiceREQ,butrejectedfromUMTS,thecause
reasoniscause_value=10(0xa)(Implicitlydetached),need3Gengineertosolved
2Cause#10,samewithaboveexplaination
3Cause#9,causefromGMM,need3Gengineertocheckexplainasfollow:
#9(UE identity cannot be derived by the network);

The UE shall set the EPS update status to EU2 NOT UPDATED (and shall store it according to subclause 5.1.3.3) and shall

delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall enter the state EMM-DEREGISTERED.

If the rejected request was not for initiating a PDN connection for emergency bearer services, the UE shall subsequently,

automatically initiate the attach procedure.

NOTE 5: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer(s) automatically.

If A/Gb mode or Iu mode is supported by the UE, the UE shall handle the GMM parameters GMM state, GPRS update

status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specied in 3GPP TS 24.008 [13] for

the case when the service request procedure is rejected with the GMM cause with the same value.

A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation which is already IMSI attached for non-EPS services is still

IMSI attached for non-EPS services.

A UE operating in CS/PS mode 1 or CS/PS mode 2 of operation shall set the update status to U2 NOT UPDATED.

Accordthecause#9wekonw MSidentitycannotbederivedbythenetworkisusuallydue
tofailureinhostresolutionwhenhandingfromSGSN/MME

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 5/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

TAUrejectedfromEMM,themainreasonasfollow:

AppleUEtestCSFBfunction,wefoundsomeproblemlikeashandoverfailure,attachand
detachedactionabnormalorTAUrejected,needknowtheCSFBprocedureisgoodforusto
analysisandsolved.

Knowledgesupplement
1.cause10ImplicitlydetachedSGSNdonotsendanymessagetoUE,thenUEdetached
2.GUTI,TMSImeanTINtempidentityusedinnextupdate,TheUEindicatesalsoinformation
elements"additionalGUTI"or"additionalPTMSI"intheAttachRequest,TAUorRAURequest.
TheseinformationelementspermittheMME/SGSNtofindthealreadyexistingUEcontextsin
thenewMMEorSGSN,whenthe"oldGUTI"or"oldPTMSI"indicatevaluesthataremapped
fromotheridentities

CS NPO

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 6/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

Related Articles

LTE FDD Network Network Planning & TDD-LTE-How to TE FDD Network

Planning & Optimization System- turn RIM (RAN Planning &
Optimization System- the missed neighbour information manager) Optimization System-
Detach Failure Due to check method based function carrier coverage issue
a Wrong TAC o... caused by h...

About Budi Prasetyo

All About LTE

SubscribetothisBlogviaEmail: Subscribe

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 7/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

Newer Post Older Post

Popular Posts

LTE Central Frequency And EARFCN

The Difference Between RSRP ( LTE) And RSCP (

UMTS)

RRC/RAB Establishment Failure

TDD-LTE-How To Turn RIM (RAN Information

Manager) Function

LTE FDD Network Planning & Optimization

System-LTE System TAU Reject Issue Analysis

Voice Over LTE

LTE Handover

Cell Radius Limited By Prach Parameters Issue

Analysis

LTE Capacity (1)

Blog Archive

2017 (4)

2016 (16)

September (3)

August (8)

April (1)

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 8/9
12/02/2017 LTEFDDNetworkPlanning&OptimizationSystemLTEsystemTAUrejectissueanalysisLTEKnowledge

February (3)

LTE FDD Network Planning &

Optimization System-LTE...

FDD-OMC-SON ANR Conguration

Introduction

LTE FDD Network Planning &

Optimization System-Det...

January (1)

2015 (111)

Powered by Blogger.

Labels More links

CORE

CS CAPACITY

CS CORE

CS DEVICE

CS NPO

Device

LTE

LTE Feature

LTEsimple

Overview

Performance

Planning

Protocol

Video

Follow by Email

Emailaddress... OK

http://www.ltehandbooks.com/2016/02/ltefddnetworkplanningoptimization_14.html 9/9