ProductTypeTechnicalProposal第. 正常情況下，某個小區周邊都存在鄰區，如果無線環境不是很差，都可以通過切換的方式改變服務小區。當某個站點缺失鄰區或者鄰區添加不合理，會導致無法切換出而掉死。因此處理掉線率較高的小區時，需要核查鄰區配置是否合理。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消息，造成切換準備失敗。切換出準備失敗，源側重建立通常是由于無線覆蓋質差導致，需要重點核查干擾、弱覆蓋、超遠覆蓋和重疊覆蓋?！銮袚Q出準備失敗，等待切換響應定時器超時在切換過程中，由于源gNodeB等待HandoverRequestAck消息定時器超時，造成切換出準備失敗。切換出準備失敗，等待切換響應定時器超時通常是由于TAC插花、外部鄰區參數配置和小區實際配置不一致、XN或是NG鏈路故障。需要重點核查TAC插花、外部鄰區參數配置、XN/NG鏈路是否丟包。■切換出準備失敗次數，目標側資源不足在切換過程中由于目標側資源準備不足，造成切換出準備失敗。切換出準備失敗，目標側資源不足通常和目標側負荷（用戶數、CPU利用率）、小區Cellbar、基站內部處理異常相關。該種原因如果目標側RRC連接最大用戶數<50、CPU利用率<60%且無Cellbar配置的情況下，建議提故障單轉研發做進一步排查。另外需關注：高鐵站點在V5.35.30之前的版本如果開啟周期性MR會導致切換過程中目標側資源不足的情況發生，建議V5.35.30之前的版本不要開啟周期性MR?！銮袚Q出準備失敗次數，其它原因除以上原因外，導致的切換出準備失敗。其它原因的準備失敗，在核查完外部鄰區參數配置，如果配置正確需要跟蹤信令確定問題現象，上報第一響應組協助進行分析?！銮袚Q出執行失敗次數，源側發生重建立在切換過程中，由于gNodeB在源小區或源gNodeB站內其他小區接收到UE的RRCReestablishmentReques消息或者接收到其他gNodeB發送的XnRetrieveUeContextRequest消息，造成切換出執行失敗。切換出執行失敗次數，源側發生重建立可能是由于切換CIO配置不合理（建議-3dB~3dB）、覆蓋問題（弱覆蓋、重疊覆蓋、超遠覆蓋）、干擾、鄰區漏配。TOP小區處理時建議根據信令判斷發生切換失敗發生時是否是在弱場、是否存在鄰區漏配、測量參數是否不合理?！銮袚Q出執行失敗次數，等待UECONTEXTRELEASE消息超時在切換過程中，由于源gNodeB等待目標側小區的UEContextRelease定時器超時，造成切換出執行失敗?！銮袚Q出執行失敗次數，其它原因統計發生除以上原因以外導致從gNodeB切換出執行失敗，需要跟蹤信令確認問題現象再做針對性的分析優化。切換成功率低處理思路切換過程中包含切換準備階段，與切換執行階段，2個階段涉及到的因素各不一樣，因此需要分開來處理。切換準備失敗，多由外部鄰小區參數配置錯誤（鄰區配置正確）或者切換準備目標基站故障引起。切換執行失敗，發生在切換命令下發后，終端執行時失敗，與無線環境，鄰區配置的合理性強相關。對于整網切換成功率較低的網絡，需要先分析切換準備與執行那個導致的失敗次數較多，再按TOP小區針對分析處理。■切換準備失敗處理切換準備失敗需要提取切換準備相關的計數器分解，查看具體的準備失敗原因。切換準備失敗主要關注鄰區參數的正確性，具體包括：切換準備失敗需要定期核查現網鄰區數據,保證數據的有效與準確；現網中鄰區參數配置錯誤的，如外部小區定義中與鄰接基站定義不一致的；定期提取規劃數據，進行核查；現網中對異廠家站點鄰區定義錯誤的，需定期索取異常家工參核查；現網中鄰區基站ID錯誤的，即不存在于異廠家網管，也不存在與中興網管中的鄰區關系。需要刪除這類鄰區數據；定期核查現網中超遠鄰區關系，以2KM為界，對于超遠鄰區且切換成功率<50%的鄰區對暫時刪除?！銮袚Q出執行失敗處理切換執行階段失敗同樣需要提取切換準備相關的計數器分解，查看具體的執行失敗原因。切換出執行失敗次數>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配置不一致，修改后問題解決。網管截圖：修改后指標統計：小區切換正常參考資料5GKPI集團規范（中移）地址鏈接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=83342245GKPI指標定義地址連接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=88864215G干擾排查指導書地址鏈接：/tsm/FileCenter/File.aspx?Mode=read&FileID=307110605G無線參數規劃操作指導書地址鏈接/UDM/Application/DocManage/FrmDocumentView.aspx?docId=7243721等待PDUSession超時問題說明地址鏈接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=8882314MSG不下發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-R