KPI指標(biāo)處理指導(dǎo)辦法

1、96/96KPI指標(biāo)處理指導(dǎo)手冊(cè)目錄 TOC o 1-3 h z u HYPERLINK l _Toc409957251 1、無(wú)線接通率 PAGEREF _Toc409957251 h 2 HYPERLINK l _Toc409957252 1.1、指標(biāo)定義 PAGEREF _Toc409957252 h 3 HYPERLINK l _Toc409957253 1.2、RRC建立成功率分析 PAGEREF _Toc409957253 h 4 HYPERLINK l _Toc409957254 1.2.1、理論介紹 PAGEREF _Toc409957254 h 4 HYPERLINK l _T

2、oc409957255 1.2.2、正常信令流程 PAGEREF _Toc409957255 h 4 HYPERLINK l _Toc409957256 1.2.3、指標(biāo)定義 PAGEREF _Toc409957256 h 5 HYPERLINK l _Toc409957257 1.2.4、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn) PAGEREF _Toc409957257 h 5 HYPERLINK l _Toc409957258 1.2.5、RRC接入成功率處理經(jīng)驗(yàn)及流程 PAGEREF _Toc409957258 h 7 HYPERLINK l _Toc409957259 1.3、S1建立成功率 PA

3、GEREF _Toc409957259 h 9 HYPERLINK l _Toc409957260 1.3.1、正常信令流程 PAGEREF _Toc409957260 h 9 HYPERLINK l _Toc409957261 1.3.2、指標(biāo)定義 PAGEREF _Toc409957261 h 9 HYPERLINK l _Toc409957262 1.3.3、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn) PAGEREF _Toc409957262 h 10 HYPERLINK l _Toc409957263 1.3.4、S1建立成功率處理經(jīng)驗(yàn)及流程 PAGEREF _Toc409957263 h 10 H

4、YPERLINK l _Toc409957264 1.4、ERAB建立成功率分析 PAGEREF _Toc409957264 h 11 HYPERLINK l _Toc409957265 1.4.1、正常信令流程 PAGEREF _Toc409957265 h 11 HYPERLINK l _Toc409957266 1.4.2、指標(biāo)定義 PAGEREF _Toc409957266 h 12 HYPERLINK l _Toc409957267 1.4.3、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn) PAGEREF _Toc409957267 h 12 HYPERLINK l _Toc409957268 1.4

5、.4、ERAB建立成功率處理經(jīng)驗(yàn)及流程 PAGEREF _Toc409957268 h 13 HYPERLINK l _Toc409957269 1.5、相關(guān)案例 PAGEREF _Toc409957269 h 13 HYPERLINK l _Toc409957270 1.5.1、PRB資源受限 PAGEREF _Toc409957270 h 13 HYPERLINK l _Toc409957271 1.5.2、告警導(dǎo)致接入成功率低 PAGEREF _Toc409957271 h 15 HYPERLINK l _Toc409957272 1.5.3、GPS故障導(dǎo)致接入成功率低 PAGEREF

6、_Toc409957272 h 16 HYPERLINK l _Toc409957273 1.5.4、天線接反導(dǎo)致模3干擾 PAGEREF _Toc409957273 h 18 HYPERLINK l _Toc409957274 2、掉線率 PAGEREF _Toc409957274 h 20 HYPERLINK l _Toc409957275 2.1、理論介紹 PAGEREF _Toc409957275 h 20 HYPERLINK l _Toc409957276 2.2、正常信令流程 PAGEREF _Toc409957276 h 20 HYPERLINK l _Toc409957277

7、2.3、指標(biāo)定義 PAGEREF _Toc409957277 h 20 HYPERLINK l _Toc409957278 2.4、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn) PAGEREF _Toc409957278 h 21 HYPERLINK l _Toc409957279 2.5、掉線率處理經(jīng)驗(yàn)及流程 PAGEREF _Toc409957279 h 21 HYPERLINK l _Toc409957280 2.6、相關(guān)案例 PAGEREF _Toc409957280 h 22 HYPERLINK l _Toc409957281 2.6.1、高上行干擾導(dǎo)致高掉線率 PAGEREF _Toc4099572

8、81 h 22 HYPERLINK l _Toc409957282 2.6.2、駐波告警導(dǎo)致高掉線率 PAGEREF _Toc409957282 h 23 HYPERLINK l _Toc409957283 3、切換成功率 PAGEREF _Toc409957283 h 24 HYPERLINK l _Toc409957284 3.1、理論介紹 PAGEREF _Toc409957284 h 24 HYPERLINK l _Toc409957285 3.2、正常信令流程 PAGEREF _Toc409957285 h 24 HYPERLINK l _Toc409957286 3.2.1、站內(nèi)切

