Nokia Ran Kpis Part 1 Rrc

Company Confidential

Nokia RAN PerformanceNokia RAN PerformancePart 2Part 2

Measurements and RRC KPIsMeasurements and RRC KPIs

2828 Sep. 2005Sep. 2005Nokia NetworksNokia Networks

Operations Solutions Operations Solutions -- Performance, TaiwanPerformance, Taiwan


ObjectivesObjectives

•• The presentation objectives are:The presentation objectives are:

•• Describing the most important counters, the triggering point or Describing the most important counters, the triggering point or the triggering period, the reliability and the usability.the triggering period, the reliability and the usability.

•• Describing the most important KPI for performance monitoring Describing the most important KPI for performance monitoring in case of troublein case of trouble--shooting or optimisation activities.shooting or optimisation activities.


RRC PerformanceRRC Performance


Service Level MeasurementService Level Measurement•• The service level measurement is carried out in the serving RNC The service level measurement is carried out in the serving RNC

(SRNC).(SRNC).•• The object of the measurement is the WBTS/WCELL, which is the The object of the measurement is the WBTS/WCELL, which is the

reference cell.reference cell.•• In anchoring case, all active set cells belong to the drift RNC In anchoring case, all active set cells belong to the drift RNC and the and the

serving RNC is not aware of their identifications.serving RNC is not aware of their identifications.•• The best active set cell may change during the call: the object The best active set cell may change during the call: the object of the of the

measurement can be different for connection establishment and measurement can be different for connection establishment and release counters.release counters.

•• RAB can be established and released in two separate measurement RAB can be established and released in two separate measurement intervals: connection establishment and release counters of the intervals: connection establishment and release counters of the same call are updated during different measurement intervals.same call are updated during different measurement intervals.

•• If a failure, which leads to RRC connection release, occurs duriIf a failure, which leads to RRC connection release, occurs during ng any RAB active phase, both RRC active and RAB failure counters aany RAB active phase, both RRC active and RAB failure counters are re updated with an appropriate cause.updated with an appropriate cause.


Location Update(LU)Location Update(LU)

RRC Connection Stage

Authentication Stage

Location Update Request

Location Update Accept

RRC Connection Release


AMR MOCAMR MOC

Call Setup Success

Disconnect and Release Procedure

RRC Connection Setup

Authentication Procedure

Radio Bearer Setup Procedure


AMR MOCAMR MOCUE BTS RN

CCS_CN

RRC_Connection_Request

RRC_Connection_Setup

RRC_Connection_Setup_Complete

CM_Service_Request

Setup

Call_Proceeding

Radio_Bearer_Setup

Radio_Bearer_Setup_Complete

Alerting

Connect

Connect_Acknowledge

Authentication_Request

Authentication Response

Security_Mode_Command

Security_Mode_Complete


PS DATA CALLPS DATA CALLRRC Connection Setup

Attach & Authentication Procedure

PDP Context Activation & Radio Bearer Setup Procedure

Radio Bearer Reconfiguration

PDP Context Deactivation Procedure

Detach & Radio Bearer Release Procedure

RRC Connection Release


PS DATA CALLPS DATA CALLUE BTS RNC PS_CN

RRC_Connection_Request

RRC_Connection_Setup

RRC_Connection_Setup_Complete

Attach_Request

Authentication_n_Ciphering Request

Authentication_n_Ciphering Response

Security_Mode_Command

Security_Mode_Complete

Attach_Accept

Attach_Complete

Activate_PDP_Context_Request

Radio_Bearer_Setup

Radio_Bearer_Setup_Complete

Activate_PDP_Context_Accept

Radio_Bearer_Reconfiguration

Radio_Bearer_Reconfiguration_Complete


RRC and RAB PhasesRRC and RAB PhasesPhases and Counters of RRC & RAB connection Phases and Counters of RRC & RAB connection

SetupSetup

completecomplete

Setup phase

AccessAccess

completecomplete

Access phase

Active Active FailuresFailures

ActiveActiveReleaseRelease

ActiveActivecompletecomplete

Active phase

Setup FailuresAnd Blocking

Access

Access Failures

Success

DropAttempts

Active phaseActive phaseAccess phaseAccess phaseSetup phaseSetup phase

Sending RAB ASSIGNMENT Sending RAB ASSIGNMENT RESPONSE RESPONSE ~ ~ RNC releases the RAB connection RNC releases the RAB connection NormallyNormally

Sending RADIO BEARER SETUP ~Sending RADIO BEARER SETUP ~Receiving RABIO BEARER SETUP Receiving RABIO BEARER SETUP COMPLETECOMPLETE

