W網(wǎng)規(guī)高培-WM200612-UTRANKPI_第1頁
W網(wǎng)規(guī)高培-WM200612-UTRANKPI_第2頁
W網(wǎng)規(guī)高培-WM200612-UTRANKPI_第3頁
W網(wǎng)規(guī)高培-WM200612-UTRANKPI_第4頁
W網(wǎng)規(guī)高培-WM200612-UTRANKPI_第5頁
已閱讀5頁,還剩40頁未讀, 繼續(xù)免費閱讀

下載本文檔

版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進行舉報或認領(lǐng)

文檔簡介

1、WCDMA UTRAN KPIIntroductionlKPI definitionKey performance indicator lKPI entityRNC levelCell levelClutter/region level (customized)lKPI analysis Network performance surveillanceTrouble shooting network problemsNetwork trend analysis UTRAN KPI OverviewlThe UTRAN KPI can be divided into 5 catalogsAcce

2、ssibility:UTRAN Call SetupRetainability:UTRAN Call DropMobility:UTRAN Mobility ManagementTraffic:Resource and Traffic managementAlgorithm: Radio Resource Management Algorithm ManagementKPIAccessibility RetainabilityMobilityTrafficAlgorithmContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobility Managem

3、entTraffic ManagementAlgorithm ManagementUTRAN Call Setup lUTRAN Call Setup includes the RRC connection setup and the RAB establish procedure. The Successful call setup involves the success RRC and RAB setup. The main indicators are RRC Setup Success RateRAB Setup Success RateRRC Setup CounterlMeasu

4、rement PointStat. Number of RRC Connection Request in Point A1 of Figure1Stat. Number of RRC Connection Setup in Point B of Figure1Stat. Number of RRC Connection Setup complete in Point C of Figure1Stat. Number of RRC Connection Reject in point A of Figure2 A1BA2CRRC CONNECTION REQUESTRRC CONNECTION

5、 SETUP COMPLETERRC CONNECTION SETUPUERNCARRC CONNECTION REQUESTRRC CONNECTION REJECTUERNC F1:successful RRC connection setup procedure F2: RRC connection reject procedure RRC Setup CounterlRRC Setup KPIRRC Connection Setup Success Rate = RRC Connection Setup complete / RRC Connection RequestlMain co

6、unterRRC Connection RequestRRC Connection SetupRRC Connection RejectRRC Connection Setup completeRRC Setup CounterlRequest cause counterOriginating conversational callTerminating conversational callInter-RAT cell re-selectionInter-RAT cell change orderRegistrationlFailure cause counterRRC RejectRRC

7、setup no responseRAB Setup CounterlMeasurement PointStat. Number of RAB Setup Request in Point A of Figure1 Stat. Number of RAB Setup Success in Point B of Figure1 Stat. Number of RAB Setup Failure in Point B of Figure2RAB ASSIGNMENTREQUESTUERNCCNABRADIO BEARERSETUPRADIO BEARERSETUP COMPLETERAB ASSI

8、GNMENTRESPONSERAB ASSIGNMENTREQUESTUERNCCNABRADIO BEARERSETUPRADIO BEARERSETUP FAILURERAB ASSIGNMENTRESPONSE F1: Successful RAB setup procedure F2: RAB setup failure procedureRAB Setup CounterlRAB Setup KPICS RAB Success rate = CS RAB Setup Success/CS RAB Setup RequestPS RAB Success rate = PS RAB Se

9、tup Success/CS RAB Setup RequestlOverall counterCS RAB Setup RequestCS RAB Setup SuccessCS RAB Setup FailurePS RAB Setup RequestPS RAB Setup SuccessPS RAB Setup FailurelTraffic class based counterConversationalStreamingInteractiveBackgroundRAB setup counterlTypical bearer based counterAMR speechCS64

10、kbpsPS64kbpsPS128kbpsPS384kbpslFailure cause counterInvalid parametersUnavailableTransport Layer failureOther causeContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobility ManagementTraffic ManagementAlgorithm ManagementCall Drop CounterlMeasurement Point Stat. Number of Call Drop in Point A of Figure1

11、 and in Point A of Figure2Definition of Call Drop : Abnormal RAB release triggered by RNCARNCCNRAB RELEASE REQUEST F1: RAB release request procedure F2: Iu connection release request procedureAIU RELEASE COMMANDIU RELEASE COMPLETERNCCNIU RELEASE REQUESTCall Drop CounterlCall Drop KPIAMR Call Drop Ra

