【文章內(nèi)容簡介】
step when indicating “GUmmei type equal to native RRC接入成功率處理經(jīng)驗及流程根據(jù)之前處理RRC接入成功率的經(jīng)驗,RRC接入成功率主要從ENB問題、弱覆蓋、干擾、資源受限、license受限等方面來分析處理。總結(jié)處理經(jīng)驗及流程如下表:失敗階段原因查找失敗原因優(yōu)化建議RRC失敗檢查告警、小區(qū)可用性、RRU的狀態(tài)及VSWRENB問題根據(jù)告警原因解決告警RRC失敗通過地圖信息檢查周邊環(huán)境及站點分布弱覆蓋調(diào)整工參或者增加新站加強(qiáng)周邊覆蓋RRC失敗根據(jù)工參信息檢查受周邊小區(qū)干擾模3干擾調(diào)整工參或者PCI解決模3干擾RRC失敗檢查上行RSSI是否偏高上行干擾解決干擾問題RRC失敗檢查上行PRB的利用率PRB資源受限增加noOfPucchSrUsers,noOfPucchcqiUsers配置RRC失敗檢查connected user的license數(shù)量license受限建議客戶進(jìn)行l(wèi)icense擴(kuò)容RRC接入成功率優(yōu)化詳細(xì)流程及counter如下如: 4 S1 建立成功率 正常信令流程S1建立流程:l UE完成SRB1承載和無線資源配置,向eNB發(fā)送RRCConnectionSetupComplete消息,包含NAS層Attach request信息,Arrach request信息中攜帶了PLMN等信息。l eNB選擇MME,向MME發(fā)送INITIAL UE MESSAGE消息,此信息攜帶了UE標(biāo)示GUTI 或 IMSI。l MME向HSS發(fā)送鑒權(quán)請求后HSS回復(fù)鑒權(quán)需要的向量(Kasme, RAND, AUTN, XRES)。MME通過DL Information Transfer向UE發(fā)起鑒權(quán)請求。 指標(biāo)定義S1建立成功率是指UE完成RRC連接后NAS層信令建立的成功率。S1建立成功率=S1建立成功率次數(shù)/S1建立請求次數(shù)*100%=pmS1SigConnEstabSucc/pmS1SigConnEstabAtt*100% 詳細(xì)counter統(tǒng)計節(jié)點Signalling connection setup triggered by initial UE message UE Initial UE RBSmessageppmS1SigConnEstabAttEm +pmS1SigConnEstabAtt +step for cause ”Emergency”pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttEm +pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttMod +pmS1SigConnEstabAttMta +pmS1SigConnEstabAttMos +pmS1SigConnEstabAttDta +step for cause ”High Prio Access”pmS1SigConnEstabAttMod +step for cause ”Mobile Originating Data”pmS1SigConnEstabAttMta +step for cause ”Mobile Terminating Access”pmS1SigConnEstabAttMos +step for cause ”Mobile Originating Signalling”pmS1SigConnEstabAttDta +RBS timeout on initial context setup request from MME?step for cause ”Delay Tolerant Access” yesEnd signallingconnection setup NoMME sends initial context setup request to RBSRBS Initial context MMESetup request(ERABs, Sec keys)Any message received on the S1 logical connection? NO Stepped for any of the following pmS1SigConnEstabSucc +messages: Yes pmS1SigConnEstabSuccEm +S1 downlink NAS transport step for cause ”Emergency” S1 UE context release mand pmS1SigConnEstabSuccHpa +pmS1SigConnEstabAttEm +pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttMod +pmS1SigConnEstabAttMta +pmS1SigConnEstabAttMos +pmS1SigConnEstabAttDta +S1 initial context setup request step for cause ”High Prio Access”S1 reset pmS1SigConnEstabSuccMod + step for cause ”Mobile Originating Data”