9、換正常信令流程 PAGEREF _Toc409957286 h 24 HYPERLINK l _Toc409957287 3.2.2、X2切換正常信令流程 PAGEREF _Toc409957287 h 25 HYPERLINK l _Toc409957288 3.2.3、S1切換正常信令流程 PAGEREF _Toc409957288 h 26 HYPERLINK l _Toc409957289 3.3、指標(biāo)定義 PAGEREF _Toc409957289 h 27 HYPERLINK l _Toc409957290 3.4、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn) PAGEREF _Toc4099572

10、90 h 28 HYPERLINK l _Toc409957291 3.5、切換成功率處理經(jīng)驗(yàn)及流程 PAGEREF _Toc409957291 h 29 HYPERLINK l _Toc409957292 3.6、相關(guān)案例 PAGEREF _Toc409957292 h 31 HYPERLINK l _Toc409957293 3.6.1、鄰區(qū)PCI沖突 PAGEREF _Toc409957293 h 31 HYPERLINK l _Toc409957294 3.6.2、弱覆蓋 PAGEREF _Toc409957294 h 32 HYPERLINK l _Toc409957295 3.6.

11、3、模3干擾 PAGEREF _Toc409957295 h 33 HYPERLINK l _Toc409957296 3.6.4、目標(biāo)小區(qū)高上行干擾 PAGEREF _Toc409957296 h 35 HYPERLINK l _Toc409957297 3.6.5、漏加鄰區(qū)與現(xiàn)有鄰區(qū)PCI沖突 PAGEREF _Toc409957297 h 36 HYPERLINK l _Toc409957298 3.6.6、ENBID配置錯(cuò)誤 PAGEREF _Toc409957298 h 37 HYPERLINK l _Toc409957299 3.6.7、室分向宏站切換問(wèn)題 PAGEREF _Toc

12、409957299 h 38 HYPERLINK l _Toc409957300 4、KPI指標(biāo)相關(guān)counter PAGEREF _Toc409957300 h 39無(wú)線接通率無(wú)線接通率可以統(tǒng)計(jì)UE成功接入LTE網(wǎng)絡(luò)的性能。無(wú)線接入主要發(fā)生在開(kāi)機(jī)附著、異系統(tǒng)重選回LTE、位置更新、收到pagging等過(guò)程中，無(wú)線接入是用戶使用LTE網(wǎng)絡(luò)的前提。無(wú)線接通率由RRC建立成功率、S1建立成功率和ERAB建立成功率3部分構(gòu)成。1.1、指標(biāo)定義無(wú)線接通率= RRC建立成功率*ERAB建立成功率*100%。RRC建立成功率=RRC接入成功率次數(shù)/RRC接入嘗試次數(shù)*100% =pmRrcConnEsta

13、bSucc/pmRrcConnEstabSucc*100%ERAB建立成功率=ERAB建立成功率次數(shù)/ERAB建立嘗試次數(shù)*100% =(PmErabEstabSuccInit+PmErabEstabSuccAdded)/(PmErabEstabAttInit+PmErabEstabAttAdded)*100%1.2、RRC建立成功率分析1.2.1、理論介紹RRC連接建立過(guò)程分為兩個(gè)階段：準(zhǔn)備階段和實(shí)施階段。在準(zhǔn)備階段中，UE會(huì)根據(jù)NAS 層的觸發(fā)原因和系統(tǒng)廣播中的接入限制信息，通過(guò)一系列檢查來(lái)判斷自己是否被允許進(jìn)行接入過(guò)程，如果可以，則執(zhí)行后續(xù)的實(shí)施階段；否則UE的RRC將啟動(dòng)相應(yīng)的定時(shí)器，

14、在該定時(shí)器超時(shí)前UE無(wú)法發(fā)起任何接入過(guò)程。上述機(jī)制的目的是負(fù)荷擁塞控制，當(dāng)網(wǎng)絡(luò)負(fù)荷較重時(shí)限制某些UE進(jìn)行接入1.2.2、正常信令流程RRC建立流程如下圖所示，其中紅點(diǎn)處為RRC建立重要counter（PmRrcConnEstabAtt和pmRrcConnEstabSucc）統(tǒng)計(jì)節(jié)點(diǎn)。RRC 建立觸發(fā)原因：IDLE態(tài)UE需變?yōu)檫B接態(tài)時(shí)發(fā)起該過(guò)程，如呼叫、響應(yīng)尋呼、TAU、Attach等。RRC連接建立成功流程RRC連接請(qǐng)求：UE通過(guò)UL_CCCH在SRB0上發(fā)送，攜帶UE的初始（NAS）標(biāo)識(shí)和建立原因等，該消息對(duì)應(yīng)于隨機(jī)接入過(guò)程的Msg3RRC連接建立：eNB通過(guò)DL_CCCH在SRB0上發(fā)送，