12、te = AMR Call Drop / AMR RAB Setup SuccessVP Call Drop Rate = VP Call Drop / VP RAB Setup SuccessPS Call Drop Rate = PS Call Drop / PS RAB Setup SuccesslOverall counterCS call dropPS call droplTraffic class based counterConversationalStreamingInteractiveBackgroundCall Drop CounterlTypical bearer bas

13、ed counterAMR speechCS64kbpsPS64KbpsPS128KbpsPS384KbpslCall drop cause counterRF lossRLC resetAAL2 failureGTPU lossOther causeContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobility ManagementTraffic ManagementAlgorithm ManagementUTRAN Mobile Management lThe UTRAN Mobile Management focus on the KPIs o

14、f the handover procedures. Soft handoverHard handoverInterRAT handoverInterRAT cell change orderCell updateSHO counterlMeasurement Point Stat. Number of SHO request in Point B of Figure1Stat. Number of SHO success in Point C of Figure1Stat. Number of SHO failure in Point C of Figure2 and in Point C

15、of Figure3CACTIVE SET UPDATEACTIVE SET UPDATE COMPLETEUERNCABMEASUREMENT REPORT l F1: Successful SHO procedure F2: SHO failure procedure (activeset update failure) F3:SHO failure procedure (time out)CACTIVE SET UPDATEACTIVE SET UPDATE FAILUREUERNCABMEASUREMENT REPORT CACTIVE SET UPDATEWAITING ACTIVE

16、 SET UPDATE COMPLETE TIME OUTUERNCABMEASUREMENT REPORT SHO counterlSoft handover KPISoft HO Success rate=Soft HO success / Soft HO requestSofter HO Success rate=Softer HO success / Softer HO requestlOverall counterSoft HO requestSoft HO successSofter HO requestSofter HO successlTypical Service based

17、 counterAMR speechCS64kbpsPS64kbpsPS128kbpsPS384kbpsSHO counterlFailure cause counterconfiguration unsupported incompatible simultaneous reconfigurationinvalid configuration No responseOther causelSHO factor counter(1 radio link, 2 radio links, 3 radio links) active setSHO factor (based on radio lin

18、k) = active set average link number -1 SHO factor (based on UE) = (2 radio links active set + 3 radio links active set) / (1 radio links active set + 2 radio links active set + 3 radio links active set) HHO counterlMeasurement PointStat. Number of HHO request in Point B of Figure1Stat. Number of HHO

19、 success in Point C of Figure1Stat. Number of HHO failure in Point A of Figure2 and in Point A of Figure3RADIO LINK SETUPREQUESTUENodeBRNCRADIO LINK SETUPRESPONSEABPHYSICAL CHANNEL RECONFIGURATIONPHYSICAL CHANNELRECONFIGURATION COMPLETECMEASUREMENT REPORTl F1: Successful HHO procedure F2: HHO failur

20、e (physical channel configuration failure) F3:HHO failure (time out)UERNCAPHYSICAL CHANNELRECONFIGURATIONPHYSICAL CHANNELRECONFIGURATION FAILUREUERNCAPHYSICAL CHANNELRECONFIGURATIONWAITING PHYSICAL CHANNELRECONFIGURATION TIME OUTHHO counterlHHO KPIIntra-frequency HHO Success rate = Intra-frequency H

21、HO success / Intra-frequency HHO requestInter-frequency HHO Success rate = Inter-frequency HHO success / Inter-frequency HHO requestlOverall counterIntra-frequency HHO requestIntra-frequency HHO successIntra-frequency HHO failureInter-frequency HHO requestInter-frequency HHO successInter-frequency H

22、HO failureHHO counterlTypical Service based counterAMR speechCS64kbpsPS64kbpsPS128kbpsPS384kbpslFailure cause counterConfiguration unsupportedPhysical channel failureIncompatible simultaneous reconfigurationCell update occurredInvalid configurationNo responseOther causeInter-RAT Handover out counter

23、lMeasurement PointStat. Number of Handover outgoing prepare in Point AStat. Number of Handover outgoing prepare success in Point B Stat. Number of Handover outgoing attempt in Point CStat. Number of Handover outgoing success in Point DRELOCATIONREQUIREDUESRNCCNHANDOVER FROMUTRAN COMMANDRELOCATIONCOM

24、MANDIU RELEASECOMMANDABCD F1: Successful inter-RAT HO outgoing procedureInter-RAT handover out counterlInter-RAT handover KPIInter-RAT handover out prepare success rate = Handover outgoing prepare success/Handover outgoing prepareHandover outgoing success rate = Handover outgoing success/Handover ou

