W(高级)-UTRAN-KPI培训课件-20050827-A-1.0.ppt

《W(高级)-UTRAN-KPI培训课件-20050827-A-1.0.ppt》由会员分享，可在线阅读，更多相关《W(高级)-UTRAN-KPI培训课件-20050827-A-1.0.ppt（46页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、IntroductionlKPI 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 catalogsAccessibility：UTRAN

2、 Call SetupRetainability：UTRAN Call DropMobility：UTRAN Mobility ManagementTraffic：Resource and Traffic managementAlgorithm： Radio Resource Management Algorithm ManagementKPIAccessibility RetainabilityMobilityTrafficAlgorithmContentsUTRAN Call SetupUTRAN Call DropUTRAN Mobility ManagementTraffic Mana

3、gementAlgorithm 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 CounterlMeasurement PointSta

4、t. 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 SETUP COMPLETE

5、RRC 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 counterRRC Connec

6、tion 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 setup no respon

7、seRAB 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 ASSIGNMENTRESPONSER

8、AB 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 Setup Success/CS

9、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 speechCS64kbpsPS64kbpsPS1

10、28kbpsPS384kbpslFailure 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 and in Point A

11、 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 Rate = AMR Call D

12、rop / 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 based counterAMR s

13、peechCS64kbpsPS64KbpsPS128KbpsPS384KbpslCall 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 of the handover

14、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 of Figure3CACTI

15、VE 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 SET UPDATE COM

16、PLETE 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 counterAMR spe

17、echCS64kbpsPS64kbpsPS128kbpsPS384kbpsSHO 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 link) = active set

18、 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 success in Poi

19、nt 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 failure (physical cha

20、nnel configuration failure) F3:HHO failure (time out)UERNCAPHYSICAL CHANNELRECONFIGURATIONPHYSICAL CHANNELRECONFIGURATION FAILUREUERNCAPHYSICAL CHANNELRECONFIGURATIONWAITING PHYSICAL CHANNELRECONFIGURATION TIME OUTHHO counterlHHO KPIIntra-frequency HHO Success rate = Intra-frequency HHO success / In

21、tra-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 HHO failureHHO c

22、ounterlTypical Service based counterAMR speechCS64kbpsPS64kbpsPS128kbpsPS384kbpslFailure cause counterConfiguration unsupportedPhysical channel failureIncompatible simultaneous reconfigurationCell update occurredInvalid configurationNo responseOther causeInter-RAT Handover out counterlMeasurement Po

23、intStat. 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 COMMANDRELOCATIONCOMMANDIU RELEASEC

24、OMMANDABCD 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 outgoing attemptl

25、Overall 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 in Target RNC o

26、r 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. Number of Han

27、dover 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 handover in count

28、erlInter-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 incoming successI

29、nter-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 cell change coun

30、terlMeasurement 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 RELEASECOMPLETED F1: UTRAN-

31、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 outgoing requestlOve

32、rall 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 update request in

33、 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 state before and

34、 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 success/Cell upd

35、ate 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 Mobility ManagementTra

36、ffic 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 throughputTraffic

37、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 and Carrier Pow

38、erCell 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 ) Chann

39、el switch success (DL Bit Rate degrade ) DCHFACH/RACH channel switch counterChannel switch success (To common channel)Channel switch success (From common channel)lAMRCUplink AMR control counter (degrade) Downlink AMR control counter (upgrade) lCACUL Admission deny counterDL Admission deny counter Ap

40、pendix: Nastar KPI Analysis RoutineDefine monitor area: RNC group or cell groupQuery Performance ItemQuery Top N cell listQuery related itemImport raw dataDefine clusterSelect IssueFind out trouble causeRaw counter AnalysisSelect performance analysis issueQuery metric item, find the fault or trouble

41、Query TopN cell list in pre-defined cluster, find the worst cell or cell groupQuery related metric item in the specified worst cellsQuery and find out the fault or trouble causeAnalyze raw counter if necessaryImport performance counter from NE M2000l Step1: Check RRC metric item by “RRC setup analys

42、is” issueRRC Setup Rate islowerAppendix: Nastar KPI Analysis Examplel Step2: Find the worst TopN cell list in former cluster by “Forward”Appendix: Nastar KPI Analysis Examplel Step3: Find the worst cell in TopN listAppendix: Nastar KPI Analysis Examplel Step4: Query RRC reject cause in specified cell by “Forward”Appendix: Nastar KPI Analysis Examplel Step5: Find the RRC reject cause in the worst cellAppendix: Nastar KPI Analysis Example