UMTS RAN Performance Trouble Shooting Guidelines Nokia Accessibility

UMTS RAN Performance Trouble Shooting Guidelines Nokia AccessibilityNational & Region Performance EngineeringDocument InitiatedNovember 05, 2008

Revision Number2.2

Revision Date August 26, 2009

Document Information

The information in these materials is confidential and proprietary to T-Mobile USA, Inc. These materials are authorized for the use of T-Mobile USA service providers and their employees and agents, solely for the purposes of the agreement under which these materials are provided. The rights granted hereunder constitute a limited, nonexclusive, revocable license and not a transfer of title. Authorized T-Mobile USA service providers and their employees and agents may view, copy or print pages of these materials solely for the purposes set forth herein, but may not otherwise use, modify, copy, print, display, reproduce, distribute, transmit, publish, license, sublicense or create derivative works from these materials in whole or in part, or remove any copyright or other proprietary notices set forth herein, without the express written permission of T-Mobile USA. The information in these materials is subject to change without notice. T-Mobile USA's liability for any errors in these materials is limited to the documentary correction of errors. T-Mobile USA will not be responsible in any event for errors in these materials or for any damages, incidental or consequential (including monetary losses), that might arise from the use of these materials or the information in them. T-Mobile, the T-Mobile logo and the World Class logo are registered or unregistered trademarks of Deutsche Telekom AG.

Acknowledgements

The following individuals are responsible for contribution to the specifications, design and implementations represented in the various revisions:Russell Foreman (South)

Sanjay Chawla (South)

Tim Zhang (FSC)Heitor Almeida (FSC)Dinesh Kumar (FSC - NSN)Protection of Information Credibility

This document contains confidential material critical to the business and is therefore a controlled document. Outdated copies must be destroyed to prevent erroneous use of obsolete information and compromised security of confidential material. Do not e-mail this file. Do send the link to correspondents so they are assured of seeing the latest revision. The most recent revision of this file is always in softcopy and can be accessed at the following link.

http://docs.eng.t-mobile.com/InfoRouter/docs/~D671503Note to revisers: For the above link to remain valid, you must use proper check out / check in procedures when you update this document.

Revision Code

The revision number will reflect the modifications by following the format Rev. x, y, whereX is the first digit, incremented for changes of substance, i.e. technical/procedural issues.

Y is the second digit, incremented when editorial only changes have been incorporated.

All draft/preliminary versions are 0.n; the first final version is Revision 1.0.

Revision History

Rev.DateAuthorInformation

1.011/05/08Russell Foreman

Sanjay ChawlaInitial document for Nokia UMTS Phase 1 Trouble Shooting Guideline document for KPI category Accessibility.

1.51/20/09Russell Foreman

Sanjay ChawlaRevamped document for Nokia Accessibility includes formulas, counter descriptions, flowcharts, and examples for troubleshooting

1.61/28/09Tim ZhangRe-format the document with standard format

1.72/5/09Dinesh Kumar (NSN)Modified on section 2.3.3

1.82/5/09Sanjay ChawlaUpdates on section 2.5

1.92/6/09Tim ZhangTroubleshooting flowchart added in Section 2.2

2.02/13/09Heitor AlmeidaUpdated the PS NRT Access Failure rate formula/section including the Rab reconfiguration phase for the rab 0/0, and added section describing the RAB 0/0 kbps Reconfiguration Phase. Excluded HS specific section since PS section is treating both R99 and PS now.

2.12/19/09Heitor Almeida , Dinesh Kumar (NSN)Updated flowchart and cell analysis for PS setup failure causes for the rab 0/0 reconfiguration phase.

2.28/26/2009Russell ForemanCorrected minor errors and removed copied data from Retainability document paste error. Also updated Tools section

Table of Contents

51.Introduction

51.1.Purpose & Scope

51.2.Definitions for this Document

82.Accessibility

82.1.T-PIM Reports

82.2.Troubleshooting Flowchart

102.3.CS Voice Accessibility

102.3.1.Nokia Accessibility Messaging Diagram (CS and PS R99)

112.3.1.1.RRC Phase

152.3.1.2.RAB Phase

182.3.2.RNC/Market/Region Level Reporting

222.3.3.Cell Analysis

222.3.3.1.RRC Setup Phase Failure Causes

232.3.3.2.RRC Access Phase Failure Causes

242.3.3.3.Voice RAB Setup Failure Causes

252.3.3.4.Voice RAB Access Failure Causes

262.4.R99 PS RAB Accessibility

272.4.1.RNC/Market/Region Level Reporting

272.4.1.1.RRC Phase

282.4.1.2.RAB Phase (0.0 kbps)

292.4.1.3.RAB 0/0 kbps Reconfiguration Phase

342.4.2.Cell Analysis

342.4.2.1.RRC Setup Phase Failure Causes

342.4.2.2.RRC Access Phase Failure Causes

342.4.2.3.PS R99 RAB Setup Phase Failure Causes

342.4.2.4.PS R99 RAB Access Phase Failure Causes

352.4.2.5.Packet Call Setup Failure Causes

363.Configuration Management

374.Troubleshooting Tools

385.References

1. Introduction

1.1. Purpose & Scope

The intent of this document is to provide UMTS Trouble Shooting and Optimization from KPI and Counter perspectives for Nokia Accessibility and provide detailed analysis strategies for identifying reason for the KPI trends and offering guidelines for improving performance by Key Optimization techniques.

The KPI/Counters described here are applicable to the RAS6 release of the Nokia UTRAN.This document is not all inclusive and is only intended to provide a quick cook book to understand available for trouble shooting and optimization best practices Guideline Document. For any information not covered here, the NSN NED documentation should be referenced.

1.2. Definitions for this Document

Term or AcronymDefinition

3GPPThird Generation Partnership Project

ASActive Set

BSICBase Station Identity Code

BTSBase Transceiver Station

CNCore Network

CPICHCommon Pilot Channel

DCHDedicated Channel

DLDownlink

DPCCHDedicated Physical Control Channel

DPCHDedicated Physical Channel

DRNCDrift Radio Network Controller

FACHForward Access Channel

FIFOFirst In First Out

GERANGSM EDGE RAN

GSMGlobal System for Mobile Communications

HCSHierarchical Cell Structure

HSDPAHigh Speed Data Packet Access

IAFIntra Frequency

IEInformation Element

IEFInter Frequency

IFHOInter Frequency Handover

Inter-RATInter Radio Access Technology

IRATInter Radio Access Technology

IurInterface between two RNCs

KPIKey Parameter Indicator

LALocation Area

LAILocation Area Indicator

NBAPNode B Application Part

Node BLogical node responsible for radio transmission and reception in one or several cells

OCNSOrthogonal Channel Noise Simulator

PLMNPublic Land Mobile Network

RARouting Area

RABRadio Access Bearer

RAIRouting Area Indicator

RANRadio Access Network

RATRadio Access Technology

RBRadio Bearer

RBSRadio Base Station another name for the Node B

RFRadio Frequency

RLRadio Link

RNCRadio Network Controller

RRCRadio Resource Control

RSCPReceived Signal Code Power

RSSIReceived Signal Strength Indicator

SIBSystem Information Block

SIRSignal to Interference Ratio

TRXTransceiver

TXTransmit

UEUser Equipment

ULUplink

UMTSUniversal Mobile Telecommunication Services

UTRANUMTS Terrestrial Radio Access Network

WCDMAWideband Code Division Multiple Access

2. AccessibilityThe metrics measures user ability to access the mobile network for circuit switched and packet switched calls. The metrics consists of two components RRC and RAB. The RRC part of the equation measures originating and terminating calls. The non-access stratum (signaling) part of the access call flow is not included in this KPI.

2.1. T-PIM Reports The primary T-PIM Reports used for the Accessibility metrics are:

AccessibilityThese reports are explained in detail in the T-PIM Report Documentation.

2.2. Troubleshooting Flowchart The following flowchart may be useful for troubleshooting the voice and ps accessibility issues based on the problem areas. Flow chart in PowerPoint

2.3. CS Voice AccessibilityFind below the Metric Definition for CS (Voice) Accessibility % as per T-PIM Specs for Nokia -

The metrics measures user ability to access the mobile network for circuit switched voice calls. The metrics consists of two Access components of CS call, RRC and RAB. The RRC part of the equation measures Conversational (originating and terminating). The RAB part of the equation measures Speech RAB and is pegged on the best cell in the active set in Serving RNC. The RRC measures Conversational Voice and Data (CSV+CSD) while RAB part measures only Speech for both originating and terminating causes. Formula:

Voice Access Failure Rate% = 100 * (1 - RRC_Access_Success_Rate * RAB_Access_Success_Rate)

Where RRC_Access_Success_Rate = (Voice Successful Rrc Connection Requests / Voice Attempted Rrc Connection Requests)RAB_Access_Success_Rate = (Voice Successful Rab Establishments / Voice Attempted Rab Establishments)And

Voice Successful Rrc Connection Requests = ((Moc_Conv_Call_Atts + Mtc_Conv_Call_Atts) - (Rrc_Acc_Rel_Mo_Conv + Rrc_Acc_Rel_Mt_Conv) - (Moc_Conv_Call_Fails + Mtc_Conv_Call_Fails))

Voice Attempted Rrc Connection Requests = ((Moc_Conv_Call_Atts + Mtc_Conv_Call_Atts) - (Rrc_Acc_Rel_Mo_Conv + Rrc_Acc_Rel_Mt_Conv) - (Rrc_Att_Rep_Mo_Conv + Rrc_Att_Rep_Mt_Conv))

Voice Successful Rab Establishments = (Rab_Acc_Comp_Cs_Voice)

Voice Attempted Rab Establishments = (Rab_Stp_Att_Cs_Voice + Rab_Stp_Fail_Cs_Not_Supp_Par + Rab_Stp_Fail_Cs_Ue_Capa)2.3.1. Nokia Accessibility Messaging Diagram (CS and PS R99)

Figure 1: Ericsson vs. Nokia counter pegging in the Access phase of the callNokia Accessibility contains RRC phase and RAB phase (due to lack of the counter, SRB phase is not counted in Accessibility now). In each of the phase, there is Setup and Access procedure. Setup procedure usually involves the resource allocation in RAN system.

2.3.1.1. RRC Phase

Note that if a failure which leads to RRC connection release occurs during any RAB phase, both RRC active and RAB (setup, access or active) failure counters are updated with an appropriate cause.

Figure 2: RRC phase and triggering of specific counters

The following details the specific RRC counters pictured in Figure 3.

1. RRC setup attempts.

2. RRC setup attempts per setup cause. 3. RRC setup failures due to

handover control

admission control

transport (Transmission)

RNC internal

frozen BTS

BTS RNTI Allocation fail

IuB AAL2

ICSU overload4. RRC setup failures per setup cause.

5. RRC setup complete.

6. RRC access failures due to

radio interface

UE

RNC internal

7. RRC access complete.

8. Special reason: RRC active release due to

SRNC Relocation

Pre-emption

9. RRC active failures due to

Iu interface (transport)

radio interface (synchronization)

BTS

Iur interface (DRNC)

RNC internal

UE

10. RRC active complete.

RRC setup phase fail counters (item 3 from Figure 2)

The RRC setup failure counters below include all traffic types, not just CS voice. So, the setup failure count from the following counters will be greater than that of the CS RRC setup attempts the CS RRC setup successes.

CounterServiceDefinition

RRC_CONN_STP_FAIL_HC AllRRC connection request rejects due to handover control entity reporting a failure

RRC_CONN_STP_FAIL_AC AllRRC connection request rejects due to the admission control entity reporting a failure (excluding frozen BTS reason).

RRC_CONN_STP_FAIL_BTS AllRRC connection request rejects due to unsuccessful radio link setup.

RRC_CONN_STP_FAIL_TRANS AllRRC connection request rejects due to transport failure. (Includes fails due to AAL2 Iub)

