You are on page 1of 52
UTRAN Key Performance Indicators 20040515
UTRAN Key Performance Indicators 20040515
UTRAN Key Performance Indicators
20040515
UTRAN Key Performance Indicators 20040515
Introduction  These slides focus only on initial UTRAN KPIs.  There is a comprehensive list

Introduction

  • These slides focus only on initial UTRAN KPIs.

  • There is a comprehensive list of raw counters from which these initial KPIs are produced.

Introduction  These slides focus only on initial UTRAN KPIs.  There is a comprehensive list
 

redefined and updated.

  • The counters as well as KPIs will continuously be

UTRAN KPI Overview  Call Setup Success Rate  Call Drop Rate of Signaling Plane 

UTRAN KPI Overview

  • Call Setup Success Rate

  • Call Drop Rate of Signaling Plane

  • Call Drop Rate of User Plane

  • Signaling Congestion Rate

  • Traffic Congestion Rate

  • Soft Handover Success Rate

  • Hard Handover Success Rate

  • Inter-RAT Hard Handover Success Rate

Contents Call Setup Call Drop Congestion Handover Traffic

Contents

  • Call Setup

  • Call Drop

  • Congestion

  • Handover

  • Traffic

Contents Call Setup Call Drop Congestion Handover Traffic
Call Setup Success Rate  Formula of Call Setup Success Rate: Call Setup Success Rate =

Call Setup Success Rate

  • Formula of Call Setup Success Rate:

Call Setup Success Rate = RRCSetupSuccRate × RABSetupSuccRate ×100%

  • Can be divided into two parts: CS&PS

  • For four types of QoS:

    • Conversational (e.g. voice and video)

    • Streaming (e.g. streaming video or audio)

    • Interactive (e.g. browsing)

    • Background (e.g. emails or file download)

RRC Setup Success Rate  The formula of RRC Setup Success Rate: RRC Setup Success Rate

RRC Setup Success Rate

  • The formula of RRC Setup Success Rate:

RRC Setup Success Rate = RRC Connection Setup Success / RRC Connection Request × 100%

  • RRC Setup Reject Causes:

    • Congestion (Walsh, Power, CE, etc.)

    • Unspecified (mostly transmission or NodeB problem)

  • Other RRC Setup failure reason

    • UE can’t receive RRC CONNECTION SETUP

    • NodeB can’t receive RRC CONNECTION SETUP COMPLETE

  • RRC Connection Setup UE NODEB SRNC RRC RRC Connection Request RRC NBAP Radio Link Setup Requset

    RRC Connection Setup

    UE NODEB SRNC RRC RRC Connection Request RRC NBAP Radio Link Setup Requset NBAP NBAP Radio
    UE
    NODEB
    SRNC
    RRC
    RRC Connection Request
    RRC
    NBAP
    Radio Link Setup Requset
    NBAP
    NBAP
    Radio Link Setup Response
    NBAP
    RRC
    RRC Connection Setup
    RRC
    RRC
    RRC Connection Setup Complete
    RRC
    Example
    Example
    Example
    Example

    RRC_REQ

    3332

    RRC_REJ

    2

    RRC_REJ_CONG

    0

    RRC_SETUP

    3330

    RRC_SETUP_SUCC

    3184

    RRC_SETUP_SUCC_RATE

    95.56%

    UE can’t receive RRC CONNECTION SETUP The downlink channel transmit power is not enough or the UE receive sensitivity is not good. NodeB can’t receive RRC CONNECTION SETUP COMPLETE

    The UE transmit power is not enough or the NodeB receive sensitivity is not

    good.

    RAB Setup Success Rate  The formula of RAB Setup Success Rate: RAB Setup Success Rate

    RAB Setup Success Rate

    • The formula of RAB Setup Success Rate:

    RAB Setup Success Rate = RAB Assignment Success / RAB Assignment Request × 100%

    • Can be divided into two parts, for four types of QoS

    • RAB Setup Failure Causes:

      • Parameter violation

      • Non supported UTRAN capabilities

      • Relocation triggered

      • Transport connection failed to establish

      • Unavailable resources

      • Protocol error

    RAB Setup Flow Chart UE NodeB SRNC CN RANAP RAB Assignment Request RANAP NBAP RL Reconfig

    RAB Setup Flow Chart

    UE NodeB SRNC CN RANAP RAB Assignment Request RANAP NBAP RL Reconfig Prepare NBAP NBAP RL
    UE
    NodeB
    SRNC
    CN
    RANAP
    RAB Assignment Request
    RANAP
    NBAP
    RL Reconfig Prepare
    NBAP
    NBAP
    RL Reconfig Ready
    NBAP
    NBAP
    RL Reconfig Commit
    NBAP
    RRC
    RB Setup
    RRC
    RRC
    RB Setup Complete
    RRC
    RANAP
    RAB Assignment Response
    RANAP
    Example
    Example
    Example
    Example

    RB_SETUP

    1057

    RB_SETUP_SUCC

    1054

    CS_RAB_REQ_SETUP_CONV

    982

    CS_RAB_SETUP_SUCC_CONV

    979

    PS_RAB_REQ_SETUP_BKG

    75

    PS_RAB_SETUP_SUCC_BKG

    75

    CS_RAB_SETUP_SUCC_RATE_CONV

    99.69%

    PS_RAB_REL_SUCC_RATE_BKG

    100.00%

    RB_SETUP_SUCC_RATE_CONV

    99.72%

    Contents Call Setup Call Drop Congestion Handover Traffic

    Contents

    • Call Setup

    • Call Drop

    • Congestion

    • Handover

    • Traffic

    Contents Call Setup Call Drop Congestion Handover Traffic
    Call Drop Rate of Signaling Plane  Call Drop Rate of Signaling Plane is calculated by

    Call Drop Rate of Signaling Plane

    • Call Drop Rate of Signaling Plane is calculated by counting RNC-originated Iu connection release.

    • Can be divided into two parts: CS&PS

    • RNC-originated Iu connection release Causes:

      • OM intervention

      • User inactivity

      • Repeated integrity checking failure

      • UE generated signaling connection release

      • RL out-of-synchronization

    Call Drop Rate of Signaling Plane  The formula of Call Drop Rate of CS Signaling

    Call Drop Rate of Signaling Plane

    • The formula of Call Drop Rate of CS Signaling Plane:

    Call Drop Rate of CS Signaling Plane = RNC-originated CS Domain Iu Connection Release / RNC-originated CS Domain Iu Connection Setup Success× 100%

    • The formula of Call Drop Rate of PS Signaling Plane:

    Call Drop Rate of PS Signaling Plane = RNC-originated PS Domain

    Iu Connection Release / RNC-originated PS Domain Iu Connection Setup Success× 100%

    RNC-originated Iu connection release Flow Chart S RN C RAN AP RAN AP RAN AP CN

    RNC-originated Iu connection release Flow Chart

    S RN C

    S RN C
    S RN C
    S RN C RAN AP RAN AP RAN AP
    S RN C RAN AP RAN AP RAN AP
    RAN AP
    RAN AP
    RAN AP
    RAN AP
    RAN AP
    RAN AP
    CN
    CN
    RAN AP RAN AP RAN AP
    RAN AP
    RAN AP
    RAN AP

    Iu Re le a s e Re que s t

    Iu Re le a s e Co m m and

    Iu Re le a s e Co m ple t e

    Example RNC_CS_IU_REL 50 RNC_PS_IU_REL 51 RNC_CS_IU_REL_DUP_INTEG 0 RNC_PS_IU_REL_DUP_INTEG 0 RNC_CS_IU_REL_OM 0 RNC_PS_IU_REL_OM 0 RNC_CS_IU_REL_RL_FAIL 26 RNC_PS_IU_REL_RL_FAIL

    Example

    RNC_CS_IU_REL

    50

    RNC_PS_IU_REL

    51

    RNC_CS_IU_REL_DUP_INTEG

    0

    RNC_PS_IU_REL_DUP_INTEG

    0

    RNC_CS_IU_REL_OM

    0

    RNC_PS_IU_REL_OM

    0

    RNC_CS_IU_REL_RL_FAIL

    26

    RNC_PS_IU_REL_RL_FAIL

    18

    RNC_CS_IU_REL_SIG_REL

    5

    RNC_PS_IU_REL_SIG_REL

    22

    RNC_CS_IU_REL_UE_INACT

    0

    RNC_PS_IU_REL_UE_INACT

    0

    RNC_CS_IU_SETUP

    3085

    RNC_PS_IU_SETUP

    251

    Call Drop Rate of CS Signaling

    1.62%

    Call Drop Rate of PS Signaling

    20.32%

    For Call Drop Rate of PS Signaling, the main reason is wrong APN configuration in UE For RL_FAIL, need optimize poor coverage and neighbors, 3G-2G handover also can improve this indicator

    Call Drop Rate of User Plane  Call Drop Rate of User Plane is calculated by

    Call Drop Rate of User Plane

    • Call Drop Rate of User Plane is calculated by counting RNC-originated RAB releases.

    • Can be divided into two parts, for four types of QoS

    • RNC-originated RAB release Causes:

      • OM intervention

      • UTRAN generated reason

      • RAB preempted

    Call Drop Rate of User Plane  The formula of Call Drop Rate of CS User

    Call Drop Rate of User Plane

    • The formula of Call Drop Rate of CS User Plane:

    Call Drop Rate of CS User Plane = RNC-originated CS Domain RAB Release / RNC-originated CS Domain RAB Setup Success × 100%

    • The formula of Call Drop Rate of PS User Plane:

    Call Drop Rate of PS User Plane = RNC-originated PS Domain RAB Release / RNC-originated PS Domain RAB Setup Success × 100%

    RNC-originated RAB release Cause UE RRC RRC SRNC RANAP RANAP RANAP RRC RRC CN RANAP RANAP

    RNC-originated RAB release Cause

    UE

    RRC RRC
    RRC
    RRC
    SRNC RANAP RANAP RANAP RRC RRC
    SRNC
    RANAP
    RANAP
    RANAP
    RRC
    RRC

    CN

    RANAP RANAP RANAP
    RANAP
    RANAP
    RANAP

    RAB Release Request

    Iu Release Command

    Iu Release Complete

    RRC Connection Release

    RRC Connection Release Complete

    Example CS_RAB_SETUP_SUCC_CONV 979 PS_RAB_SETUP_SUCC_BKG 75 RNC_CS_RAB_REL_REQ_CONV 4 RNC_PS_RAB_REL_REQ_BKG 4 Call Drop Rate of CS User Plane

    Example

    CS_RAB_SETUP_SUCC_CONV

    979

    PS_RAB_SETUP_SUCC_BKG

    75

    RNC_CS_RAB_REL_REQ_CONV

    4

    RNC_PS_RAB_REL_REQ_BKG

    4

    Call Drop Rate of CS User Plane

    0.41%

    Call Drop Rate of PS User Plane

    5.33%

    For CS/PS_RAB_REL, need optimize poor coverage and neighbors, 3G-2G handover also can improve this indicator

    Contents Call Setup Call Drop Congestion Handover Traffic

    Contents

    • Call Setup

    • Call Drop

    • Congestion

    • Handover

    • Traffic

    Contents Call Setup Call Drop Congestion Handover Traffic
    Signaling Congestion Rate  The formula of Signaling Congestion Rate: Signaling Congestion Rate = RRC Connection

    Signaling Congestion Rate

    • The formula of Signaling Congestion Rate:

    Signaling Congestion Rate = RRC Connection Reject (Cause:

    congestion) / RRC Connection Request × 100%

    U E

    U E
    U E
    U E C C R R R R
    C C
    C
    C
    R R
    R R
    R R
    R R

    N o d e B

    N o d e B
    N o d e B
    N o d e B
    N o d e B

    R N C

    R N C
    R N C
    R N C C C R R R R
    C C
    C
    C
    R R
    R R
    R R
    R R

    R R C C o n n

    e c tio n R e q u e s t

    R R C C o n n e c tio n R e j

    e c t (C a u s e : C o n g e s tio n )

    Traffic Congestion Rate  Traffic Congestion Rate is calculated by counting the RAB Assignment Setup Failure

    Traffic Congestion Rate

    • Traffic Congestion Rate is calculated by counting the RAB Assignment Setup Failure (cause: congestion).

    • Can be divided into two parts: CS&PS

    Traffic Congestion Rate  The formula of CS Traffic Congestion Rate: CS Traffic Congestion Rate =

    Traffic Congestion Rate

    • The formula of CS Traffic Congestion Rate:

    CS Traffic Congestion Rate = CS Domain RAB Assignment Setup

    Failure (Congestion) / CS Domain RAB Assignment Setup Request × 100%

    • The formula of PS Traffic Congestion Rate:

    PS Traffic Congestion Rate = PS Domain RAB Assignment Setup Failure (Congestion) / PS Domain RAB Assignment Setup Request × 100%

    Traffic Congestion Rate S R N C C N R A N A P R A

    Traffic Congestion Rate

    S R N C C N R A N A P R A B A s
    S R N C
    C N
    R
    A N A P
    R A B A s s ig n m e n t R e q u e s t
    R
    A N A P
    R
    A N A P
    R A B A s s ig n m e n t R e s p o n s e ( F a i lu re c a u s e : C o n g e s tio n )
    R
    A N A P
    Contents Call Setup Call Drop Congestion Handover Traffic

    Contents

    • Call Setup

    • Call Drop

    • Congestion

    • Handover

    • Traffic

    Contents Call Setup Call Drop Congestion Handover Traffic
    Soft (Softer) Handover Success Rate  The formula of Soft (Softer) Handover Success Rate: Soft (Softer)

    Soft (Softer) Handover Success Rate

    • The formula of Soft (Softer) Handover Success Rate:

    Soft (Softer) Handover Success Rate = Soft (Softer) Handover Success / Soft (Softer) Handover Request× 100%

    • Soft (Softer) Handover Flow Chart

    UE RRC RRC
    UE
    RRC
    RRC

    N ew N odeB

    N BAP N BAP DCCH :
    N
    BAP
    N
    BAP
    DCCH :

    SRN C

    N BAP N BAP RRC RRC
    N
    BAP
    N
    BAP
    RRC
    RRC

    Radio Link Addition Reque s t

    Radio Link Addition Re sponse

    DCCH : Ac tive Se t Update

    Ac tive Se t Update Comple te

    SHO Failure Causes  When the UE handles the ACTIVE SET UPDATE message, the abnormal cases

    SHO Failure Causes

    • When the UE handles the ACTIVE SET UPDATE message, the abnormal cases may be occurred and the UE shall transmit an ACTIVE SET UPDATE FAILURE message with the following failure causes

      • Configuration unsupported

      • Incompatible simultaneous reconfiguration

      • Protocol error

      • Invalid configuration

  • If the time expired before RNC receives the message ACTIVE SET UPDATE COMPLETE or ACTIVE SET UPDATE FAILURE from UE, RNC increases the SHO failure counter with the following cause

    • No response from UE

  • SHO Failure Flow Chart UE RRC RRC N ew N odeB N BAP N BAP DCCH

    SHO Failure Flow Chart

    UE

    UE
    UE
    RRC
    RRC
    RRC
    RRC
    N ew N odeB
    N ew N odeB
    N BAP N BAP DCCH
    N BAP
    N BAP
    DCCH
    SRN C
    SRN C
    N BAP N BAP RRC RRC
    N BAP
    N BAP
    RRC
    RRC

    Radio Link Addition Reque s t

    Radio Link Addition Re sponse

    DCCH : Ac tive Se t Update

    : Ac tive Se t Update F ailure

    Example SHO_EVAL_REQ 5652 SHO 5511 SHO_SUCC 5500 SOFTERHO 1411 SOFTERHO_SUCC 1411 SHO_SUCC_RATE 99.8%

    Example

    SHO_EVAL_REQ

    5652

    SHO

    5511

    SHO_SUCC

    5500

    SOFTERHO

    1411

    SOFTERHO_SUCC

    1411

    SHO_SUCC_RATE

    99.8%

    Hard Handover Success Rate  The formula of Hard Handover Success Rate: Hard Handover Success Rate

    Hard Handover Success Rate

    • The formula of Hard Handover Success Rate:

    Hard Handover Success Rate = Hard Handover Success / Hard Handover request× 100%

    Hard Handover Flow Chart UE Source NodeB Target NodeB SRNC NBAP Radio Link Setup Request NBAP

    Hard Handover Flow Chart

    UE Source NodeB Target NodeB SRNC NBAP Radio Link Setup Request NBAP NBAP Radio Link Setup
    UE
    Source NodeB
    Target NodeB
    SRNC
    NBAP
    Radio Link Setup Request
    NBAP
    NBAP
    Radio Link Setup Reponse
    NBAP
    RRC
    DCCH : Physical Channel Reconfiguration
    RRC
    NBAP
    Radio Link Failure Indication
    NBAP
    RRC
    D CCH : Physical Channel Reconfiguration Complete
    RRC
    NBAP
    Radio Li nk Deletion Request
    NBAP
    NBAP
    Radio Li nk Delete Response
    NBAP
    Hard Handover Failure Cause  The detail hard handover failure cause statistics include two hard handover

    Hard Handover Failure Cause

    • The detail hard handover failure cause statistics include two hard handover directions on the cell object :

      • outgoing hard handover initiated by RNC in each original cell.

      • incoming hard handover in the target cell initiated by RNC

  • When the UE handles the PHYSICAL CHANNEL RECONFIGURATION message, the abnormal cases may be occurred and the UE shall transmit an PHYSICAL CHANNEL RECONFIGURATION FAILURE message with the following failure cause:

    • Configuration unsupported

    • Physical channel failure

    • Incompatible simultaneous reconfiguration

    • Protocol error

    • Cell update occurred

    • Invalid configuration

  • If the time expired before RNC receives the message PHYSICAL CHANNEL RECONFIGURATION COMPLETE or PHYSICAL CHANNEL RECONFIGURATION FAILURE from UE, RNC increases the hard handover failure counter with the following cause

    • No response received from UE

  • Hard Handover Failure Flow Chart Source NodeB (Outgoing the Cell) NBAP NBAP NBAP Target NodeB (Incoming

    Hard Handover Failure Flow Chart

    Source NodeB

    (Outgoing the Cell)

    NBAP NBAP NBAP
    NBAP
    NBAP
    NBAP

    Target NodeB

    (Incoming the Cell)

    NBAP NBAP
    NBAP
    NBAP
    SRNC
    SRNC
    NBAP NBAP RRC NBAP RRC NBAP NBAP
    NBAP
    NBAP
    RRC
    NBAP
    RRC
    NBAP
    NBAP

    Radio Link Setup Request

    Radio Link Setup Reponse

    DCCH : Physical Channel Reconfiguration

    Radio Link Failure Indication

    DCCH : Physical Channel Reconfiguration Failure

    Radio Link Deletion Request

    Radio Link Delete Response

    InterRAT Handover to GSM Success Rate  The formula of InterRAT Handover to GSM Success Rate:

    InterRAT Handover to GSM Success Rate

    • The formula of InterRAT Handover to GSM Success Rate:

    InterRAT Handover to GSM Success Rate = inter-RAT handover from UTRAN to GSM success / inter-RAT handover from UTRAN to GSM attempts × 100%

    InterRAT Handover to GSM Flow Chart UE NodeB RNC 3G MSC 2G MSC BSS RANAP Relocation

    InterRAT Handover to GSM Flow Chart

    UE NodeB RNC 3G MSC 2G MSC BSS RANAP Relocation Required RANAP Prepare Handover Handover Request
    UE
    NodeB
    RNC
    3G MSC
    2G MSC
    BSS
    RANAP
    Relocation Required
    RANAP
    Prepare Handover
    Handover Request
    Handover Request Ack
    Prepare Handover Response
    RANAP
    Relocation Command
    RANAP
    RRC
    Handover From Utran Command
    RRC
    Handover Complete
    RANAP
    Iu Release Command
    RANAP
    RANAP
    Iu Release Complete
    RANAP
    NBAP
    Radio Link Deletion Request
    NB AP
    NBAP
    Radio Link Deletion Response
    NB AP
    InterRAT Handover to GSM Failure Cause  When the UE handles the the HANDOVER FROM UTRAN

    InterRAT Handover to GSM Failure Cause

    • When the UE handles the the HANDOVER FROM UTRAN COMMAND message, the abnormal cases may be occurred and the UE shall transmit an HANDOVER FROM UTRAN FAILURE message with the following failure causes

      • Configuration unacceptable

      • Physical channel failure

      • Protocol error

      • Inter-RAT protocol error

      • Unspecified

  • If the time expired before RNC receives the message IU RELEASE COMMAND from MSC, RNC increases the InterRAT handover to GSM failure counter with the following cause

    • InterRAT handover to GSM no response

  • InterRAT Handover to GSM Failure Flow Chart UE NodeB RNC 3G MSC 2G MSC BSS RANAP

    InterRAT Handover to GSM Failure Flow Chart

    UE NodeB RNC 3G MSC 2G MSC BSS RANAP Relocation Required RANAP Prepare Handover Handover Request
    UE
    NodeB
    RNC
    3G MSC
    2G MSC
    BSS
    RANAP
    Relocation Required
    RANAP
    Prepare Handover
    Handover Request
    Handover Request Ack
    Prepare Handover Response
    RANAP
    Relocation Command
    RANAP
    RRC
    Handover From Utran Command
    RRC
    RRC
    Handover From Utran Failure
    RRC
    Example CS_INTRAT_HO_OUT_PREP 60 CS_INTRAT_HO_OUT_PREP_SUCC 54 CS_INTRAT_HO_OUT_ATT 54 CS_INTRAT_HO_OUT_SUCC 48 CS_INTRAT_HO_OUT_SUCC_RATE(%) 88.89% CS_INTRAT_HO_OUT_FAIL_CFG_UNSUPP 0 CS_INTRAT_HO_OUT_FAIL_INTER_RAT_PROTCL 0 CS_INTRAT_HO_OUT_FAIL_NO_RSP

    Example

    CS_INTRAT_HO_OUT_PREP

    60

    CS_INTRAT_HO_OUT_PREP_SUCC

    54

    CS_INTRAT_HO_OUT_ATT

    54

    CS_INTRAT_HO_OUT_SUCC

    48

    CS_INTRAT_HO_OUT_SUCC_RATE(%)

    88.89%

    CS_INTRAT_HO_OUT_FAIL_CFG_UNSUPP

    0

    CS_INTRAT_HO_OUT_FAIL_INTER_RAT_PROTCL

    0

    CS_INTRAT_HO_OUT_FAIL_NO_RSP

    0

    CS_INTRAT_HO_OUT_FAIL_PHYCH_FAIL

    6

    CS_INTRAT_HO_OUT_FAIL_PROTCL

    0

    CS_INTRAT_HO_OUT_FAIL_RELOC_ABORT

    0

    CS_INTRAT_HO_OUT_FAIL_UNSPEC

    0

    Need optimize 3G-2G neighbors and configuration (RNC&CN), 3G-2G handover parameters for example: Report interval/Inter-RAT handover trigger time/GSM RSSI

    threshold/ Hysteresis

    InterRAT Handover to GPRS Success Rate  The formula of InterRAT Handover to GPRS Success Rate:

    InterRAT Handover to GPRS Success Rate

    • The formula of InterRAT Handover to GPRS Success Rate:

    InterRAT Handover to GPRS Success Rate = interRAT handover from UTRAN to GPRS success initiated by UTRAN / interRAT handover from UTRAN to GPRS attempts initiated by UTRAN × 100%

    InterRAT Handover to GPRS Flow Chart - initiated by UTRAN
    InterRAT Handover to GPRS Flow Chart - initiated by UTRAN
    InterRAT Handover to GPRS Flow Chart - initiated by UTRAN
    UE NodeB RNC 3G SGSN 2G SGSN BSS RRC Cell Change Order From Utran RRC Route
    UE
    NodeB
    RNC
    3G SGSN
    2G SGSN
    BSS
    RRC
    Cell Change Order From Utran
    RRC
    Route Area Update Request
    SGSN Context Request
    RANAP
    SRNS Context Request
    RANAP
    RANAP
    SRNS Context Response
    RANAP
    SGSN Context Response
    SGSN Context Ack
    RANAP
    SRNS Data Forward Command
    RANAP
    RANAP
    Forward Packet
    RANAP
    Forward Packet
    Update PDP Context Request
    Update PDP Context Request
    RANAP
    Iu Release Command
    RANAP
    RANAP
    Iu Release Complete
    RANAP
    NBAP
    Radio Link Deletion Request
    NBAP
    NBAP
    Radio Link Deletion Response
    NBAP
    Route Area Update Accept
    InterRAT Handover to GPRS Failure Cause
    InterRAT Handover to GPRS Failure Cause
    InterRAT Handover to GPRS Failure Cause
    InterRAT Handover to GPRS Failure Cause
    • When the UE handles the the CELL CHANGE ORDER FROM UTRAN message, the abnormal cases may be occurred and the UE shall transmit an CELL CHANGE ORDER FROM UTRAN FAILURE message with the following failure causes

      • Configuration unacceptable

      • Physical channel failure

      • Protocol error

      • Unspecified

  • If the time expired before RNC receives the message SRNS CONTEXT REQUEST or IU RELEASE COMMAND from SGSN, RNC increases the InterRAT handover to GPRS failure counter with the following cause

    • InterRAT handover to GPRS no response

  • InterRAT Handover to GPRS Failure Flow Chart UE RRC RRC NodeB RNC RRC RRC Cell Change

    InterRAT Handover to GPRS Failure Flow Chart

    UE RRC RRC
    UE
    RRC
    RRC
    NodeB
    NodeB
    InterRAT Handover to GPRS Failure Flow Chart UE RRC RRC NodeB RNC RRC RRC Cell Change
    RNC
    RNC
    RRC RRC
    RRC
    RRC

    Cell Change Order From Utran

    Cell Change Order From Utran Failure

    3G SGSN

       

    2G SGSN

       

    BSS

       
    Contents Call Setup Call Drop Congestion Handover Traffic

    Contents

    • Call Setup

    • Call Drop

    • Congestion

    • Handover

    • Traffic

    Contents Call Setup Call Drop Congestion Handover Traffic
    CS Traffic  One Erlang is defined as the one 12.2K CS AMR call lasting for

    CS Traffic

    • One Erlang is defined as the one 12.2K CS AMR call lasting for one hour. The traffic of other different services are derived by converting to equivalent 12.2K CS AMR call.

    • CS Traffic for two types of QoS:

      • CS Conversational Traffic (i.e. voice and video)

      • CS Streaming Traffic (e.g. streaming video or audio)

  • CS Traffic for two types of Service:

    • CS AMR Traffic (Voice)

    • CS CONV 64k Traffic (Video Phone)

  • PS Traffic  The traffic of different services are derived by converting to equivalent 12.2K CS

    PS Traffic

    • The traffic of different services are derived by converting to equivalent 12.2K CS AMR call.

    • PS Traffic for four types of QoS:

      • PS Conversational Traffic

      • PS Streaming Traffic

      • PS Interactive

      • Background Traffic

    PS Throughput PS Throughput for four types of QoS (in Bytes)  PS UL Conversational services

    PS Throughput

    PS Throughput for four types of QoS (in Bytes)

    • PS UL Conversational services Throughput

    • PS UL Streaming services Throughput

    • PS UL Interactive services Throughput

    • PS UL Background services Throughput

    • PS DL Conversational services Throughput

    • PS DL Streaming services Throughput

    • PS DL Interactive services Throughput

    • PS DL Background services Throughput

    Summary (1/3) KPI Stage Failure Cause Level - Congestion RRC Setup Success Rate - Unspecified CN

    Summary (1/3)

    KPI

    Stage

    Failure Cause

     

    Level

       
    • - Congestion

     

    RRC Setup Success Rate

    • - Unspecified

       

    CN domain:

    Call Setup

    • - Parameter violation

    -

    CS

    Success Rate

    • - Non supported UTRAN capabilities

    -

    PS

    RAB Setup Success Rate

    • - Relocation triggered

    QoS Classes:

    • - Transport connection failed to establish

    -

    Conversational

     
    • - Unavailable resources

    -

    Streaming

    • - Protocol error

    -

    Interactive

    -

    Background

       
    • - OM intervention

     
    • - User inactivity

    -

    -CS

    PS

    Signaling Plane

    • - Repeated integrity checking failure

    • - UE generated signaling connection release

     
    • - RL out-of-synchronization

     

    Call Drop Rate

       

    CN domain:

    -

    CS

     

    -

    PS

    User Plane

    • - OM intervention

    • - UTRAN generated reason

    • - RAB preempted

    QoS Classes:

    -

    Conversational

    -

    Streaming

     

    -

    Interactive

    -

    Background

    Congestion

    Signaling Congestion Rate

    RRC Connection Reject (Cause: congestion)

     

    Rate

         

    -

    CS

    Traffic Congestion Rate

    RAB Assignment Setup Failure (cause: congestion).

    -

    PS

    Summary (2/3) KPI Stage Failure Cause Level Radio Link Addition - Configuration unsupported Soft & Softer

    Summary (2/3)

    KPI

    Stage

    Failure Cause

    Level

     

    Radio Link Addition

    • - Configuration unsupported

     

    Soft & Softer

     
    • - Incompatible simultaneous reconfiguration

    Handover

    • - Protocol error

    Success Rate

    Radio Link Deletion

    • - Invalid configuration

    • - No response from UE

       
    • - Configuration unsupported

     
    • - Physical channel failure

    • - Incompatible simultaneous reconfiguration

    Hard Handover

    Success Rate

    • - Protocol error

    • - Cell update occurred

    • - Invalid configuration

    • - No response received from UE

       
    • - Configuration unacceptable

     

    InterRAT

    • - Physical channel failure

    Handover to

    • - Protocol error

    GSM Success

    • - Inter-RAT protocol error

    Rate

    • - Unspecified

    • - InterRAT handover to GSM no response

       
    • - Configuration unacceptable

     

    InterRAT

    Handover to

    GPRS Success

    Rate

    • - Physical channel failure

    • - Protocol error

    • - Unspecified

    • - InterRAT handover to GSM no response

    - initiated by UTRAN

    Summary (3/3) KPI Stage Failure Cause Level QoS Classes: - Conversational CS Traffic Erlang - Streaming

    Summary (3/3)

    KPI

    Stage

    Failure Cause

     

    Level

         

    QoS Classes:

    -

    Conversational

    CS Traffic

    Erlang

    -

    Streaming

    Bears

       

    -

    AMR Voice

    -

    CS 64K

         

    QoS Classes:

    -

    Conversational

    PS Traffic

    Erlang

    -

    Streaming

    -

    Interactive

    -

    Background

         

    QoS Classes:

    -

    Conversational

    PS Throughput

    Byte

    -

    Streaming

    -

    Interactive

    -

    Background