Receiving RAB ASSIGNMENT Receiving RAB ASSIGNMENT REQUEST ~ REQUEST ~ Sending Sending RADIO BEARER SETUP RADIO BEARER SETUP

Sending INITIAL UE MESSAGE ~ Sending INITIAL UE MESSAGE ~ RNC releases the RRC connection RNC releases the RRC connection normallynormally

Sending RRC CONNECTION SETUP Sending RRC CONNECTION SETUP ~~Receiving RRC CONNECTION Receiving RRC CONNECTION COMPLETECOMPLETE

Accepting RRC CONNECTION Accepting RRC CONNECTION REQUEST ~REQUEST ~Sending RRC CONNECTION SETUPSending RRC CONNECTION SETUP

RAB step

RRC step


RRC PhasesRRC Phases

Event 1:Event 1: RRC_CONN_STP_ATT incremented. RRC_CONN_STP_ATT incremented. Event 2:Event 2: RRC_CONN_STP_COMP incremented. RRC_CONN_STP_COMP incremented. Event 3:Event 3: RRC_CONN_ACC_COMP incremented. RRC_CONN_ACC_COMP incremented. Event 4:Event 4: RRC_CONN_ACT_COMP incremented.RRC_CONN_ACT_COMP incremented.

RRC Connection RequestRRC Connection Request

RRC Connection Setup CompleteRRC Connection Setup Complete

UEUE RNCRNC CORECORE

RRC Connection SetupRRC Connection Setup

Event 1Event 1

Event 2Event 2

Event 3Event 3

Event 4Event 4

IU Release CommandIU Release Command

Setup PhaseSetup Phase

Access PhaseAccess Phase

Active PhaseActive Phase

RRC RRC setup setup timetime


RRC Connection CountersRRC Connection CountersUEUE NodeNode--BB RNCRNC CNCN

RRC: Connection RequestRRC: Connection Request

Correctly Received messageRRC Connection Setup StartsTriggers: 1001C0 RRC Connection Attempt

RRC Connection Setup phaseResource Reservation in RNC, Node-B, Transmission

RRC: Connection Request SetupRRC: Connection Request Setup

RRC Connection Setup completedTriggers: 1001C1 RRC Con Setup Comp

RRC Connection Access phaseRNC waits for a reply from UE

RRC: Connection Setup CompleteRRC: Connection Setup Complete

RRC Connection Access completedTriggers: 1001C8 RRC Con Acc Comp

RANAP: Initial UE MessageRANAP: Initial UE Message

RRC Connection Active phaseUE-CN signaling

RANAP: IU Release CommandRANAP: IU Release Command

RRC Connection Active completedTriggers: 1001C12 RRC Con Active Comp

Failure Case:RRC Connection Setup failsDue to Triggers: 1001C2 Handover control1001C3 Admission control1001C4 BTS1001C5 Transmission network1001C6 RNC internal reason1001C7 Frozen BTS

Failure Case:RRC Connection Access failsDue to Triggers: 1001C9 L1 synchronization in BTS1001C10 UU interface1001C11 RNC internal reason

Failure Case:RRC Connection Active failsDue to Triggers: 1001C15 Iu interface 1001C16 Radio interface1001C17 BTS1001C18 Iur interface1001C19 Ciphering failure1001C20 Integrity check1001C21 RNC internal reason

Special Reason: RRC Connection Active Release Due to Triggers: 1001C13 SRNC Relocation1001C14 Pre-emption

RRC: Initial Direct TransferRRC: Initial Direct Transfer


Failure Cause ExplanationsFailure Cause Explanations


[RACH] RRC:RRC Connection Request

UE Node B RNC

NBAP: RL Setup Request

Start TX/RXNBAP: RL Setup Response

AC to check to accept or reject RRC Connection Request

(M1002C3) DCH_REQ_RRC_CONN_SRNC : includes state transitions and RRC Connections(M1002C0) DCH_REQ_LINK_SRNC : includes SHO, HHOs, state transitions and RRC ConnectionsSuccessful AC decision triggers:(M1002C7) DCH_ALLO_LINK_3_4_SRNC or (M1002C8)DCH_ALLO_LINK_13_6_SRNC(M1005C0) RL_SETUP_ATT_FOR_FIRST_RL : includes state transitions Cell_FACH -> Cell_DCH(M1005C5) RL_SETUP_SUCC_FOR_FIRST_RL_

[FACH] RRC:RRC Connection Reject : Cause Unspecified

ALCAP:ERQ

ALCAP:ECF

Failure in AAL2 connection setups triggers RRC Connection Reject message and:

(M1001C5) RRC_CONN_STP_FAIL_TRANS

Correctly Received messageRRC Connection RequestTriggers: RRC_CONN_STP_ATT (M1001C0)

