SA常见KPI优化指导书

ProductTypeTechnicalProposalZTEConfidentialProprietary©CREATEDATE\@"yyyy"2009ZTECorporation.Allrightsreserved.. 正常情况下，某个小区周边都存在邻区，如果无线环境不是很差，都可以通过切换的方式改变服务小区。当某个站点缺失邻区或者邻区添加不合理，会导致无法切换出而掉死。因此处理掉线率较高的小区时，需要核查邻区配置是否合理。3. 核查小区是否存在超远覆盖，导致覆盖孤岛，无法切换到周边邻区。可以通过后台跟踪信令，观察测量报告，并补齐漏配的邻区。随后需要对覆盖进行控制。4. 对于因弱覆盖导致掉线，若终端处于覆盖边缘，周围无可用的NR小区，可以添加系统间邻区，使用切换到4G的方式，减少掉线次数。但门限设置需要合理，不能太容易去到4G。无线掉线案例解析等待PDUSession超时导致异常释放针对GNB由于其它原因引发释放，筛选TOP小区跟踪信令，结合信令和CPA打印，基本可以确认其它原因的上下文释放主要是由于接入过程核心网在初始上下文建立请求消息中没有携带PduSessionResourceSetupIE，导致基站侧等核心网的pdusession建立10s超时，触发了上下文释放。该种释放和无线无关，和终端和核心网处理相关，在V5.35.301130及之后的版本新增了计数器“C600050034:Context释放次数，GNB由于等待核心网消息超时”，该种原因不再计为异常释放。FOA区域版本升级后，无线掉线率由0.11%下降到0.39%，其它原因引发的释放次数由1780次下降到338次。系统内切换成功率系统内切换失败原因解析切换失败原因包括切换出准备失败和切换出执行失败，具体详见下表：指标或计数器指标或计数器描述C600100002gNB间Xn同频切换出准备失败次数，源侧发生重建立C600100003gNB间Xn同频切换出准备失败次数，等待切换响应定时器超时C600100004gNB间Xn同频切换出准备失败次数，目标侧资源不足C600100005gNB间Xn同频切换出准备失败次数，其它原因C600100007gNB间Xn同频切换出执行失败次数，源侧发生重建立C600100008gNB间Xn同频切换出执行失败次数，等待UECONTEXTRELEASE消息超时C600100009gNB间Xn同频切换出执行失败次数，其它原因C600110002gNB间Ng同频切换出准备失败次数，等待切换响应定时器超时C600110003gNB间Ng同频切换出准备失败次数，目标侧资源不足C600110004gNB间Ng同频切换出准备失败次数，源侧发生重建立C600110005gNB间Ng同频切换出准备失败次数，其它原因C600110007gNB间Ng同频切换出执行失败次数，源侧发生重建立C600110008gNB间Ng同频切换出执行失败次数，等待UECONTEXTRELEASE消息超时C600110009gNB间Ng同频切换出执行失败次数，其它原因C600120005gNB内DU内小区间同频切换出执行失败次数，RRC重配完成超时C600120006gNB内DU内小区间同频切换出执行失败次数，源侧发生重建立C600120007gNB内DU内小区间同频切换出执行失败次数，其它原因■切换出准备失败，源侧发生重建立在切换过程中，由于gNodeB在源小区或源gNodeB站内其他小区接收到UE的RRCReestablishmentRequest消息或者接收到其他gNodeB发送的XnRetrieveUeContextRequest消息，造成切换准备失败。切换出准备失败，源侧重建立通常是由于无线覆盖质差导致，需要重点核查干扰、弱覆盖、超远覆盖和重叠覆盖。■切换出准备失败，等待切换响应定时器超时在切换过程中，由于源gNodeB等待HandoverRequestAck消息定时器超时，造成切换出准备失败。切换出准备失败，等待切换响应定时器超时通常是由于TAC插花、外部邻区参数配置和小区实际配置不一致、XN或是NG链路故障。需要重点核查TAC插花、外部邻区参数配置、XN/NG链路是否丢包。■切换出准备失败次数，目标侧资源不足在切换过程中由于目标侧资源准备不足，造成切换出准备失败。切换出准备失败，目标侧资源不足通常和目标侧负荷（用户数、CPU利用率）、小区Cellbar、基站内部处理异常相关。该种原因如果目标侧RRC连接最大用户数<50、CPU利用率<60%且无Cellbar配置的情况下，建议提故障单转研发做进一步排查。另外需关注：高铁站点在V5.35.30之前的版本如果开启周期性MR会导致切换过程中目标侧资源不足的情况发生，建议V5.35.30之前的版本不要开启周期性MR。■切换出准备失败次数，其它原因除以上原因外，导致的切换出准备失败。其它原因的准备失败，在核查完外部邻区参数配置，如果配置正确需要跟踪信令确定问题现象，上报第一响应组协助进行分析。■切换出执行失败次数，源侧发生重建立在切换过程中，由于gNodeB在源小区或源gNodeB站内其他小区接收到UE的RRCReestablishmentReques消息或者接收到其他gNodeB发送的XnRetrieveUeContextRequest消息，造成切换出执行失败。切换出执行失败次数，源侧发生重建立可能是由于切换CIO配置不合理（建议-3dB~3dB）、覆盖问题（弱覆盖、重叠覆盖、超远覆盖）、干扰、邻区漏配。TOP小区处理时建议根据信令判断发生切换失败发生时是否是在弱场、是否存在邻区漏配、测量参数是否不合理。■切换出执行失败次数，等待UECONTEXTRELEASE消息超时在切换过程中，由于源gNodeB等待目标侧小区的UEContextRelease定时器超时，造成切换出执行失败。■切换出执行失败次数，其它原因统计发生除以上原因以外导致从gNodeB切换出执行失败，需要跟踪信令确认问题现象再做针对性的分析优化。切换成功率低处理思路切换过程中包含切换准备阶段，与切换执行阶段，2个阶段涉及到的因素各不一样，因此需要分开来处理。切换准备失败，多由外部邻小区参数配置错误（邻区配置正确）或者切换准备目标基站故障引起。切换执行失败，发生在切换命令下发后，终端执行时失败，与无线环境，邻区配置的合理性强相关。对于整网切换成功率较低的网络，需要先分析切换准备与执行那个导致的失败次数较多，再按TOP小区针对分析处理。■切换准备失败处理切换准备失败需要提取切换准备相关的计数器分解，查看具体的准备失败原因。切换准备失败主要关注邻区参数的正确性，具体包括：切换准备失败需要定期核查现网邻区数据,保证数据的有效与准确；现网中邻区参数配置错误的，如外部小区定义中与邻接基站定义不一致的；定期提取规划数据，进行核查；现网中对异厂家站点邻区定义错误的，需定期索取异常家工参核查；现网中邻区基站ID错误的，即不存在于异厂家网管，也不存在与中兴网管中的邻区关系。需要删除这类邻区数据；定期核查现网中超远邻区关系，以2KM为界，对于超远邻区且切换成功率<50%的邻区对暂时删除。■切换出执行失败处理切换执行阶段失败同样需要提取切换准备相关的计数器分解，查看具体的执行失败原因。切换出执行失败次数>10次且切换成功率=0的小区对，建议删除同时开启系统内ANR功能对邻区进行重新添加；切换出执行失败次数>10次且切换成功率<90%,首先核查切换目标小区是否与周边站点同频同PCI，如果存在同频同PCI小区，进行PCI重规划；切换出执行次数>10次且切换成功率<90%，核查目标基站否存在上行干扰，如果存在上行干扰，即需要进行干扰排查。切换成失败案例解析NGAP未配置导致切换失败11579866-311向11579911发起HandoverRequired消息，目标侧（11579911）未收到HandoverRequest消息，AMF直接回复HandoverPreparationFailure消息（cause：ho_failure_in_target_5GC_ngran_node_or_target_system）导致NG切换准备失败。核查目标侧11579911的接入信令，目标侧收到RRCSetupComplete消息后未发送IntialUEMesseage给AMF，说明该小区接入存在异常。核查目标侧11579911NGSCTP和NGAP配置：NGSCTP配置以及状态正常，NGAP未配置。添加NGAP配置后11579866-311向11579911切换恢复正常。源侧和目标侧AMF配置不一致导致切换失败【问题现象】XN口向目标站点发送切换请求，目标侧回复Xnap_CauseRadioNetworkLayer_Root_invalid_AMF_Set_ID原因的准备失败，随后向同一个目标站点再发NG口的切换请求，并收到Ngap_CauseRadioNetwork_Root_ho_failure_in_target_5GC_ngran_node_or_target_system原因的切换准备失败。【原因分析】针对这种准备失败的原因可能是目标侧与源侧配置的AMF不一致，一般外场都会有多套AMF，全网所有的站点都需要将每条AMF配置全备，不然会出现切换准备失败的问题。切片配置错误导致无法切换【问题发现】多维分析-控制面分析--N1N2接口分析巡检发现，较多次N2切换失败，原因为 slice-not-supported，切片不支持，定界为无线【原因分析】通过下钻小区分析，有多个小区存在N2切出失败问题以MSISD例，经信令回溯分析，用户驻留小区LFSHQ1023利比玻璃-ZWH-2向基站gNB-ID为1069677发起切换，向AMF发起切换准备请求NGAPHandoverRequired，AMF回复切换失败消息，原因为切片不支持（slice-not-supported）。cell_id为4381396994协议分析，Slice(s)notsupported为NGSTEUP或者RANCONFIGURATIONUPDATE流程时，携带的切片AMF都不支持，可能是无线配置问题网元名称:APP-HBBADheAMF001BZX-05AZX011