15、攜帶SRB1的完整配置信息，該消息對(duì)應(yīng)隨機(jī)接入過(guò)程的Msg4RRC連接建立完成：UE通過(guò)UL-DCCH在SRB1上發(fā)送，攜帶上行方向NAS消息，如Attach Request、TAU Request、Service Request、Detach Request等，eNB根據(jù)這些消息進(jìn)行S1口建立RRC連接重建立拒絕流程第二步中，如果eNB中沒(méi)有UE的上下文信息，則拒絕為UE重建RRC連接，則通過(guò)DL_CCCH在SRB0上回復(fù)一條RRC連接重建立拒絕消息1.2.3、指標(biāo)定義RRC連接建立是指處于空閑狀態(tài)的UE或待開(kāi)機(jī)的UE準(zhǔn)備發(fā)起一個(gè)呼叫或響應(yīng)尋呼時(shí)發(fā)起的過(guò)程。處于降低接入時(shí)延的考慮，LTE系統(tǒng)

16、將RRC連接建立過(guò)程設(shè)計(jì)發(fā)生在ENB和MME之間的S1連接建立前，也就是在ENB尚未從MME獲得任何UE上下文前，ENB需要將RRC連接建立完畢，因此該過(guò)程主要建立最基本的SRB1。RRC連接建立成功意味著UE與網(wǎng)絡(luò)建立了信令連接，是進(jìn)行其他業(yè)務(wù)的基礎(chǔ)。RRC建立成功率公式：RRC建立成功率=RRC接入成功率次數(shù)/RRC接入嘗試次數(shù)*100% =pmRrcConnEstabSucc/pmRrcConnEstabSucc*100%指標(biāo)指標(biāo)描述RRC連接請(qǐng)求次數(shù)小區(qū)接收UE的RRC Connection Request消息次數(shù)（不包括重發(fā)）RRC連接建立完成次數(shù)小區(qū)接收UE返回的RRC Conne

17、ction Setup Complete消息次數(shù)RRC建立失敗次數(shù)資源分配失敗而導(dǎo)致連接建立失敗的次數(shù)UE無(wú)應(yīng)答而導(dǎo)致連接建立失敗的次數(shù)小區(qū)發(fā)送RRC Connection Reject消息次數(shù)1.2.4、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn)RRC建立成功率相關(guān)主要counter統(tǒng)計(jì)節(jié)點(diǎn)如下圖所示：Random accessRRC connection setup is triggered byUERRC connectionRBSRRC connection request messagerequestpmRrcConnEstabAtt +RRC connectionYessetup already

18、ongoingfor the sameS-TMSI or RandomValue?NopmRrcConnEstabAttEmstep for cause EmergencypmRrcConnEstabAttHpapmRrcConnEstabAttEm +step for cause High Prio AccesspmRrcConnEstabAttHpa +pmRrcConnEstabAttMtapmRrcConnEstabAttMta +step for cause Mobile Terminating AccesspmRrcConnEstabAttMos +pmRrcConnEstabAt

19、tMospmRrcConnEstabAttMod +step for cause Mobile Originating SignalingpmRrcConnEstabAttModstep for cause Mobile Originating DatapmRrcConnEstabAttreattEmpmRrcConnEstabAttReatt +step for cause EmergencypmRrcConnEstabAttReattHpastep for cause High Prio AccesspmRrcConnEstabAttReattEm +pmRrcConnEstabAttRe

20、attMtapmRrcConnEstabAttReattHpa +step for cause Mobile Terminating AccesspmRrcConnEstabAttReattMta +pmRrcConnEstabAttReattMospmRrcConnEstabAttReattMos +step for cause Mobile Originating SignalingpmRrcConnEstabAttReattMod +pmRrcConnEstabAttReattModstep for cause Mobile Originating DataAL0000311GA ACh

21、eck with license controlCheck with license control(number of connected users)pmRrcConnEstabFailLic +Successful license control?pmRrcConnEstabFailLic +Successful license control? Yes UE RRC connection RBSpmRrcConnEstabFailHighLoad + or pmRrcConnEstabFailOverload +High load or pmRrcConnEstabFailHighLo

22、ad + or pmRrcConnEstabFailOverload +High load or Overload? NoAll UEs bearers rejected during All UEs bearers rejected during beare admission?pmRrcConnEstabFailBpmRrcConnEstabFailBeareAdmissionRej+RRC connrequest rejecte? No UE RRC connection RRC connrequest rejecte?reject UE RRC connection RBS No st

23、up UE RRC connection RBSpmRrcConnEstabSucc+ SpmRrcConnEstabSucc+ pmRrcConnEstabSuccEm +pmRrcConnEstabpmRrcConnEstabSuccEm +pmRrcConnEstabSuccHpa +pmRrcConnEstabSuccMta +pmRrcConnEstabSuccMos +pmRrcConnEstabSuccMod +pmRrcConnEstabSuccDta +pmRrcConnEstabSuccGummeiNative + step for cause ”Emergency” pm

24、RrcConnEstabSuccHpa + step for cause ”High Prio Access” pmRrcConnEstabSuccMta + step for cause ”Mobile Terminating Access” pmRrcConnEstabSuccMos + step for cause ”Mobile Originating Signaling pmRrcConnEstabSuccMod + step for cause ”Mobile Originating Data” pmRrcConnEstabSuccDta+ step for cause “Dela