CASE : RRC Connection CASE : RRC Connection Reject Reject ((UnspecifiedUnspecified >> AAL2 >> AAL2 SetupSetup))


Call fail & dropCall fail & drop

Call setup fail due to transmission


7272 fail7272 fail


7394 is ok since May 147394 is ok since May 14


CASE : RRC Connection CASE : RRC Connection ActAct failfail

PM counter of site 7268 & 7734PM counter of site 7268 & 7734


RRC Connection KPIsRRC Connection KPIsUEUE NodeNode--BB RNCRNC CNCN













Special Reason: RRC Connection Active Release Due to Triggers: 1001C13 SRNC Relocation1001C14 Pre-emption

RRC Setup Complete Ratio (%)

RRC Setup and Access Complete Ratio (%)

RRC Drop Ratio (%)



RRC Connection by Attempt CauseRRC Connection by Attempt CauseUEUE NodeNode--BB RNCRNC CNCN













RRC Connection Setupdue to CauseTriggers: 1001C22 MOC conv call att1001C24 MOC stream call att1001C26 MOC interac call att1001C28 MOC backgr call att1001C30 MOC subscribed call att1001C32 MTC conv call att1001C34 MTC stream call att1001C36 MTC interac call att1001C38 MTC backgr call att1001C40 Emergency call att1001C42 Inter RAT cell reselection1001C44 Inter RAT cell chng ord1001C46 Registration attempt1001C48 Detach attempt1001C50 MOC high prior signaling1001C52 MTC high prior signaling1001C54 MOC low prior signaling1001C56 MTC high prior signaling1001C58 Call re establishment att1001C60 Terminating cause

unknown



RRC Connection Failures by Attempt CauseRRC Connection Failures by Attempt CauseUEUE NodeNode--BB RNCRNC CNCN














Failures by RRC Connection Setup CausesTriggers: 1001C23 MOC conv call failure1001C25 MOC stream call failure1001C27 MOC interac call failure1001C29 MOC backgr call failure1001C31 MOC subscribed call fail1001C33 MTC conv call failure1001C35 MTC stream call failure1001C37 MTC interac call failure1001C39 MTC backgr call failure1001C41 Emergency call failure1001C43 Inter RAT cell reselec fail1001C45 Inter RAT cell chng ord fail1001C47 Registration attempt fail1001C49 Detach attempt failure1001C51 MOC high prior sig failure1001C53 MTC high prior sig failure1001C55 MOC low prior sig failure1001C57 MTC high prior sig failure1001C59 Call re establishment fail1001C61 Terminating cause

unknown failure

Only Setup and Only Setup and Access phasesAccess phases


RRC Setup PhaseRRC Setup Phase•• This phase starts when UE sends the This phase starts when UE sends the

““RRC CONNECTION REQUESTRRC CONNECTION REQUEST”” message message using the PRACH channel and it is using the PRACH channel and it is completed when RNC, after reserving all completed when RNC, after reserving all the necessary resources for the RRC the necessary resources for the RRC Connection (RNC, BTS, Radio and Connection (RNC, BTS, Radio and Transmission), replies with DL Transmission), replies with DL ““RRC RRC CONNECTION SETUPCONNECTION SETUP”” message, carried message, carried over Sover S--CCPCH (FACH subCCPCH (FACH sub--channel).channel).

•• This procedure is not affected by UEThis procedure is not affected by UE’’s s behavior, provided that RACH has been behavior, provided that RACH has been detected by RNC.detected by RNC.

•• New counter in ED2 CD3: New counter in ED2 CD3: RRC Conn RRC Conn Setup Att Repeats :Setup Att Repeats :

•• The number of RRC Connection Request The number of RRC Connection Request retransmissions (successfully received by retransmissions (successfully received by the RNC) from the same UE if the RRC the RNC) from the same UE if the RRC Connection Request is rejected due to Connection Request is rejected due to unsuccessful resource reservation unsuccessful resource reservation attempt in RNC.attempt in RNC.

•• UPDATED: When a repeated RRC UPDATED: When a repeated RRC CONNECTION REQUEST is received from CONNECTION REQUEST is received from the same UE as the first RRC CONNECTION the same UE as the first RRC CONNECTION REQUEST during UEREQUEST during UE--ID buffering time ID buffering time (UEIDBuffTime='Wait Time'+N300+T300) (UEIDBuffTime='Wait Time'+N300+T300) after RRC CONNECTION REJECT has been after RRC CONNECTION REJECT has been sent to this UE.sent to this UE.

RRC: RRC Connection Request (RACH)

UE RNCNode B

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

ALCAP: Establish Request

ALCAP: Establish Confirm

FP: Downlink Sync

FP: Uplink Sync