网元类型:AMF

网元ID:1090519041

节点IP:61&29&2409:800b:5003:1705::101网元名称:APP-HBBADheSMF003BZX-05AZX012

网元类型:SMF

网元ID:1107296263

节点IP:2409:800b:5003:1705:1::301【问题解决】Slice(s)notsupported为NGSTEUP或者RANCONFIGURATIONUPDATE流程时，携带的切片AMF都不支持，可能是无线配置问题，查看小区LFSHQ1023利比玻璃-ZWH-2和基站gNB-ID为1069677其切片配置中tac与本小区tac配置不一致，修改后问题解决。网管截图：修改后指标统计：小区切换正常参考资料MSG不下发P0-Alpha问题说明NR相关定时器介绍参见协议3GPP38.331~7.1TimerStartStopAtexpiryT300UpontransmissionofRRCSetupRequest.UponreceptionofRRCSetuporRRCRejectmessage,cellre-selectionanduponabortionofconnectionestablishmentbyupperlayers.Performtheactionsasspecifiedin.T301UpontransmissionofRRCReestabilshmentRequestUponreceptionofRRCReestablishmentorRRCSetupmessageaswellaswhentheselectedcellbecomesunsuitableGotoRRC_IDLET302UponreceptionofRRCRejectwhileperformingRRCconnectionestablishmentorresume,uponreceptionofRRCReleasewithwaitTime.UponenteringRRC_CONNECTEDorRRC_IDLE,uponcellre-selectionanduponreceptionofRRCRejectmessage.InformupperlayersaboutbarringalleviationasspecifiedinT304UponreceptionofRRCReconfigurationmessageincludingreconfigurationWithSyncoruponconditionalreconfigurationexecutioni.e.whenapplyingastoredRRCReconfigurationmessageincludingreconfigurationWithSync.UponsuccessfulcompletionofrandomaccessonthecorrespondingSpCellForT304ofSCG,uponSCGreleaseForT304ofMCG,incaseofthehandoverfromNRorintra-NRhandover,initiatetheRRCre-establishmentprocedure;IncaseofhandovertoNR,performtheactionsdefinedinthespecificationsapplicableforthesourceRAT.ForT304ofSCG,informnetworkaboutthereconfigurationwithsyncfailurebyinitiatingtheSCGfailureinformationprocedureasspecifiedin5.7.3.T310UpondetectingphysicallayerproblemsfortheSpCelli.e.uponreceivingN310consecutiveout-of-syncindicationsfromlowerlayers.UponreceivingN311consecutivein-syncindicationsfromlowerlayersfortheSpCell,uponreceivingRRCReconfigurationwithreconfigurationWithSyncforthatcellgroup,anduponinitiatingtheconnectionre-establishmentprocedure.UponSCGrelease,iftheT310iskeptinSCG.IftheT310iskeptinMCG:IfASsecurityisnotactivated:gotoRRC_IDLEelse:initiatetheMCGfailureinformationprocedureasspecifiedin5.7.3bortheconnectionre-establishmentprocedureasspecifiedin5.3.7.IftheT310iskeptinSCG,InformE-UTRAN/NRabouttheSCGradiolinkfailurebyinitiatingtheSCGfailureinformationprocedureasspecifiedin5.7.3.T311UponinitiatingtheRRCconnectionre-establishmentprocedureUponselectionofasuitableNRcelloracellusinganotherRAT.EnterRRC_IDLET312IfT312isconfiguredinMCG:UpontriggeringameasurementreportforameasurementidentityforwhichT312hasbeenconfigured,whileT310inPCellisrunning.IfT312isconfiguredinSCG:UpontriggeringameasurementreportforameasurementidentityforwhichT312hasbeenconfigured,whileT310inPSCellisrunning.UponreceivingN311consecutivein-syncindicationsfromlowerlayersfortheSpCell,receivingRRCReconfigurationwithreconfigurationWithSyncforthatcellgroup,uponinitiatingtheconnectionre-establishmentprocedure,andupontheexpiryofT310incorrespondingSpCell.UponSCGrelease,iftheT312iskeptinSCGIftheT312iskeptinMCG:Ifsecurityisnotactivated:gotoRRC_IDLEelse:initiatetheconnectionre-establishmentprocedure.IftheT312iskeptinSCG,InformE-UTRAN/NRabouttheSCGradiolinkfailurebyinitiatingtheSCGfailureinformationprocedure.asspecifiedin5.7.3.T316UpontransmissionoftheMCGFailureInformationmessageUponresumptionofMCGtransmission,uponreceptionofRRCRelease,oruponinitiatingthere-establishmentprocedure,Performtheactionsasspecifiedin5.7.3b.5.T319UpontransmissionofRRCResumeRequestorRRCResumeRequest1.UponreceptionofRRCResume,RRCSetup,RRCRelease,RRCReleasewithsuspendConfigorRRCRejectmessage,cellre-selectionanduponabortionofconnectionestablishmentbyupperlayers.Performtheactionsasspecifiedin.T320Uponreceptionoft320oruponcell(re)selectiontoNRfromanotherRATwithvaliditytimeconfiguredfordedicatedpriorities(inwhichcasetheremainingvaliditytimeisapplied).UponenteringRRC_CONNECTED,uponreceptionofRRCRelease,whenPLMNselectionisperformedonrequestbyNAS,whentheUEentersRRC_IDLEfromRRC_INACTIVE,oruponcell(re)selectiontoanotherRAT(inwhichcasethetimeriscarriedontotheotherRAT).Discardthecellreselectionpriorityinformationprovidedbydedicatedsignalling.T321UponreceivingmeasConfigincludingareportConfigwiththepurposesettoreportCGIUponacquiringtheinformationneededtosetallfieldsofcgi-info,uponreceivingmeasConfigthatincludesremovalofthereportConfigwiththepurposesettoreportCGIandupondetectingthatacellisnotbroadcastingSIB1.Initiatethemeasurementreportingprocedure,stopperformingtherelatedmeasurements.T322UponrecevingmeasConfigincludingreportConfigNRwiththepurposesettoreportSFTDanddrx-SFTD-NeighMeasissettotrue.UponacquiringtheSFTDmeasurementresults,uponreceivingmeasConfigthatincludesremovalofthereportConfigwiththepurposesettoreportSFTD.Initiatethemeasurementreportingprocedure,stopperformingtherelatedmeasurements.T325UponreceptionofRRCReleasemessagewithdeprioritisationTimer.StopdeprioritisationofallfrequenciesorNRsignalledbyRRCRelease.T330UponreceivingLoggedMeasurementConfigurationmessageUponlogvolumeexceedingthesuitableUEmemory,uponinitiatingthereleaseofLoggedMeasurementConfigurationprocedurePerformtheactionsspecifiedin5.5a.1.4T331UponreceivingRRCReleasemessagewithmeasIdleDurationUponreceivingRRCSetup,RRCResume,RRCReleasewithidle/inactivemeasurementconfiguration,uponreselectingtocellthatdoesnotbelongtovalidityArea(ifconfigured),oruponcellre-selectiontoanotherRAT.Performtheactionsasspecifiedin.T342UpontransmittingUEAssistanceInformationmessagewithDelayBudgetReport.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingdelayBudgetReportingConfigsettorelease.Noaction.T345UpontransmittingUEAssistanceInformationmessagewithoverheatingAssistanceUponinitiatingtheconnectionre-establishmentprocedureanduponinitiatingtheconnectionresumptionprocedureNoaction.T346aUpontransmittingUEAssistanceInformationmessagewithdrx-Preference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingdrx-PreferenceConfigsettorelease.Noaction.T346bUpontransmittingUEAssistanceInformationmessagewithmaxBW-Preference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingmaxBW-PreferenceConfigsettorelease.Noaction.T346cUpontransmittingUEAssistanceInformationmessagewithmaxCC-Preference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingmaxCC-PreferenceConfigsettorelease.Noaction.T346dUpontransmittingUEAssistanceInformationmessagewithmaxMIMO-LayerPreference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingmaxMIMO-LayerPreferenceConfigsettorelease.Noaction.T346eUpontransmittingUEAssistanceInformationmessagewithminSchedulingOffsetPreference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingminSchedulingOffsetPreferenceConfigsettorelease.Noaction.T346fUpontransmittingUEAssistanceInformationmessagewithreleasePreference.Uponinitiatingtheconnectionre-establishment/resumeprocedures,anduponreceivingreleasePreferenceConfigsettorelease.Noaction.T380Uponreceptionoft380inRRCRelease.UponreceptionofRRCResume,RRCSetuporRRCRelease.Performtheactionsasspecifiedin5.3.13.T390WhenaccessattemptisbarredataccessbarringcheckforanAccessCategory.TheUEmaintainsoneinstanceofthistimerperAccessCategory.Uponcell(re)selection,uponenteringRRC_CONNECTED,uponreceptionofRRCReconfigurationincludingreconfigurationWithSync,uponchangeofPCellwhileinRRC_CONNECTED,uponreceptionofMobilityFromNRCommand,oruponreceptionofRRCRelease.Performtheactionsasspecifiedin.T400UpontransmissionofRRCReconfigurationSidelinkUponreceptionofRRCReconfigurationFailureSidelinkorRRCReconfigurationCompleteSidelinkPerformthesidelinkRRCreconfigurationfailureprocedureasspecifiedin.8CounterResetIncrementedWhenreachingmaxvalueN310Uponreceptionof"in-sync"indicationfromlowerlayers;uponreceivingRRCReconfigurationwithreconfigurationWithSyncforthatcellgroup;uponinitiatingtheconnectionre-establishmentprocedure.Uponreceptionof"out-of-sync"fromlowerlayerwhilethetimerT310isstopped.StarttimerT310N311Uponreceptionof"out-of-sync"indicationfromlowerlayers;uponreceivingRRCReconfigurationwithreconfigurationWithSyncforthatcellgroup;uponinitiatingtheconnectionre-establishmentprocedure.Uponreceptionofthe"in-sync"fromlowerlayerwhilethetimerT310isrunning.StopthetimerT310.NG口消息原因值定义参见3GPP协议38413~ThepurposeoftheCauseIEistoindicatethereasonforaparticulareventfortheNGAPprotocol.IE/GroupNamePresenceRangeIEtypeandreferenceSemanticsdescriptionCHOICECauseGroupM>RadioNetworkLayer>>RadioNetworkLayerCauseMENUMERATED