25、y Tolerant Access” pmRrcConnEstabSuccGummeiNative step when indicating “GUmmei type equal to nativeEnd RRC connection setup End RRC connection setup 1.2.5、RRC接入成功率處理經(jīng)驗(yàn)及流程根據(jù)之前處理RRC接入成功率的經(jīng)驗(yàn)，RRC接入成功率主要從ENB問(wèn)題、弱覆蓋、干擾、資源受限、license受限等方面來(lái)分析處理。總結(jié)處理經(jīng)驗(yàn)及流程如下表：失敗階段原因查找失敗原因優(yōu)化建議RRC失敗檢查告警、小區(qū)可用性、RRU的狀態(tài)及VSWRENB問(wèn)題根據(jù)告警

26、原因解決告警RRC失敗通過(guò)地圖信息檢查周邊環(huán)境及站點(diǎn)分布弱覆蓋調(diào)整工參或者增加新站加強(qiáng)周邊覆蓋RRC失敗根據(jù)工參信息檢查受周邊小區(qū)干擾模3干擾調(diào)整工參或者PCI解決模3干擾RRC失敗檢查上行RSSI是否偏高上行干擾解決干擾問(wèn)題RRC失敗檢查上行PRB的利用率PRB資源受限增加noOfPucchSrUsers，noOfPucchcqiUsers配置RRC失敗檢查connected user的license數(shù)量license受限建議客戶進(jìn)行l(wèi)icense擴(kuò)容RRC接入成功率優(yōu)化詳細(xì)流程及counter如下如： 1.3、S1建立成功率正常信令流程S1建立流程：UE完成SRB1承載和無(wú)線資源配置，向e

27、NB發(fā)送RRCConnectionSetupComplete消息，包含NAS層Attach request信息，Arrach request信息中攜帶了PLMN等信息。eNB選擇MME，向MME發(fā)送INITIAL UE MESSAGE消息，此信息攜帶了UE標(biāo)示GUTI 或 IMSI。MME向HSS發(fā)送鑒權(quán)請(qǐng)求后HSS回復(fù)鑒權(quán)需要的向量（Kasme, RAND, AUTN, XRES）。MME通過(guò)DL Information Transfer向UE發(fā)起鑒權(quán)請(qǐng)求。 1.3.2、指標(biāo)定義S1建立成功率是指UE完成RRC連接后NAS層信令建立的成功率。S1建立成功率=S1建立成功率次數(shù)/S1建立請(qǐng)求次

28、數(shù)*100%=pmS1SigConnEstabSucc/pmS1SigConnEstabAtt*100%1.3.3、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn)SignallingSignalling connection setup triggered by initial UE message UE Initial UE RBSmessageppmS1SigConnEstabAttEm +pmS1SigConnEstabAtt +pmS1SigConnEstabAtt +step for cause ”Emergency”pmS1SigConnEstabAttHpa +pmS1SigConnEstabAtt

29、Em +pmS1SigConnEstabAttEm +pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttMod +pmS1SigConnEstabAttMta +pmS1SigConnEstabAttMos +pmS1SigConnEstabAttDta +step for cause ”High Prio Access”pmS1SigConnEstabAttMod +step for cause ”Mobile Originating Data”pmS1SigConnEstabAttMta +step for cause ”Mobile Terminati

30、ng Access”pmS1SigConnEstabAttMos +step for cause ”Mobile Originating Signalling”pmS1SigConnEstabAttDta +RBS timeout on initial context setup request from MME?RBS timeout on initial context setup request from MME?step for cause ”Delay Tolerant Access” yesEnd End signallingconnection setup NoMME sends

31、 initial context setup request to RBSRBS Initial context MMEMME sends initial context setup request to RBSSetup request(E-RABs, Sec keys)Any message received on the S1 logical connection?Any message received on the S1 logical connection? NO Stepped for any of the following pmS1SigConnEstabSucc +mess

32、ages: Yes pmS1SigConnEstabSuccEm +pmS1SigConnEstabSucc +S1 downlink NAS transport step for cause ”Emergency” S1 UE context release command pmS1SigConnEstabSuccHpa +pmS1SigConnEstabAttEm +pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttMod +pmS1SigConnEstabAttMta +pmS1SigConnEstabAttMos +pmS1SigConnEstabA

33、ttDta +S1 initial context setup request pmS1SigConnEstabAttEm +pmS1SigConnEstabAttHpa +pmS1SigConnEstabAttMod +pmS1SigConnEstabAttMta +pmS1SigConnEstabAttMos +pmS1SigConnEstabAttDta +S1 reset pmS1SigConnEstabSuccMod + step for cause ”Mobile Originating Data” pmS1SigConnEstabSuccMta + step for cause

