中興5G SA常見KPI優(yōu)化指導(dǎo)書

ProductTypeTechnicalProposal第. 正常情況下，某個小區(qū)周邊都存在鄰區(qū)，如果無線環(huán)境不是很差，都可以通過切換的方式改變服務(wù)小區(qū)。當(dāng)某個站點缺失鄰區(qū)或者鄰區(qū)添加不合理，會導(dǎo)致無法切換出而掉死。因此處理掉線率較高的小區(qū)時，需要核查鄰區(qū)配置是否合理。3. 核查小區(qū)是否存在超遠覆蓋，導(dǎo)致覆蓋孤島，無法切換到周邊鄰區(qū)?？梢酝ㄟ^后臺跟蹤信令，觀察測量報告，并補齊漏配的鄰區(qū)。隨后需要對覆蓋進行控制。4. 對于因弱覆蓋導(dǎo)致掉線，若終端處于覆蓋邊緣，周圍無可用的NR小區(qū)，可以添加系統(tǒng)間鄰區(qū)，使用切換到4G的方式，減少掉線次數(shù)。但門限設(shè)置需要合理，不能太容易去到4G。無線掉線案例解析等待PDUSession超時導(dǎo)致異常釋放針對GNB由于其它原因引發(fā)釋放，篩選TOP小區(qū)跟蹤信令，結(jié)合信令和CPA打印，基本可以確認其它原因的上下文釋放主要是由于接入過程核心網(wǎng)在初始上下文建立請求消息中沒有攜帶PduSessionResourceSetupIE，導(dǎo)致基站側(cè)等核心網(wǎng)的pdusession建立10s超時，觸發(fā)了上下文釋放。該種釋放和無線無關(guān)，和終端和核心網(wǎng)處理相關(guān)，在V5.35.301130及之后的版本新增了計數(shù)器“C600050034:Context釋放次數(shù)，GNB由于等待核心網(wǎng)消息超時”，該種原因不再計為異常釋放。FOA區(qū)域版本升級后，無線掉線率由0.11%下降到0.39%，其它原因引發(fā)的釋放次數(shù)由1780次下降到338次。系統(tǒng)內(nèi)切換成功率系統(tǒng)內(nèi)切換失敗原因解析切換失敗原因包括切換出準(zhǔn)備失敗和切換出執(zhí)行失敗，具體詳見下表：指標(biāo)或計數(shù)器指標(biāo)或計數(shù)器描述C600100002gNB間Xn同頻切換出準(zhǔn)備失敗次數(shù)，源側(cè)發(fā)生重建立C600100003gNB間Xn同頻切換出準(zhǔn)備失敗次數(shù)，等待切換響應(yīng)定時器超時C600100004gNB間Xn同頻切換出準(zhǔn)備失敗次數(shù)，目標(biāo)側(cè)資源不足C600100005gNB間Xn同頻切換出準(zhǔn)備失敗次數(shù)，其它原因C600100007gNB間Xn同頻切換出執(zhí)行失敗次數(shù)，源側(cè)發(fā)生重建立C600100008gNB間Xn同頻切換出執(zhí)行失敗次數(shù)，等待UECONTEXTRELEASE消息超時C600100009gNB間Xn同頻切換出執(zhí)行失敗次數(shù)，其它原因C600110002gNB間Ng同頻切換出準(zhǔn)備失敗次數(shù)，等待切換響應(yīng)定時器超時C600110003gNB間Ng同頻切換出準(zhǔn)備失敗次數(shù)，目標(biāo)側(cè)資源不足C600110004gNB間Ng同頻切換出準(zhǔn)備失敗次數(shù)，源側(cè)發(fā)生重建立C600110005gNB間Ng同頻切換出準(zhǔn)備失敗次數(shù)，其它原因C600110007gNB間Ng同頻切換出執(zhí)行失敗次數(shù)，源側(cè)發(fā)生重建立C600110008gNB間Ng同頻切換出執(zhí)行失敗次數(shù)，等待UECONTEXTRELEASE消息超時C600110009gNB間Ng同頻切換出執(zhí)行失敗次數(shù)，其它原因C600120005gNB內(nèi)DU內(nèi)小區(qū)間同頻切換出執(zhí)行失敗次數(shù)，RRC重配完成超時C600120006gNB內(nèi)DU內(nèi)小區(qū)間同頻切換出執(zhí)行失敗次數(shù)，源側(cè)發(fā)生重建立C600120007gNB內(nèi)DU內(nèi)小區(qū)間同頻切換出執(zhí)行失敗次數(shù)，其它原因■切換出準(zhǔn)備失敗，源側(cè)發(fā)生重建立在切換過程中，由于gNodeB在源小區(qū)或源gNodeB站內(nèi)其他小區(qū)接收到UE的RRCReestablishmentRequest消息或者接收到其他gNodeB發(fā)送的XnRetrieveUeContextRequest消息，造成切換準(zhǔn)備失敗。切換出準(zhǔn)備失敗，源側(cè)重建立通常是由于無線覆蓋質(zhì)差導(dǎo)致，需要重點核查干擾、弱覆蓋、超遠覆蓋和重疊覆蓋?！銮袚Q出準(zhǔn)備失敗，等待切換響應(yīng)定時器超時在切換過程中，由于源gNodeB等待HandoverRequestAck消息定時器超時，造成切換出準(zhǔn)備失敗。切換出準(zhǔn)備失敗，等待切換響應(yīng)定時器超時通常是由于TAC插花、外部鄰區(qū)參數(shù)配置和小區(qū)實際配置不一致、XN或是NG鏈路故障。需要重點核查TAC插花、外部鄰區(qū)參數(shù)配置、XN/NG鏈路是否丟包?！銮袚Q出準(zhǔn)備失敗次數(shù)，目標(biāo)側(cè)資源不足在切換過程中由于目標(biāo)側(cè)資源準(zhǔn)備不足，造成切換出準(zhǔn)備失敗。切換出準(zhǔn)備失敗，目標(biāo)側(cè)資源不足通常和目標(biāo)側(cè)負荷（用戶數(shù)、CPU利用率）、小區(qū)Cellbar、基站內(nèi)部處理異常相關(guān)。該種原因如果目標(biāo)側(cè)RRC連接最大用戶數(shù)<50、CPU利用率<60%且無Cellbar配置的情況下，建議提故障單轉(zhuǎn)研發(fā)做進一步排查。另外需關(guān)注：高鐵站點在V5.35.30之前的版本如果開啟周期性MR會導(dǎo)致切換過程中目標(biāo)側(cè)資源不足的情況發(fā)生，建議V5.35.30之前的版本不要開啟周期性MR?！銮袚Q出準(zhǔn)備失敗次數(shù)，其它原因除以上原因外，導(dǎo)致的切換出準(zhǔn)備失敗。其它原因的準(zhǔn)備失敗，在核查完外部鄰區(qū)參數(shù)配置，如果配置正確需要跟蹤信令確定問題現(xiàn)象，上報第一響應(yīng)組協(xié)助進行分析?！銮袚Q出執(zhí)行失敗次數(shù)，源側(cè)發(fā)生重建立在切換過程中，由于gNodeB在源小區(qū)或源gNodeB站內(nèi)其他小區(qū)接收到UE的RRCReestablishmentReques消息或者接收到其他gNodeB發(fā)送的XnRetrieveUeContextRequest消息，造成切換出執(zhí)行失敗。切換出執(zhí)行失敗次數(shù)，源側(cè)發(fā)生重建立可能是由于切換CIO配置不合理（建議-3dB~3dB）、覆蓋問題（弱覆蓋、重疊覆蓋、超遠覆蓋）、干擾、鄰區(qū)漏配。TOP小區(qū)處理時建議根據(jù)信令判斷發(fā)生切換失敗發(fā)生時是否是在弱場、是否存在鄰區(qū)漏配、測量參數(shù)是否不合理。■切換出執(zhí)行失敗次數(shù)，等待UECONTEXTRELEASE消息超時在切換過程中，由于源gNodeB等待目標(biāo)側(cè)小區(qū)的UEContextRelease定時器超時，造成切換出執(zhí)行失敗?！銮袚Q出執(zhí)行失敗次數(shù)，其它原因統(tǒng)計發(fā)生除以上原因以外導(dǎo)致從gNodeB切換出執(zhí)行失敗，需要跟蹤信令確認問題現(xiàn)象再做針對性的分析優(yōu)化。切換成功率低處理思路切換過程中包含切換準(zhǔn)備階段，與切換執(zhí)行階段，2個階段涉及到的因素各不一樣，因此需要分開來處理。切換準(zhǔn)備失敗，多由外部鄰小區(qū)參數(shù)配置錯誤（鄰區(qū)配置正確）或者切換準(zhǔn)備目標(biāo)基站故障引起。切換執(zhí)行失敗，發(fā)生在切換命令下發(fā)后，終端執(zhí)行時失敗，與無線環(huán)境，鄰區(qū)配置的合理性強相關(guān)。對于整網(wǎng)切換成功率較低的網(wǎng)絡(luò)，需要先分析切換準(zhǔn)備與執(zhí)行那個導(dǎo)致的失敗次數(shù)較多，再按TOP小區(qū)針對分析處理?！銮袚Q準(zhǔn)備失敗處理切換準(zhǔn)備失敗需要提取切換準(zhǔn)備相關(guān)的計數(shù)器分解，查看具體的準(zhǔn)備失敗原因。切換準(zhǔn)備失敗主要關(guān)注鄰區(qū)參數(shù)的正確性，具體包括：切換準(zhǔn)備失敗需要定期核查現(xiàn)網(wǎng)鄰區(qū)數(shù)據(jù),保證數(shù)據(jù)的有效與準(zhǔn)確；現(xiàn)網(wǎng)中鄰區(qū)參數(shù)配置錯誤的，如外部小區(qū)定義中與鄰接基站定義不一致的；定期提取規(guī)劃數(shù)據(jù)，進行核查；現(xiàn)網(wǎng)中對異廠家站點鄰區(qū)定義錯誤的，需定期索取異常家工參核查；現(xiàn)網(wǎng)中鄰區(qū)基站ID錯誤的，即不存在于異廠家網(wǎng)管，也不存在與中興網(wǎng)管中的鄰區(qū)關(guān)系。需要刪除這類鄰區(qū)數(shù)據(jù)；定期核查現(xiàn)網(wǎng)中超遠鄰區(qū)關(guān)系，以2KM為界，對于超遠鄰區(qū)且切換成功率<50%的鄰區(qū)對暫時刪除?！銮袚Q出執(zhí)行失敗處理切換執(zhí)行階段失敗同樣需要提取切換準(zhǔn)備相關(guān)的計數(shù)器分解，查看具體的執(zhí)行失敗原因。切換出執(zhí)行失敗次數(shù)>10次且切換成功率=0的小區(qū)對，建議刪除同時開啟系統(tǒng)內(nèi)ANR功能對鄰區(qū)進行重新添加；切換出執(zhí)行失敗次數(shù)>10次且切換成功率<90%,首先核查切換目標(biāo)小區(qū)是否與周邊站點同頻同PCI，如果存在同頻同PCI小區(qū)，進行PCI重規(guī)劃；切換出執(zhí)行次數(shù)>10次且切換成功率<90%，核查目標(biāo)基站否存在上行干擾，如果存在上行干擾，即需要進行干擾排查。切換成失敗案例解析NGAP未配置導(dǎo)致切換失敗11579866-311向11579911發(fā)起HandoverRequired消息，目標(biāo)側(cè)（11579911）未收到HandoverRequest消息，AMF直接回復(fù)HandoverPreparationFailure消息（cause：ho_failure_in_target_5GC_ngran_node_or_target_system）導(dǎo)致NG切換準(zhǔn)備失敗。核查目標(biāo)側(cè)11579911的接入信令，目標(biāo)側(cè)收到RRCSetupComplete消息后未發(fā)送IntialUEMesseage給AMF，說明該小區(qū)接入存在異常。核查目標(biāo)側(cè)11579911NGSCTP和NGAP配置：NGSCTP配置以及狀態(tài)正常，NGAP未配置。添加NGAP配置后11579866-311向11579911切換恢復(fù)正常。源側(cè)和目標(biāo)側(cè)AMF配置不一致導(dǎo)致切換失敗【問題現(xiàn)象】XN口向目標(biāo)站點發(fā)送切換請求，目標(biāo)側(cè)回復(fù)Xnap_CauseRadioNetworkLayer_Root_invalid_AMF_Set_ID原因的準(zhǔn)備失敗，隨后向同一個目標(biāo)站點再發(fā)NG口的切換請求，并收到Ngap_CauseRadioNetwork_Root_ho_failure_in_target_5GC_ngran_node_or_target_system原因的切換準(zhǔn)備失敗?！驹蚍治觥酷槍@種準(zhǔn)備失敗的原因可能是目標(biāo)側(cè)與源側(cè)配置的AMF不一致，一般外場都會有多套AMF，全網(wǎng)所有的站點都需要將每條AMF配置全備，不然會出現(xiàn)切換準(zhǔn)備失敗的問題。切片配置錯誤導(dǎo)致無法切換【問題發(fā)現(xiàn)】多維分析-控制面分析--N1N2接口分析巡檢發(fā)現(xiàn)，較多次N2切換失敗，原因為 slice-not-supported，切片不支持，定界為無線【原因分析】通過下鉆小區(qū)分析，有多個小區(qū)存在N2切出失敗問題以MSISD例，經(jīng)信令回溯分析，用戶駐留小區(qū)LFSHQ1023利比玻璃-ZWH-2向基站gNB-ID為1069677發(fā)起切換，向AMF發(fā)起切換準(zhǔn)備請求NGAPHandoverRequired，AMF回復(fù)切換失敗消息，原因為切片不支持（slice-not-supported）。cell_id為4381396994協(xié)議分析，Slice(s)notsupported為NGSTEUP或者RANCONFIGURATIONUPDATE流程時，攜帶的切片AMF都不支持，可能是無線配置問題網(wǎng)元名稱:APP-HBBADheAMF001BZX-05AZX011