(Unspecified,TXnRELOCOverallexpiry,Successfulhandover,ReleaseduetoNG-RANgeneratedreason,Releasedueto5GCgeneratedreason,Handovercancelled,Partialhandover,Handoverfailureintarget5GC/NG-RANnodeortargetsystem,Handovertargetnotallowed,TNGRELOCoverallexpiry,TNGRELOCprepexpiry,Cellnotavailable,UnknowntargetID,Noradioresourcesavailableintargetcell,UnknownlocalUENGAPID,InconsistentremoteUENGAPID,Handoverdesirableforradioreasons,Timecriticalhandover,Resourceoptimisationhandover,Reduceloadinservingcell,Userinactivity,RadioconnectionwithUElost,Radioresourcesnotavailable,InvalidQoScombination,Failureintheradiointerfaceprocedure,Interactionwithotherprocedure,UnknownPDUSessionID,UnknownQoSFlowID,MultiplePDUSessionIDInstances,MultipleQoSFlowIDInstances,Encryptionand/orintegrityprotectionalgorithmsnotsupported,NGintra-systemhandovertriggered,NGinter-systemhandovertriggered,Xnhandovertriggered,Notsupported5QIvalue,UEcontexttransfer,IMSvoiceEPSfallbackorRATfallbacktriggered,UPintegrityprotectionnotpossible,UPconfidentialityprotectionnotpossible,Slice(s)notsupported,UEinRRC_INACTIVEstatenotreachable,Redirection,Resourcesnotavailablefortheslice(s),UEmaximumintegrityprotecteddataratereason,ReleaseduetoCN-detectedmobility,…,N26interfacenotavailable,Releaseduetopre-emption,MultipleLocationReportingReferenceIDInstances)>TransportLayer>>TransportLayerCauseMENUMERATED