34、”Mobile Terminating Access” pmS1SigConnEstabSuccMos + step for cause ”Mobile Originating Signalling” pmS1SigConnEstabSuccDta + step for cause Delay Tolerant Access”1.3.4、S1建立成功率處理經(jīng)驗(yàn)及流程失敗階段原因查找失敗原因優(yōu)化建議S1失敗檢查小區(qū)可用性、告警等，可能多個(gè)站點(diǎn)出現(xiàn)類似問(wèn)題傳輸問(wèn)題解決傳輸問(wèn)題S1失敗檢查T(mén)AC在MME上的配置TAC配置問(wèn)題修復(fù)TAC配置S1失敗檢查T(mén)AC與LAC在MME映射關(guān)系LAC-TAC映射問(wèn)

35、題重選規(guī)劃并配置問(wèn)題TAC-LAC映射關(guān)系1.4、ERAB建立成功率分析1.4.1、正常信令流程ERAB建立信令流程及重要counter統(tǒng)計(jì)節(jié)點(diǎn)如下圖：ERAB建立信令流程：Initial Context Setup過(guò)程通過(guò)MME向ENB下發(fā)的INITIAL CONTEXT SETUP REQUEST信令觸發(fā)。此條信令包含了初始ERAB建立請(qǐng)求信息、并包含安全算法和安全密匙。RBS通過(guò)SECURITY MODE COMMAND信令要求UE使用安全模式。UE回復(fù)SECURITY MODE COMPLETE后UE與RBS間的通信將進(jìn)行加密和完整性保護(hù)。安全模式激活后，RBS通過(guò)向UE下發(fā)RRC C

36、ONNECTION RECONFIGURATION為數(shù)據(jù)承載分配資源。UE上發(fā)RRC CONNECTION RECONFIGURATION COMPLETE，ENB上發(fā)INITIAL CONTEXT SETUP RESPONSE。1.4.2、指標(biāo)定義E-RAB建立成功是成功為用戶分配了用戶平面的連接比例。E-RAB建立成功率用E-RAB建立請(qǐng)求個(gè)數(shù)和E-RAB建立成功個(gè)數(shù)的比表示，E-RAB建立請(qǐng)求（E-RAB SETUP REQUEST）用于E-RAB建立；在初始上下文建立請(qǐng)求（Initial Context Setup Request）消息中含有E-RAB to Be Setup List

37、 IE，也可以用于E-RAB建立。ERAB建立成功率= E-RAB建立成功數(shù)/E-RAB建立請(qǐng)求數(shù)*100%=(pmErabEstabSuccInit+pmErabEstabSuccAdded)/(pmErabEstabAttInit+pmErabEstabAttAdded)*100%1.4.3、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn)S1cnnSuccS1cnnSuccNote:CorrespondingNote:Corresponding counter per QCI pmErabEstabAttlnitQcipmpmUeCtxtEstabAtt+pmErabEstabAttlnit+pmErabEs

38、tabAttlnitArp+ Stepped for each E-RAB that has thepmErabEstabAttlnitArp+ given ARP Priority LevelpmErabEstabAttlnitPa+ Stepped for attempted setup of bearerpmErabEstabAttlnitPa+ No With priviliged accessLicense for number ofE-RABs per user/License for RLC UM OK ? UE RRC connection License for number

39、 ofE-RABs per user/License for RLC UM OK ? reconfiguration pmErabEstabFailLlinitLic+ UE RRC connection RBS pmErabEstabFailLlinitLic+ Reconfiguration complete Yes DL/UL GBR resource overload?UE Linitial context RBS DL/UL GBR resource overload? Setup failure YespmErabEstabFailGbrDIEnb+orpmErabEstabFai

40、lGbrDIEnb+or pmErabEstabGbrUlENB+RBS sends initial context setup response to MME NoRBS sends initial context setup response to MME RBS Initial context MME Setup responseUE Initial context RBS Note:Corresponding counter per QCI pmErabEstabSucclNote:Corresponding counter per QCI pmErabEstabSucclnitQci

41、pmUeCtxtEstabSucc + pmErabEstabSuccInit +pmErabEstabSuccInitArppmErabEstabSuccInitArp + Stepped for each successfully setup E-RAB that has the given ARP Prionity LevepmErabEstabSuccInitPa + Stepped for successfully setup of bearer with privileged accesspmErabEstabSuccInitPa +End End signaling connec

42、tion setup1.4.4、ERAB建立成功率處理經(jīng)驗(yàn)及流程失敗階段原因查找失敗原因優(yōu)化建議ERAB失敗通過(guò)UETR信令消息查看原因值Security update failures問(wèn)題解決SIM，UE，ENB或MME安全性參數(shù)問(wèn)題ERAB失敗通過(guò)UETR信令消息查看原因值vendor/UE specific issues問(wèn)題解決SIM，UE，ENB或MME參數(shù)配置問(wèn)題ERAB失敗檢查MME容量licens容量問(wèn)題增加MME容量ERAB失敗通過(guò)地圖信息檢查周邊環(huán)境及站點(diǎn)分布弱覆蓋問(wèn)題調(diào)整工參或者增加新站增強(qiáng)周邊覆蓋ERAB失敗檢查小區(qū)可用性、告警等，可能多個(gè)站點(diǎn)出現(xiàn)類似問(wèn)題傳輸問(wèn)題解決傳輸