網(wǎng)元類型:AMF

網(wǎng)元ID:1090519041

節(jié)點IP:61&29&2409:800b:5003:1705::101網(wǎng)元名稱:APP-HBBADheSMF003BZX-05AZX012

網(wǎng)元類型:SMF

網(wǎng)元ID:1107296263

節(jié)點IP:2409:800b:5003:1705:1::301【問題解決】Slice(s)notsupported為NGSTEUP或者RANCONFIGURATIONUPDATE流程時，攜帶的切片AMF都不支持，可能是無線配置問題，查看小區(qū)LFSHQ1023利比玻璃-ZWH-2和基站gNB-ID為1069677其切片配置中tac與本小區(qū)tac配置不一致，修改后問題解決。網(wǎng)管截圖：修改后指標(biāo)統(tǒng)計：小區(qū)切換正常參考資料5GKPI集團規(guī)范（中移）地址鏈接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=83342245GKPI指標(biāo)定義地址連接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=88864215G干擾排查指導(dǎo)書地址鏈接：/tsm/FileCenter/File.aspx?Mode=read&FileID=307110605G無線參數(shù)規(guī)劃操作指導(dǎo)書地址鏈接/UDM/Application/DocManage/FrmDocumentView.aspx?docId=7243721等待PDUSession超時問題說明地址鏈接：/UDM/Application/DocManage/FrmDocumentView.aspx?DocId=8882314MSG不下發(fā)P0-Alpha問題說明NR相關(guān)定時器介紹參見協(xié)議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協(xié)議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協(xié)議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