25、tgoing attemptlOverall counterHandover outgoing prepareHandover outgoing prepare successHandover outgoing attemptHandover outgoing successInter-RAT handover out counterlFailure cause counterPrepare failureRelocation Failure in Target CN/RNC or Target SystemTRELOCalloc ExpiryRelocation not supported

26、in Target RNC or Target systemNo Resource Available Unknown Target RNCNo responseHandover failureConfiguration UnsupportedPhysical Channel FailureUnspecified Relocation abortNo responseOther causeInter-RAT handover in counterlMeasurement Point Stat. Number of Handover incoming request in Point AStat

27、. Number of Handover incoming prepare success in Point BStat. Number of Handover incoming success in Point C F1: Successful inter-RAT HO incoming procedureRELOCATIONREQUESTCNTRNCAHANDOVER TOUTRAN COMPLETERELOCATIONREQUESTACKNOWLEDGEBCRELOCATIONCOMPLETEDNodeBUERADIO LINKRESTOREINDICATION Inter-RAT ha

28、ndover in counterlInter-RAT handover in KPIHandover in prepare success rate = Handover incoming prepare success/Handover incoming requestHandover in success rate = Handover incoming success/Handover incoming requestlOverall counterHandover incoming requestHandover incoming prepare successHandover in

29、coming successInter-RAT handover in counterlFailure causePrepare failure No Resource Available Relocation Failure in Target CN/RNC or Target System Relocation not supported in Target RNC or Target system Relocation abort Other causeHandover failure Relocation abort No response Other causeInter-RAT c

30、ell change counterlMeasurement PointStat. Number of cell change outgoing request in Point B of Figure1 and Point A of Figure2Stat. Number of cell change outgoing success in Point D of Figure1 and Point B of Figure2UESRNCCNCELL CHANGEORDER FROMUTRANIU RELEASECOMMANDABCMEASUREMENTREPORTIU RELEASECOMPL

31、ETED F1: UTRAN-controlled cell change outgoing procedure F2: UE-controlled cell change outgoing procedureASRNS CONTEXT RESPONSESRNS CONTEXT REQUESTSRNCCNIU RELEASE COMMANDIU RELEASE COMPLETEBInter-RAT cell change counterlInter-RAT cell change KPISuccess rate = Cell change success / Cell change outgo

32、ing requestlOverall counterCell change outgoing requestCell change outgoing successlTypical bearer based counterPS64kbpsPS128kbpsPS384kbpslFailure cause counterConfiguration unacceptable Physical Channel Failure UnspecifiedNo responseOtherCell update counterlMeasurement Point Stat. Number of cell up

33、date request in Point A Stat. Number of cell update success in Point B in case1 or case2Stat. Number of cell update success in Point C in case3uCase1:the UE camps on the same cells and keeps in CELL_PCH state before and after cell update uCase2:the UE camps on the same cells and keeps in CELL_FACH s

34、tate before and after cell update, also the update cause is not cell reselectionuCase3: all cases except case1 and case2BCELL UPDATECELL UPDATE CONFIRMUERNCPHYSICAL CHANNEL RECONFIGURATION COMPLETECA F1: cell update procedureCell update counterlCell update KPICell update success rate = Cell update s

35、uccess/Cell update requestlOverall CounterCell update requestCell update successlCell update cause counterCell reselectionPeriodical cell updateUplink data transmissionPaging responseRe-entered service areaRadio link failureRLC unrecoverable error ContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobilit

36、y ManagementTraffic ManagementAlgorithm ManagementTraffic CounterlUser numberRRC state based user numberCell DCH, Cell FACH, Cell PCH, URA PCHTraffic class based equivalent userConversationalStreamingInteractive and backgroundlCell throughputDirectional counterCell uplink throughputCell downlink thr

37、oughputTraffic class based counterConversational, streaming, interactive, backgroundAll supported bandwidthTraffic CounterlIub bandwidth utilizationCommon channel (RACH, FACH, PCH) volumeTraffic class based service volumeUplink and downlink volumelOVSF code utilizationSF based SF=4 SF=8 SF=512lRTWP

38、and Carrier PowerCell RTWPTransmission Carrier PowerContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobility ManagementTraffic ManagementAlgorithm ManagementAlgorithm CounterlDCCCOverall counterChannel switch requestChannel switch successDCHDCH channel switch counterChannel switch success (DL Bit Rate upgrade ) Channel switch success (DL Bit Rate degrade ) DCHFACH/RACH channel swi

溫馨提示

  • 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。

評論

0/150

提交評論