43、問(wèn)題1.5、相關(guān)案例1.5.1、PRB資源受限一、問(wèn)題描述在岳陽(yáng)武廣火車(chē)站3小區(qū)接通率偏低為91.05%，且發(fā)現(xiàn)該小區(qū)Erab接通率正常為99.39%，可RRC接通率只有91.05%，RRC建立失敗了4263次。二、原因分析PRB資源受限。下圖可以看出Pucch請(qǐng)求CQI和SR資源未響應(yīng)次數(shù)較高，說(shuō)明該小區(qū)有業(yè)務(wù)需求但是資源無(wú)法滿足分配。pmPucchSrCqiResCongSr ：The number of times a PUCCH allocation request for SR resource(s) could not be granted.pmPucchSrCqiResCongC

44、qi ：The number of times a PUCCH allocation request for CQI resource(s) could not be granted進(jìn)一步分析發(fā)現(xiàn)，該小區(qū)RRC最大連接數(shù)超過(guò)設(shè)定上限。 該站覆蓋岳陽(yáng)高鐵站，元旦假日臨近人流量增大用戶數(shù)增多，資源分配不足，導(dǎo)致RRC建立成功率不高。三、解決措施確定PRB資源受限，因此需要增加no0fPucchCqiUsers和no0fPucchSrUsers配置。令后臺(tái)更改參數(shù)如下：MO Class AttributeRecommendedEUtranCellTDDnoOfPucchSrUsers200EUtra

45、nCellTDDnoOfPucchCqiUsers0EUtranCellTDDcommonSrPeriodicity 20四、處理結(jié)果參數(shù)更改后，該站現(xiàn)網(wǎng)配置如下：RRC接通率恢復(fù)為：1.5.2、告警導(dǎo)致接入成功率低一、問(wèn)題描述岳陽(yáng)市漁光社區(qū)2、3小區(qū)接通率變差分別為52.49%、48.24%。該站接通變差主要由于RRC建立成功率變差引起，RRC接通率分別只有52.58%和48.37%，兩個(gè)小區(qū)RRC建立都失敗了四千余次。二、原因分析基站電源故障。當(dāng)時(shí)查得該站并無(wú)強(qiáng)干擾，也未出現(xiàn)業(yè)務(wù)量激增的情況。登錄后臺(tái)查詢告警情況時(shí)，也未發(fā)現(xiàn)實(shí)時(shí)告警產(chǎn)生。后進(jìn)一步查詢?cè)撜镜臍v史告警，發(fā)現(xiàn)該站曾短時(shí)間內(nèi)頻繁的

46、出現(xiàn)了電源告警。三、解決措施查得告警將該情況反饋給工程部，并令后臺(tái)將該站暫時(shí)鎖住，以免KPI指標(biāo)繼續(xù)下滑。工程組實(shí)地勘察得知，該站近日新開(kāi)了2G站點(diǎn)與之共站，共用電源。而電源額定功率不足，無(wú)法負(fù)荷兩個(gè)基站，于是導(dǎo)致我4G站點(diǎn)頻繁電源告警，基站處于通而未通斷而未斷的狀態(tài)，用戶接通受到嚴(yán)重影響。工程部對(duì)該站電源進(jìn)行整改。四、處理結(jié)果工程整改后， RRC接通率恢復(fù)為：1.5.3、GPS故障導(dǎo)致接入成功率低一、問(wèn)題描述：一站點(diǎn)RRC接入成功率由平時(shí)的99.5以上驟降到80%左右，并且其周邊小區(qū)接入成功率也同時(shí)開(kāi)始下降。二、問(wèn)題分析后臺(tái)查詢此站及周邊站點(diǎn)UL_RSSI，發(fā)現(xiàn)此站低噪變的極高，三個(gè)小區(qū)低噪

47、均達(dá)到-91.5dBm，周邊小區(qū)干擾也均以此站為中心干擾呈逐步下降的趨勢(shì)。重啟站點(diǎn)、閉解小區(qū)均未能解決問(wèn)題。懷疑此站與周邊小區(qū)形成干擾。 三、解決措施與工程相關(guān)人員溝通發(fā)現(xiàn)此問(wèn)題站點(diǎn)當(dāng)天凌晨進(jìn)行過(guò)施工，進(jìn)機(jī)房檢查GPS設(shè)備發(fā)現(xiàn)GPS接收器接口未擰緊，且接口線受損；更換此站GPS接收器。四、處理結(jié)果經(jīng)過(guò)處理后，此基站級(jí)周邊基站底噪恢復(fù)正常。 故障30日冷晨產(chǎn)生，在12點(diǎn)中處理時(shí)閉小區(qū)1小時(shí)，13點(diǎn)后恢復(fù)正常。1.5.4、天線接反導(dǎo)致模3干擾一、問(wèn)題描述在TOPN處理時(shí)：發(fā)現(xiàn)ZYHZ0327C接入性能較差dateEUTRANCELLTDDpmRrcConnEstabSuccpmRrcConnEst