NBAP: Synchronisation Indication

RRC: RRC Connection Setup (FACH)

L1 Synchronisation

RRC: RRC Connection Setup Complete (DCH)


UE RNCNode B





FP: Downlink Sync

FP: Uplink Sync



L1 Synchronisation



RRC Access PhaseRRC Access Phase•• It begins when RNC sends DL It begins when RNC sends DL ““RRC RRC

CONNECTION SETUPCONNECTION SETUP”” message to UE and message to UE and it is successfully completed upon it is successfully completed upon receiving UL receiving UL ““RRC CONNECTION SETUP RRC CONNECTION SETUP COMPLETECOMPLETE”” message UE transmits using message UE transmits using the established dedicated channel.the established dedicated channel.

•• This procedure can be quite critical This procedure can be quite critical since it includes both UL and DL L1 since it includes both UL and DL L1 synchronization of the signaling synchronization of the signaling dedicated channel to be setup. dedicated channel to be setup.

•• New counter in ED2 CD3: New counter in ED2 CD3: RRC Conn Acc RRC Conn Acc Release due to Cell Reselection:Release due to Cell Reselection:

•• The number of RRC Connection Access The number of RRC Connection Access releases due to cell reselection. This is releases due to cell reselection. This is the case when the UE has sent a new RRC the case when the UE has sent a new RRC connection request to the new cell while connection request to the new cell while the RRC connection setup phase is still the RRC connection setup phase is still ongoing in the old cell. The RNC releases ongoing in the old cell. The RNC releases resources for the old RRC connection resources for the old RRC connection attempt.attempt.

•• UPDATED: When the RRC Connection UPDATED: When the RRC Connection attempt is released before the RRC attempt is released before the RRC Connection Setup Complete is received Connection Setup Complete is received from the UE due to a new RRC from the UE due to a new RRC Connection Request to another cell.Connection Request to another cell.


UE RNCNode B





FP: Downlink Sync

FP: Uplink Sync



L1 Synchronisation



UE RNCNode B





FP: Downlink Sync

FP: Uplink Sync



L1 Synchronisation



RRC Connection Setup and Access KPIsRRC Connection Setup and Access KPIs•• This KPI does not necessarily represent the UE perception of RRCThis KPI does not necessarily represent the UE perception of RRC

connection success rate. connection success rate. •• If PRACH coverage is inadequate the RNC may not receive the RRC If PRACH coverage is inadequate the RNC may not receive the RRC

CONNECTION REQUEST message. The RRC connection attempt would CONNECTION REQUEST message. The RRC connection attempt would then fail without the RNC having any knowledge of the attempt.then fail without the RNC having any knowledge of the attempt.

•• In case of failure Layer 3 of the UE will reIn case of failure Layer 3 of the UE will re--attempt failed RRC attempt failed RRC connections as defined by the parameters N300 and T300 connections as defined by the parameters N300 and T300

•• The KPI is meaningful for cluster/cell level and on day/hour basThe KPI is meaningful for cluster/cell level and on day/hour basis.is.

(M1001C1) RRC_CONN_STP_COMP RRC Connection Setup Success = --------------------------------------------------- * 100%

(M1001C0) RRC_CONN_STP_ATT

(M1001C8) RRC_CONN_ACC_COMP RRC Connection Setup and Access Success = --------------------------------------------------- * 100%

(M1001C0) RRC_CONN_STP_ATT


T300/N300/T300/N300/Wait time in RRC connection request rejectionWait time in RRC connection request rejection

3 sec for conversational.3 sec for conversational.Defines the value of the parameter Wait Time included in the RRCDefines the value of the parameter Wait Time included in the RRC: RRC Connection Reject message. : RRC Connection Reject message. The MS waits for at least the duration of the time period specifThe MS waits for at least the duration of the time period specified in the parameter before it sends a ied in the parameter before it sends a new RRC:new RRC:RRC Connection Request message, or enters idle mode if the maximRRC Connection Request message, or enters idle mode if the maximum number of attempts has um number of attempts has already been reached. Value 0 of the parameter indicates that realready been reached. Value 0 of the parameter indicates that repeated requests are not allowed.peated requests are not allowed.The value of the parameter is dependant on the value of the EstaThe value of the parameter is dependant on the value of the Establishment Cause received originally in blishment Cause received originally in the RRC: RRC Connection Request message.the RRC: RRC Connection Request message.

•• WaitTimeRRCbackgroundWaitTimeRRCbackground

•• WaitTimeRRCconversationalWaitTimeRRCconversational

•• WaitTimeRRCemergencyWaitTimeRRCemergency

•• WaitTimeRRChighPrioritySignallingWaitTimeRRChighPrioritySignalling