RRC_CONN_STP_FAIL_RNC AllRRC connection request rejects due to RNC internal failure.

RRC_CONN_STP_FAIL_FROZBS AllRRC connection request rejects due to admission control entity blocking the radio link establishment in order to ensure the setup of high priority calls.

RRC_CONN_STP_FAIL_RNTI_ALLO AllRRC connection request rejects due to RNTI allocation failure caused by RRMU overload.

RRC_CONN_STP_FAIL_IUB_AAL2 AllRRC connection request rejects due to Iub transport resource shortage between RNC and WBTS.

RRC_CONN_STP_FAIL_ICSU_OVERL AllRRC connection request rejects due to ICSU overload. (Counter not currently loaded into TPIM, pre-RAS 06 load)

* RRC setup fails due to transport errors (T1 slips, DIP errors, etc.), but not due to Iub congestion must be calculated as RRC_CONN_STP_FAIL_TRANS - RRC_CONN_STP_FAIL_IUB_AAL2

RRC access phase fail counters (item 6 from Figure 2)

CounterServiceDefinition

RRC_CONN_ACC_FAIL_RADIOAllRNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6 seconds, and the RNC has not received the NBAP message which indicates that L1 synchronization has been established between UE and BTS.

RRC_CONN_ACC_FAIL_MSAllRNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE within 6 seconds, and the RNC has received the NBAP message which indicates that L1 synchronization has been established between UE and BTS.

RRC_CONN_ACC_FAIL_RNCAllRNC internal failure occurs before receiving the RRC: RRC CONNECTION SETUP COMPLETE message from the UE.

2.3.1.2. RAB Phase

Figure 3: RAB phase and triggering of counters

Note that RAB active phase is completed also when CN sends RANAP: Iu Release Command.

1. RAB setup attempts. Separate counter per each RAB type. Details in the section RAB setup.

2. RAB setup failures due to (separate counter for each RAB type)

admission control

transport (transmission)

RNC internal

frozen BTS

BTS (RT only)

anchoring (NRT only)

3. RAB setup complete. Separate counter per each RAB type.

4. RAB access failures due to (separate counters per each RAB type)

UE

RNC internal

5. RAB access complete. Separate counters per each RAB type.

6. Special reason: RAB active release due to (separate counters per each RAB type)

SRNC relocation

pre-emption

7. RAB active failures due to (separate counters per each RAB type)

Iu interface (transport)

radio interface (synchronization)

BTS

Iur interface (DRNC)

RNC internal

UE.

8. RAB reconfiguration attempts.

9. RAB reconfiguration failures.

10. RAB active complete. Separate counters per each RAB type.

RAB setup phase fail counters (item 2 from Figure 3)

CounterServiceDefinition

RAB_STP_FAIL_CS_VOICE_AC CS (Voice)RNC rejects the CS voice RAB request because the admission control entity reports a failure (excluding frozen BTS reason).

RAB_STP_FAIL_CS_VOICE_BTS CS (Voice)RAB assignment fails due to radio link setup or reconfiguration failure. The failure can happen either in the Iub or in the Iur interface.

RAB_STP_FAIL_CS_VOICE_TRANS CS (Voice)RNC rejects the CS voice RAB request due to transport failure. (Includes fails due to AAL2 Iub)

RAB_STP_FAIL_CS_VOICE_RNC CS (Voice)RNC decides to reject the CS voice RAB request due to RNC internal failure.

RAB_STP_FAIL_CS_VOICE_FROZBS CS (Voice)RNC rejects the CS voice RAB request because the admission control entity blocks the radio link establishment to ensure the setup of high priority calls.

RAB_STP_FAIL_CS_V_IUB_AAL2 CS (Voice)RNC decides to reject the CS voice RAB request due to Iub transport resource shortage between RNC and WBTS.

RAB_STP_FAIL_CS_NOT_SUPP_PARCS (Voice) CS RAB setup attempt is not started due to requested parameters are not supported by the RNC. (CS data calls)

RAB_STP_FAIL_CS_UE_CAPACS (Voice)CS RAB setup attempt is not started due to requested parameters are not supported by the UE. (CS Data calls)

RAB access phase fail counters (item 4 from Figure 4)

CounterServiceDefinition

RAB_ACC_FAIL_CS_VOICE_MS CS (Voice)RAB access setup for a CS Voice Call fails because of the UE.

RAB_ACC_FAIL_CS_VOICE_RNC CS (Voice)RAB setup access failures for CS Voice Calls caused by RNC's internal reasons.

2.3.2. RNC/Market/Region Level Reporting

This section covers analysis of Accessibility % for Nokia and identification of issues using the available Nokia accessibility Counters.

Atlanta

In the analysis, data for Atlanta from the South region has been presented. The following charts clearly indicates the following

Atlanta Market has three RNCs and has daily traffic of around 5,500 Erlangs for the timeframe under consideration.

The majority of days show that RRC Failure rate is the highest contributing factor to the Total Accessibility score

G1 launch elevated traffic and call setup attempts

RNC2 and RNC3 had incorrect RNC level parameters for Iur parameter, AAL2 CPS-SDU multiplexing delay. One RNC end point had 10 ms, while the other RNCs end point had 100 ms.

Accessibility was impacted due to this incorrect Iur parameter and the elevated traffic from the G1 launch

Parameter was fixed on Oct 28, 2008

Problem also impacted SHO failure rate and MOU/drop negatively.

Figure 4: Atlanta's accessibility mostly influenced by RAB Failures

The G1 launch increased traffic in ATRNC002 and ATRNC003 tremendously. It highlighted a problem not seen before the G1 launch.

Figure 5: Raw counts of RRC and RAB Failures

RAB Failures increased disproportionally as the G1 launch increased RAB attempts across the Iur interface. Whereas before the G1 launch the volume of RAB attempts across the Iur boundaries was not sufficient to reveal the issue.

Figure 6: Atlanta shows mobile originated calls as having the worst problem in Access Fails

No real change in the RRC fail reasons of terminated calls as opposed to originating calls. Mobile originated calls bear a greater percentage of failures over mobile terminating call.

Figure 7: In RAB Setup phase, the majority of Atlantas problems are in the non Iub transport and the RNC level reasons for access failures

When the Iur parameter mismatch was fixed, there is an immediate decrease in the transport related RAB setup fails on Oct. 28.

Figure 8: RAB access fail reasons show the UE as being the weak link which is more an indication of RF conditions rather than the UE being faulty

No major impacts on RAB access fail reasons of the UE as opposed to the RNC relating to this Iur problem.

Figure 9: RRC connection setup fails in Atlanta for the most part is dominated by RNC errors with some contribution from Access Control and BTS errors

The increase in IUB AAL2 (blocking in the Iub reservations) RRC setup fails can be seen starting mainly on 10/20 which corresponds to the launch of the G1. This fail metric is starting to dominate the RRC setup failures. The solution is to start adding Iub capacity and to utilize more Iub saving features where additional capacity is not feasible.

Figure 10: RRC Access fails show the RF conditions are the majority of the problems reside in the radio link for Atlanta2.3.3. Cell Analysis2.3.3.1. RRC Setup Phase Failure CausesPlease note all these RRC failure counters for all type of services or establishment causes (not just voice).a) RRC Request Reject due to Handover ControlWhen the RNC decides to reject the RRC connection request because the handover control entity reports a failure.

Identify, if the problem is RNC wide or spread over a group of cells and report to tier 2 for further investigation.b) RRC Request Reject due to Admission Control

The RNC will check the available resources during the RRC setup stage; DL Codes, UL Load (Prx total), DL load (Downlink Tx power). (Note the RNC does not check for CE in the NodeB)

Detailed analysis can be done to find exactly which resource is causing the admission problem from traffic and cell resource counters.c) RRC Request Reject due to Transport Failure (include failure due to AAL2)Transport failures are mostly due to T1 related issues which can be checked from BER counters. This counter will also include the number of times the T1 was congested (AAL2 blocking).Detailed analysis can be done from AAl2 resource reservation counters.

d) RRC Request Reject due to RNC Internal FailureThis counter is pegged if the RNC can not assign the failure to any other failure counters or if there is a RNC hardware/software/resource problem/L2 failure. This counter needs to be monitored for any step changes for it might indicate RNC is having some internal problem like hanging resources. e) RRC Request Reject due to Frozen BTSThis counter pegs in the event when the RNC rejected the RRC setup to ensure the setup of high priority calls. This is related to congestion & should be analyzed as per RRC Request Reject due to Admission Controlf) RRC Request Reject due to RNTI Allocation Failure

This counter point out resource issues in the RRMU. Investigate RNC dimensioning.

g) RRC Request Reject due to Iub AAL2 Transport This counter points out T1 capacity problems between RNC and NodeB..Before a T1 upgrade is raised for cells having a high count in Iub congestion a detail analysis must be done to investigate if the congestion can be resolved by improving the Soft Handover Overhead (by down tilt or parameter change).Detailed analysis can be done from AAl2 CAC/ resource reservation counters.

h) RRC Request Reject due to ICSU OverloadIt is unlikely that this will be a cell specific issue and would rather be an RNC wide or multiple sites connected to the ICSU. There is a few know problems in the RNC that are related to the ICSU load and dimensioning issues, see List of Generic Faults LGF-RNC-2008-07 Radio Controllers WCDMA RNC RN2.2, RN3.0 on NED for more details.i) RRC Request Reject due BTSThis counter is showing that there is potentially a hardware, configuration or resource issue in the NodeB.

Resource problems can be verified from the CE usage counters, if the traffic is low and the CE usage is high it is due to hanging resources. If the traffic is high it might be that there is not enough license keys for CE. (Compare the max CE used counters with installed license keys in the WBTS) Also check the number of users in Compressed Mode, currently defined as maximum of 16 with the T-Mobile USA baseline parameter set. If the number of users in compressed mode is high when there is no traffic in the cell it is also indicates that there is hanging resources in the cell.

A site reset normally corrects these problems, if the problem does not clear or repeats a ticket should be open with the field technicians to investigate. Potential issues on the site that can cause this problem can be: Incorrect configuration data (audit the commissioning file for any discrepancies)

Corrupt files in the NodeB (Recommissioning should resolve this problem)

Corrupt software in the NodeB (Software upgrade/ downgrade can be used to reload the software in the site)

Faulty hardware (System module). It has been seen that replacing the system module resolved this problem. Note in these instances there were no alarms on the site to indicate that there was a hardware issue.

2.3.3.2. RRC Access Phase Failure Causesa) RRC Connections Access Failure due to Radio Reasons

These failures are mostly RF related and can be split between: Bad Coverage (Low RSCP)

Interference (Low Ec/No)

Route cause analysis will in most cases require drive test analysis.

Also verify that the uplink PRXnoise for these sites is within acceptable range. b) RRC Connections Access Failure due to MS FailuresThe cause for this counter can be coverage even though L1 synchronization has been achieved it can still be that a sudden loss in coverage was experienced. If only one site is showing a high count for this counter the most likely cause is that it is coverage related. If this is an RNC wide problem it needs to be determine if it is a specific UE type that is causing the problem, this will require advance analysis with the help of K18 and potentially the Xmine team.

Also verify that the uplink PRXnoise for the site is within acceptable range. c) RRC Connections Access Failure due to RNC Failures

If the counter is showing a step change it might be related to a new software load that was loaded on the RNC or core network side. To trouble shoot these problem it will require in-depth analysis on the RNC which should be done by Tier 2. If only particular sites are showing a high count for this counter investigate if there is any common point of failure for these cells ( Same RNC, same Transmission path/ hardware) Also investigate if the T1 for these sites are error free ( Look at the cell availability and BER for T1)2.3.3.3. Voice RAB Setup Failure Causes