(Transportresourceunavailable,Unspecified,

…)>NAS>>NASCauseMENUMERATED(Normalrelease,Authenticationfailure,Deregister,Unspecified,…)>Protocol>>ProtocolCauseMENUMERATED

(Transfersyntaxerror,

Abstractsyntaxerror(reject),

Abstractsyntaxerror(ignoreandnotify),

Messagenotcompatiblewithreceiverstate,Semanticerror,Abstractsyntaxerror(falselyconstructedmessage),Unspecified,…)>Miscellaneous>>MiscellaneousCauseMENUMERATED

(Controlprocessingoverload,Notenoughuserplaneprocessingresources,

Hardwarefailure,

O&Mintervention,

UnknownPLMN,Unspecified,…)Themeaningofthedifferentcausevaluesisdescribedinthefollowingtables.Ingeneral,"notsupported"causevaluesindicatethattherelatedcapabilityismissing.Ontheotherhand,"notavailable"causevaluesindicatethattherelatedcapabilityispresent,butinsufficientresourceswereavailabletoperformtherequestedaction.RadioNetworkLayercauseMeaningUnspecifiedSentforradionetworklayercausewhennoneofthespecifiedcausevaluesapplies.TXnRELOCOverallexpiryThetimerguardingthehandoverthattakesplaceoverXnhasabnormallyexpired.SuccessfulhandoverSuccessfulhandover.ReleaseduetoNG-RANgeneratedreasonReleaseisinitiatedduetoNG-RANgeneratedreason.Releasedueto5GCgeneratedreasonReleaseisinitiateddueto5GCgeneratedreason.HandovercancelledThereasonfortheactioniscancellationofHandover.PartialhandoverProvidesareasonforthehandovercancellation.TheHANDOVERCOMMANDmessagefromAMFcontainedPDUSessionResourcetoReleaseListIEorQoSflowtoReleaseListandthesourceNG-RANnodeestimatedservicecontinuityfortheUEwouldbebetterbynotproceedingwithhandovertowardsthisparticulartargetNG-RANnode.Handoverfailureintarget5GC/NG-RANnodeortargetsystemThehandoverfailedduetoafailureintarget5GC/NG-RANnodeortargetsystem.HandovertargetnotallowedHandovertotheindicatedtargetcellisnotallowedfortheUEinquestion.TNGRELOCoverallexpiryThereasonfortheactionisexpiryoftimerTNGRELOCoverall.TNGRELOCprepexpiryHandoverPreparationprocedureiscancelledwhentimerTNGRELOCprepexpires.CellnotavailableTheconcernedcellisnotavailable.UnknowntargetIDHandoverrejectedbecausethetargetIDisnotknowntotheAMF.NoradioresourcesavailableintargetcellLoadontargetcellistoohigh.UnknownlocalUENGAPIDTheactionfailedbecausethereceivingnodedoesnotrecognisethelocalUENGAPID.InconsistentremoteUENGAPIDTheactionfailedbecausethereceivingnodeconsidersthatthereceivedremoteUENGAPIDisinconsistent.HandoverdesirableforradioreasonsThereasonforrequestinghandoverisradiorelated.TimecriticalhandoverHandoverisrequestedfortimecriticalreasoni.e.,thiscausevalueisreservedtorepresentallcriticalcaseswheretheconnectionislikelytobedroppedifhandoverisnotperformed.ResourceoptimisationhandoverThereasonforrequestinghandoveristoimprovetheloaddistributionwiththeneighbourcells.ReduceloadinservingcellLoadonservingcellneedstobereduced.Whenappliedtohandoverpreparation,itindicatesthehandoveristriggeredduetoloadbalancing.UserinactivityTheactionisrequestedduetouserinactivityonallPDUsessions,e.g.,NGisrequestedtobereleasedinordertooptimisetheradioresources.RadioconnectionwithUElostTheactionisrequestedduetolosingtheradioconnectiontotheUE.RadioresourcesnotavailableNorequestedradioresourcesareavailable.InvalidQoScombinationTheactionwasfailedbecauseofinvalidQoScombination.FailureintheradiointerfaceprocedureRadiointerfaceprocedurehasfailed.InteractionwithotherprocedureTheactionisduetoanongoinginteractionwithanotherprocedure.UnknownPDUSessionIDTheactionfailedbecausethePDUSessionIDisunknownintheNG-RANnode.UnknownQoSFlowIDTheactionfailedbecausetheQoSFlowIDisunknownintheNG-RANnode.MultiplePDUSessionIDinstancesTheactionfailedbecausemultipleinstanceofthesamePDUSessionhadbeenprovidedto/fromtheNG-RANnode.MultipleQoSFlowIDinstancesTheactionfailedbecausemultipleinstancesofthesameQoSflowhadbeenprovidedtotheNG-RANnode.Encryptionand/orintegrityprotectionalgorithmsnotsupportedTheNG-RANnodeisunabletosupportanyoftheencryptionand/orintegrityprotectionalgorithmssupportedbytheUE.NGintra-systemhandovertriggeredTheactionisduetoaNGintra-systemhandoverthathasbeentriggered.NGinter-systemhandovertriggeredTheactionisduetoaNGinter-systemhandoverthathasbeentriggered.XnhandovertriggeredTheactionisduetoanXnhandoverthathasbeentriggered.Notsupported5QIvalueTheQoSflowsetupfailedbecausetherequested5QIisnotsupported.UEcontexttransferTheactionisduetoaUEresumesfromtheNG-RANnodedifferentfromtheonewhichsenttheUEintoRRC_INACTIVEstate.IMSvoiceEPSfallbackorRATfallbacktriggeredThesetupofQoSflowisfailedduetoEPSfallbackorRATfallbackforIMSvoiceusinghandoverorredirection.UPintegrityprotectionnotpossibleThePDUsessioncannotbeacceptedaccordingtotherequireduserplaneintegrityprotectionpolicy.UPconfidentialityprotectionnotpossibleThePDUsessioncannotbeacceptedaccordingtotherequireduserplaneconfidentialityprotectionpolicy.Slice(s)notsupportedSlice(s)notsupported.UEinRRC_INACTIVEstatenotreachableTheactionisrequestedduetoRANpagingfailure.RedirectionThereleaseisrequestedduetointer-systemredirectionorintra-systemredirection.Resourcesnotavailablefortheslice(s)Therequestedresourcesarenotavailablefortheslice(s).UEmaximumintegrityprotecteddataratereasonTherequestisnotacceptedinordertocomplywiththemaximumdatarateforintegrityprotectionsupportedbytheUE.ReleaseduetoCN-detectedmobilityThecontextreleaseisrequestedbytheAMFbecausetheUEisalreadyservedbyanotherCNnode(sameordifferentsystem),oranotherNGinterfaceofthesameCNnode.N26interfacenotavailableTheactionfailedduetoatemporaryfailureoftheN26interface.Releaseduetopre-emptionReleaseisinitiatedduetopre-emption.MultipleLocationReportingReferenceIDInstancesTheactionfailedbecausemultipleareasofinterestaresetwiththesameLocationReportingReferenceID.TransportLayercauseMeaningTransportresourceunavailableTherequiredtransportresourcesarenotavailable.UnspecifiedSentwhennoneoftheabovecausevaluesappliesbutstillthecauseisTransportNetworkLayerrelated.NAScauseMeaningNormalreleaseThereleaseisnormal.AuthenticationfailureTheactionisduetoauthenticationfailure.DeregisterTheactionisduetoderegister.UnspecifiedSentwhennoneoftheabovecausevaluesappliesbutstillthecauseisNASrelated.ProtocolcauseMeaningTransfersyntaxerrorThereceivedmessageincludedatransfersyntaxerror.Abstractsyntaxerror(reject)Thereceivedmessageincludedanabstractsyntaxerrorandtheconcerningcriticalityindicated"reject".Abstractsyntaxerror(ignoreandnotify)Thereceivedmessageincludedanabstractsyntaxerrorandtheconcerningcriticalityindicated"ignoreandnotify".MessagenotcompatiblewithreceiverstateThereceivedmessagewasnotcompatiblewiththereceiverstate.SemanticerrorThereceivedmessageincludedasemanticerror.Abstractsyntaxerror(falselyconstructedmessage)ThereceivedmessagecontainedIEsorIEgroupsinwrongorderorwithtoomanyoccurrences.UnspecifiedSentwhennoneoftheabovecausevaluesappliesbutstillthecauseisProtocolrelated.MiscellaneouscauseMeaningControlprocessingoverloadControlprocessingoverload.NotenoughuserplaneprocessingresourcesNotenoughresourcesareavailablerelatedtouserplaneprocessing.HardwarefailureActionrelatedtohardwarefailure.O&MinterventionTheactionisduetoO&Mintervention.UnknownPLMNTheAMFdoesnotidentifyanyPLMNprovidedbytheNG-RANnode.UnspecifiedfailureSentwhennoneoftheabovecausevaluesappliesandthecauseisnotrelatedtoanyofthecategoriesRadioNetworkLayer,TransportNetworkLayer,NASorProtocol.XN口消息原因值定义参见3GPP协议38423~ThepurposeoftheCauseIEistoindicatethereasonforaparticulareventfortheXnAPprotocol.IE/GroupNamePresenceRangeIETypeandReferenceSemanticsDescriptionCHOICECauseGroupM>RadioNetworkLayer>>RadioNetworkLayerCauseMENUMERATED

