目录TOC\o"1-5"\h\z1概述22ESRVCC切换成功率指标介绍2HYPERLINK\l"bookmark4"\o"CurrentDocument"2.1ESRVCC指标统计信令节点3HYPERLINK\l"bookmark8"\o"CurrentDocument"2.2ESRVCC失败原因分析4HYPERLINK\l"bookmark10"\o"CurrentDocument"2.2.1LTE到GSM的切换出准备失败次数，目标侧准备失败4HYPERLINK\l"bookmark14"\o"CurrentDocument"2.2.2LTE到GSM的切换出准备失败次数，等待切换响应定时器超时6HYPERLINK\l"bookmark16"\o"CurrentDocument"2.2.3LTE到GSM的切换出准备失败次数，其它原因72.2.4LTE到GSM的切换出执行失败次数，源侧发生重建立8HYPERLINK\l"bookmark46"\o"CurrentDocument"2.2.5等待UECONTEXTRELEASE消息超时11HYPERLINK\l"bookmark60"\o"CurrentDocument"2.2.6LTE到GSM的切换出执行失败次数，其他原因11SRVCC(SingleRadioVoiceCallContinuity)是3GPP提出的一种VoLTE语音业务连续概述性方案，主要是为了解决当单射频UE在LTE/Pre-LTE网络和2GCS网络之间移动时，如何保证语音呼叫连续性的问题，即保证单射频UE在IMS控制的VoIP语音和CS域语音之间的平滑切换。LTE网络建设初期，其覆盖范围有限，当用户在使用LTE网络进行语音通话过程中，移动到LTE信号较弱，但GERAN网络信号覆盖较好的区域时，为了保证语音呼叫连续性(VoiceCallContinuity，VCC)，需要将话路由LTE切换到GERAN。由于目前还没有能够在LTE和GERAN同时附着并收发数据的终端，因此LTE和2G之前的业务连续性都基于SingleRadio模式，即双模单待方式。目前3GPP已经制定出双模单待方式的语音业务连续性方案，即3G
ppt
关于艾滋病ppt课件精益管理ppt下载地图下载ppt可编辑假如ppt教学课件下载triz基础知识ppt
S23.216R9中提出的双模单待无线语音呼叫连续性(SingleRadioVoiceCallContinuity，SRVCC)方案。1eSRVCC切换成功率指标介绍eSRVCC切换成功率=切换至2G的切换成功次数(C373333312)/切换至2G的切换请求次数(C373333330)。其中：切换至2G的切换成功次数：源eNB接收到MME发送的“UE上下文释放”消息(UECONTEXTRELEASECOMMAND)，指示系统间(EUTRAN->GERAN)分组域切换执行成功。(3GPPTS36.413)切换至2G的切换请求次数：源eNB向MME发送的切换请求”消息(HANDOVERREQUIRED),HandoverTypeIE(LTEtoGERAN)指示系统间(EUTRAN->GERAN)分组域切换请求。(3GPPTS36.413)1.1eSRVCC指标统计信令节点NMERR（^Cvnffw^dpniRc«94：j
'k贱时卑样『•h梯TMod出壮S^iMEv遇的HiBdtfEt梢息BJ驭样Jit.41tn^NndtBUWMUE駅迟的Hittalnnm（:障*丿」T「、：，，」iHl1kk>vfTb^klfTihjj.I1-.瑕惮直6tENdtkB^IMME.j^iJCMobikcyliuinLLI'riLA<：E>niBuiiJ.1*）[J：iiJKHLA?i離*N^ieHti.切*执布曲段戰剧U£址ilffJRKCCwiukimh血nntK^urt.fiiFJu"HrHiffilr'H.taLimiMMIAjL“八息摺平卫申'.-失败原因对应计数器失败原因描述统计节点LTE至UGSM的切换出准备失败次数，等待切换响应定时器超时C373333309源eNodeB等HandoverCommand消息定时器超时采样点4LTE至UGSM的切换出准备失败次数，目标侧准备失败C373333310源eNodeB接收到从MME来的HandoverPreparationfailures消息采样点5LTE至UGSM的切换出准备失败次数，其它原因C373333311源eNodeB在切换准备阶段发生除上述2种原因外其它失败采样点3LTE至UGSM的切换出执行失败次数，源侧发生重建立C373333313在切换执行阶段源eNodeB收到RRC连接重建立请求消息采样点7LTE至UGSM的切换出执行失败次数，等待UECONTEXTRELEASE消息超时C373333314源eNodeB等待MME的UeContextRelease消息定时器超采样点8LTE至UGSM的切换出执行失败次数，其他原因C373333315源eNodeB在切换执行阶段发生除上述原因外其它失败采样点91.2eSRVCC失败原因分析HandovereSRVCC切换分为切换准备阶段和切换执行阶段：切换准备阶段发生在Required-->HandoverCommand，切换执行阶段发生在MobilityFromEUTRACommand-->UeContextRealeaseCommand。切换准备阶段为eNodeB-->MME-->eMSC-->GSM基站之间的信令交互，和空口覆盖无关；切换执行阶段从采样节点来看匚只有MobilityFromEUTRACommand和LTE空口覆盖相关，当LTE下行覆盖较差(弱RSRP或弱RSRQ)时会增加UE接收MobilityFromEUTRACommand失败的概率从而造成eSRVCC失败，该原因造成的失败会统计到源eNodeB等待MME的UeContextRelease消息定时器超，其它的失败原因值和LTE覆盖、上行干扰、基站故障关系不大。LTE到GSM的切换出准备失败次数，目标侧准备失败sourceeNBMMEHANDOVERREQUIREDHANDOVERPREPARATIONFAILURE-*】IftheEPCorthetar^tiysterniinotabletoacceptanyoftHebeareriora.failuiecccuisduringtheHandoverPreparation,theMMEsend^thePRLEPAKAUONFAILUREanappropriatecausevaluetpth?SOUIEE(XE才IftheCSGJifIEandnoCsJ!AmG&sModeIEarereceivedintheHANDOVER.REQUIILEDmessageandtheaccesscontrolisunsuccessfulandnoneoftheE-RABsha&aparticularARPvalue(seeTSJj.401[11])theMME如UlendtheHANDO\~ERPE.EPARATIONFAILUREmessageanappropriatecauseahierothesourceeNBfexcept^tienoneoftheE^RABihasaparticularAE.Pvalue(seeT523.401[lipUponreception.th.esourceeMBmaydecidetopresenthandoiexfor(hitU£towardsCSG(ClosedAccessMode)cellswithconespendingCSGId.<-TS36.413协议规定如果EPC或是目标侧不接受任何一个承载或是在切换准备阶段发生错误，MME会回复"handoverPreparationfailure”消息，eNode收至Uhandoverpreparationfailure消息后会统计到“目标侧准备失败”中。造成目标侧准备失败的主要原因包括：LTE侧GSM外部邻区参数配置、EPC参数配置错误、eMSC侧参数配置、GSM侧基站接纳失败、其它原因。1.2.1.1GSM外部邻区参数核查GSM外部邻区核查主要是和核查GSMCGI相关参数，在handoverrequire中主要依靠CGI参数来进行目标侧寻址，如果CGI参数配置错误会导致核心网/GSM侧认为发生错误从而导致切换准备失败。CGI(CellGlobalIndentfier)全球小区识别=MCC+MNC+LAC+CI需要重点核查：1、核查“管理网元->无线参数->TD-LTE->邻接小区配置->GERAN邻接小区”中“邻接小区所在的移动国家码”、“邻接小区所在的移动网络码”参数配置是否正确2、核查“管理网元->无线参数->TD-LTE->邻接小区配置->GERAN邻接小区”中的“位置区码”和”小区标识”的对应关系和GSM工参一致。■Item4;id-I^rgetTD■ProtocolIE*Fieldid:id-TargetID(4)criticality:(G)/value丄TargetID:cGI(2)*cGIpLMNidentity;64代00MobileCountryCode(MCC):China(460)MobileNetworkCode(MNC):匚himMobile(00)LAC：9377cl:08621.2.1.2eMSC侧参数核查eMSC侧相关参数配置如下：1、eMSC检查eSRVCC相关控制开关和参数配置2、eMSC检查LAI和VMSC切换数据配置121.3EPC侧参数核查待补充。。。1.2.1.4GSM侧参数核查待补充。。。121.5其它原因排查
流程
快递问题件怎么处理流程河南自建厂房流程下载关于规范招聘需求审批流程制作流程表下载邮件下载流程设计
門隔网愕阿岡岡隔|严卜“匕¥3刊11审nnrfc二能加XIfffM0|<.Spiitting5b.Freph+D5c^tlocHOR*q6s.For^'ordRtlccReq7b.FtrwardRetacResp♦•:二Eke-卡&:；RgtocHOJ^acAdtfiaReIdcHOReqAoJb.fttpHOR«T>■*9.kiilgtknTrarsfef[ST^-S只orE-5TN-SR}12.PSbCS切换准备涉及到LTE、核心网、GSM，在排查参数配置问题后可能需要核心网或GSM共同进行排查。TS23.216622规定了eSRVCC相关的信令流程，我们在做问题排查时依据相关的信令节点做问题定位排查，排查步骤如下：1、MME收到HandoverRequired后是否给eMSC发送了PStoCSReq，如果MME直接回复了HandoverPreparationFailure，可能由于核心网参数配置或是核心网处理异常导致切换失败导致，需要核心网协助进行排查2、如果eMSC收到PStoCSReq之后回复的HandoverPreparationFailure，则需要GSM协助进行排查LTE到GSM的切换出准备失败次数，等待切换响应定时器超时“管理网元-＞无线参数-＞TD-LTE-＞控制面定时器TDD”中“S1HO时等待HOCOMMAND的定时器（毫秒）”设置为10000ms（10s），在源侧发送HandoverRequired后再10s内未收到HandoverCommand命令造成eSRVCC切换失败。造成定时器超时的原因主要有：核心网/GSM侧参数配置错误导致核心网寻址错误；传输问题导致核心网/GSM侧未收到sRVCC相关信令；GSM基站故障未响应sRVCC切换命令。1.2.2.1参数核查1、LTE侧“管理网元-＞无线参数-＞TD-LTE-＞控制面定时器TDD-＞S1HO时等待HOCOMMAND的定时器（毫秒）”参数核查：确定参数配置为10000ms2、eMSC侧核查：VMSC检查和eMSC之间切换数据、VMSC检查LAI&CI和BSC关联数据配置1.2.2.2其它原因排查流程1、MME是否收到HandoverRequied消息：如果MME未收到HandoverRequired消息,核查eNodeB<-->MME之间的传输可靠性。核查方法：使用—ems的“IP通道测试功能”检查eNodeB<-->MME通道是否丢包，如果存在丢包的情况协调传输解决传输问题2、MME收到HandoverRequied后是否向eMSC进行了PstoCsReq消息转发，如果MME未进行消息转发，协调MME共同进行排查3、eMSC是否收到PstoCsreq消息，如果未收到核查MME<-->eMSC之间的传输4、eMSC收到PstoCsreq后是否回复了PstoCsRsp，如果未回复，协调GSM侧共同进行排查5、eMSC回复PstoCsRsp后MME是否收到，如果未收到，核查MME<-->eMSC之间的传输6、MME收到PstoCsRsp是否向eNodeB发送了HandoverCommand，如果未发送，协调MME共同进行排查7、MME发送HandoverCommand后eNodeB是否收到，如果未收到，核查eNodeB<-->MME传输LTE到GSM的切换出准备失败次数，其它原因切换出准备失败，其它原因是指未收到MME发送的HandoverpreparationFailure,S1HO时等待HOCOMMAND的定时器也未超时，其它未知原因造成的失败，失败的原因可能有：eNodeB处理异常、MME/GSM处理异常、MME/GSM处理异常：类似于类似于在eNodeB发送HandoverRequired后，发起了UEContextReleaseRequest造成sRVCCC切换失败。对于eNodeB处理异常的情况需要根据信令分析找出问题的根本原因。|MME处理异常举例说明：类似于在eNodeB发送HandoverRequired后收到MME发送的UEContextReleaseCommand命令造成sRVCC切换准备失败。对于MME处理异常的情况，根据信令分析情况联合核心网共同进行排查。总之准备失败的其它原因比较复杂，需要详细分析信令后再做进一步处理。124LTE到GSM的切换出执行失败次数，源侧发生重建立2&32052016C32916:03:297132016-0251tt0029713201(1-05-29応时2$7133534(0D534C0053硕1113OB2305230證--UUS1RHLC.OdleiHlobieutrntorrmondHandoverc&mrMhdFvftnlnluDoiflfwdReu44644755346(]1咖2DCM^CM訂5创皿舸舸闭已tahAdRsp44£2072016-C3-2S16；0C5-2«72385346013052raNLC.OiiterEvRniuRnicDataifwdR$p4482016Q32C1&0030OS3B5MCQ130B2WLC^OiWrEvRnicOcf^rcRoos^bHoq4834C：2092016C32916:03300G2353460130B2DCM_CMDCmdProDctr^olfcackHcq2102016-03^51&0330M33534C013帕2KM_CMDCmUXIR&lbacKRsp4032112015-03-35It0330M3B534C01创曬OCM.CMDCrndLomIgIsiRollMckReq4832122016-C3-2516:0]30Q£335^4601加RhLC_n«ieiEvRnliuiRnicDalzrwx冷■亡赳L&ck484213p016^03^016；0330083853460130&2DCM_CUD口识OWacER购4832142016032C16OJ30OS3853460130B2RbLCOiWrEvRniport斂4G：12152016C32S1&03300G3353460130RftLC_O«lcrEvRilcRniuDalafwdCnnceilUq21ft2016-03-2916W50M3AS34M13062DCl.t-CMDCmdLosaiefGRo140421?2016-03-2^If0030M3的34网130-RNLC.OilppFirThf和Re484213GC1&-03-29160130M3B534fiQ13062Htinidnv&rcanc^219853460130&2・・・DCU.CMDcmdPTocctr«oit>acknep4B42202016C32016:0J300S3B534E0130B2UURrccoonocDanra4ctabn&nmontr«qu»t221PQ1«^3ra16:03300B3S53460130&2DCI.VCMDCmdSIRolibBckRsp"403-在切换执行过程中源侧收到UE的rrcconnectionreestablishmentrequest消息，源侧发起handovercancel造成切换失败。在eSRVCC切换执行阶段造成UE重建立的原因包括：无线链路失败、Mobilityfromeutra失败。1.2.4.1无线链路失败无线链路失败主要是由于LTE覆盖较差造成UE上行/下行失步，造成失步的原因主要是弱RSRQ、弱RSRQ、上行干扰、基站功率相关告警、测量时间过长造成切换延迟、切换准备阶段handoverrequire-->handovercommad时延比较大造成切换延迟。目前版本sRVCC时参数默认配置为B2（LTE）:-115dBm/B2（GSM）:-95dBm，当下行干扰（mode3干扰、或重叠覆盖较高时），UE下行失步的概率较高，对于下行干扰严重区域，建议提高B2（LTE）门限降低下行失步的概率。参数配置路径参数名称默认值管理网元->无线参数->TD-LTE->测量参数配置->UE系统间测量参数测量配置号1012:语B2(LTE):-115dBm/B2(GSM):-95dBm音B2RSRP门限上行干扰会造成上行失步UE进行重建，建议：（1）干扰排查（2）对于上行干扰站点可以尝试调整功控方式“闭环”-->"开环"，同时修改P0_Nominal为"-87"->"-75"基站功率相关告警包括：驻波告警、功率异常、RRU故障等告警测量时间长短和“测量参数->GERAN载频测量配置”相关，配置的冗余频点过多会增加UE检测时间，造成切换延迟，建议对GERAN载频进行精细优化-0E-TP-ii-i[>J<<3iTftptfrriais(H■hfl?i5ipti-F.一右为耳呻制H?fS!!it-^ICIC峥■J'-ElOto=5W.F[*霜毗血-切换准备阶段时延过大造成切换延迟，优化建议：（1）核查切换时延大原因，进行时延优化（2）提高B2（LTE）门限使切换提前1.242Mobilityfromeutra失败Mobiltyfromeutracommand失败原因包括：（1）T304超时（2）在2G未能进行成功接入（3）UE和Mobiltyfromeutracommand消息中部分
内容
财务内部控制制度的内容财务内部控制制度的内容人员招聘与配置的内容项目成本控制的内容消防安全演练内容
不匹配Mobiltyfromeutracommand失败超时主要和邻区配置、GSM覆盖相关、特定UE、GSM侧未知故障等因素相关。邻区配置异常包括邻区漏配、邻区频点漏配、配置超远邻区。邻区漏配需要精细化的邻区优化来完成。邻区频点漏配是指“管理网元->无线参数->TD-LTE->邻接小区配置->GERAN邻接小区->BCCH载波的ARFCN”在“测量参数->GERAN载频测量配置”未配置造成部分邻区UE不测量从而影响eSRVCC切换成功率。优化建议核查“测量参数->GERAN载频测量配置”要包含所有“GERAN邻接小区->BCCH载波的ARFCN”。匡］鼻■电■-ObTiH-jir：u4t_13上ig■rfisiupti-■下衍讷工痔飢-^ICIC'4EW.FVI=T||~”*0917D0*«M31injFbftO；4.21>UJ11"jtDfl-DEilltMSB拱1毘聞•:」BterfedOsatn匚口lTD>D=T|4SI,DD.l2dfl1(3«847|'HinFBBfMiOMriC#rT&D=i甲帕呛竝剁irid睛u他犯1ceiLde.IldM曲此诂|亡妣EfteHi■也snCdlTD(D・T144tD,l42»firJElfl4l)咁如IL.曲E-«f|iHGMHCflilTOD-1Z(4«D.I0.加1-B5I&)THXJIII星•妞叶■MlrfeNGMnCMrTQDri冲初山Q绅11IBVMrNLaElllM3ll・鼻暫落花富Martg&unCflllTODsll^iDjflCi.?2?B1」D盯可lUHiliN〔須Lonflllrhl冲科竿斷E氐甜胃・卫0佈C^rTDQFl爭箱・山也竝験1.讪盯勺WVMEtiLnrBliEti-1791鬲严蠻6抚辰EZefidG:«nLrilTE-D»7tiR■却』口济21."A6£iUj⑷LDUIISM?!}K'-V^.REWTaiGsmCeilTDD-ir^SD.OCi^KBI:1075]fl-nre&LJtiiidri2!)已IETFSiGzitriCeilTL.'D-LMtJ.DQj25=n.l副旷[>相测co-SLncalld^-l皆羔战裤E^arrHGsm亡口ITD口二IMfil.DO22591r2E4BE)JHW|tHLDHZetBl怕泗gE&D=J〔45・』・总站勒・滋4聘-MmcHLde.IldM曲LtoidGsmGdlTDD--：4tJ.DO225釧壬i咁汕口CVL0tlllik129驴剧匕務磋皿E姬*HOWiL创TM叱I".l.OQ2^1.1^^tawH跟幻T池刑DfefT』：価|：讪Tl：A?肿皿倍汩.l&Tgi)lavniEHLni.11鮎曲Erfw■卫Gmit空lTT・Dit|J|hMU丁再討』轴乳ilawm妒ItEFwriirimr-^llTiD=«-Ifl.nnTflW.CAJrallAsi3DE£円■册GMtiU卸T>|jR』：IOH副叭1肿IftlttfiLorilltf=13DMrMQfmMITni^ltfVO^ZZNUD29Q>nsnrWuIIeM3Dan毗伽c桜E：4;甜訓肌1.芒詞i.却璋切ErtLj]Enllik=13QBter・afGsmCrirrDg阳曲■gdqZHSf」DBS2)啊l・lfailribAllrihHm宣二>■QPt二S；MFj-ei-p^i-zmrciiTrin.r_iv>=ai-币止刃GSM覆盖：目标侧GSM信号质量差会造成GSM接入失败，目前版本默认B2(GSM):-95dBm，对于重建立失败较高的TOP小区适当提高B2(GSM)门限以保障在GSM侧能够正常接入。参数配置路径参数名称默认值管理网元->无线参数->TD-LTE->测量参数配置->UE系统间测量参数测量配置号1012:语音B2RSRP门限B2(LTE):-115dBm/B2(GSM):-95dBma-uzir*Hits&zy仙小|inuin^.~n^n-Ri-^7R4q7HR7R1-iniliw■r.■TVnD^TAIDMsplMameRWLCOj1^EvRnlLiRnlplJ:jcchS^nalnU1ULIRriXQiTin&dlignrtqu&5lnecuCi/pCnfi^ocWAngchRiiixQnn'&Jilcn.„D€U£18CmdAtacrjJS^^pijrjcDCH.CMDRhLr_CHj1frFvRrm^nirsm^d^ilRspRNLC.DulerF'hHnliSRnri呂帕dFltRM特定终端影响主要是指某个或某款终端在GSM侧接入异常导致。确定是否是某个终端导致切换异常可以通过(1)netmax切换智能分析可以基于"IMSI的汇总”来分析(2)通过汇总M-TMSI来进行分析；确定是否是某款终端导致同一通过“FGI(FeatureGroupID)”汇总进行分析图1-1NetmaxIMSI汇总IWSIaua通IDC^llIDCtllCallTint16000179313737766578L海淀上鰹OU二期ZUFI18:07:11^600012919^594766578L海淀上地MOM匸期ZLNT2015-11-0916:1^709^fi0077013M5205繭518L海淀上期的匸期2口-$2015-11-M18：5仁伯图1-2M-TMSI信息查询»口u中口rrwnse]numw■=B甲二"f*Qnumblfi=322dUU-(fcDhJ830(l-EX)QeETflhuhrtiericause■4Eitannsn^rV(JiCJiaDnumbib1造成命令携带其它原因值的原因有：中兴MME版本、其它原因图1-3FGI信息查询15E61556155ft15^6■4CEC-HML；_uuterRtJLC_OuterRNLC_OulferkMLC_auterRHLC_OuterF3NLC_DuterEvlpTbS«tUpAClCcRinlL'U^ctriCfcReqEirfpTbS^tupR:旳EvWrlEfapU总ctnugbteqfri.二rrlh.-i~^jfm；EVRTdCE匕MM-@dbgFt@q口wPr^amE)@Lf@TimiO-0IHdfwLEFsaLireFressit=17厂J忙m自匚UpF电atured^UEFeaurGGroupanc-2144337562□p&cR^kiaSuFp-crled-0GSM侧未知故障造成UE在GSM接入异常，该问题需要跟踪GSM、LTE侧信令共同进行分析。1.2.5等待UECONTEXTRELEASE消息超时“S1源侧切换成功后等待MME释放定时器（毫秒）”配置为15s,eNodeB下发Mobilityformeutracommand”后15s内未收至UMME的Uecontextreleasecommand，eNodeB会记录一次eSRVCC切换失败。造成超时的原因可能有：MME版本问题、传输问题、其它未知问题。MME版本问题：在R11之前的协议中未明确规定在eSRVCC切换完成后必须下发Uecontextreleasecommand。UE在sRVCC成功切换到GSM后，某些厂家的MME不下发Uecontextreleasecommand从而造成等待UECONTEXTRELEASE消息。该问题优化建议：（1）MME版本升级（2）升级602版本后会对这部分进行TY，可以对这部分失败不做统计。传输问题由于传输丢包造成Uecontextreleasecommand未收到，该问题建议进行传输可靠性核查。其它未知问题分析：端到端信令进行分析。1.2.6LTE到GSM的切换出执行失败次数，其他原因当eNodeB收到MME的Uecontextreleasecommand时，只有当里面携带的原因值为successfulhandover才认为是sRVCC切换成功，所有其它携带的原因值都认为是执行失败L1OE3Hlit^romcutracommandHaiiflov^rEuRnluRnlcDalahudCmdInlermbOatzrfwdRspCmdProrHrlllr]ho%IJerlxtRF4€m<9Herplpase*comnnflvidCmdProctrlPosLleReltM&liidcmdiYoccifiiuitiaacu'ccutReiCfndyI~impiMSigblE_Etlfrt>ionsFr«tenl"jmUE_UE_31AP_D-4J15511jeMB_UE_S1AFJD-1175辛Qcauafi.T口UP怕川=2用"AFUdu哉只自凸加:：协刑一甘sfuLhiarwo/TrCmdS1!ilnO£L>dClMlHjQiH£pcnwfieioa&tS1u«cixhKiicma1.261中兴MME版本问题中兴MME在R11之前的版本中eSRVCC切换完成后，核心网下发UECONTEXTREALEASECOMMAND，携带的原因值为TS1AP_CauseNAS_Root_normal_release。根据TS36.413921.3，当切换成功导致的上下文释放，携带的原因值应该为HandoverSuccess而不是NormalRelease。网管目前统计eNBeSRVCC切换执行成功也是统计源eNB接收到MME发送的“UE上下文释放”消息(UECONTEXTRELEASECOMMAND)，释放原因是"handoversuccess”。目前MMEV4.10.18已经取得入网证并在全网进行升级，对于未升级的区域建议尽快进行MME版本升级。1.2.6.2其它原因详见附录A，释放原因说明。需要根据UECONTEXTRELEASECOMMAND携带的原因值再进行进一步的定位。在P02版本中计划对其它原因造成的失败进行TY，按照原因值分为4个开关：NormalRelease、ReleaseduetoE-UTRANGeneratedReason、FailureintheRadioInterfaceProcedure、其它所有原因，4个开关可以通关B类参数进行控制，可以根据优化需求有选择性的关闭其中某个或全部失败原因值的统计。附录A释放原因说明(TS36.413921.3)IE/GroupNamePresenceRangeIETypeandReferenceSemanticsDescriptionCHOICECauseGroupM>RadioNetworkLayer>>RadioNetworkLayerCauseMENUMERATED(Unspecified,TX2RELOCOverallExpiry,SuccessfulHandover,ReleaseduetoE-UTRANGeneratedReason,HandoverCancelled,PartialHandover,HandoverFailureInTargetEPC/eNBOrTargetSystem,HandoverTargetnotallowed,TS1RELOCoverallExpiry,TS1RELOCprepExpiry,Cellnotavailable,UnknownTargetID,NoRadioResourcesAvailableinTargetCell,UnknownoralreadyallocatedMMEUES1APID,UnknownoralreadyallocatedeNBUES1APID,UnknownorinconsistentpairofUES1APID,Handoverdesirableforradioreasons,Timecriticalhandover,Resourceoptimisationhandover,Reduceloadinservingcell,Userinactivity,RadioConnectionWithUELost,LoadBalancingTAURequired,CSFallbackTriggered,UENotAvailableForPSService,Radioresourcesnotavailable,FailureintheRadioInterfaceProcedure,InvalidQoScombination,Inter-RATredirection,Interactionwithotherprocedure,UnknownE-RABID,MultipleE-RABIDinstances,Encryptionand/orintegrityprotectionalgorithmsnotsupported,S1intrasystemHandovertriggered,S1intersystemHandovertriggered,X2Handovertriggered,Redirectiontowards1xRTT,NotsupportedQCIvalue,invalidCSGId)>TransportLayer>>TransportLayerCauseMENUMERATED(TransportResourceUnavailable,Unspecified,…)>NAS>>NASCauseMENUMERATED(NormalRelease,Authenticationfailure,Detach,Unspecified,,CSGSubscriptionExpiry)>Protocol>>ProtocolCauseMENUMERATED(TransferSyntaxError,AbstractSyntaxError(Reject),AbstractSyntaxError(IgnoreandNotify),MessagenotCompatiblewithReceiverState,SemanticError,AbstractSyntaxError(FalselyConstructedMessage),Unspecified,…)>Misc>>MiscellaneousCauseMENUMERATED(ControlProcessingOverload,NotenoughUserPlaneProcessingResources,HardwareFailure,O&MIntervention,Unspecified,UnknownPLMN,…)Themeaningofthedifferentcausevaluesisdescribedinthefollowingtable.Ingeneral,"notsupported”causevaluesindicatethattherelatedcapabilityismissing.Ontheotherhand,"notavailable'causevaluesindicatethattherelatedcapabilityispresent,butinsufficientresourceswereavailabletoperformtherequestedaction.RadioNetworkLayercauseMeaningUnspecifiedSentforradionetworklayercausewhennoneofthespecifiedcausevaluesapplies.TX2RELOCOverallExpiryThetimerguardingthehandoverthattakesplaceoverX2hasabnormallyexpired.SuccessfulHandover「Successfulhandover.ReleaseduetoE-UTRANgeneratedreasonReleaseisinitiatedduetoE-UTRANgeneratedreason.HandoverCancelledThereasonfortheactioniscancellationofHandover.PartialHandoverProvidesareasonforthehandovercancellation.TheHANDOVERCOMMANDmessagefromMMEcontainedE-RABstoReleaseListIEandthesourceeNBestimatedservicecontinuityfortheUEwouldbebetterbynotproceedingwithhandovertowardsthisparticulartargeteNB.HandoverFailureInTargetEPC/eNBOrTargetSystemThehandoverfailedduetoafailureintargetEPC/eNBortargetsystem.HandoverTargetnotallowedHandovertotheindicatedtargetcellisnotallowedfortheUEinquestion.TS1RELOCoverallExpiryThereasonfortheactionisexpiryoftimerTS1RELOCoverall.TS1RELOCprepExpiryHandoverPreparationprocedureiscancelledwhentimerTS1RELOCprepexpires.CellnotavailableTheconcernedcellisnotavailable.UnknownTargetIDHandoverrejectedbecausethetargetIDisnotknowntotheEPC.NoradioresourcesavailableintargetcellLoadontargetcellistoohigh.UnknownoralreadyallocatedMMEUES1APIDTheactionfailedbecausetheMMEUES1APIDiseitherunknown,or(forafirstmessagereceivedattheeNB)isknownandalreadyallocatedtoanexistingcontext.UnknownoralreadyallocatedeNBUES1APIDTheactionfailedbecausetheeNBUES1APIDiseitherunknown,or(forafirstmessagereceivedattheMME)isknownandalreadyallocatedtoanexistingcontext.UnknownorinconsistentpairofUES1APIDTheactionfailedbecausebothUES1APIDsareunknown,orareknownbutdonotdefineasingleUEcontext.HandoverDesirableforRadioReasonsThereasonforrequestinghandoverisradiorelated.TimeCriticalHandoverHandoverisrequestedfortimecriticalreasoni.e.,thiscausevalueisreservedtorepresentallcriticalcaseswheretheconnectionislikelytobedroppedifhandoverisnotperformed.ResourceOptimisationHandoverThereasonforrequestinghandoveristoimprovetheloaddistributionwiththeneighbourcells.ReduceLoadinServingCellLoadonservingcellneedstobereduced.Whenappliedtohandoverpreparation,itindicatesthehandoveristriggeredduetoloadbalancing.UserInactivityTheactionisrequestedduetouserinactivityonallE-RABs,e.g.,S1isrequestedtobereleasedinordertooptimisetheradioresources.RadioConnectionWithUELostTheactionisrequestedduetolosingtheradioconnectiontotheUE.LoadBalancingTAURequiredTheactionisrequestedforallloadbalancingandoffloadcasesintheMME.CSFallbacktriggeredTheactionisduetoaCSfallbackthathasbeentriggered.WhenitisincludedinUECONTEXTRELEASEREQUESTmessage,itindicatesthePSservicesuspensionisnotrequiredintheEPC.UENotAvailableforPSServiceTheactionisrequestedduetoaCSfallbacktoGERANthathasbeentriggered.WhenitisincludedintheUECONTEXTRELEASEREQUESTmessage,itindicatesthatthePSservicesuspensionisrequiredintheEPCduetothetargetGERANcellortheUEhasnoDTMcapability.RadioresourcesnotavailableNorequestedradioresourcesareavailable.InvalidQoScombinationTheactionwasfailedbecauseofinvalidQoScombination.Inter-RATRedirectionThereleaseisrequestedduetointer-RATredirection.WhenitisincludedinUECONTEXTRELEASEREQUESTmessage,itindicatesthePSservicesuspensionisnotrequiredintheEPC.FailureintheRadioInterfaceProcedureRadiointerfaceprocedurehasfailed.InteractionwithotherprocedureTheactionisduetoanongoinginteractionwithanotherprocedure.UnknownE-RABIDTheactionfailedbecausetheE-RABIDisunknownintheeNB.MultipleE-RABIDInstancesTheactionfailedbecausemultipleinstanceofthesameE-RABhadbeenprovidedtotheeNB.Encryptionand/orintegrityprotectionalgorithmsnotsupportedTheeNBisunabletosupportanyoftheencryptionand/orintegrityprotectionalgorithmssupportedbytheUE.S1IntrasystemHandovertriggeredTheactionisduetoaS1intrasystemhandoverthathasbeentriggered.S1IntersystemHandovertriggeredTheactionisduetoaS1intersystemhandoverthathasbeentriggered.X2HandovertriggeredTheactionisduetoanX2handoverthathasbeentriggered.Redirectiontowards1xRTTThereleaseoftheUE-associatedlogicalS1connectionisrequestedduetoredirectiontowardsaIxRTTsysteme.g.,CSfallbacktoIxRTT,orSRVCCtoIxRTT,whenthePSservicesuspensionisrequiredintheEPC.Duringthisprocedure,theradiointerfacemessagemightbutneednotincluderedirectioninformation.NotsupportedQCIValueTheE-RABsetupfailedbecausetherequestedQCIisnotsupported.InvalidCSGIdTheCSGIDprovidedtothetargeteNBwasfoundinvalid.TransportLayercauseMeaningTransportResourceUnavailableTherequiredtransportresourcesarenotavailable.UnspecifiedSentwhennoneoftheabovecausevaluesappliesbutstillthecauseisTransportNetworkLayerrelated.NAScauseMeaningNormalReleaseThereleaseisnormal.AuthenticationFailureTheactionisduetoauthenticationfailure.DetachTheactionisduetodetach.UnspecifiedSentwhennoneoftheabovecausevaluesappliesbutstillthecauseisNASrelated.CSGSubscriptionExpiryTheactionisduetotheUEbecominganon-memberofthecurrentlyusedCSG.ProtocolcauseMeaningTransferSyntaxErrorThereceivedmessageincludedatransfersyntaxerror.AbstractSyntaxError(Reject)Thereceivedmessageincludedanabstractsyntaxe
浙公网安备 33021202002483