a) Voice RAB Setup Failure Due to Admission ControlSame as RRC admission control (2.3.3.1) only difference is that now the exact number of voice attempts rejected due to admission can be seen rather than the total for all the services.

b) Voice RAB Setup Failure Due to BTS

Same as RRC setup failures due to BTS (2.3.3.1)

c) Voice RAB Setup Failure Due to Transport (includes failures due to AAL2 Iub)

Same as RRC setup failures due to Transport (2.3.3.1)

d) Voice RAB Setup Failure Due to RNCSame as RRC setup failures due to RNC (2.3.3.1)e) Voice RAB Setup Failure Due to Frozen BTSSame as RRC setup failures due to Frozen BTS (2.3.3.1)f) Voice RAB Setup Failure Due to AAL2 IubSame as RRC setup failures due to AAL2 (2.3.3.1)g) Voice RAB Setup Failure Due to Non-support Request

CS RAB setup attempt is not started due to requested parameters are not supported by the RNC. (CS data calls) It should be looked into if this is a specific device that is requesting the unsupported RAB configuration, this investigation can only be done with the help of K18 or similar advance tracing equipment.h) Voice RAB Setup Failure Due to UE Capability

Same as above, voice RAB Failure Due to Non-supported Request.2.3.3.4. Voice RAB Access Failure Causes

a) Voice RAB Access Failure Due to UE

Same as RRC access failures due to MS (2.3.3.2)b) Voice RAB Access Failure Due to RNC Internal Failures

Same as RRC setup failures due to RNC (2.3.3.1)2.4. R99 PS RAB AccessibilityFind below the Metric Definition for PS (Packet) Accessibility as per T-PIM Specs for Nokia

PS NRT Access Failure Rate (%)

The metrics measures user ability to access the mobile network for PS, both HSPA and R99, interactive and background connections. The metrics consists of three components of PS Access call, RRC, RAB and RAB 0/0 reconfiguration.

Figure 11 Three phases considered in the PS Access Failure formula

The RRC part of the equation measures RRC failures for both originating and terminating calls. The RAB part of the equation measures failures for the PS NRT RAB 0/0 kbps both originating and terminating and is pegged on the best cell in the active set in Serving RNC. The RAB 0/0 reconfiguration part measures the failures when trying to actual reserve resources to reconfigure the RAB 0/0 and assign it certain bit rate.The non-access stratum (signaling) and PDP access part of the access call flow is not included in this KPI.

Formulas:

PS NRT Access Failure Rate (%) = 100*(1-(Ps Successful RRC Connection Requests / Ps Attempted RRC Connection Requests) * (Ps Successful RAB Establishments / Ps Attempted RAB Establishments) * (Packet Call Allocation Success/Packet Call Attempts)) Where:Ps Successful Rrc Connection Requests = (Moc_Inter_Call_Atts + Mtc_Inter_Call_Atts + Moc_Backg_Call_Atts + Mtc_Backg_Call_Atts) - (Rrc_Acc_Rel_Mo_Interactive + Rrc_Acc_Rel_Interactive + Rrc_Acc_Rel_Mo_Background + Rrc_Acc_Rel_Mt_Background) - ( Moc_Inter_Call_Fails+Mtc_Inter_Call_Fails + Moc_Backg_Call_Fails+ Mtc_Backg_Call_Fails )

Ps Attempted Rrc Connection Requests = (Moc_Inter_Call_Atts + Mtc_Inter_Call_Atts + Moc_Backg_Call_Atts + Mtc_Backg_Call_Atts) - (Rrc_Acc_Rel_Mo_Interactive + Rrc_Acc_Rel_Interactive + Rrc_Acc_Rel_Mo_Background + Rrc_Acc_Rel_Mt_Background) - (Rrc_Att_Rep_Mo_Interactive + Rrc_Att_Rep_Interactive + Rrc_Att_Rep_Mo_Background + Rrc_Att_Rep_Mt_Background)

Ps Successful Rab Establishments = Rab_Acc_Comp_Ps_Inter + Rab_Acc_Comp_Ps_Backg

Ps Attempted Rab Establishments = Rab_Stp_Att_Ps_Inter + Rab_Stp_Att_Ps_BackgPacket Call Allocation Success = Hs_E_Req_Hs_E_Allo_Int + Hs_E_Req_Hs_E_Allo_gr + Hs_E_Req_Hs_D_Allo_Int + Hs_E_Req_Hs_D_Allo_Bgr + Hs_D_Req_Hs_D_Allo_Int + Hs_D_Req_Hs_D_Allo_Bgr + Hs_E_Req_D_D_Allo_Int + Hs_E_Req_D_D_Allo_Bgr + Hs_D_Req_D_D_Allo_Int + Hs_D_Req_D_D_Allo_Bgr + D_D_Req_D_D_Allo_Int + D_D_Req_D_D_Allo_Bgr Packet Call Attempts = Ps_Att_Hsdsch_Edch_Int+Ps_Att_Hsdsch_Edch_Bgr + Ps_Att_Hsdsch_Dch_Int + Ps_Att_Hsdsch_Dch_Bgr + Ps_Att_Dch_Dch_Int + Ps_Att_Dch_Dch_Bgr 2.4.1. RNC/Market/Region Level Reporting

2.4.1.1. RRC PhaseSame RRC phase signaling diagram is used for both Voice and R99 PS RRC phase. Please refer to section 2.3.1.1.

RRC setup phase fail counters

Same RRC setup phase failure cause counters are applied for both Voice and PS R99 service. Please refer to section 2.3.1.1 for detail.

RRC Access phase fail counters

Same RRC Access phase failure cause counters are applied for both Voice and PS R99 service. Please refer to section 2.3.1.1 for detail.

In addition, there are a few more RRC Access failure counters available for PS only.

CounterServiceDefinition

RRC_ACC_REL_MO_INTERACTIVEPSNumber of RRC connection access releases due to cell reselection for calls established with the cause originating interactive call

RRC_ACC_REL_INTERACTIVEPSNumber of RRC connection access releases due to cell reselection for calls established with the cause terminating interactive call

RRC_ACC_REL_MO_BACKGROUNDPSNumber of RRC connection access releases due to cell reselection for calls established with the cause originating background call

RRC_ACC_REL_MT_BACKGROUNDPSNumber of RRC connection access releases due to cell reselection for calls established with the cause terminating background call

2.4.1.2. RAB Phase (0.0 kbps)RAB setup phase fail counters (item 2 from Figure 4)

CounterServiceDefinition

RAB_STP_FAIL_PS_CONV_ACPS R99 Conv/streamRAB setup failures due to rejection of the PS data conversational RAB request because the admission control entity reports a failure (excluding frozen BTS reason)

RAB_STP_FAIL_PS_CONV_BTSPS R99 Conv/streamRAB assignment fails due to radio link setup or reconfiguration failure. The failure can happen either in the Iub or in the Iur interface.

RAB_STP_FAIL_PS_CONV_TRANSPS R99 Conv/streamRAB setup failures caused by transport for PS data conversational.

RAB_STP_FAIL_PS_CONV_RNCPS R99 Conv/streamRAB setup failures caused by RNC internal failure for PS data conversational.

RAB_STP_FAIL_PS_CONV_FROZBSPS R99 Conv/streamWhen the RNC decides to reject the PS data conversational RAB request because the admission control entity blocks the radio link establishment to ensure the setup of high priority calls

RAB_STP_FAIL_PS_INTER_ACPS R99 InterRAB setup failures due to rejection of the PS data interactive RAB request because the admission control entity reports a failure (excluding frozen BTS reason)

RAB_STP_FAIL_PS_INTER_RNCPS R99 InterRAB setup failures caused by RNC internal failure for PS data interactive.

RAB_STP_FAIL_PS_INTER_FROZBSPS R99 InterWhen the RNC decides to reject the PS data interactive RAB request because the admission control entity blocks the radio link establishment to ensure the setup of high priority calls

RAB_STP_FAIL_PS_INTER_ANCHPS R99 InterNumber of RAB setup failures caused by anchoring for PS data interactive

RAB_STP_FAIL_PS_BACKG_ACPS R99 BackgRAB setup failures due to rejection of the PS data background RAB request because the admission control entity reports a failure (excluding frozen BTS reason)

RAB_STP_FAIL_PS_ BACKG _RNCPS R99 BackgRAB setup failures caused by RNC internal failure for PS data background.

RAB_STP_FAIL_PS_ BACKG _FROZBSPS R99 BackgWhen the RNC decides to reject the PS data background RAB request because the admission control entity blocks the radio link establishment to ensure the setup of high priority calls

RAB_STP_FAIL_PS_ BACKG _ANCHPS R99 BackgNumber of RAB setup failures caused by anchoring for PS data background

RAB access phase fail counters (item 4 from Figure 4)

CounterServiceDefinition

RAB_ACC_FAIL_PS_CONV_MS PS R99 Conv/steamRAB access setup for a PS conversational Call fails because of the UE.

RAB_ACC_FAIL_ PS_CONV_RNC PS R99 Conv/streamRAB setup access failures for PS conversational Calls caused by RNC's internal reasons.

RAB_ACC_FAIL_PS_INTER_MSPS R99 InterRAB access setup for a PS Interactive Call fails because of the UE.

RAB_ACC_FAIL_PS_INTER_RNCPS R99 InterRAB setup access failures for PS Interactive Calls caused by RNC's internal reasons.

RAB_ACC_FAIL_ PS_BACKG_MS PS R99 BackgRAB access setup for a PS background Call fails because of the UE.

RAB_ACC_FAIL_ PS_ BACKG _RNC PS R99 BackgRAB setup access failures for PS background Calls caused by RNC's internal reasons.

2.4.1.3. RAB 0/0 kbps Reconfiguration Phase

In NSN, for non-real time (NRT) services, the radio access bearers (RAB) are initially created without immediate reservation of radio resources (RAB 0/0 kbps). Instead, radio resources are allocated after that, based on the capacity requests (event 4A). Therefore the HS and R99 resources are only verified during the attempt to reconfigure the RAB 0/0 to a certain bit rate different than 0/0.

The packet call attempts measured in this kpi are updated when the UE-specific packet scheduler attempts to allocate an HS-DSCH/E-DCH, HS-DSCH/DCH or DCH/DCH transport channels for the NRT RAB that has no dedicated/shared channels that are already allocated for the RAB (RAB 0/0). So only RAB 0/0 kpbs to higher bit rate RAB or FACH to DCH channel switches are computed. Packet call channel switches from RAB>0/0 kbps to higher or lower bit rate are not considered in this KPI.Below is the formula for the RAB Reconfiguration component of the headline PS Access Failure Rate metric.Packet Call Allocation Failure Rate (%) = 100*(1- (Packet Call Allocation Success/Packet Call Attempts)) Where,Packet Call Allocation Success = Hs_E_Req_Hs_E_Allo_Int + Hs_E_Req_Hs_E_Allo_gr + Hs_E_Req_Hs_D_Allo_Int + Hs_E_Req_Hs_D_Allo_Bgr + Hs_D_Req_Hs_D_Allo_Int + Hs_D_Req_Hs_D_Allo_Bgr + Hs_E_Req_D_D_Allo_Int + Hs_E_Req_D_D_Allo_Bgr + Hs_D_Req_D_D_Allo_Int + Hs_D_Req_D_D_Allo_Bgr + D_D_Req_D_D_Allo_Int + D_D_Req_D_D_Allo_Bgr Packet Call Attempts = Ps_Att_Hsdsch_Edch_Int+Ps_Att_Hsdsch_Edch_Bgr + Ps_Att_Hsdsch_Dch_Int + Ps_Att_Hsdsch_Dch_Bgr + Ps_Att_Dch_Dch_Int + Ps_Att_Dch_Dch_Bgr The formula considers the user point of view in terms that as long as the customer gets the data service access, it is considered a successful allocation. For example, if the transport channel allocation request was for HS-DSCH/DCH - HSDPA on the downlink and R99 on the uplink (counter Ps_Att_Hsdsch_Dch_Bgr) - and the actual allocation was DCH/DCH - R99 on both downlink and uplink (counter Hs_D_Req_D_D_Allo_Bgr ) - , it is still considered a successful access since the user got the data service anyway.The figure below shows the possible types of packet allocation requests and their respective successful allocations types. There are counters for each of them.