•• WaitTimeRRCinterRATreselectionWaitTimeRRCinterRATreselection

•• WaitTimeRRCinteractiveWaitTimeRRCinteractive

•• WaitTimeRRClowPrioritySignallingWaitTimeRRClowPrioritySignalling

•• WaitTimeRRCotherWaitTimeRRCother

•• WaitTimeRRCregistrationWaitTimeRRCregistration

•• WaitTimeRRCstreamingWaitTimeRRCstreaming

•• WaitTimeRRCsubscribedWaitTimeRRCsubscribed

•• WaitTimeRRCunknownWaitTimeRRCunknown

Wait time in Wait time in RRC connection RRC connection request request rejectionrejection

3 times3 timesRRC CONNECTION REQUEST retransmission counter (MS counter).RRC CONNECTION REQUEST retransmission counter (MS counter).This parameter is part of System Information Block 1.This parameter is part of System Information Block 1.

N300N300

2sec2secThe RRC CONNECTION REQUEST retransmission timer (MS timer).The RRC CONNECTION REQUEST retransmission timer (MS timer).This parameter is part of System Information Block 1.This parameter is part of System Information Block 1.

T300T300

ValueValueDescriptionDescriptionParameter Parameter


T300/N300/T300/N300/Wait time in RRC connection request rejectionWait time in RRC connection request rejection

N300 Wait time in RRC con reqrejection


RRC CONN REQ HANDLING RRC CONN REQ HANDLING –– CD3CD3•• SCENARIO1:SCENARIO1:

•• Mobile sends RRC CONNECTION Mobile sends RRC CONNECTION REQUEST but it is REQUEST but it is ““deafdeaf”” on on FACH FACH it does not receive RRC it does not receive RRC CONN SETUP sent by RNCCONN SETUP sent by RNC









UEUE RNCRNC

M1001C0 RRC_CONN_STP_ATT=4M1001C0 RRC_CONN_STP_ATT=4M1001C1 RRC_CONN_STP_COMP=1M1001C1 RRC_CONN_STP_COMP=1M1001C8 RRC_CONN_ACC_COMP=0M1001C8 RRC_CONN_ACC_COMP=0

same RNTI (Buffering) same RNTI (Buffering) only one only one PMI ticketPMI ticket

M1001C242 RRC_CONN_STP_ATT_REPET=3M1001C242 RRC_CONN_STP_ATT_REPET=3

THE USER PERCEIVES 4THE USER PERCEIVES 4--3=1 FAILURE ONLY3=1 FAILURE ONLY

Buffering is stopped if:Buffering is stopped if:--succ proceduresucc procedure--timer T300 ( 2S) *N300 (3) timer T300 ( 2S) *N300 (3) expiresexpires--RRC CONN REJECT sent to UERRC CONN REJECT sent to UE--T_RRC_Resp_CCH (3s) expiresT_RRC_Resp_CCH (3s) expires


RRC CONN REQ HANDLING RRC CONN REQ HANDLING –– CD3CD3

•• SCENARIO2:SCENARIO2:•• Mobile sends 4 RRC CONNECTION REQUEST msg and RNC answers Mobile sends 4 RRC CONNECTION REQUEST msg and RNC answers

4 times (N300=3) with RRC CONNECTION REJECT (e.g. due to 4 times (N300=3) with RRC CONNECTION REJECT (e.g. due to congestion)congestion)


RRC Connection RejectRRC Connection Reject







UEUE RNCRNCM1001C0 RRC_CONN_STP_ATT=4M1001C0 RRC_CONN_STP_ATT=4M1001C1 RRC_CONN_STP_COMP=0M1001C1 RRC_CONN_STP_COMP=0M1001C8 RRC_CONN_ACC_COMP=0M1001C8 RRC_CONN_ACC_COMP=0

M1001C242 RRC_CONN_STP_ATT_REPET=3M1001C242 RRC_CONN_STP_ATT_REPET=3

THE USER PERCEIVES 4THE USER PERCEIVES 4--3=1 FAILURE ONLY3=1 FAILURE ONLY


RRC CONN REQ HANDLING RRC CONN REQ HANDLING –– CD3CD3

•• SCENARIO3:SCENARIO3:•• Cell ReselectionCell Reselection•• New counter has impact to RRC Access Procedure.New counter has impact to RRC Access Procedure.





RRC Connection Setup CompleteRRC Connection Setup Complete

UEUE RNCRNCM1001C0 RRC_CONN_STP_ATT (A)=1M1001C0 RRC_CONN_STP_ATT (A)=1M1001C1 RRC_CONN_STP_COMP (A)=1M1001C1 RRC_CONN_STP_COMP (A)=1M1001C8 RRC_CONN_ACC_COMP (A)=0M1001C8 RRC_CONN_ACC_COMP (A)=0