(CellnotAvailable,HandoverDesirableforRadioReasons,HandoverTargetnotAllowed,InvalidAMFSetID,NoRadioResourcesAvailableinTargetCell,PartialHandover,ReduceLoadinServingCell,ResourceOptimisationHandover,TimeCriticalHandover,TXnRELOCoverallExpiry,TXnRELOCprepExpiry,UnknownGUAMIID,UnknownLocalNG-RANnodeUEXnAPID,InconsistentRemoteNG-RANnodeUEXnAPID,EncryptionAnd/OrIntegrityProtectionAlgorithmsNotSupported,ProtectionAlgorithmsNotSupported,MultiplePDUSessionIDInstances,UnknownPDUSessionID,UnknownQoSFlowID,MultipleQoSFlowIDInstances,SwitchOffOngoing,Notsupported5QIvalue,TXnDCoverallExpiry,TXnDCprepExpiry,ActionDesirableforRadioReasons,ReduceLoad,ResourceOptimisation,TimeCriticalaction,TargetnotAllowed,NoRadioResourcesAvailable,InvalidQoScombination,EncryptionAlgorithmsNotSupported,Procedurecancelled,RRMpurpose,ImproveUserBitRate,UserInactivity,RadioConnectionWithUELost,FailureintheRadioInterfaceProcedure,BearerOptionnotSupported,UPintegrityprotectionnotpossible,UPconfidentialityprotectionnotpossible,Resourcesnotavailablefortheslice(s),UEMaximumintegrityprotecteddataratereason,CPIntegrityProtectionFailure,UPIntegrityProtectionFailure,Slice(s)notsupportedbyNG-RAN,MNMobility,SNMobility,Countreachesmaxvalue,UnknownOldNG-RANnodeUEXnAPID,PDCPOverload,DRBIDnotavailable,Unspecified,…,UEContextIDnotknown,Non-relocationofcontext,CHO-CPCresourcestobechanged,RSNnotavailablefortheUP,NPNaccessdenied)>TransportLayer>>TransportLayerCauseMENUMERATED