Below is the description of all the counters used on the RAB 0/0 kbps Reconfiguration Phase part of the ps access failure metric.CounterDescriptionConditionMO Class

PS_ATT_HSDSCH_EDCH_INT

PS_ATT_HSDSCH_EDCH_BGRThe number of HS-DSCH/E-DCH packet call attempts for the interactive or background traffic class.Updated: When the UE-specific packet scheduler attempts to allocate an HS-DSCH/E-DCH transport channel for the NRT RAB, and there are no dedicated/shared channels that are already allocated for the RAB.Packet Call (M1022)

PS_ATT_HSDSCH_DCH_INT

PS_ATT_HSDSCH_DCH_BGRThe number of HS-DSCH/DCH packet call attempts for the interactive or background traffic class.Updated: When the UE-specific packet scheduler attempts to allocate an HS-DSCH/DCH transport channel for the NRT RAB, and there are no dedicated/shared channels that are already allocated for the RAB.Packet Call (M1022)

PS_ATT_DCH_DCH_INT

PS_ATT_DCH_DCH_BGRThe number of DCH/DCH packet call attempts for the interactive or background traffic class.Updated: When the UE-specific packet scheduler attempts to allocate a DCH/DCH transport channel

for the NRT RAB, and there are no dedicated/shared channels that are already allocated for the RAB.Packet Call (M1022)

HS_E_REQ_HS_E_ALLO_INT

HS_E_REQ_HS_E_ALLO_BGRThe number of allocations for the HS-DSCH/E-DCH after an HS-DSCH/E-DCH request for the interactive or background traffic class.

Updated: When the user's HS-DSCH/E-DCH user plane allocation is successfully completed.Packet Call (M1022)

HS_E_REQ_HS_D_ALLO_INT

HS_E_REQ_HS_D_ALLO_BGRThe number of HS-DSCH/DCH allocations after an HS-DCSH/E-DCH request for the interactive or background traffic class.Updated: When the user is successfully allocated to the HS-DSCH/DCH user plane and the request was for the HS-DSCH/E-DCH.Packet Call (M1022)

HS_D_REQ_HS_D_ALLO_INT

HS_D_REQ_HS_D_ALLO_ BGR

The number of HS-DSCH/DCH allocations after an HS-DSCH/DCH request for the interactive or background traffic class.Updated: When the user is successfully allocated to the HS-DSCH/DCH user plane and the request was for the HS-DSCH/DCH.Packet Call (M1022)

HS_E_REQ_D_D_ALLO_INT

HS_E_REQ_D_D_ALLO_ BGR

The number of DCH/DCH allocations after an HS-DSCH/E-DCH request for the interactive traffic class.Updated: When the user is successfully allocated to the DCH/DCH user plane and the request was for the HS-DSCH/E-DCH.Packet Call (M1022)

HS_D_REQ_D_D_ALLO_INT

HS_D_REQ_D_D_ALLO_ BGR

The number of DCH/DCH allocations after an HS-DSCH/DCH request for the interactive traffic class.Updated: When the user is successfully allocated to the DCH/DCH user plane and the request was for the HS-DSCH/DCH.Packet Call (M1022)

D_D_REQ_D_D_ALLO_INT

D_D_REQ_D_D_ALLO_ BGR

The number of DCH/DCH allocations after a DCH/DCH request for the interactive or background traffic class.Updated: When the user is successfully allocated to the DCH/DCH user plane and the request was for the DCH/DCH.Packet Call (M1022)

If the PS user plane allocation fails due to some reason, the corresponding packet call setup failure counters are updated. The following setup failures are seen with these counters:

Admission Control (AC) failures

BTS failures

DMPG resource allocation failures

Iub transport failures

Failures due to UE

Any other failures not covered by the other failure countersCounterDescriptionConditionMO Class

PS_SETUP_FAIL_AC_INTPS_SETUP_FAIL_AC_BGRThe number of packet call setup failures due to the admission control for the interactive or background traffic class.Updated: When the PS user plane allocation is rejected by the admission control.Packet Call (M1022)

PS_SETUP_FAIL_BTS_INTPS_SETUP_FAIL_BTS_ BGRThe number of packet call setup failures due to the BTS for the interactive or background traffic class.Updated: When the PS user plane allocation fails due to the BTS responding with an NBAP: RADIO

LINK SETUP FAILURE or an NBAP: RADIO LINK RECONFIGURATION FAILURE message, or not responding at all.Packet Call (M1022)

PS_SETUP_FAIL_DMCU_INTPS_SETUP_FAIL_DMCU_ BGRThe number of packet call setup failures due to lack of DMCU resources for the interactive or background traffic class.Updated: When the PS user plane allocation fails due to a DMCU resource allocation failure.Packet Call (M1022)

PS_SETUP_FAIL_TRANS_INTPS_SETUP_FAIL_TRANS_ BGRThe number of packet call setup failures due to transport for the interactive or background traffic class.Updated: When the PS user plane allocation fails due to an Iub transport setup failure.Packet Call (M1022)

PS_SETUP_FAIL_UE_INTPS_SETUP_FAIL_UE_ BGRThe number of packet call setup failures due to the UE for the interactive or background traffic class.Updated: When the PS user plane allocation fails due to the UE responding with an RRC: RADIO

BEARER RECONFIGURATION FAILURE message or not responding at all.Packet Call (M1022)

PS_SETUP_FAIL_OTHER_INTPS_SETUP_FAIL_OTHER_ BGRThe number of packet call setup failures for the interactive or background traffic class due to other reasons than those covered by the other failure counters.Updated: When the PS user plane allocation fails due to any other reason not covered by the other failure counters.Packet Call (M1022)

Below is a snapshot of the current distribution per market of the packet call setup failure counters described above.

2.4.2. Cell Analysis2.4.2.1. RRC Setup Phase Failure Causes

The PS RRC Setup Phase Failure Causes are same as Voice. Please refer to section 2.3.3.1 for detail.

2.4.2.2. RRC Access Phase Failure Causes

The PS RRC Access Failure due to Radio Reason, UE or RNC is same as Voice. Please refer to section 2.3.3.2 for detail.2.4.2.3. PS R99 RAB Setup Phase Failure Causes

a) PS R99 RAB Setup Failure Due to Admission ControlSame as RRC admission control (2.3.3.1)b) PS R99 RAB Setup Failure Due to BTS FailureSame as RRC setup failures due to BTS (2.3.3.1)c) PS R99 RAB Setup Failure Due to TransportSame as RRC setup failures due to Transport (2.3.3.1)

d) PS R99 RAB Setup Failure Due to RNCSame as RRC setup failures due to RNC (2.3.3.1)e) PS R99 RAB Setup Failure Due to Frozen BTSSame as RRC setup failures due to Frozen BTS (2.3.3.1)f) PS R99 RAB Setup Failure Due to Anchoring for PS Data Background

This happens when NRT RAB setup requested, but NRT RAB is not allowed during anchoring2.4.2.4. PS R99 RAB Access Phase Failure Causes

a) PS R99 RAB Access Failure Due to UESame as RRC access failures due to MS (2.3.3.2)b) PS R99 RAB Access Failure Due to RNC Internal Failures

Same as RRC setup failures due to RNC (2.3.3.1)2.4.2.5. Packet Call Setup Failure Causesa) Packet Call Setup Failure due to Admission Control (AC)

In case the starting state of the terminal is Cell_FACH (Cell_PCH) or DCH 0/0 and AC rejects the bit rate allocation and the terminal stays at same state. This scenario will trigger this counter. Check RRC admission control section (2.3.3.1- b) for more details on AC failures.b) Packet Call Setup Failure due to BTS

This is mainly caused by CE shortage or no response from BTS. Check RRC admission control section (2.3.3.1-i) for more details on BTS failuresc) Packet Call Setup Failure due to DMPG resource allocation

This is mainly caused by lack of DMCU resources. Check the DSP performance measurements in RNC or report to tier 2 as there might be an issue with the DMCU capacity or the HW in the RNC. If the failures are high then it will require in-depth analysis on the RNC which should be done by Tier 2.d) Packet Call Setup Failure due to Iub transport

These failures are mainly caused by lack of IuB resources (T1). Detailed analysis can be done from AAl2 CAC/ resource reservation counters. If T1 is loaded then see the possibility of activating some additional features or modifying parameters otherwise follow the T-Mobile process to trigger the additional T1.e) Packet Call Setup Failure due to Failures due to UEThis happens when UE doesnt respond to RB reconfiguration message or reports a failure. For more detail please refer to section 3.3.3.2-b.f) Packet Call Setup Failure due to OtherAll other failures i.e. NOT AC, BTS, DMCU, TRANS or UE are counted as OTHER failures. If there are lots of failures due to other reasons then report to tier2 for further investigation.

3. Configuration ManagementConfiguration Management tools and methods should also be used in improving accessibility. Some of these items have been discussed already but these include:

Neighbour List Optimization

Counts (3G-3G)

Removals

Additions

Antenna Changes

Tilts

Azimuths

xConfig should also be used to ensure all parameters are consistent with the FSC Baseline Set unless otherwise agreed for performance reasons.

4. Troubleshooting Tools

The following tools can be used for troubleshooting: Tektronix K-18

This is a protocol analyzer used for analysis of the Iu and Iub links and the layer 1, 2 and 3 messaging. This can be used for further analysis of the call flows More detailed information on this can be found in the Tektronix Documentation

Optimizer The Optimizer is Nokia OSS Tool which provides suggestions on missing neighbour additions and neighbour removals It also can provide geographical PRACH analysis for distance from serving sector at call setup More detail on this tool can be found in NED5. References1. 3GPP TS 25.331 V 5.19.0 UMTS Radio Resource Control Protocol Specification.

2. NED (Nokia Online)3. Alejandro Aguirre, Sireesha Panchagnula Ericsson UTRAN Parameters.4. 3GPP TS 25.304 V 5.9.0 UMTS UE Procedures in Idle Mode and Procedures for Cell Reselection in Connected Mode.

5. UMTS Network KPI, U12 UMTS Network KPI v6.14 080406TMO LR.doc

6. UMTS Network KPI Level 2, UMTS Network KPI Level-2_v1_20070205ERI_Updated.doc

7. UMTS RNC LCS KPI definitions and Formulas, Michael Gebretsadik

8. 3GPP TS 25.331, UMTS RRC protocol specification.

9. 3GPP TS 25.211 V 5.8.0, UMTS Physical channels and mapping of transport channels onto physical channels.

10. 3GPP TS 25.413 V 5.12.0, UTRAN Iu Interface RANAP Signaling.

11. 3GPP TS 25.214, UMTS Physical Layer Procedures FDD.

Copyright 2008 T-Mobile USA, Inc. All rights reserved.Confidential and proprietary information of T-Mobile USA, Inc. Not for distribution outside T-Mobile.T-Mobile USA, INC. ConfidentialRev. 2.2 August 26, 20094 of 38

_1295776537.xlsData