M1001C241 RRC_CONN_ACC_REL_RESEL (A)=1M1001C241 RRC_CONN_ACC_REL_RESEL (A)=1

NO PROBLEM FOR THE USER AND CELL B; CELL A COUNTS 1 RESELECTIONNO PROBLEM FOR THE USER AND CELL B; CELL A COUNTS 1 RESELECTION

M1001C0 RRC_CONN_STP_ATT (B)=1M1001C0 RRC_CONN_STP_ATT (B)=1M1001C1 RRC_CONN_STP_COMP (B)=1M1001C1 RRC_CONN_STP_COMP (B)=1M1001C8 RRC_CONN_ACC_COMP (B)=1M1001C8 RRC_CONN_ACC_COMP (B)=1

Cell ACell A

Cell BCell B

Cell BCell B


New (CD03) RC Connection Setup and Access New (CD03) RC Connection Setup and Access KPIsKPIs

•• After CD03 new RRC counters are implemented:After CD03 new RRC counters are implemented:•• RRC Connection Setup repetitionRRC Connection Setup repetition•• RRC Connection Access for cell reselectionRRC Connection Access for cell reselection

•• New formula for KPIs:New formula for KPIs:

•• The KPI is meaningful for cluster/cell level and on day/hour basThe KPI is meaningful for cluster/cell level and on day/hour basis.is.

RRC_CONN_STP_COMP RRC Connection Setup Success (user) = --------------------------------------------------------------- * 100%

RRC_CONN_STP_ATT - RRC_CONN_STP_ATT_REPEAT

RRC_CONN_ACC_COMP RRC Connection Setup and Access Success = -------------------------------------------------------------- * 100%

RRC_CONN_STP_ATT - RRC_CONN_ACC_REL_RESEL

RRC_CONN_STP_COMP RRC Connection Setup Success = --------------------------- * 100%

RRC_CONN_STP_ATT

RRC_CONN_ACC_COMP RRC Connection Setup and Access Success (user) = ----------------------------------------- * 100%

RRC_CONN_STP_ATT –RRC_CONN_STP_ATT_REPEAT -RRC_CONN_ACC_REL_RESEL

Now


RRC Drop Rate KPIRRC Drop Rate KPI•• There are two formulas for RRC Drop Rate:There are two formulas for RRC Drop Rate:

•• Normal RRC releases are taken into account.Normal RRC releases are taken into account.

•• UE mobility may cause this KPI to exceed 100 % or become UE mobility may cause this KPI to exceed 100 % or become negative i.e. a UE establishes its RRC connection in one cell annegative i.e. a UE establishes its RRC connection in one cell and d then releases it in a different cell.then releases it in a different cell.

•• RRC release failures are taken into account .RRC release failures are taken into account .

•• Some of the failures might not be counted.Some of the failures might not be counted.

•• These KPIs are meaningful for These KPIs are meaningful for cluster/cellcluster/cell level and on level and on day/hour day/hour basis.basis.

Drop might be dueto problems in the target cell e.g. SHO

failure

DropDrop might bemight be duedueto problemsto problems in the in the targettarget cellcell e.g. SHOe.g. SHO

failurefailure

RRC_CONN_ACT_COMP + RRC_CONN_ACT_REL_P_EMP + RRC_CONN_ACT_REL_SRNC RRC Drop Ratio = 100 – 100 * ------------------------------------------------------------------------------------------------- %

RRC_CONN_ACC_COMP

Σ RRC_CONN_ACT_FAIL_xxx RRC Drop Ratio = 100 * ---------------------------------------------------------------- %

RRC_CONN_ACT_COMP + Σ RRC_CONN_ACT_FAIL_xxx Now


RRC Counters (1/4)RRC Counters (1/4)

Since Since RN1.5RN1.5

M1001C6M1001C6A number of RRC Connection setup failures caused by RNCA number of RRC Connection setup failures caused by RNC’’ssinternal reasons.internal reasons.When the RRC connection setup is rejected because of RNCWhen the RRC connection setup is rejected because of RNC’’s s internal reasons (for example, parameter mismatch, timer expiry)internal reasons (for example, parameter mismatch, timer expiry)..UPDATED: When the RRC connection setup fails for RNCUPDATED: When the RRC connection setup fails for RNC’’s internal s internal reasons.reasons.

GCN8GCN8RRC_CONN_STP_FAIL_RNCRRC_CONN_STP_FAIL_RNC


M1001C5M1001C5A number of RRC connection setup failures caused by a A number of RRC connection setup failures caused by a transmission failure.transmission failure.UPDATED: When the RRC connection setup fails due to transmissionUPDATED: When the RRC connection setup fails due to transmissionsetup failure.setup failure.

