3 wcdma ran access kpi and relative counters ran10

WCDMA RAN Access Counters and KPI Introduction

Confidential Information of Huawei. No Spreading Without

Permission

www.huawei.com

Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

WCDMA RAN Access

KPI and Relative Counters



Permission

Page1Copyright © 2009 Huawei Technologies Co., Ltd. All rights reserved.

Foreword

� In UTRAN, the whole access process includes following

steps:

� RRC connection

establishment

� Initial direct transfer

� Authentication

� Security mode

� Radio access bearer

(RAB) establishment



Permission


Objectives

� Upon completion of this course, you will be able to:

� Know the relevant access counters in UTRAN

� Know the architecture for access counters

� Know the access KPI



Permission


Contents

1. RRC Establishment Counters and KPI

2. RAB Establishment Counters and KPI



Permission


RRC Establishment Flow

� RRC connection request

� Establishment request for different cause

� The establishment causes of RRC connection are defined in

3GPP TS.25.331

� Establishment request on

different TrCH

� Common channel

� Dedicated channel

� The establishment cause of RRC connection are defined in 3GPP TS.25.331. RRC connection

should be carried by CCH or DCH due to different causes.

Originating Conversational Call

Originating Streaming Call

Originating Interactive Call

Originating Background Call

Originating Subscribed Traffic Call

Terminating Conversational Call

Terminating Streaming Call

Terminating Interactive Call

Terminating Background Call

Emergency Call

Inter-RAT Cell Re-selection

Registration

Detach

Originating High Priority Signaling

Originating Low Priority Signaling

Call Re-establishment

Terminating High Priority Signaling

Terminating Low Priority Signaling

Terminating - Cause Unknown

RRC Connection

Establishment Cause



Permission



� RRC connection setup

� Established on different channel

� Common channel




Permission



� RRC connection setup complete

� RRC connection setup complete for different causes

� RRC connection setup complete on different channels

� Common channel




Permission



� RRC connection setup failure

� RRC connection setup failure

� RRC connection setup failure due to network congestion



Permission


RRC Connection Successful Ratio

� According to Huawei definition, the RRC Connection

Successful Ratio is calculate by the following formula:

NumberAttemptConnectionRRC

NumberSuccessfulConnectionRRCRatioSuccessfulConnectionRC =R



Permission


Contents


1.1 RRC Establishment Counters for RNC

1.2 RRC Establishment Counters for Cell

1.3 RRC Establishment KPI



Permission


RRC Establishment Counters for RNC

� The RNC counters for RRC connection request

� Number of RRC Connection Requests Received by RNC

� VS.RRC.AttConnEstab.Msg

� Number of RRC Connection Requests Handled by the RNC

� VS.RRC.AttConnEstab

� VS.RRC.AttConnEstab.Msg provides the number of RRC CONNECTION REQUEST

messages from UEs to the RNC. When a UE attempts to access the network, it sends an RRC

CONNECTION REQUEST message to the RNC possibly many times to increase the

connection probability. Each time the RNC receives the RRC CONNECTION REQUEST

message, the measurement is triggered.

� VS.RRC.AttConnEstab provides the number of RRC CONNECTION REQUEST messages

actually processed by the RNC (without retransmission condition).