Period start timeMARKETVoice Traffic (Erlang)DL R99 Data Traffic (MB)Voice Access Failure rate (%)Voice Access Failures (RRC+RAB)Conversational RRC Failure Rate (%)Voice RAB Failure Rate (%)Video Access Failure (%)Video Access Failures (RRC+RAB)PS Access Failure Rate (%)PS RAB Access Failure Rate (%)PS Streaming Access Failure Rate (%)PS Streaming RAB Access Failure Rate (%)PS Streaming RAB Access FailuresPS Interactive Access Failure Rate (%)PS interactive Access Failures (RRC+RAB)PS Interactive RAB Failure Rate (%)PS Background Access Failure Rate (%)HSDPA Access Failure Rate (%)RRC Setup CompletionsRRC Setup Completed After DirectedRRC Setup Completed and DirectedRRC Setup Fail due to HCRRC Setup Fail due to ACRRC Setup Fail due to BTSRRC Setup Fail due to TransportRRC Setup Fail due to RNC Internal ReasonRRC Setup Fail due to Frozen BTSRRC Setup Fail due to RNTI Allocaton FailRRC Setup Fail due to IUB AAL2RRC Access CompletionsRRC Access Fail due to Radio Int SynchRRC Access Fail due to UURRC Access Fail due to RNC Internal ReasonRRC Access Release due to Cell ReselectionRadio Beared Setup CompleteRadio Beared Setup FailRadio Bearer Setup Fail due to Unsupported ConfigurationPeriod Duration

11.03.2008Atlanta9,996.353,684.740.571,6410.290.287890.220.08000.170.703,022,2570019193534601003193,000,9235,413732815,1811,193,74181291,403

11.04.2008Atlanta11,083.483,935.700.652,0970.380.271,1420.910.08001.040.793,242,0970068968941,568444719003713,082,0315,6167295153,7161,251,94298271,384

11.05.2008Atlanta10,646.373,412.200.601,7270.320.278700.510.09000.531.473,253,27400383827,922584619004723,125,2695,24172010122,0341,257,16473341,402

Voice Traffic (Erlang)

DL R99 Data Traffic (MB)

Voice Access Failure rate (%)

Voice Access Failures (RRC+RAB)

Conversational RRC Failure Rate (%)

Voice RAB Failure Rate (%)

Video Access Failure (%)

Video Access Failures (RRC+RAB)

PS Access Failure Rate (%)

PS RAB Access Failure Rate (%)

PS Streaming Access Failure Rate (%)

PS Streaming RAB Access Failure Rate (%)

PS Streaming RAB Access Failures

PS Interactive Access Failure Rate (%)

PS interactive Access Failures (RRC+RAB)

PS Interactive RAB Failure Rate (%)

PS Background Access Failure Rate (%)

HSDPA Access Failure Rate (%)

RRC Setup Completions

RRC Setup Completed After Directed

RRC Setup Completed and Directed

RRC Setup Fail due to HC

RRC Setup Fail due to AC

RRC Setup Fail due to BTS

RRC Setup Fail due to Transport

RRC Setup Fail due to RNC Internal Reason

RRC Setup Fail due to Frozen BTS

RRC Setup Fail due to RNTI Allocaton Fail

RRC Setup Fail due to IUB AAL2

RRC Access Completions

RRC Access Fail due to Radio Int Synch

RRC Access Fail due to UU

RRC Access Fail due to RNC Internal Reason

RRC Access Release due to Cell Reselection

Radio Beared Setup Complete

Radio Beared Setup Fail

Radio Bearer Setup Fail due to Unsupported Configuration

Period Duration

Documentation

Report TitleAccessibility

Report IDcustom/Nokia_RAN/reports/Nokia_Ran_Accessibility.xml

Report DescriptionThis report contains KPIs that provides a view of ability to access the network

Start Time11.03.2008 00:00:00

End Time11.06.2008 00:00:00

ObjectsLevel: Market; Atlanta ('Atlanta')

Object Aggregation LevelMarket

Time Aggregation Levelday

Thresholdnone

Sortingnone

Data SourcepmrPool

KPI IDKPI AliasKPI TitleKPI FormulaUnit

Voice_TrafficVoice Traffic (Erlang)Voice Traffic (Erlang)(SERVLEV.avg_rab_hld_tm_cs_voice) / (100 * 60 * 60)Erlangs

DL_R99_Data_TrafficDL R99 Data Traffic (MB)DL R99 Data Traffic (MB)RCPMRLC.RLC_AM_SDU_DL_PS_VOL_R99/(1024*1024)MB