48、abAttpmErabEstabSuccInitpmErabEstabAttInit無(wú)線接通失敗次數(shù)無(wú)線接通率5/21ZYHZ0327C28763082248125212460.918二、問(wèn)題分析查看無(wú)任何告警，底噪小區(qū)狀態(tài)查看，整體良好，但結(jié)合切換分析，發(fā)現(xiàn)該小區(qū)切換主要集中在ZYHZ0245B與ZYHZ0244B之間，且存在同模干擾。懷疑ZYHZ0327天線存在接反或者方位角不準(zhǔn)的情況。ZYHZ0327C切換統(tǒng)計(jì)：dateEUTRANCELLTDDEUTRANCELLRELATION同頻切換出成功次數(shù)異頻切換出成功次數(shù)同頻切換出請(qǐng)求次數(shù)異頻切換出請(qǐng)求次數(shù)切換成功率5/21ZYHZ0327C

49、4600-542312-673073015/21ZYHZ0327C4600-542312-44804900.985/21ZYHZ0327C4600-960406-53103300.995/21ZYHZ0327C4600-542311-42803100.905/21ZYHZ0327C4600-542311-62502600.965/21ZYHZ0327C4600-960439-51601601如上圖所示：數(shù)據(jù)結(jié)合圖例，由于ZYHZ0327小區(qū)接反，造成對(duì)周?chē)靖蓴_，影響接入及切換。三、解決措施上站勘測(cè)，發(fā)現(xiàn)此站小區(qū)缺失存在天線接反的情況，對(duì)此站天線接反情況進(jìn)行了處理。四、處理結(jié)果通過(guò)調(diào)整后，對(duì)比

50、效果如下：dateEUTRANCELLTDDpmRrcConnEstabSuccpmRrcConnEstabAttpmErabEstabSuccInitpmErabEstabAttInit無(wú)線接通失敗次數(shù)無(wú)線接通率5-27ZYHZ0327C60760753653601掉線率2.1、理論介紹無(wú)線掉線率反映了系統(tǒng)的業(yè)務(wù)通訊保持能力，也反映了系統(tǒng)的穩(wěn)定性和可靠性。2.2、正常信令流程RBS Initiated UE Context Release2.3、指標(biāo)定義無(wú)線掉線率=(eNB請(qǐng)求釋放上下文數(shù)-正常的eNB請(qǐng)求釋放上下文數(shù))/初始上下文建立成功次數(shù)*100%UE context release

51、is triggered by UE context release request2.4、詳細(xì)counter統(tǒng)計(jì)節(jié)點(diǎn)UE context release is triggered by UE context release request RBS UE context release request MME RBS UE context release command MME Successful handover? Successful handover?Normal release?Normal release? NopmUeCtxtRelAbmonmalEnb+pmUeCtxtRelA

52、bmonmalEnb+pmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbAct+ pmUeCtxtRelAbmonmalEnbActTnFail+Rlease due to S1 beaerRlease due to S1 beaer(GTP-U) error indicationDData in UL or DL buffer? YespmUeCtxtRelAbmonmalEnbActTnFail+pmUeCtxtRelAbmonmalEnbActTnFail+ NoRlease due to S1 UE pre-emption?Rlease due t

53、o S1 UE pre-emption?pmUeCtxtRelAbmonmalEnbPe+pmUeCtxtRelAbmonmalEnbPe+ Yes Data in UL or DL buffer? NoData in UL or DL buffer?NOpmUeCtxtRelAbmonmalEnbNOpmUeCtxtRelAbmonmalEnbAct+ Yes NoCBACBACBACBAUE lost due to S1 UE lost due to S1 I/F down?pmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbActTnfAaiL+ Ye

54、sHO fails UE dropped? NoHO fails UE dropped?pmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbActfHO+ YesUE connection lost? NoUE connection lost?pmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbActfUELost+ Yes NoUE lost due to cell downtime (manual intervention)UE lost due to cell downtime (manual interventio

55、n)pmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbActfActCad+ YesRelease due to UE pre-empltion NoRelease due to UE pre-empltionpmUeCtxtRelAbmonmalEnbpmUeCtxtRelAbmonmalEnbActfActCad+ Yes NoEnd of UE context releaseEnd of UE context release2.5、掉線率處理經(jīng)驗(yàn)及流程失敗counter原因查找失敗原因優(yōu)化建議pmUeCtxtRelAbnormalEnbActUeLo