GCN7GCN7RRC_CONN_STP_FAIL_TRANSRRC_CONN_STP_FAIL_TRANS


M1001C4M1001C4A number of RRC connection setup failures caused by a BTS.A number of RRC connection setup failures caused by a BTS.When the BTS rejects an initial RL setup.When the BTS rejects an initial RL setup.UPDATED: When the BTS rejects an RRC connection setup attempt.UPDATED: When the BTS rejects an RRC connection setup attempt.

GCN6GCN6RRC_CONN_STP_FAIL_BTSRRC_CONN_STP_FAIL_BTS


M1001C3M1001C3A number of RRC connection setup failures caused by AC.A number of RRC connection setup failures caused by AC.UPDATED: When AC rejects an RRC connection setup attempt.UPDATED: When AC rejects an RRC connection setup attempt.

GCN5GCN5RRC_CONN_STP_FAIL_ACRRC_CONN_STP_FAIL_AC


M1001C2M1001C2A number of RRC connection setup failures caused by HC.A number of RRC connection setup failures caused by HC.UPDATED: When HC rejects an RRC connection setup attempt.UPDATED: When HC rejects an RRC connection setup attempt.

GCN4GCN4RRC_CONN_STP_FAIL_HCRRC_CONN_STP_FAIL_HC


M1001C1M1001C1A number of RRC connection setups completed.A number of RRC connection setups completed.UPDATED: When the RRC connection setup is complete.UPDATED: When the RRC connection setup is complete.

GCN3GCN3RRC_CONN_STP_COMPRRC_CONN_STP_COMP


M1001C0M1001C0A number of RRC connection setup attempts. A number of RRC connection setup attempts. UPDATED: When the RRC Connection setup starts.UPDATED: When the RRC Connection setup starts.

GCN2GCN2RRC_CONN_STP_ATTRRC_CONN_STP_ATT

ReleaseReleaseOMeSIDOMeSIDDescriptionDescriptionCounter Counter name in name in

tabletableCounter name in viewCounter name in view




M1001C11M1001C11A number of RRC connection access failures caused by RNCA number of RRC connection access failures caused by RNC’’s s internal reasons.internal reasons.When the RRC connection access is rejected because of RNCWhen the RRC connection access is rejected because of RNC’’s s internal reasons (for example, parameter mismatch, timer expiry)internal reasons (for example, parameter mismatch, timer expiry)..UPDATED: When the RRC connection access fails because of RNCUPDATED: When the RRC connection access fails because of RNC’’s s internal reasons.internal reasons.

GCN13GCN13RRC_CONN_ACC_FAIL_RNCRRC_CONN_ACC_FAIL_RNC


M1001C10M1001C10A number of RRC connection access failures caused by UU interfacA number of RRC connection access failures caused by UU interface.e.When the RNC does not receive RRC_CONNECTION_SETUP from the When the RNC does not receive RRC_CONNECTION_SETUP from the UE.UE.UPDATED: When RRC connection access fails due to the UU UPDATED: When RRC connection access fails due to the UU interface.interface.

GCN12GCN12RRC_CONN_ACC_FAIL_MSRRC_CONN_ACC_FAIL_MS


M1001C9M1001C9A number of RRC connection access failures caused by radio A number of RRC connection access failures caused by radio interface synchronisation.interface synchronisation.If the BTS fails to establish synchronisation at radio L1 duringIf the BTS fails to establish synchronisation at radio L1 duringtimer t_inisyf, it will send an RL failure message indicating a timer t_inisyf, it will send an RL failure message indicating a cause cause ‘‘synchronisation failuresynchronisation failure’’ to the RNC.to the RNC.UPDATED: When the RRC connection access fails due to radio UPDATED: When the RRC connection access fails due to radio interface synchronisation.interface synchronisation.

GCN11GCN11RRC_CONN_ACC_FAIL_RADIORRC_CONN_ACC_FAIL_RADIO


M1001C8M1001C8A number of RRC connection access completions.A number of RRC connection access completions.UPDATED: When the RRC connection access is complete.UPDATED: When the RRC connection access is complete.

GCN10GCN10RRC_CONN_ACC_COMPRRC_CONN_ACC_COMP


M1001C7M1001C7A number of RRC connection setup failures caused by a frozen BTSA number of RRC connection setup failures caused by a frozen BTS..When the RRC connection setup is rejected because of a frozen When the RRC connection setup is rejected because of a frozen BTS.BTS.Frozen BTS means that currently no new RRC connections are Frozen BTS means that currently no new RRC connections are allowed.allowed.UPDATED: When the RRC connection setup fails because of the UPDATED: When the RRC connection setup fails because of the frozen BTS.frozen BTS.