(TransportResourceUnavailable,Unspecified,

…)>Protocol>>ProtocolCauseMENUMERATED

(TransferSyntaxError,

AbstractSyntaxError(Reject),

AbstractSyntaxError(IgnoreandNotify),

MessagenotCompatiblewithReceiverState,SemanticError,AbstractSyntaxError(FalselyConstructedMessage),Unspecified,…)>Misc>>MiscellaneousCauseMENUMERATED

(ControlProcessingOverload,

HardwareFailure,O&MIntervention,NotenoughUserPlaneProcessingResources,Unspecified,…)Themeaningofthedifferentcausevaluesisspecifiedinthefollowingtable.Ingeneral,“notsupported”causevaluesindicatethattherelatedcapabilityismissing.Ontheotherhand,“notavailable”causevaluesindicatethattherelatedcapabilityispresent,butinsufficientresourceswereavailabletoperformtherequestedaction.RadioNetworkLayercauseMeaningCellnotAvailableTheconcernedcellisnotavailable.HandoverDesirableforRadioReasonsThereasonforrequestinghandoverisradiorelated.HandoverTargetnotAllowedHandovertotheindicatedtargetcellisnotallowedfortheUEinquestion.InvalidAMFSetIDThetargetNG-RANnodedoesn’tbelongtothesameAMFSetofthesourceNG-RANnode,i.e.NGhandoversshouldbeattemptedinstead.NoRadioResourcesAvailableinTargetCellThetargetcelldoesn’thavesufficientradioresourcesavailable.PartialHandoverProvidesareasonforthehandovercancellation.Thetarg