56、st查看是否存在弱覆蓋弱覆蓋引起掉話調(diào)整工參或者增加新站加強(qiáng)覆蓋pmUeCtxtRelAbnormalEnbActUeLost查看PUCCH和PUSCH是否存在上行干擾干擾引起的掉話如果UE引起的干擾，可嘗試優(yōu)化P0參數(shù)；如果是外部干擾，需清除干擾源pmUeCtxtRelAbnormalEnbActTnFail檢查告警信息，看是否存在傳輸問(wèn)題傳輸異常引起掉話解決傳輸問(wèn)題pmUeCtxtRelAbnormalEnbActCdt查看告警及小區(qū)歷史不可用信息ENB問(wèn)題查找小區(qū)down的原因，恢復(fù)小區(qū)可用性pmUeCtxtRelAbnormalEnbActHo檢查源小區(qū)的鄰區(qū)里是否存在和目標(biāo)小區(qū)同頻的

57、相同PCI鄰區(qū)HO引起的掉話解決越區(qū)覆蓋問(wèn)題，并刪除不合理的鄰區(qū)；或者修改其中一條鄰區(qū)的PCIpmUeCtxtRelAbnormalEnbActHo目標(biāo)小區(qū)是否存在上行干擾HO引起的掉話解決干擾問(wèn)題pmUeCtxtRelAbnormalEnbActHo目標(biāo)小區(qū)是否擁塞，或者license受限HO引起的掉話擴(kuò)容，或者分流pmUeCtxtRelAbnormalEnbActHo目標(biāo)小區(qū)是否弱覆蓋HO引起的掉話調(diào)整工參或者增加新站加強(qiáng)覆蓋2.6、相關(guān)案例2.6.1、高上行干擾導(dǎo)致高掉線率一、問(wèn)題描述岳陽(yáng)岳陽(yáng)金緣花園-3小區(qū)無(wú)限掉線率較高，該小區(qū)無(wú)接入無(wú)切換，異常的eNB請(qǐng)求釋放上下文數(shù)205，初始上下

58、文建立成功次數(shù)0.二、原因分析后臺(tái)登錄該站發(fā)現(xiàn)該站不存在基站故障告警，有強(qiáng)干擾。三、解決措施重啟基站觀察結(jié)果。四、處理結(jié)果干擾自動(dòng)消除。掉線率和接通率都恢復(fù)正常。2.6.2、駐波告警導(dǎo)致高掉線率一、問(wèn)題描述室分站點(diǎn)小區(qū)4687901因駐波比超限，導(dǎo)致該站點(diǎn)的接入成功率、無(wú)線掉線率較差。主要指標(biāo)如下圖：站點(diǎn)date無(wú)線建立成功率無(wú)線掉線率空口上行業(yè)務(wù)量空口下行業(yè)務(wù)量切換成功率46879012014/10/889.43%9.59%0.0035610.04284396.15%二、問(wèn)題分析通過(guò)后臺(tái)對(duì)該站點(diǎn)進(jìn)行駐波查證，發(fā)現(xiàn)該站點(diǎn)內(nèi)A、B小區(qū)的駐波比都有超限的情況，如下圖：三、解決措施通過(guò)現(xiàn)場(chǎng)對(duì)該站點(diǎn)的

59、連接線路以及各接口間的細(xì)致排查，發(fā)現(xiàn)天線與RRU之間連接連續(xù)的一個(gè)接口有松動(dòng)，經(jīng)處理，駐波比超限情況得到解決。四、處理結(jié)果處理后指標(biāo)如下：站點(diǎn)date無(wú)線建立成功率無(wú)線掉線率空口上行業(yè)務(wù)量空口下行業(yè)務(wù)量切換成功率46879012014/10/999.88%0.00%0.0045210.0389299.11%2.6.3 、目標(biāo)小區(qū)擁塞導(dǎo)致高掉線一、問(wèn)題描述小區(qū)7742431無(wú)線掉線率較差，主要掉線原因?yàn)榍袚Q失敗。主要指標(biāo)如下圖：DateERBS NameEUtranCell Id無(wú)線掉線率pmUeCtxtRelAbnormalEnbActHo2015-2-24YUYMLzheqiaoEL-R66

60、01774243PT77424313803%198二、問(wèn)題分析通過(guò)后臺(tái)對(duì)該站點(diǎn)進(jìn)行KPI核查，主要掉線原因?yàn)橄?742433切換失敗導(dǎo)致掉線：DateEUtranCellTDDEUtranCellRelationpmHoExeSuccLteIntraFpmHoExeAttLteIntraF2015-2-247742431774243340715042 核查7742433小區(qū)，發(fā)現(xiàn)該小區(qū)當(dāng)日擁塞：DateEUtranCell Id無(wú)線接通率RRC連接建立成功率pmPucchSrCqiResCongCqipmPucchSrCqiResCongSr2015-2-24774243393.8791399