� The measurement of above counters are triggered at point A in the following figure `



Permission




� Number of processed RRC connection setup requests in

CELL_FACH target state

� VS.RRC.AttConnEstab.CCH

� Number of processed RRC connection setup requests in

CELL_DCH target state

� VS.RRC.AttConnEstab.DCH

� VS.RRC.AttConnEstab contains the

VS.RRC.AttConnEstab.DCH and VS.RRC.AttConnEstab.CCH

� The above counters are trigged at point A in the following figure

� The above counters increases by one after the RNC receives an RRC CONNECTION

REQUEST message from a UE. The RNC does not count the RRC CONNECTION REQUEST

messages repetitively sent by the UE.

� VS.RRC.AttConnEstab contains the VS.RRC.AttConnEstab.DCH and

VS.RRC.AttConnEstab.CCH

Counter Sub-counter

VS.RRC.AttConnEstab.DCH

VS.RRC.AttConnEstab.CCHVS.RRC.AttConnEstab



Permission




� Number of RRC CONNECTION REQUEST messages that the

RNC receives from the UEs and then actually processes for

different RRC connection request causes

� The RRC connection request causes as listed in following table

are classified in section 10.3.3.11 of 3GPP TS 25.331

� VS.RRC.AttConnEstab.CAUSEx

� VS.RRC.AttConnEstab contains the VS.RRC.AttConnEstab.CAUSEx

� The different causes for RRC connection attempt counter per RNC

Counter Sub-counter Description

VS.RRC.AttConnEstab.OrgConv Originating Conversational Call

VS.RRC.AttConnEstab.OrgStr Originating Streaming Call

VS.RRC.AttConnEstab.OrgInt Originating Interactive Call

VS.RRC.AttConnEstab.OrgBkg Originating Background Call

VS.RRC.AttConnEstab.OrgSubs Originating Subscribed Traffic Call

VS.RRC.AttConnEstab.TrmConv Terminating Conversational Call

VS.RRC.AttConnEstab.TrmStr Terminating Streaming Call

VS.RRC.AttConnEstab.TrmInt Terminating Interactive Call

VS.RRC.AttConnEstab.TrmBkg Terminating Background Call

VS.RRC.AttConnEstab.Emg Emergency Call

VS.RRC.AttConnEstab.CellRes Inter-RAT Cell Re-selection

VS.RRC.AttConnEstab.Reg Registration

VS.RRC.AttConnEstab.Detach Detach

VS.RRC.AttConnEstab.OrgHPSig Originating High Priority Signaling

VS.RRC.AttConnEstab.OrgLPSig Originating Low Priority Signaling

VS.RRC.AttConnEstab.Rest Call Re-establishment

VS.RRC.AttConnEstab.TmHPSig Terminating High Priority Signaling

VS.RRC.AttConnEstab.TmLPSig Terminating Low Priority Signaling

VS.RRC.AttConnEstab.Unknown Terminating - Cause Unknown

VS.RRC.AttConnEstab



Permission



� The RNC counters for RRC connection setup

� Number of RRC CONNECTION SETUP messages sent by the

RNC to the UE

� VS.RRC.SetupConnEstab

� Number of RRC CONNECTION SETUP messages sent by the

RNC to the UE that assign the UE to set up RRC connection in

CELL_DCH state

� VS.RRC.SetupConnEstab.DCH

� These two counters provide the number of RRC CONNECTION SETUP messages that the

RNC sends to the UEs according to different channels for RRC connection setups.

� VS.RRC.SetupConnEstab: number of RRC CONNECTION SETUP messages that the RNC

sends to the UEs.

� VS.RRC.SetupConnEstab.DCH: number of RRC CONNECTION SETUP messages that the

RNC sends to the UEs and through which the RRC connections need to be set up on the

DCHs.

� If the RNC receives a repeated RRC CONNECTION REQUEST message from a UE, it will

send the corresponding RRC CONNECTION SETUP message repeatedly to the UE but

measures this item only once.

� The above counters are triggered at point B in the following figure



Permission



� The RNC counters for RRC connection setup complete

� Number of RRC CONNECTION SETUP COMPLETE

messages received by the RNC from the UE

� VS.RRC.SuccConnEstab


messages with the target state CELL_DCH received by the

RNC from the UE

� VS.RRC.SuccConnEstab.DCH

� The above counters are triggered at point C as shown in the following figure. When the RNC

receives an RRC CONNECTION SETUP COMPLETE message from a UE, the counter shall

be incremented.



Permission





messages with the target state CELL_FACH received by the

RNC from the UE

� VS.RRC.SuccConnEstab.CCH


messages with the target state CELL_DCH received by the

RNC from the UE.

� VS.RRC.SuccConnEstab.DCH

� VS.RRC.SuccConnEstab contains the VS.RRC.SuccConnEstab.DCH

and VS.RRC.SuccConnEstab.CCH

� VS.RRC.SuccConnEstab contains the VS.RRC.SuccConnEstab.DCH and

VS.RRC.SuccConnEstab.CCH

Counter Sub-counter

VS.RRC.SuccConnEstab.CCH

VS.RRC.SuccConnEstab.DCHVS.RRC.SuccConnEstab



Permission





messages sent by the RNC to a UE by the RRC connection

request cause

� VS.RRC.SuccConnEstab.CAUSEx

� RRC connection successful counter for different cause

Counter Sub-counter Description

VS.RRC.SuccConnEstab.OrgConv Originating Conversational Call

VS.RRC.SuccConnEstab.OrgStr Originating Streaming Call

VS.RRC.SuccConnEstab.OrgInt Originating Interactive Call

VS.RRC.SuccConnEstab.OrgBkg Originating Background Call

VS.RRC.SuccConnEstab.OrgSubs Originating Subscribed Traffic Call

VS.RRC.SuccConnEstab.TrmConv Terminating Conversational Call

VS.RRC.SuccConnEstab.TrmStr Terminating Streaming Call

VS.RRC.SuccConnEstab.TrmInt Terminating Interactive Call

VS.RRC.SuccConnEstab.TrmBkg Terminating Background Call

VS.RRC.SuccConnEstab.Emg Emergency Call

VS.RRC.SuccConnEstab.CellRes Inter-RAT Cell Re-selection

VS.RRC.SuccConnEstab.Reg Registration

VS.RRC.SuccConnEstab.Detach Detach

VS.RRC.SuccConnEstab.OrgHPSi Originating High Priority Signaling

VS.RRC.SuccConnEstab.OgLPSig Originating Low Priority Signaling

VS.RRC.SuccConnEstab.Rest Call Re-establishment

VS.RRC.SuccConnEstab.TmHPSi Terminating High Priority Signaling

VS.RRC.SuccConnEstab.TmLPSi Terminating Low Priority Signaling

VS.RRC.SuccConnEstab.Unknown Terminating - Cause Unknown

VS.RRC.SuccConnEstab



Permission




� RRC successfully established number for the first RRC connection

request

� VS.RRC.SuccConnEstab.First.RNC

� RRC successfully established number for the second RRC connection

request

� VS.RRC.SuccConnEstab.Second.RNC

� RRC successfully established number for the third RRC connection

request

� VS.RRC.SuccConnEstab.Third.RNC

� The measurement is triggered at point A in the figure. The VS.RRC.SuccConnEstab.First.RNC

counter is incremented by one after the RNC receives an RRC CONNECTION SETUP

COMPLETE message from the UE.



Permission

� The measurement is triggered at point A in the figure. The

VS.RRC.SuccConnEstab.Second.RNC counter is incremented by one after the RNC receives

an RRC CONNECTION SETUP COMPLETE message from the UE.

� The measurement is triggered at point A in the figure. The

VS.RRC.SuccConnEstab.Third.RNC counter is incremented by one after the RNC receives an

RRC CONNECTION SETUP COMPLETE message from the UE.



Permission



� The RNC counters for RRC connection setup failure

� Number of rejected RRC connections

� VS.RRC.FailConEst.RNC

� Number of RRC CONNECTION REJECT messages sent from

the RNC to the UE due to network congestion

� VS.RRC.FailConEst.Cng.RNC

� The VS.RRC.FailConEst.RNC contains the value of the

VS.RRC.FailConEst.Cng.RNC

� The above counters are triggered at point A in the following figure. If the RNC fails to set up an

RRC connection for a UE, the RNC sends an RRC CONNECTION REJECT message to the

UE.



Permission


Contents




1.3 RRC Connection Establishment KPI



Permission


RRC Establishment Counters for Cell

� The cell counters for RRC connection request

� Total number of RRC connection requests

� VS.RRC.AttConnEstab.Cell

Notes:

The counter does not count

the RRC CONNECTION REQUEST

messages repeatedly sent by UEs

� The measurement is triggered at point A in the figure. After the RNC receives an RRC

CONNECTION REQUEST message from a UE, the cell where the UE is located measures

this item.



Permission




� RRC connection requests with the UE target state being CELL_DCH

� VS.RRC.AttConEst.DCH

� RRC connection requests with the UE target state being CELL_CCH

� VS.RRC.AttConEst.CCH

� Notes: The counter does not count the RRC CONNECTION REQUEST

messages repeatedly sent by UEs

� The measurement is triggered at point A in the figure. After the RNC receives an RRC

CONNECTION REQUEST message from a UE, the cell where the UE is located measures

this item according to the target RRC status of the UE.

� The counters relation

Counter Sub-counter

VS.RRC.AttConEst.CCH

VS.RRC.AttConEst.DCHVS.RRC.AttConnEstab.Cell



Permission




� As shown by point A in the figure, the RNC counts the RRC

CONNECTION REQUEST messages from a UE in the home cell of

the UE by reason of the RRC connection request

� For the classification of the reasons,

see the 3GPP TS 25.331

� RRC.AttConnEstab.CAUSEx

� Note: The RNC does not count the RRC

CONNECTION REQUEST messages

repetitively sent by the UE

� The following table describes the meanings of each counter

Counter Description

RRC.AttConnEstab.OrgConvCall Originating conversational call

RRC.AttConnEstab.OrgStrCall Originating streaming call

RRC.AttConnEstab.OrgInterCall Originating interactive call

RRC.AttConnEstab.OrgBkgCall Originating background call

RRC.AttConnEstab.OgSubCall Originating subscribed traffic call

RRC.AttConnEstab.TmConvCall Terminating conversational call

RRC.AttConnEstab.TmStrCall Terminating streaming call

RRC.AttConnEstab.TmInterCall Terminating interactive call

RRC.AttConnEstab.TmBkgCall Terminating background call

RRC.AttConnEstab.EmgCall Emergency call

RRC.AttConnEstab.IRATCelRes Inter-RAT cell re-selection

RRC.AttConnEstab.IRATCCO Inter-RAT cell change order

RRC.AttConnEstab.Reg Registration

RRC.AttConnEstab.Detach Detach

RRC.AttConnEstab.OgHhPrSig Originating high priority signaling

RRC.AttConnEstab.OgLwPrSig Originating low priority signaling

RRC.AttConnEstab.CallReEst Call re-establishment

RRC.AttConnEstab.TmHhPrSig Terminating high priority signaling

RRC.AttConnEstab.TmLwPrSig Terminating low priority signaling

RRC.AttConnEstab.Unknown Terminating - cause unknown



Permission



� The cell counters for RRC connection setup

� After receiving an RRC CONNECTION REQUEST message from a

UE, the RNC sends an RRC CONNECTION SETUP message to the

UE. At this time, the cell where the UE is located measures this item

� VS.RRC.SetupConnEstab.Cell

� Note: The RNC does not count RRC

CONNECTION SETUP messages

repeatedly sent to UEs



Permission



� The cell counters for RRC connection setup complete

� Total number of RRC connection requests

� RRC.SuccConnEstab.sum

� The measurement is triggered at point

C in Figure. After the RNC receives

an RRC CONNECTION SETUP

COMPLETE message from a UE, the

cell where the UE is located measures

this item



Permission




� RRC connection requests with the UE target state being CELL_DCH

� VS.RRC.SuccConEst.DCH

� RRC connection requests with the UE target state being CELL_FACH

� VS.RRC.SuccConEst.CCH

� The counter relation

Counter Sub-Counter

VS.RRC.SuccConEst.DCH

VS.RRC.SuccConEst.CCHRRC.SuccConnEstab.sum



Permission




� The measurement is triggered at point C in the figure. After the RNC

receives an RRC CONNECTION SETUP COMPLETE message from

a UE, the cell where the UE is located measures this item according

to the RRC connection request cause in the RRC CONNECTION

REQUEST message

� For the classification of the reasons,

see the 3GPP TS 25.331

� RRC.SuccConnEstab.CAUSEx

� The following table describes the meanings of each counter

Counter Description

RRC.SuccConnEstab.OgConvCall Originating conversational call

RRC.SuccConnEstab.OrgStrCall Originating streaming call

RRC.SuccConnEstab.OrgItrCall Originating interactive call

RRC.SuccConnEstab.OrgBkgCall Originating background call

RRC.SuccConnEstab.OrgSubCall Originating subscribed traffic call

RRC.SuccConnEstab.TmConvCall Terminating conversational call

RRC.SuccConnEstab.TmStrCall Terminating streaming call

RRC.SuccConnEstab.TmItrCall Terminating interactive call

RRC.SuccConnEstab.TmBkgCall Terminating background call

RRC.SuccConnEstab.EmgCall Emergency call

RRC.SuccConnEstab.IRATCelRes Inter-RAT cell re-selection

RRC.SuccConnEstab.IRATCCO Inter-RAT cell change order

RRC.SuccConnEstab.Reg Registration

RRC.SuccConnEstab.Detach Detach

RRC.SuccConnEstab.OgHhPrSig Originating high priority signaling

RRC.SuccConnEstab.OgLwPrSig Originating low priority signaling

RRC.SuccConnEstab.CallReEst Call re-establishment

RRC.SuccConnEstab.TmHhPrSig Terminating high priority signaling

RRC.SuccConnEstab.TmLwPrSig Terminating low priority signaling

RRC.SuccConnEstab.Unkown Terminating - unknown cause



Permission




� Number of RRC CONNECTION SETUP COMPLETE messages received by

the RNC from UEs in a cell if RNC receives an RRC connection request once

from the UE

� VS.RRC.SuccConnEstab.First


the RNC from UEs in a cell if RNC receives an RRC connection request twice

from the UE

� VS.RRC.SuccConnEstab.Second


the RNC from UEs in a cell if RNC receives an RRC connection request 3

times from the UE

� VS.RRC.SuccConnEstab.Third

� The above counters is triggered at point A in the figure.



Permission



� The cell counters for RRC connection setup failure

� This measurement counter provides the number of failed RRC

connection setups in a cell

� VS.RRC.FailConnEstab

� The measurement is triggered at point

A in the figure

� In this case, the cell where the UE is

located measures the item



Permission




� Number of Rejected RRC Connection Requests in a Cell for Iub

Interface Failure

� Number of rejected RRC connection setups due to RL

establishment failure (excluding RL establishment failure due to

CE congestion)

– VS.RRC.Rej.RL.Fail

� Number of rejected RRC connection setups due to TNL

establishment failure

– VS.RRC.Rej.AAL2.Fail

� The measurement is triggered at point A in the figure. The RNC sends an RRC CONNECTION

REJECT message to a UE. The related measurement counter is incremented according to the

cell where the UE is located and for different rejection causes.

� VS.RRC.FailConnEstab contains following counters

Counter Sub-counter

VS.RRC.Rej.RL.Fail

VS.RRC.Rej.AAL2.Fail

RRC.FailConnEstab.Cong

VS.RRC.FailConnEstab



Permission




� Number of RRC CONNECTION REJECT messages sent by

the RNC to UEs in a cell for congestion

� RRC.FailConnEstab.Cong

– VS.RRC.Rej.Power.Cong

– VS.RRC.Rej.ULIUBBandCong

– VS.RRC.Rej.DLIUBBandCong

– VS.RRC.Rej.UL.CE.Cong

– VS.RRC.Rej.DL.CE.Cong

– VS.RRC.Rej.Code.Cong

� The measurement is triggered at point A in the figure. The RNC sends an RRC CONNECTION

REJECT message to a UE. The measurement counter is incremented by one if the rejection

cause is congestion.

� RRC.FailConnEstab.Cong contains the following counters

Counter Sub-Counter

VS.RRC.Rej.Power.Cong

VS.RRC.Rej.UL.CE.Cong

VS.RRC.Rej.DL.CE.Cong

VS.RRC.Rej.Code.Cong

VS.RRC.Rej.ULIUBBandCong

VS.RRC.Rej.DLIUBBandCong




Permission




� Number of RRC redirections in a cell with different frequencies

� VS.RRC.Rej.Redir.Inter.Att

� Number of RRC redirections in a cell with different systems

� VS.RRC.Reject.Redir.Intrat

� The measurement is triggered at point A in the figure. When the RNC fails to set up an RRC

connection for a UE, the RNC sends an RRC CONNECTION REJECT message to the UE. To

improve the access success rate of the UE, the RNC can carry redirection information in the

message. In this case, the cell where the UE is located measures the items according to the

redirection types.



Permission




� The measurement counter provides the times no RRC CONNECT

SETUP COMPLETE messages are received from UEs after the RNC

sends RRC CONNECT SETUP messages to UEs

� RRC.FailConnEstab.NoReply



Permission



� The RRC setup failure counters relation in cell

Counter Sub-counter Sub-counter

VS.RRC.Rej.RL.Fail -

VS.RRC.Rej.AAL2.Fail -

VS.RRC.Rej.Power.Cong

VS.RRC.Rej.UL.CE.Cong

VS.RRC.Rej.DL.CE.Cong

VS.RRC.Rej.Code.Cong

VS.RRC.Rej.ULIUBBandCong

VS.RRC.Rej.DLIUBBandCong

RRC.FailConnEstab.NoReply - -


VS.RRC.FailConnEstab



Permission


Contents




1.3 RRC Establishment KPI



Permission


RRC Establishment KPI

� RRC Setup Success Ratio (other)

� The RRC setup procedure is trigged by different reasons which are divided into

two classes

� related service

� other reasons



Permission



� RRC Setup Success Ratio (service)

� RRCConnectionAttemptservice (Cell) = RRC.AttConnEstab.OrgConvCall +

RRC.AttConnEstab.OrgStrCall + RRC.AttConnEstab.OrgInterCall +

RRC.AttConnEstab.OrgBkgCall + RRC.AttConnEstab.OgSubCall +

RRC.AttConnEstab.TmConvCall + RRC.AttConnEstab.TmStrCall +

RRC.AttConnEstab.TmInterCall + RRC.AttConnEstab.TmBkgCall +

RRC.AttConnEstab.EmgCall +RRC.AttConnEstab.Unknown + RRC.AttConnEstab.OgHhPrSig

+RRC.AttConnEstab.OgLwPrSig + RRC.AttConnEstab.CallReEst

+RRC.AttConnEstab.TmHhPrSig + RRC.AttConnEstab.TmLwPrSig

� RRCConnectionSuccessservice (Cell) = RRC.SuccConnEstab.OgConvCall +

RRC.SuccConnEstab.OrgStrCall + RRC.SuccConnEstab.OrgItrCall +

RRC.SuccConnEstab.OrgBkgCall + RRC.SuccConnEstab.OrgSubCall +

RRC.SuccConnEstab.TmConvCall + RRC.SuccConnEstab.TmStrCall +

RRC.SuccConnEstab.TmItrCall + RRC.SuccConnEstab.TmBkgCall +

RRC.SuccConnEstab.EmgCall + RRC.SuccConnEstab.Unkown +

RRC.SuccConnEstab.OgHhPrSig + RRC.SuccConnEstab.OgLwPrSig +

RRC.SuccConnEstab.CallReEst + RRC.SuccConnEstab.TmHhPrSig +

RRC.SuccConnEstab.TmLwPrSig



Permission



� RRC Setup Success Ratio in Statistic



Permission


Discussion

� We found the following problem during this week

� RRC Setup Success Ratio (service) has deteriorated from

99.5% to 97%

� We found RSSR deterioration due to

VS.RRC.Rej.Power.Cong after analysis

� Which factors effects the RSSRservice

� How to analyze the reason for this problem



Permission


Discussion

� Which factors effects the RSSR deterioration

� Admission strategy for RRC connection

� Check the RTWP and TCP for TopN bad cells

� RTWP for TopN bad cells

� RTWP rise due to traffic

� RTWP rise due to abnormal interference

� RTWP rise due to missing neighbor

� ……

� TCP for TopN bad cells

� TCP rise due to traffic

� TCP rise due to other reasons

� ……



Permission


Discussion


� Admission strategy for RRC connection

� RRC connection request with other reasons

– Enable OLC (Overload Control)

~ UL / DL OLC trigger threshold as admission

– Disable OLC (Overload Control)

~ Direct Admission

� Emergency call, Detach, Registration

– Direct Admission



Permission


Discussion


� We should check VS.MaxRTWP and VS.MaxTCP for TopN

bad cells

� excessive RTWP rise results in UL power congestion

� excessive TCP rise results in DL power congestion



Permission


Discussion


� The main reasons results in excessive RTWP rise

� excessive RTWP rise due to traffic

– Check traffic counters

� excessive RTWP rise due to abnormal interference

� excessive RTWP rise due to missing neighbor

� Related traffic counters UL DL

VS.AMR.Ctrl.DL12.2 VS.AMR.Ctrl.UL12.2

VS.RB.DLConvCS.64 VS.RB.ULConvCS.64

VS.RB.DLInterPS.8 VS.RB.ULInterPS.8








VS.RB.DLBkgPS.8 VS.RB.ULBkgPS.8








HSPA User VS.HSDPA.UE.Mean.Cell VS.HSUPA.UE.Mean.Cell

VS.PS.Int.Kbps.DL8 VS.PS.Int.Kbps.UL8








VS.PS.Bkg.Kbps.DL8 VS.PS.Bkg.Kbps.UL8








VS.HSDPA.MeanChThroughput VS.HSUPA.MeanChThroughput

VS.HSDPA.MeanChThroughput.TotalBytes VS.HSUPA.MeanChThroughput.TotalBytes

VS.MeanTCP VS.MeanRTWP

VS.MaxTCP VS.MaxRTWP

VS.MinTCP VS.MinRTWP

VS.RRC.AttConnEstab.Cell VS.RRC.AttConnEstab.Cell

VS.RAB.AttEstab.AMR VS.RAB.AttEstab.AMR

VS.RAB.AttEstCS.Conv.64 VS.RAB.AttEstCS.Conv.64

VS.RAB.AttEstabPS.Cell VS.RAB.AttEstabPS.Cell

VS.HSDPA.RAB.AttEstab VS.HSDPA.RAB.AttEstab

VS.HSUPA.RAB.AttEstab VS.HSUPA.RAB.AttEstab

Power

Call Attempt Times

Throughput

R99 PS Throughput

HSPA Traffic

RB Number

CS Erlang

PS Erlang



Permission


Discussion


� The main reasons results in excessive TCP rise

� excessive TCP rise due to traffic

� excessive TCP rise due to other reasons



Permission


Contents





Permission


Contents


2.1 RAB Establishment Counters for RNC

2.2 RAB Establishment Counters for Cell

2.3 RAB Establishment KPI



Permission


RAB Establishment Successful Ratio

� According to Huawei definition, the RAB Setup Successful

Ratio is calculate by the following formula:

NumberAttemptSetupRAB

NumberSuccessfulSetupRABRatioSuccessfulSetupAB =R



Permission


RAB Establishment Counters for RNC

� CS RAB Establishment Counters for RNC

� Number of CS RABs Requested to Establish

� Based on traffic class

– CS conversational ; CS streaming

� Based on traffic class and DL MBR (Max. bit rate)

– Conv0.32 ; Conv32.64

– Str0.32 ; Str32.64

� RAB setup procedure



Permission




� Number of CS RABs Successfully Established on Request

� Based on traffic class and queuing

– CS Conv Noqueuing; CS Conv Queuing

– CS Str Noqueuing; CS Str Queuing


– Conv0.32 ; Conv32.64

– Str0.32 ; Str32.64



Permission






– Number of CS RABs requested to establish for conversational services

~ RAB.AttEstabCS.Conv

– Number of CS RABs requested to

establish for streaming services

~ RAB.AttEstabCS.Strm

� The measurement is triggered at point A as shown in the figure. When the RNC receives from

the CN a RAB ASSIGNMENT REQUEST message and if the message is from the CS domain,

the RNC measures these items according to different types of services.



Permission




� Number of CS RABs Requested to Establish at Different Max DL Bit

Rates

� Number of CS RABs requested to establish for conversational

services (max DL bit rate in [0.32] kbit/s)

– VS.RAB.AttEstCSConv0.32.RNC

� Number of CS RABs requested to establish for conversational

services (max DL bit rate in (32.64] kbit/s)

– VS.RAB.AttEstCSConv32.64.RNC



Permission




� Number of CS RABs Requested to Establish at Different Max DL Bit

Rates

� Number of CS RABs requested to establish for streaming services

(max DL bit rate in [0.32] kbit/s)

– VS.RAB.AttEstCSStr0.32.RNC

� Number of CS RABs requested to establish for streaming services

(max DL bit rate in (32.64] kbit/s)

– VS.RAB.AttEstCSStr32.64.RNC


Counter Sub-Counter

VS.RAB.AttEstCSConv0.32.RNC

VS.RAB.AttEstCSConv32.64.RNC

VS.RAB.AttEstCSStr0.32.RNC

VS.RAB.AttEstCSStr32.64.RNCRAB.AttEstabCS.Strm

RAB.AttEstabCS.Conv



Permission




� Number of CS RABs Successfully Established on Request (No

Queuing)


– Number of CS RABs successfully established for conversational

services (no queuing)

~ RAB.SuccEstabCSNoQueuing.Conv

– Number of CS RABs successfully established for streaming services

(no queuing)

~ RAB.SuccEstabCSNoQueuing.Strm



Permission




� Number of CS RABs Successfully Established on Request (With

Queuing)


– Number of CS RABs successfully established for conversational

services (with queuing)

~ RAB.SuccEstabCSQueuing.Conv

– Number of CS RABs established successfully for streaming services

(with queuing)

~ RAB.SuccEstabCSQueuing.Strm



Permission




� Number of CS RABs Successfully Established at Different Max DL Bit

Rates

� Number of CS RABs successfully established for conversational


– VS.RAB.SucEstCSConv0.32.RNC

� Number of CS RABs successfully established for conversational


– VS.RAB.SucEstCSConv32.64.RNC



Permission




� Number of CS RABs Successfully Established at Different Max DL Bit

Rates

� Number of CS RABs successfully established for streaming


– VS.RAB.SucEstCSStr0.32.RNC

� Number of CS RABs successfully established for streaming


– VS.RAB.SucEstCSStr32.64.RNC



Permission



� PS RAB Establishment Counters for RNC

� Number of PS RABs Requested to Establish


– Conversational; Streaming; Interactive; Background


– Conv0.32 ; ConvMore32

– Str0.32 ; Str32.64 ; Str64.144 ; Str144.384 ; StrMore384

– Int0.32 ; Int32.64 ; Int64.144 ; Int144.384 ; IntMore384

– Bkg0.32 ; Bkg32.64 ; Bkg64.144 ; Bkg144.384 ; BkgMore384



Permission




� Number of PS RABs Successfully Established on Request

� Based on traffic class and queuing

– PS Conv Noqueuing ; PS Conv Queuing

– PS Str Noqueuing ; PS Str Queuing

– PS Int Noqueuing ; PS Int Queuing

– PS Bkg Noqueuing ; PS Bkg Queuing


– Conv0.32 ; ConvMore32

– Str0.32 ; Str32.64 ; Str64.144 ; Str144.384 ; StrMore384

– Int0.32 ; Int32.64 ; Int64.144 ; Int144.384 ; IntMore384

– Bkg0.32 ; Bkg32.64 ; Bkg64.144 ; Bkg144.384 ; BkgMore384



Permission





� Number of the PS RABs requested to establish for conversational services

– RAB.AttEstabPS.Conv

� Number of the PS RABs requested to establish for streaming services

– RAB.AttEstabPS.Strm

� Number of the PS RABs requested to establish for interactive services

– RAB.AttEstabPS.Intact

� Number of the PS RABs requested to establish for background services

– RAB.AttEstabPS.Bgrd



Permission





Counter Description

VS.RAB.AttEstPSConv0.32.RNCNumber of PS RABs requested to establish for conversational

services (max DL bit rate in [0,32] kbit/s)

VS.RAB.AttEstPSConvMor32.RNCNumber of PS RABs requested to establish for conversational

services (max DL bit rate more than 32 kbit/s)

VS.RAB.AttEstPSStr0.32.RNCNumber of PS RABs requested to establish for streaming services

(max DL bit rate in [0,32] kbit/s)


(max DL bit rate in (32,64] kbit/s)



VS.RAB.AttEstPSStr144384.RNCNumber of PS RABs requested to establish for streaming services


VS.RAB.AttEstPSStrMor384Number of PS RABs requested to establish for streaming services

(max DL bit rate more than 384 kbit/s)

VS.RAB.AttEstPSInt0.32.RNCNumber of PS RABs requested to establish for interactive services

(max DL bit rate in [0,32] kbit/s)





VS.RAB.AttEstPSInt144384.RNCNumber of PS RABs requested to establish for interactive services


VS.RAB.AttEstPSIntMor384.RNCNumber of PS RABs requested to establish for interactive services

(max DL bit rate more than 384 kbit/s)

VS.RAB.AttEstPSBkg0.32.RNCNumber of PS RABs requested to establish for background



services (max DL bit rate in (32,64] kbit/s)



VS.RAB.AttEstPSBkg144384.RNCNumber of PS RABs requested to establish for background


VS.RAB.AttEstPSBkgMor384.RNCNumber of PS RABs requested to establish for background




Permission




� Number of PS RABs Successfully Established on Request (No

Queuing)

� Number of PS RABs successfully established for conversational services

(no queuing)

– RAB.SuccEstabPSNoQueuing.Conv

� Number of PS RABs successfully established for streaming services (no

queuing)

– RAB.SuccEstabPSNoQueuing.Strm

� Number of PS RABs successfully established for interactive services (no

queuing)

– RAB.SuccEstabPSNoQueuing.Intact

� Number of PS RABs successfully established for background services (no

queuing)

– RAB.SuccEstabPSNoQueuing.Bgrd



Permission




� Number of PS RABs Successfully Established on Request (with

Queuing)

� Number of PS RABs successfully established for conversational services

(with queuing)

– RAB.SuccEstabPSQueuing.Conv

� Number of PS RABs successfully established for streaming services (with

queuing)

– RAB.SuccEstabPSQueuing.Strm

� Numbers of PS RABs successfully established for interactive services (with

queuing)

– RAB.SuccEstabPSQueuing.Intact

� Numbers of PS RABs successfully established for background services

(with queuing)

– RAB.SuccEstabPSQueuing.Bgrd



Permission




� Number of PS RABs Successfully Established

Counter Description

VS.RAB.SucEstPSConv0.32.RNCNumber of PS RABs successfully established for conversational


VS.RAB.SucEstPSConvMor32.RNCNumber of PS RABs successfully established for conversational


VS.RAB.SucEstPSStr0.32.RNCNumber of PS RABs successfully established for streaming






VS.RAB.SucEstPSStr144384.RNCNumber of PS RABs successfully established for streaming


VS.RAB.SucEstPSStrMor384.RNCNumber of PS RABs successfully established for streaming


VS.RAB.SucEstPSInt0.32.RNCNumber of PS RABs successfully established for interactive






VS.RAB.SucEstPSInt144384.RNCNumber of PS RABs successfully established for interactive


VS.RAB.SucEstPSIntMor384.RNCNumber of PS RABs successfully established for interactive


VS.RAB.SucEstPSBkg0.32.RNCNumber of PS RABs successfully established for background






VS.RAB.SucEstPSBkg144384.RNCNumber of PS RABs successfully established for background


VS.RAB.SucEstPSBkgMor384.RNCNumber of PS RABs successfully established for background




Permission




� Number of CS RABs Unsuccessfully Established on Request

for Different Causes (No Queuing) Counter Description

RAB.FailEstabCSNoQueuing.DirRetry Directed retry

RAB.FailEstabCSNoQueuing.DLGrateUnavail Requested Guaranteed Bit Rate For DL Not Available

RAB.FailEstabCSNoQueuing.DLMaxrateUnavail Requested Maximum Bit Rate For DL Not Available

RAB.FailEstabCSNoQueuing.InvGrate Condition violation for guaranteed bit rate

RAB.FailEstabCSNoQueuing.InvRABId Invalid RAB ID

RAB.FailEstabCSNoQueuing.InvRABparam Invalid RAB parameters value

RAB.FailEstabCSNoQueuing.InvRABPComb Invalid RAB parameters combination

RAB.FailEstabCSNoQueuing.InvSDUparam Condition violation for SDU parameters

RAB.FailEstabCSNoQueuing.InvTrfPri Condition violation for traffic handling priority

RAB.FailEstabCSNoQueuing.IUEstabFail IU transport connection failed to establish

RAB.FailEstabCSNoQueuing.MaxrateUnavail Requested max bit rate not available

RAB.FailEstabCSNoQueuing.RelocTrig Relocation triggered

RAB.FailEstabCSNoQueuing.ResUnavail No resource available

RAB.FailEstabCSNoQueuing.TrfClassUnavail Requested traffic class not available

RAB.FailEstabCSNoQueuing.ULGrateUnavail Requested Guaranteed Bit Rate For UL Not Available

RAB.FailEstabCSNoQueuing.ULMaxrateUnavail Requested Maximum Bit Rate For UL Not Available

RAB.FailEstabCSNoQueuing.UPverUnsupp User plane versions not supported

� The measurement are triggered at point B as shown in the figure. When the RNC sends the

CN a RAB ASSIGNMENT RESPONSE message indicating unsuccessful CS RAB setup and if

the message is from the CN domain and these RABs have not queued for the request, the

RNC measures these items according to different failure causes in the message.



Permission




� Number of CS RABs Unsuccessfully Established on Request

for Different Causes (With Queuing)

Counter Description

RAB.FailEstabCSQueuing.DirRetry Directed retry

RAB.FailEstabCSQueuing.DLGrateUnavail Requested Guaranteed Bit Rate For DL Not Available

RAB.FailEstabCSQueuing.DLMaxrateUnavail Requested Maximum Bit Rate For DL Not Available

RAB.FailEstabCSQueuing.IUEstabFail IU transport connection failed to establish

RAB.FailEstabCSQueuing.RadioFail Failure in the radio interface procedure

RAB.FailEstabCSQueuing.RelocTrig Relocation triggered

RAB.FailEstabCSQueuing.ReqSupsed Request superseded

RAB.FailEstabCSQueuing.ResUnavail No resource available

RAB.FailEstabCSQueuing.TqueExp Queuing Expiry

RAB.FailEstabCSQueuing.ULGrateUnavail Requested Guaranteed Bit Rate For UL Not Available

RAB.FailEstabCSQueuing.ULMaxrateUnavail Requested Maximum Bit Rate For UL Not Available

� The measurement is triggered at point B as shown in the figure. When the RNC sends the CN

a RAB ASSIGNMENT RESPONSE message indicating unsuccessful CS RAB setup, and if the

message is from the CS domain and these RABs have queued for the request, the RNC

measures these items according to different failure causes in the message.



Permission




� Number of PS RABs Unsuccessfully Established on Request for

Different Causes (No Queuing)

Counter Description

RAB.FailEstabPSNoQueuing.DLGrateUnavail Requested Guaranteed Bit Rate For DL Not Available

RAB.FailEstabPSNoQueuing.DLMaxrateUnavail Requested Maximum Bit Rate For DL Not Available

RAB.FailEstabPSNoQueuing.InvGrate Condition violation for guaranteed bit rate

RAB.FailEstabPSNoQueuing.InvRABId Invalid RAB ID

RAB.FailEstabPSNoQueuing.InvRABparam Invalid RAB parameters value

RAB.FailEstabPSNoQueuing.InvRABPComb Invalid RAB parameters combination

RAB.FailEstabPSNoQueuing.InvSDUparam Condition violation for SDU parameters

RAB.FailEstabPSNoQueuing.InvTrfPri Condition violation for traffic handling priority

RAB.FailEstabPSNoQueuing.IUEstabFail IU transport connection failed to establish

RAB.FailEstabPSNoQueuing.RelocTrig Relocation triggered

RAB.FailEstabPSNoQueuing.ReqSupsed Request superseded

RAB.FailEstabPSNoQueuing.ResUnavail No resource available

RAB.FailEstabPSNoQueuing.TrDelayUnavail Requested transfer delay not achievable

RAB.FailEstabPSNoQueuing.TrfClassUnavail Requested traffic class not available

RAB.FailEstabPSNoQueuing.ULGrateUnavail Requested Guaranteed Bit Rate For UL Not Available

RAB.FailEstabPSNoQueuing.ULMaxrateUnavail Requested Maximum Bit Rate For UL Not Available

RAB.FailEstabPSNoQueuing.UPverUnsupp User plane versions not supported


a RAB ASSIGNMENT RESPONSE message indicating that the PS RAB setup fails and these

RABs have not queued, the RNC measures these items according to the failure cause in the

message.



Permission




� Number of CS RABs Unsuccessfully Established on Request for

Different Causes (with Queuing)

Counter Description

RAB.FailEstabPSQueuing.DirRetry Directed retry

RAB.FailEstabPSQueuing.DLGrateUnavail Requested Guaranteed Bit Rate For DL Not Available

RAB.FailEstabPSQueuing.DLMaxrateUnavail Requested Maximum Bit Rate For DL Not Available

RAB.FailEstabPSQueuing.IUEstabFail IU transport connection failed to establish

RAB.FailEstabPSQueuing.RadioFail Failure in the radio interface procedure

RAB.FailEstabPSQueuing.RelocTrig Relocation triggered

RAB.FailEstabPSQueuing.ReqSupsed Request superseded

RAB.FailEstabPSQueuing.ResUnavail No resource available

RAB.FailEstabPSQueuing.TqueExp Queuing Expiry

RAB.FailEstabPSQueuing.ULGrateUnavail Requested Guaranteed Bit Rate For UL Not Available

RAB.FailEstabPSQueuing.ULMaxrateUnavail Requested Maximum Bit Rate For UL Not Available


a RAB ASSIGNMENT RESPONSE message indicating that the PS RAB setup fails and these

RABs have ever queued, the RNC measures these items according to the failure cause in the

message.



Permission


Contents







Permission


RAB Establishment Counters for Cell

� CS RAB Establishment Counters for Cell



– Conversational ; streaming


– AMR ; AMRWB ; AMR.12.2 ; AMR.4.75 ; AMR.5.9 ; AMR.7.95 ; Conv64 ; HSPA

� Number of Successfully Established CS RABs


– Conversational ; streaming


– AMR ; AMRWB ; AMR.12.2 ; AMR.4.75 ; AMR.5.9 ; AMR.7.95 ; Conv64 ; HSPA

� The measurement is triggered at point B as shown in the figure



Permission





Counter Description

VS.RAB.AttEstabCS.Conv Number of CS conversational service RABs to be established in the best cell

VS.RAB.AttEstabCS.Str Number of CS streaming service RABs to be established in the best cell

VS.RAB.AttEstab.AMR Number of CS AMR service RABs to be established in the best cell

VS.RAB.AttEstCS.Conv.64 Number of CS 64 kbit/s service RABs to be established in the best cell

VS.RAB.AttEstabCS.AMR.12.2 Number of CS 12.2 kbit/s AMR service RABs to be established in the best cell

VS.RAB.AttEstCS.AMR.4.75 Number of CS 4.75 kbit/s AMR service RABs to be established in the best cell



� VS.RAB.AttEstab.AMR contains the following counters

Counter Sub-counter

VS.RAB.AttEstabCS.AMR.12.2

VS.RAB.AttEstCS.AMR.7.95



VS.RAB.AttEstab.AMR



Permission




� Number of Successfully Established CS RABs

Counter Description

VS.RAB.SuccEstabCS.Conv Number of CS conversational service RABs successfully established in the best cell

VS.RAB.SuccEstabCS.Str Number of CS streaming service RABs successfully established in the best cell

VS.RAB.SuccEstab.AMR Number of CS AMR service RABs successfully established in the best cell

VS.RAB.SuccEstCS.Conv.64 Number of CS 64 kbit/s service RABs successfully established in the best cell

VS.RAB.SuccEstabCS.AMR.12.2 Number of CS 12.2 kbit/s AMR service RABs successfully established in the best cell

VS.RAB.SuccEstCS.AMR.4.75 Number of CS 4.75 kbit/s AMR service RABs successfully established in the best cell



� VS.RAB.SuccEstab.AMR contains the following counters

Counter Sub-counter

VS.RAB.SuccEstabCS.AMR.12.2

VS.RAB.SuccEstCS.AMR.7.95



VS.RAB.SuccEstab.AMR



Permission



� PS RAB Establishment Counters for Cell



– Conversational ; streaming ; interactive ; background


� Number of Successfully Established PS RABs


– Conversational ; streaming ; interactive ; background


� The measurement is triggered at point B as shown in the figure



Permission



� Number of PS RABs Requested to Establish (Cell)

� The measurement items provide the number of PS RABs requested to

establish in the best cell according to different types of service

� The measurement items do not differentiate between R99 traffic and HSPA

traffic, as shown below

� Number of PS conversational service RABs requested to establish in the best cell

– VS.RAB.AttEstabPS.Conv

� Number of PS streaming service RABs requested to establish in the best cell

– VS.RAB.AttEstabPS.Str

� Number of PS interactive service RABs requested to establish in the best cell

– VS.RAB.AttEstabPS.Inter

� Number of PS background service RABs requested to establish in the best cell

– VS.RAB.AttEstabPS.Bkg

� The measurement is triggered at point A as shown in the figure. If the RNC finds that some

RABs need to be established after receiving a RAB ASSIGNMENT REQUEST message about

the PS domain from the SGSN, the RNC measures the items according to the types of service

and the quantity of RABs requested to establish in the best cell.



Permission



� Number of Successfully Established PS RABs (Cell)

� The measurement items provide the number of PS RABs successfully

established in a cell, regardless of R99 or HSPA

� Number of PS conversational service RABs successfully established in the best cell

– VS.RAB.SuccEstabPS.Conv

� Number of PS streaming service RABs successfully established in the best cell

– VS.RAB.SuccEstabPS.Str

� Number of PS interactive service RABs successfully established in the best cell

– VS.RAB.SuccEstabPS.Inter

� Number of PS background service RABs successfully established in the best cell

– VS.RAB.SuccEstabPS.Bkg

� The measurement is triggered at point B as shown in the figure. If the RNC finds that some

RABs have been successfully set up after receiving a RADIO BEARER SETUP COMPLETE

message about the PS domain from the UE, the RNC measures the items according to the

types of service and the quantity of RABs successfully established in the best cell.



Permission




� Number of PS RABs Requested to Establish at Different DL MBR

(Max. Bit Rate)

� The measurement items provide the number of PS RABs requested to

establish in the best cell according to different service types and

maximum downlink bit rates, regardless of R99 or HSPA

Counter Description

VS.RAB.Att.Est.PS.Str.0.32Number of PS RABs requested to establish for streaming

services (Max DL bit rate is in the scope of [0,32] kbit/s.)


services (Max DL bit rate is in the scope of (32,64] kbit/s.)



VS.RAB.Att.Est.PS.Str.144384Number of PS RABs requested to establish for streaming


VS.RAB.Att.Est.PS.Str.Mor384Number of PS RABs requested to establish for streaming

services (Max DL bit rate is larger than 384 kbit/s.)

VS.RAB.Att.Est.PS.Int.0.32Number of PS RABs requested to establish for interactive






VS.RAB.Att.Est.PS.Int.144384Number of PS RABs requested to establish for interactive


VS.RAB.Att.Est.PS.Int.Mor384Number of PS RABs requested to establish for interactive


VS.RAB.Att.Est.PS.Bkg.0.32Number of PS RABs requested to establish for background


VS.RAB.Att.Est.PS.Bkg.32.64

Number of PS RABs requested to establish for background


VS.RAB.Att.Est.PS.Bkg.64.144



VS.RAB.Att.Est.PS.Bkg.144384



VS.RAB.Att.Est.PS.Bkg.Mor384


services ( Max DL bit rate is larger than 384 kbit/s.)



Permission




� Number of PS RABs Successfully Established at Different DL MBR

(Max. Bit Rate)

� The measurement items provide the number of PS RABs successfully

established in the best cell according to different types of service and

maximum downlink bit rates, regardless of R99 or HSPA

Counter Description

VS.RAB.Suc.Est.PS.Str.0.32Number of PS RABs successfully established for streaming






VS.RAB.Suc.Est.PS.Str144384Number of PS RABs successfully established for streaming


VS.RAB.SucEstPS.StrMor384Number of PS RABs successfully established for streaming


VS.RAB.Suc.Est.PS.Int.0.32Number of PS RABs successfully established for interactive






VS.RAB.Suc.Est.PS.Int.144384Number of PS RABs successfully established for interactive


VS.RAB.SucEstPS.IntMor384Number of PS RABs successfully established for interactive


VS.RAB.Suc.Est.PS.Bkg.0.32Number of PS RABs successfully established for background


VS.RAB.Suc.Est.PS.Bkg.32.64

Number of PS RABs successfully established for background


VS.RAB.Suc.Est.PS.Bkg.64.144



VS.RAB.Suc.Est.PS.Bkg.144384



VS.RAB.SucEstPS.BkgMor384





Permission



� CS RABs Unsuccessfully Established for cell

� Number of CS RABs Unsuccessfully Established due to different reasons

� The measurement is triggered at point B as shown in the figure, when the RNC

sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the

operation fails and the failure cause

� In this case, the RNC measures each

item in the best cell that the UE camps

on



Permission




� Number of CS RABs Unsuccessfully Established due to Congestion

� VS.RAB.FailEstabCS.Cong

– VS.RAB.FailEstCs.Power.Cong

– VS.RAB.FailEstab.CS.DLIUBBand.Cong

– VS.RAB.FailEstab.CS.ULIUBBand.Cong

– VS.RAB.FailEstCs.ULCE.Cong

– VS.RAB.FailEstCs.DLCE.Cong

– VS.RAB.FailEstCs.Code.Cong

� “VS.RAB.FailEstabCS.Cong” is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "Requested Maximum Bit Rate not Available"," Requested Maximum Bit Rate for DL not Available" ,"Requested Maximum Bit Rate for UL not Available" ," Radio Resources Available in Target cell" ," No resource available" or "TQUEUING Expiry". In this case, the RNC measures each item in the best cell that the UE camps on.


Counter Sub-counter

VS.RAB.FailEstCs.Power.Cong

VS.RAB.FailEstCs.ULCE.Cong

VS.RAB.FailEstCs.DLCE.Cong

VS.RAB.FailEstCs.Code.Cong

VS.RAB.FailEstab.CS.DLIUBBand.Cong

VS.RAB.FailEstab.CS.ULIUBBand.Cong

VS.RAB.FailEstabCS.Cong



Permission




� Number of CS RABs Unsuccessfully Established due to Transport

Network Layer Failures

� VS.RAB.FailEstabCS.TNL

� Number of CS RABs Unsuccessfully Established due to Radio

Network Layer Failures

� VS.RAB.FailEstabCS.RNL

� “VS.RAB.FailEstabCS.TNL” is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "Transport Layer Cause". In this case, the RNC measures each item in the best cell that the UE camps on.

� “VS.RAB.FailEstabCS.RNL” is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "Radio Network Layer Cause". In this case, the RNC measures each item in the best cell that the UE camps on.



Permission




� Number of CS RABs Unsuccessfully Established due to Relocation

Process

� VS.RAB.FailEstCS.Relo

� Number of CS RABs Unsuccessfully Established due to Air Interface

Failures

� VS.RAB.FailEstCS.RIPFail

� “VS.RAB.FailEstCS.Relo” is triggered at point B as shown in the figure, when the RNC sends back a RAB ASSIGNMENT RESPONSE message with the cause of "Relocation Triggered" to the CN. In this case, the RNC measures each item in the best cell that the UE camps on.

� “VS.RAB.FailEstCS.RIPFail” is triggered at point B as shown in the figure, when the RNC sends the CN a RAB ASSIGNMENT RESPONSE message indicating that the operation fails and the failure cause is "Failure in the Radio Interface Procedure". The RNC measures this item in the best cell that the UE camps on.



Permission



� The CS RAB setup failure counters relation in cell

Counter Sub-counter (Level 1) Sub-counter (Level 2)

VS.RAB.FailEstCs.Power.Cong

VS.RAB.FailEstCs.ULCE.Cong


VS.RAB.FailEstCs.Code.Cong

VS.RAB.FailEstab.CS.DLIUBBand.Cong

VS.RAB.FailEstab.CS.ULIUBBand.Cong

VS.RAB.FailEstabCS.TNL

VS.RAB.FailEstabCS.Cong

VS.RAB.FailEstabCS.RNL

VS.RAB.FailEstCS.Relo

VS.RAB.FailEstCS.RIPFail



Permission



� PS RABs Unsuccessfully Established for cell

� Number of RABs Failing to Be Set Up in PS Domain due to

Congestion

� VS.RAB.FailEstPS.Unsp

– VS.RAB.FailEstab.PS.DLIUBBand.Cong

– VS.RAB.FailEstab.PS.ULIUBBand.Cong

– VS.RAB.FailEstPs.Power.Cong

– VS.RAB.FailEstPs.ULCE.Cong

– VS.RAB.FailEstPs.DLCE.Cong

– VS.RAB.FailEstPs.Code.Cong


Counter Sub-counter

VS.RAB.FailEstPs.Power.Cong

VS.RAB.FailEstPs.ULCE.Cong


VS.RAB.FailEstPs.Code.Cong

VS.RAB.FailEstab.PS.DLIUBBand.Cong

VS.RAB.FailEstab.PS.ULIUBBand.Cong

VS.RAB.FailEstPS.Unsp



Permission




� Number of PS RABs unsuccessfully established because of

radio network layer failures

� VS.RAB.FailEstPS.RNL


transmission network layer failures

� VS.RAB.FailEstPS.TNL

� The items VS.RAB.FailEstPS.RNL, VS.RAB.FailEstPS.TNL, and

VS.RAB.FailEstPS.NResAvail are in parallel with each other



Permission






parameter failures (cause value: Invalid RAB Parameters Value,

Invalid RAB Parameters Combination, Condition Violation for SDU

Parameters, Condition Violation for Traffic Handling Priority, or

Condition Violation for Guaranteed Bit Rate)

– VS.RAB.FailEstPS.Par

� Number of PS RABs unsuccessfully established due to relocation

(cause value: Relocation Triggered)

– VS.RAB.FailEstPS.Relo


Counter Sub-counter

VS.RAB.FailEstPS.Par

VS.RAB.FailEstPS.Relo


VS.RAB.FailEstPS.RIPFail

VS.RAB.FailEstPS.RNL



Permission





� Number of PS RABs unsuccessfully established because of radio

interface failure (cause value: Failure in the Radio Interface

Procedure)

– VS.RAB.FailEstPS.RIPFail


Counter Sub-counter








Permission





lack of system resources, for instance, a shortage of memory

(cause value: No Resource Available)

� VS.RAB.FailEstPS.NResAvail



Permission



� The PS RAB setup failure counters relation in cell

Counter Sub-counter (Level 1) Sub-counter (Level 2)

VS.RAB.FailEstPs.Power.Cong

VS.RAB.FailEstPs.ULCE.Cong


VS.RAB.FailEstPs.Code.Cong

VS.RAB.FailEstab.PS.DLIUBBand.Cong

VS.RAB.FailEstab.PS.ULIUBBand.Cong

VS.RAB.FailEstPS.TNL

VS.RAB.FailEstPS.NResAvail








Permission




� Number of Unsuccessful PS RAB Setups for Different Services due to

Congestion

Counter Description

VS.RAB.Block.PS.Conv.0.32 Conversational service Max DL bit rate is in the scope of [0,32] kbit/s.

VS.RAB.BlockPS.ConvMor32 Conversational service Max DL bit rate greater than 32 kbit/s.

VS.RAB.Block.PS.Str.64.144 Streaming service Max DL bit rate is in the scope of (64, 144] kbit/s.

VS.RAB.Block.PS.Str.144.384 Streaming service Max DL bit rate is in the scope of (144, 384] kbit/s.

VS.RAB.BlockPS.StrMor384 Streaming service Max DL bit rate greater than 384 kbit/s.

VS.RAB.Block.PS.Int.0.32 Interactive service Max DL bit rate is in the scope of [0,32] kbit/s.

VS.RAB.Block.PS.Int.32.64 Interactive service Max DL bit rate is in the scope of (32, 64] kbit/s.

VS.RAB.Block.PS.Int.64.144 Interactive service 64 less than Max DL bit rate not more than144 kbit/s.

VS.RAB.Block.PS.Int.144.384 Interactive service Max DL bit rate is in the scope of (144, 384] kbit/s.

VS.RAB.BlockPS.IntMor384 Interactive service Max DL bit rate greater than 384 kbit/s.

VS.RAB.Block.PS.Bkg.0.32 Background service Max DL bit rate is in the scope of [0,32] kbit/s.

VS.RAB.Block.PS.Bkg.32.64 Background service Max DL bit rate is in the scope of (32, 64] kbit/s.

VS.RAB.Block.PS.Bkg.64.144 Background service 64 less than Max DL bit rate not more than144 kbit/s.

VS.RAB.Block.PS.Bkg.144.384 Background service Max DL bit rate is in the scope of (144, 384] kbit/s.

VS.RAB.BlockPS.BkgMor384 Background service Max DL bit rate greater than 384 kbit/s.

� The measurement is triggered at point B as shown in the figure, when the RNC sends the SGSN a RAB ASSIGNMENT RESPONSE message indicating an unsuccessful operation and the failure cause is "Requested Maximum Bit Rate not Available", "Requested Maximum Bit Rate for DL not Available", "Requested Maximum Bit Rate for UL not Available", "No Radio Resources Available in Target cell", "No resource available", or "TQUEUING Expiry". In this case, the RNC measures the items in the best cell that the UE camps on.



Permission



� HSDPA RAB Establishment Counters for Cell

� Number of Requests for Setup of HSDPA Service

� VS.HSDPA.RAB.AttEstab

� Number of Successful Setups of HSDPA Service

� VS.HSDPA.RAB.SuccEstab

� The RNC measures this item in the serving cell of the HSDPA service

� Attempt: at point A

� Success: at point B



Permission



� HSUPA RAB Establishment Counters for Cell

� Number of Requests for Setup of HSUPA Service

� VS.HSUPA.RAB.AttEstab

� Number of Successful Setups of HSDPA Service

� VS.HSUPA.RAB.SuccEstab

� The RNC measures this item in the serving cell of the HSUPA service

� Attempt: at point A

� Success: at point B



Permission


Contents







Permission


RAB Establishment KPI

� AMR RAB Setup Success Ratio

� VP RAB Setup Success Ratio



Permission



� CS RAB Setup Success Ratio

� PS RAB Setup Success Ratio



Permission



� R99 RAB Setup Success Ratio in Statistic



Permission



� HSDPA RAB Setup Success Ratio



Permission



� HSDPA RAB Setup Success Ratio in Statistic



Permission



� HSUPA RAB Setup Success Ratio



Permission



� HSUPA RAB Setup Success Ratio in Statistic



Permission

Thank youwww.huawei.com

3 wcdma ran access kpi and relative counters ran10

Documents