Voice_Access_Failure_rateVoice Access Failure rate (%)Voice Access Failure rate (%)100 *(1 -((DECODE(((SERVLEV.moc_conv_call_atts + SERVLEV.mtc_conv_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV)), 0, NULL, ((SERVLEV.moc_conv_call_atts +SERVLEV.mtc_conv_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV) -(SERVLEV.moc_conv_call_fails +SERVLEV.mtc_conv_call_fails)) / ((SERVLEV.moc_conv_call_atts + SERVLEV.mtc_conv_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV)))*(1 -(DECODE((SERVLEV.rab_stp_att_cs_voice +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA), 0, NULL, (SERVLEV.rab_acc_fail_cs_voice_ms +SERVLEV.rab_acc_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_ac +SERVLEV.rab_stp_fail_cs_voice_bts +SERVLEV.rab_stp_fail_cs_voice_trans +SERVLEV.rab_stp_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_frozbs +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA) / (SERV...%

Voice_Access_Failures_RRC_RABVoice Access Failures (RRC+RAB)Voice Access Failures (RRC+RAB)(SERVLEV.moc_conv_call_fails +SERVLEV.mtc_conv_call_fails) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV) +(SERVLEV.rab_acc_fail_cs_voice_ms +SERVLEV.rab_acc_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_ac +SERVLEV.rab_stp_fail_cs_voice_bts +SERVLEV.rab_stp_fail_cs_voice_trans +SERVLEV.rab_stp_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_frozbs +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA)#

Conversational_RRC_FRConversational RRC Failure Rate (%)Conversational RRC Failure Rate (%)100*DECODE(((SERVLEV.moc_conv_call_atts + SERVLEV.mtc_conv_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV)), 0, NULL, ((SERVLEV.moc_conv_call_fails +SERVLEV.mtc_conv_call_fails) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV)) / ((SERVLEV.moc_conv_call_atts + SERVLEV.mtc_conv_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MT_CONV)))%

Voice_RAB_FRVoice RAB Failure Rate (%)Voice RAB Failure Rate (%)100*(DECODE((SERVLEV.rab_stp_att_cs_voice +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA), 0, NULL, (SERVLEV.rab_acc_fail_cs_voice_ms +SERVLEV.rab_acc_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_ac +SERVLEV.rab_stp_fail_cs_voice_bts +SERVLEV.rab_stp_fail_cs_voice_trans +SERVLEV.rab_stp_fail_cs_voice_rnc +SERVLEV.rab_stp_fail_cs_voice_frozbs +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA) / (SERVLEV.rab_stp_att_cs_voice +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA)))%

Video_Access_FailVideo Access Failure (%)Video Access Failure (%)100*(1 -((DECODE(((SERVLEV.moc_conv_call_atts +SERVLEV.moc_strea_call_atts +SERVLEV.mtc_conv_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV +SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MO_STREAMING +SERVLEV.RRC_ATT_REP_MT_CONV +SERVLEV.RRC_ATT_REP_MT_STREAMING)), 0, NULL, ((SERVLEV.moc_conv_call_atts +SERVLEV.moc_strea_call_atts +SERVLEV.mtc_conv_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV +SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV.moc_conv_call_fails +SERVLEV.moc_strea_call_fails +SERVLEV.mtc_conv_call_fails +SERVLEV.mtc_strea_call_fails)) / ((SERVLEV.moc_conv_call_atts +SERVLEV.moc_strea_call_atts +SERVLEV.mtc_conv_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV +SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV....%

Video_Access_Fail_RRC_RABVideo Access Failures (RRC+RAB)Video Access Failures (RRC+RAB)(SERVLEV.moc_conv_call_fails +SERVLEV.moc_strea_call_fails +SERVLEV.mtc_conv_call_fails +SERVLEV.mtc_strea_call_fails) -(SERVLEV.RRC_ATT_REP_MO_CONV +SERVLEV.RRC_ATT_REP_MO_STREAMING +SERVLEV.RRC_ATT_REP_MT_CONV +SERVLEV.RRC_ATT_REP_MT_STREAMING) +(SERVLEV.rab_stp_fail_cs_conv_ac +SERVLEV.rab_stp_fail_cs_conv_bts +SERVLEV.rab_stp_fail_cs_conv_trans +SERVLEV.rab_stp_fail_cs_conv_rnc +SERVLEV.rab_stp_fail_cs_conv_frozbs +SERVLEV.rab_acc_fail_cs_conv_ms +SERVLEV.rab_acc_fail_cs_conv_rnc +SERVLEV.rab_stp_fail_cs_strea_ac +SERVLEV.rab_stp_fail_cs_strea_bts +SERVLEV.rab_stp_fail_cs_strea_trans +SERVLEV.rab_stp_fail_cs_strea_rnc +SERVLEV.rab_stp_fail_cs_strea_frozbs +SERVLEV.rab_acc_fail_cs_strea_ms +SERVLEV.rab_acc_fail_cs_strea_rnc +SERVLEV.RAB_STP_FAIL_CS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_CS_UE_CAPA)#

PS_Access_FRPS Access Failure Rate (%)PS Access Failure Rate (%)100 *(1 -((DECODE(((SERVLEV.moc_conv_call_atts +SERVLEV.mtc_conv_call_atts + SERVLEV.moc_strea_call_atts +SERVLEV.mtc_strea_call_atts + SERVLEV.moc_inter_call_atts +SERVLEV.mtc_inter_call_atts + SERVLEV.moc_backg_call_atts +SERVLEV.mtc_backg_call_atts) -(SERVLEV.RRC_ACC_REL_MO_CONV +SERVLEV.RRC_ACC_REL_MT_CONV +SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING + SERVLEV.RRC_ACC_REL_MO_INTERACTIVE +SERVLEV.RRC_ACC_REL_INTERACTIVE + SERVLEV.RRC_ACC_REL_MO_BACKGROUND + SERVLEV.RRC_ACC_REL_MT_BACKGROUND) -(SERVLEV.RRC_ATT_REP_MO_CONV + SERVLEV.RRC_ATT_REP_MT_CONV + SERVLEV.RRC_ATT_REP_MO_STREAMING + SERVLEV.RRC_ATT_REP_MT_STREAMING + SERVLEV.RRC_ATT_REP_MO_INTERACTIVE + SERVLEV.RRC_ATT_REP_INTERACTIVE + SERVLEV.RRC_ATT_REP_MO_BACKGROUND + SERVLEV.RRC_ATT_REP_MT_BACKGROUND)), 0, NULL, ((SERVLEV.moc_conv_call_atts +SERVLEV.mtc_conv_call_atts + SERVLEV.moc_strea_call_atts +SERVLEV.mtc_strea_call_atts + SERVLEV.moc_inter_call_atts +SERVLEV.mtc_inter_call_atts + SERVLEV.moc_backg_call_atts +SERVLEV...%

PS_RAB_Access_FRPS RAB Access Failure Rate (%)PS RAB Access Failure Rate (%)100*(DECODE((SERVLEV.rab_stp_att_ps_conv +SERVLEV.RAB_STP_ATT_PS_STREA +SERVLEV.rab_stp_att_ps_inter +SERVLEV.RAB_STP_ATT_PS_BACKG +SERVLEV.RAB_STP_FAIL_PS_NOT_SUPP_PAR +SERVLEV.RAB_STP_FAIL_PS_UE_CAPA), 0, NULL, (SERVLEV.rab_stp_fail_ps_conv_ac +SERVLEV.rab_stp_fail_ps_conv_bts +SERVLEV.rab_stp_fail_ps_conv_trans +SERVLEV.rab_stp_fail_ps_conv_rnc +SERVLEV.rab_stp_fail_ps_conv_frozbs +SERVLEV.rab_acc_fail_ps_conv_ms +SERVLEV.rab_acc_fail_ps_conv_rnc +SERVLEV.rab_stp_fail_ps_strea_ac +SERVLEV.rab_stp_fail_ps_strea_bts +SERVLEV.rab_stp_fail_ps_strea_trans +SERVLEV.rab_stp_fail_ps_strea_rnc +SERVLEV.rab_stp_fail_ps_strea_frozbs +SERVLEV.rab_acc_fail_ps_strea_ms +SERVLEV.rab_acc_fail_ps_strea_rnc +SERVLEV.rab_stp_fail_ps_inter_ac +SERVLEV.rab_stp_fail_ps_inter_rnc +SERVLEV.rab_stp_fail_ps_inter_anch +SERVLEV.rab_stp_fail_ps_inter_frozbs +SERVLEV.rab_acc_fail_ps_inter_ms +SERVLEV.rab_acc_fail_ps_inter_rnc +SERVLEV.rab_stp_fail_ps_backg_ac +SERVLEV.rab_stp_fail_ps_backg_rnc +SERVLEV.rab_stp_fail_ps_backg_anch +S...%

PS_Streaming_Access_FRPS Streaming Access Failure Rate (%)PS Streaming Access Failure Rate (%)100*(1 -((DECODE(((SERVLEV.moc_strea_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV.mtc_low_prior_sign_fails +SERVLEV.RRC_ATT_REP_MT_STREAMING)), 0, NULL, ((SERVLEV.moc_strea_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV.moc_strea_call_fails +SERVLEV.mtc_strea_call_fails)) / ((SERVLEV.moc_strea_call_atts +SERVLEV.mtc_strea_call_atts) -(SERVLEV.RRC_ACC_REL_MO_STREAMING +SERVLEV.RRC_ACC_REL_MT_STREAMING) -(SERVLEV.mtc_low_prior_sign_fails +SERVLEV.RRC_ATT_REP_MT_STREAMING))))*(1 -(DECODE(SERVLEV.RAB_STP_ATT_PS_STREA, 0, NULL, (SERVLEV.rab_stp_fail_ps_strea_ac +SERVLEV.rab_stp_fail_ps_strea_bts +SERVLEV.rab_stp_fail_ps_strea_trans +SERVLEV.rab_stp_fail_ps_strea_rnc +SERVLEV.rab_stp_fail_ps_strea_frozbs + SERVLEV.rab_acc_fail_ps_strea_ms +SERVLEV.rab_acc_fail_ps_strea_rnc) / SERVLEV.RAB_STP_ATT_PS_STREA)))))%

PS_Streaming_RAB_Access_FRPS Streaming RAB Access Failure Rate (%)PS Streaming RAB Access Failure Rate (%)100*(DECODE(SERVLEV.RAB_STP_ATT_PS_STREA, 0, NULL, (SERVLEV.rab_stp_fail_ps_strea_ac +SERVLEV.rab_stp_fail_ps_strea_bts +SERVLEV.rab_stp_fail_ps_strea_trans +SERVLEV.rab_stp_fail_ps_strea_rnc +SERVLEV.rab_stp_fail_ps_strea_frozbs + SERVLEV.rab_acc_fail_ps_strea_ms +SERVLEV.rab_acc_fail_ps_strea_rnc) / SERVLEV.RAB_STP_ATT_PS_STREA))%

PS_Streaming_RAB_Access_FailPS Streaming RAB Access FailuresPS Streaming RAB Access Failures(SERVLEV.rab_stp_fail_ps_strea_ac +SERVLEV.rab_stp_fail_ps_strea_bts +SERVLEV.rab_stp_fail_ps_strea_trans +SERVLEV.rab_stp_fail_ps_strea_rnc +SERVLEV.rab_stp_fail_ps_strea_frozbs +SERVLEV.rab_acc_fail_ps_strea_ms +SERVLEV.rab_acc_fail_ps_strea_rnc)#

PS_Interactive_Access_FRPS Interactive Access Failure Rate (%)PS Interactive Access Failure Rate (%)100*(1 -((DECODE(((SERVLEV.moc_inter_call_atts +SERVLEV.mtc_inter_call_atts) -(SERVLEV.RRC_ACC_REL_MO_INTERACTIVE +SERVLEV.RRC_ACC_REL_INTERACTIVE) -(SERVLEV.RRC_ATT_REP_MO_INTERACTIVE +SERVLEV.RRC_ATT_REP_INTERACTIVE)), 0, NULL, ((SERVLEV.moc_inter_call_atts +SERVLEV.mtc_inter_call_atts) -(SERVLEV.RRC_ACC_REL_MO_INTERACTIVE +SERVLEV.RRC_ACC_REL_INTERACTIVE) -(SERVLEV.moc_inter_call_fails +SERVLEV.mtc_inter_call_fails)) / ((SERVLEV.moc_inter_call_atts +SERVLEV.mtc_inter_call_atts) -(SERVLEV.RRC_ACC_REL_MO_INTERACTIVE +SERVLEV.RRC_ACC_REL_INTERACTIVE) -(SERVLEV.RRC_ATT_REP_MO_INTERACTIVE +SERVLEV.RRC_ATT_REP_INTERACTIVE))))*(1 -(DECODE(SERVLEV.rab_stp_att_ps_inter, 0, NULL, (SERVLEV.rab_stp_fail_ps_inter_ac +SERVLEV.rab_stp_fail_ps_inter_rnc +SERVLEV.rab_stp_fail_ps_inter_anch +SERVLEV.rab_stp_fail_ps_inter_frozbs +SERVLEV.rab_acc_fail_ps_inter_ms +SERVLEV.rab_acc_fail_ps_inter_rnc) / SERVLEV.rab_stp_att_ps_inter)))))%

PS_InterA_Access_Fail_RRC_RABPS interactive Access Failures (RRC+RAB)PS interactive Access Failures (RRC+RAB)(SERVLEV.moc_inter_call_fails +SERVLEV.mtc_inter_call_fails) -(SERVLEV.RRC_ATT_REP_MO_INTERACTIVE +SERVLEV.RRC_ATT_REP_INTERACTIVE) +(SERVLEV.rab_stp_fail_ps_inter_ac +SERVLEV.rab_stp_fail_ps_inter_rnc +SERVLEV.rab_stp_fail_ps_inter_anch +SERVLEV.rab_stp_fail_ps_inter_frozbs +SERVLEV.rab_acc_fail_ps_inter_ms +SERVLEV.rab_acc_fail_ps_inter_rnc)#

PS_Interactive_RAB_FRPS Interactive RAB Failure Rate (%)PS Interactive RAB Failure Rate (%)100*(DECODE(SERVLEV.rab_stp_att_ps_inter, 0, NULL, (SERVLEV.rab_stp_fail_ps_inter_ac +SERVLEV.rab_stp_fail_ps_inter_rnc +SERVLEV.rab_stp_fail_ps_inter_anch +SERVLEV.rab_stp_fail_ps_inter_frozbs +SERVLEV.rab_acc_fail_ps_inter_ms +SERVLEV.rab_acc_fail_ps_inter_rnc) / SERVLEV.rab_stp_att_ps_inter))%

PS_Background_Access_FRPS Background Access Failure Rate (%)PS Background Access Failure Rate (%)100*(1 -((DECODE(((SERVLEV.moc_backg_call_atts +SERVLEV.mtc_backg_call_atts) -(SERVLEV.RRC_ACC_REL_MO_BACKGROUND +SERVLEV.RRC_ACC_REL_MT_BACKGROUND) -(SERVLEV.RRC_ATT_REP_MO_BACKGROUND +SERVLEV.RRC_ATT_REP_MT_BACKGROUND)), 0, NULL, ((SERVLEV.moc_backg_call_atts +SERVLEV.mtc_backg_call_atts) -(SERVLEV.RRC_ACC_REL_MO_BACKGROUND +SERVLEV.RRC_ACC_REL_MT_BACKGROUND) -(SERVLEV.moc_backg_call_fails +SERVLEV.mtc_backg_call_fails)) / ((SERVLEV.moc_backg_call_atts +SERVLEV.mtc_backg_call_atts) -(SERVLEV.RRC_ACC_REL_MO_BACKGROUND +SERVLEV.RRC_ACC_REL_MT_BACKGROUND) -(SERVLEV.RRC_ATT_REP_MO_BACKGROUND +SERVLEV.RRC_ATT_REP_MT_BACKGROUND))))*(1 -(DECODE(SERVLEV.RAB_STP_ATT_PS_BACKG, 0, NULL, (SERVLEV.rab_stp_fail_ps_backg_ac +SERVLEV.rab_stp_fail_ps_backg_rnc +SERVLEV.rab_stp_fail_ps_backg_anch +SERVLEV.rab_stp_fail_ps_backg_frozbs +SERVLEV.rab_acc_fail_ps_backg_ms +SERVLEV.rab_acc_fail_ps_backg_rnc) / SERVLEV.RAB_STP_ATT_PS_BACKG)))))%

HSDPA_Access_FRHSDPA Access Failure Rate (%)HSDPA Access Failure Rate (%)100*(1 -(DECODE((TRAFFIC.ALLO_HS_DSCH_FLOW_INT +TRAFFIC.ALLO_HS_DSCH_FLOW_BGR +TRAFFIC.REJ_HS_DSCH_RET_INT +TRAFFIC.REJ_HS_DSCH_RET_BGR +TRAFFIC.SETUP_FAIL_RNC_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_IUB_MAC_D_INT +TRAFFIC.SETUP_FAIL_UE_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_BTS_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_64_IUB_HSDSCH_INT +TRAFFIC.SETUP_FAIL_128_IUB_HSDSCH_IN +TRAFFIC.SETUP_FAIL_384_IUB_HSDSCH_IN +TRAFFIC.SETUP_FAIL_RNC_HS_DSCH_BGR +TRAFFIC.SETUP_FAIL_IUB_MAC_D_BGR +TRAFFIC.SETUP_FAIL_UE_HS_DSCH_BGR +TRAFFIC.SETUP_FAIL_BTS_HS_DSCH_BGR +TRAFFIC.SETUP_FAIL_64_IUB_HSDSCH_BGR +TRAFFIC.SETUP_FAIL_128_IUB_HSDSCH_BG +TRAFFIC.SETUP_FAIL_384_IUB_HSDSCH_BG), 0, NULL, (TRAFFIC.ALLO_HS_DSCH_FLOW_INT +TRAFFIC.ALLO_HS_DSCH_FLOW_BGR) / (TRAFFIC.ALLO_HS_DSCH_FLOW_INT +TRAFFIC.ALLO_HS_DSCH_FLOW_BGR +TRAFFIC.REJ_HS_DSCH_RET_INT +TRAFFIC.REJ_HS_DSCH_RET_BGR +TRAFFIC.SETUP_FAIL_RNC_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_IUB_MAC_D_INT +TRAFFIC.SETUP_FAIL_UE_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_BTS_HS_DSCH_INT +TRAFFIC.SETUP_FAIL_64_IUB_HSDSCH_INT ...%

RRC_Setup_CompletionsRRC Setup CompletionsRRC Setup CompletionsSERVLEV.rrc_conn_stp_comp#

RRC_Setup_Comp_After_DirectedRRC Setup Completed After DirectedRRC Setup Completed After DirectedSERVLEV.RRC_CONN_SETUP_COMP_AFT_DIR#

RRC_Setup_Comp_and_DirectedRRC Setup Completed and DirectedRRC Setup Completed and DirectedSERVLEV.RRC_CON_SETUP_COMP_DIRECTED#

RRC_Setup_Fail_due_to_HCRRC Setup Fail due to HCRRC Setup Fail due to HCSERVLEV.rrc_conn_stp_fail_ac#

RRC_Setup_Fail_due_to_ACRRC Setup Fail due to ACRRC Setup Fail due to ACSERVLEV.rrc_conn_stp_fail_ac#

RRC_Setup_Fail_due_to_BTSRRC Setup Fail due to BTSRRC Setup Fail due to BTSSERVLEV.rrc_conn_stp_fail_bts#

RRC_Setup_Fail_due_TransportRRC Setup Fail due to TransportRRC Setup Fail due to TransportSERVLEV.rrc_conn_stp_fail_trans#

RRC_Setup_Fail_RNC_InternalRRC Setup Fail due to RNC Internal ReasonRRC Setup Fail due to RNC Internal ReasonSERVLEV.rrc_conn_stp_fail_rnc#

RRC_Setup_Fail_Frozen_BTSRRC Setup Fail due to Frozen BTSRRC Setup Fail due to Frozen BTSSERVLEV.rrc_conn_stp_fail_frozbs#

RRC_Setup_Fail_RNTI_Alloc_FailRRC Setup Fail due to RNTI Allocaton FailRRC Setup Fail due to RNTI Allocaton FailSERVLEV.RRC_CONN_STP_FAIL_RNTI_ALLO#

RRC_Setup_Fail_due_to_IUB_AAL2RRC Setup Fail due to IUB AAL2RRC Setup Fail due to IUB AAL2SERVLEV.RRC_CONN_STP_FAIL_IUB_AAL2#

RRC_Access_CompletionsRRC Access CompletionsRRC Access CompletionsSERVLEV.rrc_conn_acc_comp#

RRC_Access_Fail_Radio_Int_SyncRRC Access Fail due to Radio Int SynchRRC Access Fail due to Radio Int SynchSERVLEV.rrc_conn_acc_fail_radio#

RRC_Access_Fail_due_to_UURRC Access Fail due to UURRC Access Fail due to UUSERVLEV.rrc_conn_acc_fail_ms#

RRC_Access_Fail_RNC_Int_ReasonRRC Access Fail due to RNC Internal ReasonRRC Access Fail due to RNC Internal ReasonSERVLEV.rrc_conn_acc_fail_rnc#

RRC_Access_Release_CellReselecRRC Access Release due to Cell ReselectionRRC Access Release due to Cell ReselectionSERVLEV.RRC_CONN_ACC_REL_CELL_RESEL#

Radio_Beared_Setup_CompleteRadio Beared Setup CompleteRadio Beared Setup CompleteRRC.rb_setup_complete#

Radio_Beared_Setup_FailRadio Beared Setup FailRadio Beared Setup FailRRC.RB_SETUP_FAIL#

Rad_Bear_Setup_F_Unsup_ConfigRadio Bearer Setup Fail due to Unsupported ConfigurationRadio Bearer Setup Fail due to Unsupported ConfigurationRRC.RB_SETUP_FAIL_UNS_CONF#

Period_DurationPeriod Durationperiod_durationSERVLEV.period_duration_timemin

Level: MarketAtlanta ('Atlanta')

sum(AVG_RAB_HLD_TM_CS_VOICE)/(100 * 60 * 60)

RLC_AM_SDU_DL_PS_VOL/(1024*1024)

100 *(1-((((MOC_CONV_CALL_ATTS+MTC_CONV_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV)-(MOC_CONV_CALL_FAILS+MTC_CONV_CALL_FAILS))/((MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MT_CONV))*(1-((RAB_ACC_FAIL_CS_VOICE_MS+RAB_ACC_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_AC+RAB_STP_FAIL_CS_VOICE_BTS+RAB_STP_FAIL_CS_VOICE_TRANS+RAB_STP_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_FROZBS+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)/(RAB_STP_ATT_CS_VOICE+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA))))))

(MOC_CONV_CALL_FAILS+MTC_CONV_CALL_FAILS)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MT_CONV)+(RAB_ACC_FAIL_CS_VOICE_MS+RAB_ACC_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_AC+RAB_STP_FAIL_CS_VOICE_BTS+RAB_STP_FAIL_CS_VOICE_TRANS+RAB_STP_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_FROZBS+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)

100*((MOC_CONV_CALL_FAILS+MTC_CONV_CALL_FAILS)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MT_CONV))/((MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MT_CONV))

100*((RAB_ACC_FAIL_CS_VOICE_MS+RAB_ACC_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_AC+RAB_STP_FAIL_CS_VOICE_BTS+RAB_STP_FAIL_CS_VOICE_TRANS+RAB_STP_FAIL_CS_VOICE_RNC+RAB_STP_FAIL_CS_VOICE_FROZBS+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)/(RAB_STP_ATT_CS_VOICE+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA))

100*(1-((((MOC_CONV_CALL_ATTS+MOC_STREA_CALL_ATTS+MTC_CONV_CALL_ATTS+MTC_STREA_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV+RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING)-(MOC_CONV_CALL_FAILS+MOC_STREA_CALL_FAILS+MTC_CONV_CALL_FAILS+MTC_STREA_CALL_FAILS))/((MOC_CONV_CALL_ATTS+MOC_STREA_CALL_ATTS+MTC_CONV_CALL_ATTS+MTC_STREA_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV+RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MO_STREAMING+RRC_ATT_REP_MT_CONV+RRC_ATT_REP_MT_STREAMING)))*(1-((RAB_STP_FAIL_CS_CONV_AC+RAB_STP_FAIL_CS_CONV_BTS+RAB_STP_FAIL_CS_CONV_TRANS+RAB_STP_FAIL_CS_CONV_RNC+RAB_STP_FAIL_CS_CONV_FROZBS+RAB_ACC_FAIL_CS_CONV_MS+RAB_ACC_FAIL_CS_CONV_RNC+RAB_STP_FAIL_CS_STREA_AC+RAB_STP_FAIL_CS_STREA_BTS+RAB_STP_FAIL_CS_STREA_TRANS+RAB_STP_FAIL_CS_STREA_RNC+RAB_STP_FAIL_CS_STREA_FROZBS+RAB_ACC_FAIL_CS_STREA_MS+RAB_ACC_FAIL_CS_STREA_RNC+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)/(RAB_STP_ATT_CS_CONV+RAB_STP_ATT_CS_STREA+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)))))

(MOC_CONV_CALL_FAILS+MOC_STREA_CALL_FAILS+MTC_CONV_CALL_FAILS+MTC_STREA_CALL_FAILS)-(RRC_ATT_REP_MO_CONV+RRC_ATT_REP_MO_STREAMING+RRC_ATT_REP_MT_CONV+RRC_ATT_REP_MT_STREAMING)+(RAB_STP_FAIL_CS_CONV_AC+RAB_STP_FAIL_CS_CONV_BTS+RAB_STP_FAIL_CS_CONV_TRANS+RAB_STP_FAIL_CS_CONV_RNC+RAB_STP_FAIL_CS_CONV_FROZBS+RAB_ACC_FAIL_CS_CONV_MS+RAB_ACC_FAIL_CS_CONV_RNC+RAB_STP_FAIL_CS_STREA_AC+RAB_STP_FAIL_CS_STREA_BTS+RAB_STP_FAIL_CS_STREA_TRANS+RAB_STP_FAIL_CS_STREA_RNC+RAB_STP_FAIL_CS_STREA_FROZBS+RAB_ACC_FAIL_CS_STREA_MS+RAB_ACC_FAIL_CS_STREA_RNC+RAB_STP_FAIL_CS_NOT_SUPP_PAR+RAB_STP_FAIL_CS_UE_CAPA)

100 *(1-((((MOC_CONV_CALL_ATTS+MTC_CONV_CALL_ATTS + MOC_STREA_CALL_ATTS+MTC_STREA_CALL_ATTS + MOC_INTER_CALL_ATTS+MTC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS+MTC_BACKG_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV+RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING + RRC_ACC_REL_MO_INTERACTIVE+RRC_ACC_REL_INTERACTIVE + RRC_ACC_REL_MO_BACKGROUND + RRC_ACC_REL_MT_BACKGROUND)-(MOC_CONV_CALL_FAILS+MTC_CONV_CALL_FAILS + MOC_STREA_CALL_FAILS+ MTC_STREA_CALL_FAILS + MOC_INTER_CALL_FAILS+MTC_INTER_CALL_FAILS + MOC_BACKG_CALL_FAILS+ MTC_BACKG_CALL_FAILS))/((MOC_CONV_CALL_ATTS+MTC_CONV_CALL_ATTS + MOC_STREA_CALL_ATTS+MTC_STREA_CALL_ATTS + MOC_INTER_CALL_ATTS+MTC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS+MTC_BACKG_CALL_ATTS)-(RRC_ACC_REL_MO_CONV+RRC_ACC_REL_MT_CONV+RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING + RRC_ACC_REL_MO_INTERACTIVE+RRC_ACC_REL_INTERACTIVE + RRC_ACC_REL_MO_BACKGROUND + RRC_ACC_REL_MT_BACKGROUND)-(RRC_ATT_REP_MO_CONV + RRC_ATT_REP_MT_CONV + RRC_ATT_REP_MO_STREAMING + RRC_ATT_REP_MT_STREAMING + RRC_ATT_REP_MO_INTERACTIVE + RRC_ATT_REP_INTERACTIVE + RRC_ATT_REP_MO_BACKGROUND + RRC_ATT_REP_MT_BACKGROUND)))*(1-((RAB_STP_FAIL_PS_CONV_AC+RAB_STP_FAIL_PS_CONV_BTS+RAB_STP_FAIL_PS_CONV_TRANS+RAB_STP_FAIL_PS_CONV_RNC+RAB_STP_FAIL_PS_CONV_FROZBS+RAB_ACC_FAIL_PS_CONV_MS+RAB_ACC_FAIL_PS_CONV_RNC+RAB_STP_FAIL_PS_STREA_AC+RAB_STP_FAIL_PS_STREA_BTS+RAB_STP_FAIL_PS_STREA_TRANS+RAB_STP_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_STREA_FROZBS+RAB_ACC_FAIL_PS_STREA_MS+RAB_ACC_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_INTER_AC+RAB_STP_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_INTER_ANCH+RAB_STP_FAIL_PS_INTER_FROZBS+RAB_ACC_FAIL_PS_INTER_MS+RAB_ACC_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_BACKG_AC+RAB_STP_FAIL_PS_BACKG_RNC+RAB_STP_FAIL_PS_BACKG_ANCH+RAB_STP_FAIL_PS_BACKG_FROZBS+RAB_ACC_FAIL_PS_BACKG_MS+RAB_ACC_FAIL_PS_BACKG_RNC+RAB_STP_FAIL_PS_NOT_SUPP_PAR+RAB_STP_FAIL_PS_UE_CAPA)/(RAB_STP_ATT_PS_CONV+RAB_STP_ATT_PS_STREA+RAB_STP_ATT_PS_INTER+RAB_STP_ATT_PS_BACKG+RAB_STP_FAIL_PS_NOT_SUPP_PAR+RAB_STP_FAIL_PS_UE_CAPA)))))

100*((RAB_STP_FAIL_PS_CONV_AC+RAB_STP_FAIL_PS_CONV_BTS+RAB_STP_FAIL_PS_CONV_TRANS+RAB_STP_FAIL_PS_CONV_RNC+RAB_STP_FAIL_PS_CONV_FROZBS+RAB_ACC_FAIL_PS_CONV_MS+RAB_ACC_FAIL_PS_CONV_RNC+RAB_STP_FAIL_PS_STREA_AC+RAB_STP_FAIL_PS_STREA_BTS+RAB_STP_FAIL_PS_STREA_TRANS+RAB_STP_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_STREA_FROZBS+RAB_ACC_FAIL_PS_STREA_MS+RAB_ACC_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_INTER_AC+RAB_STP_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_INTER_ANCH+RAB_STP_FAIL_PS_INTER_FROZBS+RAB_ACC_FAIL_PS_INTER_MS+RAB_ACC_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_BACKG_AC+RAB_STP_FAIL_PS_BACKG_RNC+RAB_STP_FAIL_PS_BACKG_ANCH+RAB_STP_FAIL_PS_BACKG_FROZBS+RAB_ACC_FAIL_PS_BACKG_MS+RAB_ACC_FAIL_PS_BACKG_RNC+RAB_STP_FAIL_PS_NOT_SUPP_PAR+RAB_STP_FAIL_PS_UE_CAPA)/(RAB_STP_ATT_PS_CONV+RAB_STP_ATT_PS_STREA+RAB_STP_ATT_PS_INTER+RAB_STP_ATT_PS_BACKG+RAB_STP_FAIL_PS_NOT_SUPP_PAR+RAB_STP_FAIL_PS_UE_CAPA))

100*(1-((((MOC_STREA_CALL_ATTS+MTC_STREA_CALL_ATTS)-(RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING)-(MOC_STREA_CALL_FAILS+MTC_STREA_CALL_FAILS))/((MOC_STREA_CALL_ATTS+MTC_STREA_CALL_ATTS)-(RRC_ACC_REL_MO_STREAMING+RRC_ACC_REL_MT_STREAMING)-(MTC_LOW_PRIOR_SIGN_FAILS+RRC_ATT_REP_MT_STREAMING)))*(1-((RAB_STP_FAIL_PS_STREA_AC+RAB_STP_FAIL_PS_STREA_BTS+RAB_STP_FAIL_PS_STREA_TRANS+RAB_STP_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_STREA_FROZBS+ RAB_ACC_FAIL_PS_STREA_MS+RAB_ACC_FAIL_PS_STREA_RNC)/RAB_STP_ATT_PS_STREA))))

100*((RAB_STP_FAIL_PS_STREA_AC+RAB_STP_FAIL_PS_STREA_BTS+RAB_STP_FAIL_PS_STREA_TRANS+RAB_STP_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_STREA_FROZBS+ RAB_ACC_FAIL_PS_STREA_MS+RAB_ACC_FAIL_PS_STREA_RNC)/RAB_STP_ATT_PS_STREA)

(RAB_STP_FAIL_PS_STREA_AC+RAB_STP_FAIL_PS_STREA_BTS+RAB_STP_FAIL_PS_STREA_TRANS+RAB_STP_FAIL_PS_STREA_RNC+RAB_STP_FAIL_PS_STREA_FROZBS+RAB_ACC_FAIL_PS_STREA_MS+RAB_ACC_FAIL_PS_STREA_RNC)

100*(1-((((MOC_INTER_CALL_ATTS+MTC_INTER_CALL_ATTS)-(RRC_ACC_REL_MO_INTERACTIVE+RRC_ACC_REL_INTERACTIVE)-(MOC_INTER_CALL_FAILS+MTC_INTER_CALL_FAILS))/((MOC_INTER_CALL_ATTS+MTC_INTER_CALL_ATTS)-(RRC_ACC_REL_MO_INTERACTIVE+RRC_ACC_REL_INTERACTIVE)-(RRC_ATT_REP_MO_INTERACTIVE+RRC_ATT_REP_INTERACTIVE)))*(1-((RAB_STP_FAIL_PS_INTER_AC+RAB_STP_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_INTER_ANCH+RAB_STP_FAIL_PS_INTER_FROZBS+RAB_ACC_FAIL_PS_INTER_MS+RAB_ACC_FAIL_PS_INTER_RNC)/RAB_STP_ATT_PS_INTER))))

(MOC_INTER_CALL_FAILS+MTC_INTER_CALL_FAILS)-(RRC_ATT_REP_MO_INTERACTIVE+RRC_ATT_REP_INTERACTIVE)+(RAB_STP_FAIL_PS_INTER_AC+RAB_STP_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_INTER_ANCH+RAB_STP_FAIL_PS_INTER_FROZBS+RAB_ACC_FAIL_PS_INTER_MS+RAB_ACC_FAIL_PS_INTER_RNC)

100*((RAB_STP_FAIL_PS_INTER_AC+RAB_STP_FAIL_PS_INTER_RNC+RAB_STP_FAIL_PS_INTER_ANCH+RAB_STP_FAIL_PS_INTER_FROZBS+RAB_ACC_FAIL_PS_INTER_MS+RAB_ACC_FAIL_PS_INTER_RNC)/RAB_STP_ATT_PS_INTER)

100*(1-((((MOC_BACKG_CALL_ATTS+MTC_BACKG_CALL_ATTS)-(RRC_ACC_REL_MO_BACKGROUND+RRC_ACC_REL_MT_BACKGROUND)-(MOC_BACKG_CALL_FAILS+MTC_BACKG_CALL_FAILS))/((MOC_BACKG_CALL_ATTS+MTC_BACKG_CALL_ATTS)-(RRC_ACC_REL_MO_BACKGROUND+RRC_ACC_REL_MT_BACKGROUND)-(RRC_ATT_REP_MO_BACKGROUND+RRC_ATT_REP_MT_BACKGROUND)))*(1-((RAB_STP_FAIL_PS_BACKG_AC+RAB_STP_FAIL_PS_BACKG_RNC+RAB_STP_FAIL_PS_BACKG_ANCH+RAB_STP_FAIL_PS_BACKG_FROZBS+RAB_ACC_FAIL_PS_BACKG_MS+RAB_ACC_FAIL_PS_BACKG_RNC)/RAB_STP_ATT_PS_BACKG))))

100*(1-((ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FLOW_BGR)/(ALLO_HS_DSCH_FLOW_INT+ALLO_HS_DSCH_FLOW_BGR+REJ_HS_DSCH_RET_INT+REJ_HS_DSCH_RET_BGR+SETUP_FAIL_RNC_HS_DSCH_INT+SETUP_FAIL_IUB_MAC_D_INT+SETUP_FAIL_UE_HS_DSCH_INT+SETUP_FAIL_BTS_HS_DSCH_INT+SETUP_FAIL_64_IUB_HSDSCH_INT+SETUP_FAIL_128_IUB_HSDSCH_IN+SETUP_FAIL_384_IUB_HSDSCH_IN+SETUP_FAIL_RNC_HS_DSCH_BGR+SETUP_FAIL_IUB_MAC_D_BGR+SETUP_FAIL_UE_HS_DSCH_BGR+SETUP_FAIL_BTS_HS_DSCH_BGR+SETUP_FAIL_64_IUB_HSDSCH_BGR+SETUP_FAIL_128_IUB_HSDSCH_BG+SETUP_FAIL_384_IUB_HSDSCH_BG)))

RRC_CONN_STP_COMP

RRC_CONN_SETUP_COMP_AFT_DIR

RRC_CON_SETUP_COMP_DIRECTED

RRC_CONN_STP_FAIL_AC

RRC_CONN_STP_FAIL_AC

RRC_CONN_STP_FAIL_BTS

RRC_CONN_STP_FAIL_TRANS

RRC_CONN_STP_FAIL_RNC

RRC_CONN_STP_FAIL_FROZBS

RRC_CONN_STP_FAIL_RNTI_ALLO

RRC_CONN_STP_FAIL_IUB_AAL2

RRC_CONN_ACC_COMP

RRC_CONN_ACC_FAIL_RADIO

RRC_CONN_ACC_FAIL_MS

RRC_CONN_ACC_FAIL_RNC

RRC_CONN_ACC_REL_CELL_RESEL

RB_SETUP_COMPLETE

RB_SETUP_FAIL

RB_SETUP_FAIL_UNS_CONF

AVG(period_duration)

Voice_Traffic

DL_R99_Data_Traffic

Voice_Access_Failure_rate

Voice_Access_Failures_RRC_RAB

Conversational_RRC_FR

Voice_RAB_FR

Video_Access_Fail

Video_Access_Fail_RRC_RAB

PS_Access_FR

PS_RAB_Access_FR

PS_Streaming_Access_FR

PS_Streaming_RAB_Access_FR

PS_Streaming_RAB_Access_Fail

PS_Interactive_Access_FR

PS_InterA_Access_Fail_RRC_RAB

PS_Interactive_RAB_FR

PS_Background_Access_FR

HSDPA_Access_FR

RRC_Setup_Completions

RRC_Setup_Comp_After_Directed

RRC_Setup_Comp_and_Directed

RRC_Setup_Fail_due_to_HC

RRC_Setup_Fail_due_to_AC

RRC_Setup_Fail_due_to_BTS

RRC_Setup_Fail_due_Transport

RRC_Setup_Fail_RNC_Internal

RRC_Setup_Fail_Frozen_BTS

RRC_Setup_Fail_RNTI_Alloc_Fail

RRC_Setup_Fail_due_to_IUB_AAL2

RRC_Access_Completions

RRC_Access_Fail_Radio_Int_Sync

RRC_Access_Fail_due_to_UU

RRC_Access_Fail_RNC_Int_Reason

RRC_Access_Release_CellReselec

Radio_Beared_Setup_Complete

Radio_Beared_Setup_Fail

Rad_Bear_Setup_F_Unsup_Config

Period_Duration

_1296548443.ppt

Voice Access Failure

PS Access Failure

Conversational RRC Failure

Voice RAB Failure

PS RRC Failure

PS RAB Failure

RRC Setup or RRC Access?

PS RAB Setup or RAB Access?

RRC or RAB?

RRC , RAB or RAB 0/0 Reconfiguration?

RRC Setup Failure

RRC Access Failure

Voice RAB Setup Failure

Voice RAB Access Failure

PS RAB Setup Failure

PS RAB Access Failure

Voice RAB Setup or RAB Access?

Failure / Handover Control

Failure / Admission Control

Failure / Transport

Failure / RNC

Failure / Frozen BTS

Failure / RHTI Allocation

Failure / Iub AAL2

Failure / ICSU Overload

Failure / BTS

Failure / MS

Failure Cause Analysis

Identify the problem is RNC wide or cluster level. Report to Tier2 for further analysis.

check the available resources during the RRC setup stage: DL Codes, UL Load (Prx total), DL load (Downlink Tx power)

T1 issues, if the failure due to Iub AAL2 doesnt increase.

Iub Congestion. Before add more T1, check SHO overhead. Detail analysis can be done from AAL2 CAC resource counters

This is related to congestion & should be analyzed as failure due to Admission Control

This counter point out resource issues in the RRMU. Investigate RNC dimensioning

Most happens in RNC wide or multiple sites connected to ICSU. Check List of Generic Faults LGF-RNC-2008-07 Radio Controllers WCDMA RNC RN2.2, RN3.0 on NED

Potentially a hardware, configuration or resource issue in the NodeB check CE usage, Num of user in compress mode.

Failure / Radio

Reports to Tier2 for deep analysis.Check common parts if problem happens on particular sites.

Coverage issue if only few sites has problem. UE problem if problem happens in RNC wide. Also check the UL noise level.

RF related issue. Bad coverage or Interference (UL or DL).

PS Trouble Shoot Path

Voice Trouble Shooting Path

Common Path

Packet Allocation Failure

Page 2

NSN Accessibility Troubleshooting Flowchart

Packet Allocation Failure

NSN Accessibility Troubleshooting Flowchart

Failure / Admission Control

Failure / Transport

Failure / BTS

Failure / UE

Packet Call Setup Failures

Check the availability of resources the such as DL Codes, UL Load (Prx total), DL load (Downlink Tx power)

Mainly caused by lack of IuB resources (T1). Detailed analysis can be done from AAl2 CAC/ resource reservation counters.

Potentially a hardware, configuration or resource issue in the NodeB check CE usage at the capacity report, number of user in compress mode.

Failure / Other

Coverage issue if only few sites has problem. UE problem if problem happens in RNC wide. Also check the UL noise level.

All other failures i.e. not AC, BTS, DMCU, TRANS or UE are counted as OTHER failures. Could be RF related, check bad coverage or Interference (UL or DL).

Failure / DMCU

Mainly caused by lack of DMCU resources. Check the DSP performance measurements in RNC. Very high pegging should be reported to tier 2 as there might be an issue with the DMCU HW.

*