GCN9GCN9RRC_CONN_STP_FAIL_FROZBSRRC_CONN_STP_FAIL_FROZBS






M1001C17M1001C17A number of RRC connection active failures caused by a BTS.A number of RRC connection active failures caused by a BTS.UPDATED: When the RRC connection active fails for reasons UPDATED: When the RRC connection active fails for reasons originated in the BTS.originated in the BTS.

GCN19GCN19RRC_CONN_ACT_FAIL_BTSRRC_CONN_ACT_FAIL_BTS


M1001C16M1001C16A number of RRC connection active failures caused by a radio A number of RRC connection active failures caused by a radio interface.interface.UPDATED: When the RRC connection active fails due to a radio UPDATED: When the RRC connection active fails due to a radio interface.interface.

GCN18GCN18RRC_CONN_ACT_FAIL_RADIORRC_CONN_ACT_FAIL_RADIO


M1001C15M1001C15A number of RRC connection active failures caused by the lu A number of RRC connection active failures caused by the lu Interface.Interface.When, for example, the signaling connection fails between the When, for example, the signaling connection fails between the RNC and CN.RNC and CN.UPDATED: When the RRC connection active fails because of the IurUPDATED: When the RRC connection active fails because of the Iurinterface.interface.

GCN17GCN17RRC_CONN_ACT_FAIL_IURRC_CONN_ACT_FAIL_IU


M1001C13M1001C13A number of RRC Connection active releases due to SRNC A number of RRC Connection active releases due to SRNC relocation.relocation.NOTE! This counter includes both SRNS relocations and interNOTE! This counter includes both SRNS relocations and inter--RNC RNC intraintra--frequency hard handovers.frequency hard handovers.UPDATED: When the RRC active connection is released due to the UPDATED: When the RRC active connection is released due to the SRNC relocation. This counter is also updated in case of ISHO.SRNC relocation. This counter is also updated in case of ISHO.

GCN15GCN15RRC_CONN_ACT_REL_SRNCRRC_CONN_ACT_REL_SRNC


M1001C12M1001C12A number of RRC connection active completions.A number of RRC connection active completions.UPDATED: When the RRC connection active is released normally.UPDATED: When the RRC connection active is released normally.

GCN14GCN14RRC_CONN_ACT_COMPRRC_CONN_ACT_COMP


M1001C14M1001C14A number of RRC connection active releases due to preA number of RRC connection active releases due to pre--emption.emption.UPDATED: When the RRC active connection is released due to UPDATED: When the RRC active connection is released due to preemption.preemption.

GCN16GCN16RRC_CONN_ACT_REL_P_EMPRRC_CONN_ACT_REL_P_EMP






M1001C18M1001C18A number of RRC connection active failures caused by the Iur A number of RRC connection active failures caused by the Iur Interface.Interface.When, for example, the SRNC relocation procedure fails because oWhen, for example, the SRNC relocation procedure fails because of f the Iur Interface.the Iur Interface.UPDATED: When the RRC connection active fails for reasons causedUPDATED: When the RRC connection active fails for reasons causedby the Iur interface.by the Iur interface.

GCN20GCN20RRC_CONN_ACT_FAIL_IURRRC_CONN_ACT_FAIL_IUR


M1001C19M1001C19A number of RRC connection active failures caused by a cipheringA number of RRC connection active failures caused by a cipheringfailure.failure.UPDATED: When ciphering fails.UPDATED: When ciphering fails.

GCN21GCN21RRC_CONN_ACT_FAIL_CIPHRRC_CONN_ACT_FAIL_CIPH


M1001C21M1001C21A number of RRC connection active failures caused by RNCA number of RRC connection active failures caused by RNC’’s s internal reasons (for example, parameter mismatch, timer expiry)internal reasons (for example, parameter mismatch, timer expiry)..UPDATED: When the RRC connection active fails during the RRC UPDATED: When the RRC connection active fails during the RRC connection active phase or when moving to RRC active state.connection active phase or when moving to RRC active state.

GCN23GCN23RRC_CONN_ACT_FAIL_RNCRRC_CONN_ACT_FAIL_RNC


M1001C20M1001C20A number of RRC connection active failures caused by an integritA number of RRC connection active failures caused by an integrity y check failure.check failure.UPDATED: When the integrity check fails.UPDATED: When the integrity check fails.

GCN22GCN22RRC_CONN_ACT_FAIL_I_CHKRRC_CONN_ACT_FAIL_I_CHK




Thank You!Thank You!

Nokia Ran Kpis Part 1 Rrc

Documents

Transcript of Nokia Ran Kpis Part 1 Rrc