Retainability Formulas v2

1

FORMULAS REVISION:RETAINABILITY

4th.November.2008

Q U A L C O M M C O N F I D E N T I A L2

INTRODUCTIONThis presentation covers the Revision of the following Formulas proposed so far for each of the three vendors (NSN, Ericsson and Huawei):

PS RetainabilityHS Retainability

Some topics need to be discussed amongst all AMX operators in order to agree about the formulas to be used, so they are not only correct but also as similar as possible for the three vendors, for benchmarking purposes.


Topics for discussion

• DCR (%) versus Retainability (%) = 100 – DCR (%)Agreement on using DCR.

• zeros in the denominators.Agreement on DCR=0% if no calls in the cell.

• PS versus R99Clarification done on the formulas proposed for R99 PS DCR. They are really covering an overall PS DCR.Under investigation how to produce (if possible) a DCR specific for R99.

• PS StreamingTo be consistent with the agreement reached on Accessibility Benchmarking Formulas (NOT to include PS Streaming), we will also remove PS Streaming from PS Retainability Benchmarking Formulas. PS Streaming will be included as one of the additional options for each of the Vendor-specific formulas.

• HandoversAgreement about SRNS Relocations and Outgoing Hard Handover (both intra and inter system) being considered as success calls in the cell (i.e., to be added in the denominators of the formulas).


Next stepsFor harmonization purposes between the three vendors, main consideration is to ensure that the formulas for the three of them are considering exactly the same Normal/Abnormal Releases.

Next slides go through what each vendor consider Normal/Abnormal releases for PS & HS DCR:

PS NORMAL RELEASES• Three of them consider the Normal RAB Release and the successful Relocations.• E/// and Huawei include also Inactivity and Network Optimization• E/// includes also 'release-due-to-UE-generated-signalling-connection-release‘ (available in a specific Counter in Huawei)• NSN includes also inter-RNC hard handovers, inter-system handovers and Directed Signalling Connection Re-establishments. And in table Packet Call: also Inactivity and state transitions to DCH (0/0)/FACH/PCH.

•For these reasons, we suggest to use PacketCall counters in NSN also for PS overall DCR.•In E/// and Huawei we should include counters for HardHandovers.•To clarify if cause 'release-due-to-UE-generated-signalling-connection-release” is available in NSN and cause Directed Signalling Connection Re-establishments is available in E/// and Huawei.•To clarify if cause Network Optimization is available in NSN.•And in case we use Packet Call counters, we need to identify the corresponding ones for state transitions to DCH (0/0)/FACH/PCH in E/// and Huawei.•To be investigated if RAB releases due to Inactivity also peg counters on Transitions to Cell_FACH for all verdors.


Next steps

HS NORMAL RELEASES

• We suggest to use PacketCall counters in NSN also for HS DCR.• To investigate the concept of HardHandovers in HSDPA.•To clarify if cause 'release-due-to-UE-generated-signalling-connection-release” is available in NSN•To investigate cause Network Optimization for HS and its availability in both NSN and Huawei.•And in case we use Packet Call counters, we need to identify the corresponding ones for state transitions to DCH (0/0)/FACH/PCH in E/// and Huawei.

ABNORMAL RELEASES in PS and HSTo be investigated preemption, and RT over NRT causes in NSN and their translation into E/// and Huawei.

FORMULAS PROPOSED IN THE COMING SLIDES ARE TO BE REVISED BASED ON THE PREVIOUS COMMENTS


NORMAL RELEASE TYPES CONSIDERED for PS RETAINABILITY • NSNTable ServiceLevel:Normal RAB Release, SRNS relocations, inter-RNC hard handovers, inter-system handovers, Directed Signalling Connection Re-establishmentsPacket Call:Due to inactivity, RAB release, Outgoing SRNC relocations, outgoing Inter-RNC hard handovers, Inter-System hard handovers, and state transitions to DCH (0/0)/FACH/PCH.

ERICSSONDue to a RANAP Iu Release Command or RAB Assignment Request message with "release cause" = 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated-signalling-connection-release‘

• HUAWEI"Successful Relocation", "User Inactivity", "Normal Release" or "Network Optimization",


ABNORMAL RELEASE TYPES CONSIDERED for PS RETAINABILITY • NSNServiceLevel:IU, RADIO, BTS, IUR, RNC, UE, UNSPE (see NSN documentation)Packet Call:Radio link failures, preemption, and RT over NRT. In case of RL failure, all radio links go out of sync state during a packet call, and as a consequence, the dedicated user plane allocation is released and the call is dropped into the Cell_FACH or Cell_PCH state. The counter for other failures is updated when a packet all is released due to some other failure cause than a radio link failure, pre-emption, or RT over NRT. The counter is updated, for example, if the reservation of the DMPG resource does not succeed when switching the HSPA to a DCH, or when a DSP runtime error occurs.

ERICSSONDue to a RANAP Iu Release Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated- signalling-connection-release'.

• HUAWEI"abnormally released RABs" (refer to all released RABs except "normally released RABs" and "released RABs triggered by the RNC due to RF reason”)


NORMAL RELEASE TYPES CONSIDERED for HS RETAINABILITY • NSNPacket Call:Due to inactivity, RAB release, Outgoing SRNC relocations, outgoing Inter-RNC hard handovers, Inter-System hard handovers, and state transitions to DCH (0/0)/FACH/PCH.Traffic:•HS-DSCH normal releases due to 1A event triggered state transitions to FACH,•or due to mobility-related HS-DSCH to DCH transitions: The reasons for release can be for example IFHO/ISHO measurements for AMR multi-service, low UL SIRerror value, removal of HS-DSCH radio link due to event 1B/1C, radio link failure, Rx-Tx time difference measurement, relocation of HS-DSCH radio link or event 6A..•or due to other than mobility-related HS-DSCH to DCH switch (e.g. multi-RAB restrictions) •or due to pre-emptions

• ERICSSONSame reasons as for stepping the existing counter pmNoNormalRabReleasePacket: Due to a RANAP Iu Release Command or RAB Assignment Request message with "release cause" = 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated-signalling-connection-release‘

• HUAWEI“Successful Relocation" or "Normal Release” (VS.HSDPA.RAB.Loss.Norm)"Radio Connection With UE Lost“, "Failure in the Radio Interface Procedure“ (VS.HSDPA.RAB.Loss.RF)


ABNORMAL RELEASE TYPES CONSIDERED for HS RETAINABILITY • NSNPacket Call:Radio link failures, preemption, and RT over NRT. In case of RL failure, all radio links go out of sync state during a packet call, and as a consequence, the dedicated user plane allocation is released and the call is dropped into the Cell_FACH or Cell_PCH state. The counter for other failures is updated when a packet all is released due to some other failure cause than a radio link failure, pre-emption, or RT over NRT. The counter is updated, for example, if the reservation of the DMPG resource does not succeed when switching the HSPA to a DCH, or when a DSP runtime error occurs.Traffic:The number of HS-DSCH allocation releases due to radio link failure, RLC protocol reset or uplink RLC unrecoverable error (Cell Update sent by UE) or due to other than radio link failure in the SRNC.

• ERICSSONSame reasons as for stepping the existing counter pmNoNormalRabReleasePacket: Due to a RANAP IuRelease Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated- signalling-connection-release'.

• HUAWEICauses other than the following: "Radio Connection With UE Lost" "Failure in the Radio Interface Procedure" "Successful Relocation" "User Inactivity" "Normal Release“ (VS.HSDPA.RAB.Loss.Abnorm.NonRF)


FORMULAS PROPOSED FOR NSNPS Retainability

sum(RAB_ACT_FAIL_PS_INTER_IU + RAB_ACT_FAIL_PS_INTER_RADIO + RAB_ACT_FAIL_PS_INTER_BTS + RAB_ACT_FAIL_PS_INTER_IUR + RAB_ACT_FAIL_PS_INTER_RNC + RAB_ACT_FAIL_PS_BACKG_IU + RAB_ACT_FAIL_PS_BACKG_RADIO + RAB_ACT_FAIL_PS_BACKG_BTS + RAB_ACT_FAIL_PS_BACKG_IUR + RAB_ACT_FAIL_PS_BACKG_RNC +RAB_ACT_FAIL_PS_BACKG_UE + RAB_ACT_FAIL_PS_INTER_UE+RAB_ACT_REL_PS_I_UNSPE_ER_CN + RAB_ACT_REL_PS_B_UNSPE_ER_CN (TREATED AS FAILURES)- RAB_ACT_FAIL_PS_BACKG_PCH - RAB_ACT_FAIL_PS_INT_PCH) / (UNDER INVESTIGATION if need to be removed)

sum(RAB_ACT_COMP_PS_INTER + RAB_ACT_COMP_PS_BACKG +RAB_ACT_REL_PS_INTER_SRNC + RAB_ACT_REL_PS_BACKG_SRNC +RAB_ACT_REL_PS_I_UNSPE_ER_CN + RAB_ACT_REL_PS_B_UNSPE_ER_CN +RAB_ACT_FAIL_PS_INTER_IU + RAB_ACT_FAIL_PS_INTER_RADIO + RAB_ACT_FAIL_PS_INTER_BTS + RAB_ACT_FAIL_PS_INTER_IUR + RAB_ACT_FAIL_PS_INTER_RNC + RAB_ACT_FAIL_PS_BACKG_IU + RAB_ACT_FAIL_PS_BACKG_RADIO + RAB_ACT_FAIL_PS_BACKG_BTS +RAB_ACT_FAIL_PS_BACKG_IUR + RAB_ACT_FAIL_PS_BACKG_RNC + RAB_ACT_FAIL_PS_BACKG_UE + RAB_ACT_FAIL_PS_INTER_UE)

Notes: Idea behind subtracting RAB_ACT_FAIL_PS_BACKG_PCH y RAB_ACT_FAIL_PS_INT_PCH is to NOT consider those drops not perceived by the user. Clarifications provided on PS drops due to RadioLink failure recued by Call Re-establishment. That is why it is common to distinguish between System and User perceived Drops in PS. In fact, the PS call (understood as PDP context active) stays alive acording to a timer and really only drops because of the UE requesting this (maybe due to Protocol Error,..).All counters in [ServiceLevel]


FORMULAS PROPOSED FOR NSNHS Retainability100 *Sum (REL_ALLO_OTH_FAIL_HSDSCH_INT + REL_ALLO_OTH_FAIL_HSDSCH_BGR +

REL_ALLO_RL_FAIL_HS_DSCH_INT + REL_ALLO_RL_FAIL_HS_DSCH_BGR ) /

Sum (REL_ALLO_NORM_HS_DSCH_INT + REL_ALLO_NORM_HS_DSCH_BGR +REL_ALLO_OTH_FAIL_HSDSCH_INT + REL_ALLO_OTH_FAIL_HSDSCH_BGR +REL_ALLO_RL_FAIL_HS_DSCH_INT + REL_ALLO_RL_FAIL_HS_DSCH_BGR )

Counters in [Traffic]


FORMULAS PROPOSED FOR NSN

HS Retainability (NEW PROPOSAL FOR DISCUSSION)

100 *[sum(PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR) +PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR +PS_REL_PRE_EMP_HS_D_INT + PS_REL_PRE_EMP_HS_D_BGR] /

[sum(PS_REL_NORM_HS_D_INT + PS_REL_NORM_HS_D_BGR +PS_REL_PRE_EMP_HS_D_INT + PS_REL_PRE_EMP_HS_D_BGR +PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR +PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR)]

Counters in [PacketCall]


FORMULAS PROPOSED FOR ERICSSONPS Retainability

100 *

( Pmnosystemrabreleasepacket ) / ( Pmnonormalrabreleasepacket + Pmnosystemrabreleasepacket )

All counters in [UtranCell]

HS Retainability

100 * pmNoSystemRbReleaseHs / (pmNoNormalRbReleaseHs+pmNoSystemRbReleaseHs)

All counters in [UtranCell]


FORMULAS PROPOSED FOR HUAWEIPS Retainability

100 * ( VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm) /

( VS.RAB.Loss.PS.Norm + VS.RAB.Loss.PS.RF + VS.RAB.Loss.PS.Abnorm )

All counters in [Cell Performance Measurement (CELL)]

HS Retainability100 * (VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF) /

(VS.HSDPA.RAB.Loss.Abnorm.NonRF + VS.HSDPA.RAB.Loss.RF+VS.HSDPA.RAB.Loss.Norm + VS.HSDPA.RAB.Loss.InActivity + VS.HSDPA.ChR.HSDSCHtoDCH + VS.HSDPA.ChR.HSDSCHtoFACH + VS.HSDPA.HHO.H2D.SuccOutIntraRNCIntraFreq + VS.HSDPA.HHO.H2D.SuccOutIntraRNCInterFreq)

All counters in [Cell Performance Measurement (CELL)]

Q U A L C O M M C O N F I D E N T I A L

SUPPORT MATERIAL

15


PS Data – Call Setup


Admission control in RAB establishment(taken from NSN doc.)


RRC & RAB PHASES in NSN


NSN counters in Table Service Level

19

RAB_ACT_COMP_PS_INTER The number of normal completions of RAB active phases for PS data interactive. [Updated: When the RNC sends an RANAP: RAB ASSIGNMENT RESPONSE or RANAP: IU RELEASE COMPLETE to the CN after normal RAB release for PS data interactive.]RAB_ACT_REL_PS_INTER_SRNC The number of RAB releases due to SRNC relocation for PS data interactive calls. ---This counter includes SRNS relocations, inter-RNC hard handovers, inter-system handovers andDirected Signalling Connection Re-establishments. [Updated: When the RNC receives an RANAP: IU RELEASE COMMAND message from the CN in the end of SRNC relocation or Directed SignallingConnection Re-establishment procedure, and the RAB type is PS data interactive.]RAB_ACT_FAIL_PS_INTER_IUThe number of RAB active failures caused by Iu-interface related problem for PS datainteractive. [Updated: When the RAB is released due to some abnormal reason related to Iu-interface.]RAB_ACT_FAIL_PS_INTER_RADIOThe number of RAB active failures caused by radio interface synchronisation for PS data interactive. RAB_ACT_FAIL_PS_INTER_BTSThe number of RAB active failures caused by BTS (for example, radio link setup orreconfiguration problem) for PS data interactive.RAB_ACT_FAIL_PS_INT_PCHThe number of RAB active failures in cell-PCH state for PS data with interactive class service.Updated: When a call with the PS data interactive RAB in cell-PCH state is dropped.RAB_ACT_REL_PS_I_UNSPE_ER_CNThe number of RAB active releases for PS interactive class calls with "unspecified failure"cause received from CN. [Updated: When a RANAP: IU RELEASE COMMAND or RAB ASSIGNMENT REQUEST message for releasing a RAB with cause "unspecified failure" is received from CN.


3.1 Introduction to packet call measurements(NSN)

A packet call is a data transfer session that uses DCH, HS-DSCH, or EDCH channels, starting from a successful capacity allocation (AC, BTS, transmission, RNC-internal) and ending to a dedicated resource release (for example, transfer to FACH/PCH, DCH 0/0, RAB release, outgoingrelocation, HHO, ISHO).

Packet call sessions are active data transfer periods, and one RAB can contain multiple packet calls. The packet call counters cover all the dedicated or shared channels along with HSPA. Thismeasurement is needed to fulfil accessibility and retainability requirements.

…

Packet Call Accessibility = successful_allocations/attemptsPacket Call Retainability = normal_releases/all_releases

NSN counters in Table Packet Call


3.7 Packet call releases (NSN)

21

With these counters the RNC counts the packet call releases. The packet call release counters are needed to see the proportion of normal packet call releases in relation to abnormal releases. The releases are classified as follows:. Normal releases. Failure releases

The following normal release situations are counted:. HS-DSCH/E-DCH Packet Call release. HS-DSCH/DCH Packet Call release. DCH/DCH Packet Call release

The normal release counters are updated, for example, due to inactivity or an RAB release. The counters are also updated in case of outgoing SRNC relocations, outgoing Inter-RNC hard handovers, Inter-System hard handovers, and state transitions to DCH (0/0)/FACH/PCH.

Note that RT over NRT and RAB pre-emption actions are not counted as normal releases.

The failure release counters are updated in case of radio link failures, preemption, and RT over NRT. In case of RL failure, all radio links go out of sync state during a packet call, and as a consequence, the dedicated user plane allocation is released and the call is dropped into the Cell_FACH or Cell_PCH state. The counter for other failures is updated when a packet all is released due to some other failure cause than a radio link failure, pre-emption, or RT over NRT. The counter is updated, for example, if the reservation of the DMPG resource does not succeed when switching the HSPA to a DCH, or when a DSP runtime error occurs.


NSN counters in Table Traffic: HS-DSCH allocation releases

22

REL_ALLO_NORM_HS_DSCH_INTThe number of HS-DSCH MAC-d flow normal releases in the SRNC for interactive classconnections. Includes also HS-DSCH releases due to 1A event triggered state transitions to FACH.

REL_ALLO_HS_DSCH_MOB_DCH_INTThe number of HS-DSCH releases due to mobility-related HS-DSCH to DCH transitions inthe SRNC for interactive class connections. [Updated: When the HS-DSCH MAC-d flow and its return channel allocations are released due to mobility-related HS-DSCH to DCH transition. The reasons for release can be for example IFHO/ISHO measurements for AMR multi-service, low UL SIRerror value, removal of HS-DSCH radio link due to event 1B/1C, radio link failure, Rx-Tx time difference measurement, relocation of HS-DSCH radio link or event 6A.]

REL_ALLO_HS_DSCH_OTH_DCH_INTThe number of HS-DSCH allocation normal releases due to other than mobility-related HS-DSCH to DCH switch (e.g. multi-RAB restrictions) for interactive class connections.

REL_ALLO_HS_DSCH_PRE_EMP_INTThe number of HS-DSCH allocation normal releases due to pre-emptions for interactive class connections.REL_ALLO_RL_FAIL_HS_DSCH_INTThe number of HS-DSCH allocation releases due to radio link failure, RLC protocol resetor uplink RLC unrecoverable error for interactive class connections. [Updated: When the user's HS-DSCH allocation is released due to radio link failure, RLC protocol reset or uplink RLC unrecoverable error (Cell Update sent by UE).REL_ALLO_OTH_FAIL_HSDSCH_INTThe number of HS-DSCH allocation releases due to other than radio link failure in theSRNC for interactive class connections. [Updated: When the HS-DSCH MAC-d flow and its return channel allocations are released with a failure cause other than radio link failure.]


ERICSSON Counters: ALEX – MO: UtranCell

23

pmNoNormalRabReleasePacketNumber of successful normal RAB releases (PS Data) for the best cell in the active set. When releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell.This counter is only increased due to a RANAPIu Release Command or RAB Assignment Request message with "release cause" = 'Normal Release', 'Successful Relocation', 'Resource OptimisationRelocation', 'User Inactivity' or 'release-due-to-UE-generated-signalling-connection-release'. It is for the Best Cell in the Active Set and when releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell.pmNoSystemRabReleasePacketNumber of successful system RAB releases (PS Data) for the best cell in the active set. When releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell.This counter is only increased due to a RANAP Iu Release Command or RAB Assignment Request message with "release cause" = anything except 'Normal Release', 'Successful Relocation', 'Resource Optimisation Relocation', 'User Inactivity' or 'release-due-to-UE-generated- signalling-connection-release'. This counter is incremented for the best cell in the Active Set in the SRNC and when releasing a HS RAB, this counter is stepped for the Serving HS-DCH cell.

pmNoNormalRabReleasePacketUra Is this counter included in the previous one?Number of normal RAB Release of Packet RAB while on URA_PCH.This counter is increased each time there is a normal RAB release of a Packet RAB, while in URA_PCH. Note: This counter is only incremented in the SRNC.


ERICSSON Counters: ALEX – MO: UtranCell

24

pmNoNormalRbReleaseHsNumber of successful normal releases of packet RABs mapped on HS-DSCH in the Serving HS-DSCH cell.The counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoNormalRabReleasePacket.

pmNoSystemRbReleaseHsNumber of successful system releases of packet RABs mapped on HS-DSCH in the Serving HS-DSCH cell.The counter is stepped for the Serving HS-DSCH cell at RAB/RB combination transition from PS Interactive 64/HS (or 384/HS or EUL/HS) - HS-DSCH to SRB-DCH or to Idle mode due to the same reasons as for stepping the existing counter pmNoSystemRabReleasePacket.


ERICSSON Counters: ALEX – MO: IurLink

25

Be aware there are counters with the same name but different meaning in a different MO:

pmNoNormalRabReleasePacketNumber of normal packet RAB releases over Iur (that is, normal releases of a drifting packet call), referred to the IurLink representing the DRNC for the best cell in the active set.Incremented whenever the best cell in the active set of a Packet RAB is released over Iur (DRNC case) due to RAB Assignment Request or Iu Release Command with cause Normal, Successful Relocation, User Inactivity, or Resource Optimisation Relocation.

pmNoSystemRabReleasePacketNumber of system packet RAB releases over Iur (that is, system releases of a drifting packet call), referred to the IurLink representing the DRNC for the best cell in the active set.Incremented whenever the best cell in the active set of a Packet RAB is released over Iur (DRNC case) due to RAB Assignment Request or Iu Release Command with cause other than Normal, Successful Relocation, User Inactivity, or Resource Optimisation Relocation.


HUAWEI Counters

26


HUAWEI Counters

27


HUAWEI Counters

28

Retainability Formulas v2

Documents

Transcript of Retainability Formulas v2