3G Counters Troubleshooting Guideline

1 (81) Prepared (also subject responsible if other) No.

Approved Checked Date Rev Reference

9/26/2011 PA1

3G Counters Troubleshooting Guideline

Abstract

The document gives a summary of 3G counters troubleshooting methodology & tips. The guideline gives the processes to be followed while analyzing and breaking down a problem in Accessibility, Retainability, and Mobility.



9/26/2011 PA1

1 Introduction

The purpose of Counter analysis is to satisfy the needs of the project in terms of accessibility, Retainability and Integrity agreed requirements so as to ensure a good quality of service (QoS) and Quality of Experience (QoE).

2 Performance Management Areas

This section describes the counter flowcharts grouped according to the following performance management areas:

Accessibility

The ability to successfully establish a radio connection for a requested Quality of Service (QoS). Flowcharts for Accessibility include the setup of a Packet-Switched (PS) and Circuit-Switched (CS) Radio Resource Control (RRC) connection, the establishment of a Radio Access Bearer (RAB) for each of the different service types, and paging of the User Equipment (UE), initiated from the Core Network (CN).

Retainability

The ability to maintain an established radio connection until terminated normally by the user. Flowcharts for Retainability include signaling connection handling, which covers release of the RRC and RAB connections due to both normal and abnormal causes; admission control as requested from the radio link reconfiguration, radio link setup, radio link delete, radio link addition and compressed mode usage traffic scenarios; and flowcharts for the loss of a radio connection due to a variety of reasons.

Quality

The quality of a requested service as perceived by an end-user. Flowcharts for Quality include channel switches for various reasons from common to dedicated channel, from dedicated to common channel, from dedicated to dedicated channel, and to idle mode.



9/26/2011 PA1

System Utilization

Covers system usage and availability, channel and code usage, and congestion situations. Flowcharts for System Utilization include detection of congestion situations, resolution of congestion situations, code allocation and usage, compressed mode usage, cell availability, and cell update.

Mobility

Covers all handover types. Flowcharts for Mobility include Inter-frequency Handover, Radio link Setup/Addition/Deletion/Reconfiguration, Soft Handover Addition/Deletion/Replacement, and Performance Statistics - Flowcharts for Counters Incoming/Outcoming Inter-radio Access Technology



9/26/2011 PA1

Accessibility

This section describes the Accessibility main traffic scenarios as follows:

• RRC Connection Setup – PS

• RRC Connection Setup – CS

• RAB Establishment

• Paging – CN Initiated

RRC Connection Setup – PS

This traffic scenario describes both successful and unsuccessful attempts to setup an RRC Connection for an originating or terminating packet-switched call. The main counters for this scenario are as follows:

• pmTotNoRrcConnectReq

• pmTotNoRrcConnectReqSucc

• pmTotNoRrcConnectReqPs

• pmTotNoRrcConnectReqSuccPs

• pmTotNoUtranRejRrcConnReq

• pmNoRejRrcConnMpLoadC

• pmNoRrcReqDeniedAdm

• pmNoRrcPsReqDeniedAdm



9/26/2011 PA1

Figure RRC Connection Setup - PS Scenario

RRC Connection Setup – CS

This traffic scenario describes both successful and unsuccessful attempts to set up an RRC connection for an originating or terminating circuit-switched call. The main counters for this scenario are as follows:



9/26/2011 PA1


• pmTotNoRrcConnectReqSucc

• pmTotNoRrcConnectReqCs

• pmTotNoRrcConnectReqSuccCs


• pmNoRejRrcConnMpLoadC

• pmNoRrcReqDeniedAdm

• pmNoRrcCsReqDeniedAdm

RRC Connection Setup - CS Scenario



9/26/2011 PA1

RAB Establishment

This traffic scenario describes both successful and unsuccessful attempts to set up a Radio Access Bearer for a requested service. The main counters for this scenario are as follows:

• pmNoRabEstablishAttempts

• pmNoRabEstablishAttemptSpeech

• pmNoRabEstablishAttemptCs64

• pmNoRabEstablishAttemptCs57

• pmNoRabEstablishAttemptPacketInteractive

• pmNoRabEstablishAttemptPacketStream

• pmNoInvalidRabEstablishAttempts

• pmCmAttUlSf2

• pmCmAttDlSf2

• pmCmAttUlHls

• pmCmAttDlHls

• pmNoRabEstablishSuccess

• pmNoRabEstablishSuccessSpeech

• pmNoRabEstablishSuccessCs64

• pmNoRabEstablishSuccessCs57

• pmNoRabEstablishSuccessPacketInteractive

• pmNoRabEstablishSuccessPacketStream

• pmCmStop

• pmCmSuccUlSf2

• pmCmSuccDlSf2



9/26/2011 PA1

• pmCmSuccUlHls

• pmCmSuccDlHls

• pmNoRabEstablishAttemptHs

• pmNoRabEstablishSuccessHs

• pmNoRabEstablishAttemptPacketStream128

• pmNoRabEstablishSuccessPacketStream128

• pmNoRabEstablishFailureUeCapability

• pmNoFailedRabEstAttemptExceedConnLimit

• pmNoFailedRabEstAttemptLackDlAse

• pmNoFailedRabEstAttemptLackUlAse

• pmNoFailedRabEstAttemptLackDlChnlCode

• pmNoFailedRabEstAttemptLackDlPwr

• pmLevelPsInteractive



9/26/2011 PA1

A flowchart for the RAB Establishment scenario is shown in the following Figure:

RAB Establishment Scenario.



9/26/2011 PA1

Successful RAB Establishment Scenario



9/26/2011 PA1

Paging – CN Initiated

This traffic scenario describes attempted, rejected, and discarded pages in the RNC. The main counters for this scenario are as follows:

• pmNoPagingAttemptCnInitDcch

• pmCnInitPagingToIdleLa

• pmNoPageDiscardCmpLoadC

• pmCnInitPagingToIdleRa

• pmCnInitPagingToIdleUe

• pmNoPagiginAttemptUtranRejected

A flowchart for the Paging CN - initiated scenario is shown in the following Figure:



9/26/2011 PA1

Flowchart for Paging CN - Initiated Scenario

Retainability

This section describes the Retainability main traffic scenarios as follows:

• Signaling Connection Handling

• RRC Connection Release

• Radio Access Bearer Release

• Admission Control



9/26/2011 PA1

Signaling Connection Handling

This traffic scenario describes Signaling Connection Release Handling. This procedure may use either the RAB Release or the RRC Connection Release procedure, depending on whether the UE has a connection to more than one CN and a RAB towards the CN requested to be disconnected. There are no counters directly impacted in this flowchart.

Signaling Connection Handling Scenario

RRC Connection Release

This traffic scenario describes the release of an RRC Connection due to various causes and from different service types.

The main counters for this scenario are as follows:

• pmNoCellDchDisconnectNormal, pmNoCellDchDisconnectAbnormal

• pmNoNormalRabReleaseSpeech, pmNoSystemRabReleaseSpeech

• pmNoSpeechDchDiscNormal, pmNoSpeechDchDiscAbnormal

• pmNoCs64DchDiscNormal, pmNoCs64DchDiscAbnormal



9/26/2011 PA1

• pmNoNormalRabReleaseCs64, pmNoSystemRabReleaseCs64

• pmNoCsStreamDchDiscNormal, pmNoCsStreamDchDiscAbnormal

• pmNoNormalRabReleaseCsStream, pmNoSystemRabReleaseCsStream

• pmNoPacketDchDiscNormal, pmNoPacketDchDiscAbnormal

• pmNoNormalRabReleasePacket, pmNoSystemRabReleasePacket

• pmNoPsStream64Ps8DchDiscNormal, pmNoPsStream64Ps8DchDiscAbnorm

• pmNoNormalRabReleasePacketStream, pmNoSystemRabReleasePacketStream

• pmNoCellFachDiscNormal, pmNoCellFachDiscAbnormal

• pmNoNormalRabReleasePacketStream128, pmNoSystemRabReleasePacketStream128

Other impacted counters are included in the following flowcharts which are referenced from the RRC Connection Release flowchart



9/26/2011 PA1

RRC Connection Release Scenario



9/26/2011 PA1

RAB Release

This traffic scenario describes the steps involved in RAB Release. The main counters for this scenario are as follows:

• pmNoNormalRabReleaseSpeech, pmNoSystemRabReleaseSpeech

• pmNoNormalRabReleaseCs64, pmNoSystemRabReleaseCs64

• pmNoNormalRabReleaseCsStream, pmNoSystemRabReleaseCsStream

• pmNoNormalRabReleasePacket, pmNoSystemRabReleasePacket

• pmNoNormalRabReleasePacketStream, pmNoSystemRabReleasePacketStream

• pmNoInvalidRabReleaseAttempts, pmNoRabReleaseSuccess,pmNoTpSwitchsp64Speech

• pmNoNormalRbReleaseHs, pmNoSystemRbReleaseHs

• pmNoNormalRabReleasePacketStream128, pmNoSystemRabReleasePacketStream128

Other impacted counters are included in the following flowcharts:

RAB Release Scenario Start



9/26/2011 PA1

RAB Release Scenario, Error 1 and Error 2

RAB Release Scenario, SRNC



9/26/2011 PA1

RAB Release Scenario, SRNC-DCH RAB



9/26/2011 PA1

RAB Release Scenario, SRNC-PS Streaming



9/26/2011 PA1

RAB Release Scenario, SRNC-Speech + PS 64



9/26/2011 PA1

RAB Release Scenario, SRNC- RAB Type



9/26/2011 PA1

RAB Release Scenario, SRNC-PS Data on FACH

RAB Release Scenario, DRNC



9/26/2011 PA1

RAB Release Scenario, DRNC-DCH RAB



9/26/2011 PA1

RAB Release Scenario, DRNC-PS Streaming



9/26/2011 PA1

RAB Release Scenario, DRNC-Speech + PS 64



9/26/2011 PA1

RAB Release Scenario, DRNC-PS Data on FACH



9/26/2011 PA1

Admission Control

This traffic scenario describes the handling of Admission Control requests from various traffic scenarios including Radio Link Addition, Radio Link Setup, Radio Link Deletion, Radio Link Reconfiguration, and Start Compressed Mode usage. The main counters for this scenario are as follows:

• pmNoFailedAfterAdm

• pmNoReqDeniedAdm

• pmNoOfNonHoReqDeniedSpeech

• pmNoOfNonHoReqDeniedCs

• pmNoOfNonHoReqDeniedInteractive

• pmNoOfNonHoReqDeniedPsStreaming

• pmLevelAseUl

• pmLevelAseDl

• pmLevelCompMode

• pmNoOfNonHoReqDeniedHs

• pmNoOfDiscardedNbapMessages

• pmLevelSf4Ul

• pmNoOfNonHoReqDeniedPsStr128

Note: pmLevelAseUl, pmLevelAseDl, and pmLevelCompMode are internal counters not visible in the output statistics ROP file. They are mapped to the related pmSumOfSampAseUL, pmSumOfSampAseDL, pmNoOfSampAseU, and pmNoOfSampAseDL counters as follows:



9/26/2011 PA1

pmNoOfSampAseUl: Number of samples of uplink (UL) Air-interface Speech Equivalents (ASE). Increased every time the pmLevelAseUL counter is read.

pmSumOfSampAseUL: Sum of all sample values recorded for the total ASE UL. This counter is the sum of all sample values of total UL ASE in use in the cell recorded during a 15–minute recording output period. The internal counter, pmLevelAseUl, monitors the current level of ASE in the cell. Every 30 seconds when the internal counter is read, its value is added to this counter, and the related counter pmNoOfSampAseUl is increased by one.

pmNoOfSampAseDL: Number of samples of downlink (DL) Air-interface Speech Equivalents (ASE). Increased every time the pmLevelAseDL counter is read.

pmSumOfSampAseDL: Sum of all sample values recorded for the total ASE DL. This counter is the sum of all sample values of total DL ASE in use in the cell recorded during a 15–minute recording output period. The internal counter, pmLevelAseDl, monitors the current level of ASE in the cell. Every 30 seconds when the internal counter is read, its value is added to this counter, and the related counter pmNoOfSampAseDl is increased by one.

pmSumCompMode: A snapshot of the number of compressed mode users is read once every 30 seconds in each cell from an internal counter, pmLevelCompMode. The counter pmLevelCompMode contains the sum of all snapshot values.

pmSamplesCompMode: The counter is increased at every occasion when the corresponding sum counter is increased. Other impacted counters are included in the following flowcharts, which are referenced from the Admission Control flowchart.

A flowchart for the Admission Control scenario is shown in the figure below:



9/26/2011 PA1

Admission Control Scenario (Part A)



9/26/2011 PA1

Admission Control Scenario (Part B)



9/26/2011 PA1

Quality

Channel Switching, Common to Dedicated

This traffic scenario describes the switching of a channel from common to dedicated as a result of a Channel Switching Evaluation decision based on downlink buffer load and traffic volume measurements from the UE. The main counters for this scenario are as follows:

• pmChSwitchFachDch


• pmLevelRabFach

• pmLevelUesWith1Rls1RlInActSet

• pmNoOfRlForNonDriftingUes

• pmFailedChSwitch

• pmDlUpswitchAttemptHs

• pmDlUpswitchSuccessHs

• pmUlUpswitchAttemptLow

• pmUlUpswitchSuccessLow

• pmUpswitchFachHsAttempt

• pmUpswitchFachHsSuccess

Note: The internal counters pmLevelRabFach, pmLevelPsInteractive, and pmLevelUesWith1Rls1RlInActSet are not visible in the output Statistics ROP file. For explanation of these counters, see the explanation in the Radio Link Setup flowchart.



9/26/2011 PA1

Channel Switching, Common to Dedicated Scenario



9/26/2011 PA1

Channel Switching, Dedicated to Common

This traffic scenario describes the switching of a channel from dedicated to common as a result of a Channel Switching Evaluation decision. The main counters for this scenario are as follows:

• pmFailedDchChSwitch

• pmChSwitchDch64Fach



• pmNoCellUpdAttempt

• pmNoCellUpdSuccess

• pmCmStop

• pmGsmMeasStop

• pmInterFreqMeasNoCmStop

• pmInterFreqMeasCmStop


• pmLevelRabFach










9/26/2011 PA1



• pmNoOfRlForDriftingUes

• pmNoOfRlForDriftingUesPerDrnc

• pmFailedChSwitch

• pmDownSwitchAttempt

• pmDownSwitchSuccess


Note: The internal counters pmLevel <serviceType> RabEstablish and pmLevelUesWithXRlsYRlInActSet are not visible in the output Statistics ROP file. For explanation of these counters, see the explanation in the Radio Link Setup flowchart figure.



9/26/2011 PA1

Channel Switching, Dedicated to Common Scenario



9/26/2011 PA1

Channel Switching, upswitch Dedicated to Dedicated

This traffic scenario describes the switching between dedicated channels as a result of a Channel Switching Evaluation decision. The main counters for this scenario are as follows:


• pmChSwitchP64P128


• pmCmAttUlSf2

• pmCmAttDlSf2

• pmCmAttUlHls

• pmCmAttDlHls

• pmCmSuccUlSf2

• pmCmSuccDlSf2

• pmCmSuccUlHls

• pmCmSuccDlHls

• pmCmStop

• pmUlUpswitchAttemptMedium

• pmUlUpswitchSuccessMedium


• pmDlUpswitchSuccessHs

• pmUlUpswitchSuccessHigh

• pmDlUpswitchAttemptHs

• pmUlUpswitchAttemptHigh



9/26/2011 PA1

Channel Switching, upswitch Dedicated to Dedicated Scenario

Channel Switching, downswitch Dedicated to Dedicated

This traffic scenario describes the switching between dedicated channels as a result of a Channel Switching Evaluation decision. The main counters for this scenario are as follows:





9/26/2011 PA1


• pmCmAttUlSf2

• pmCmAttDlSf2

• pmCmAttUlHls

• pmCmAttDlHls

• pmCmSuccUlSf2

• pmCmSuccDlSf2

• pmCmSuccUlHls

• pmCmSuccDlHls

• pmCmStop

• pmDownSwitchAttempt

• pmDownSwitchSuccess


• pmHsToDchAttempt

• pmHsToDchSuccess



9/26/2011 PA1

Channel Switching, downswitch Dedicated to Dedicated Scenario



9/26/2011 PA1

Channel Switching to Idle

This traffic scenario describes the switching from either Common Channel to Idle, Dedicated Channel to Idle, or PS HS- to Idle. The main counters for this scenario are pmChSwitchFachIdle (common to dedicated channel) and pmInactivityHsIdle (HS-).

.

Channel Switching To Idle Scenario



9/26/2011 PA1

System Utilization

This section describes the System Utilization main traffic scenarios as follows:

• Detect Cell Congestion

• Resolve Congestion Actions

• Code Allocation/Usage

• Start Compressed Mode

• Stop Compressed Mode

• Cell Availability

• Cell Update

Detect Cell Congestion

This traffic scenario describes the detection of congestion in a cell. The main counters for this scenario are as follows:

• pmSumOfTimesMeasOlDl

• pmSumOfTimesMeasOlUl

• pmTotalTimeDlCellCong

• pmTotalTimeUlCellCong



9/26/2011 PA1

Detect Cell Congestion Scenario (Part A)



9/26/2011 PA1

Detect Cell Congestion Scenario (Part B)



9/26/2011 PA1

Resolve DL Congestion Actions

This traffic scenario describes the actions taken by congestion control when congestion is detected in a cell. The main counters for this scenario are as follows:

• pmNoOfSwDownNgCong

• pmNoOfIurSwDownNgCong

• pmNoOfTermSpeechCong

• pmNoOfTermCsCong

• pmNoOfIurTermSpeechCong

• pmNoOfIurCsCong

• pmNoOfIurTermHsCong

• pmNoOfSwDownHsCong

Other impacted counters are included in the following flowcharts which are referenced from the Resolve Congestion Actions flowchart:



9/26/2011 PA1

Resolve Congestion Actions Scenario (Part A)



9/26/2011 PA1



9/26/2011 PA1

Code Allocation/Usage

This traffic scenario describes the attempts, successes, and failures to allocate codes on request by various traffic scenarios including compressed mode usage, Radio Link Reconfiguration, Radio Link Addition, Common Channel Configuration and Radio Link Setup. The main counters for this scenario are as follows:

• pmNoOfDlChCodeAllocAttemptsSf8, pmNoOfDlChCodeAllocFailureSf8


• pmNoOfDlChCodeAllocAttemptsSf32, pmNoOfDlChCodeAllocFailuref32







9/26/2011 PA1

Code Allocation/Usage Scenario

Start Compressed Mode

This traffic scenario describes the starting of compressed mode. The main counters for this scenario are as follows:

• pmCmAttUlSf2, pmCmSuccUlSf2

• pmCmAttDlSf2, pmCmSuccDlSf2

• pmCmAttUlHls, pmCmSuccUlHls

• pmCmAttDlHls, pmCmSuccDlHls



9/26/2011 PA1


Start of Compressed Mode Scenario

Stop Compressed Mode

This traffic scenario describes the stopping of compressed mode. The main counters for this scenario are as follows:

• pmCmStop




9/26/2011 PA1

Stop Compressed Mode Scenario

Cell Availability

This traffic scenario describes the scenarios for cell downtime caused by manual and automatic intervention. The main counters for this scenario are as follows:

• pmCellDowntimeMan

• pmCellDowntimeAuto

• pmHsDowntimeMan

• pmHsDowntimeAuto



9/26/2011 PA1

Cell Availability Scenario Part A



9/26/2011 PA1

Cell Availability Scenario Part B

Cell Update

This traffic scenario describes Cell Update situations in the RNC. The main counters for this scenario are as follows:

• pmNoCellUpdAttempt

• pmNoCellUpdSuccess



9/26/2011 PA1

Cell Update Scenario



9/26/2011 PA1

Mobility

Interfrequency Handover

This traffic scenario describes successful and failed inter-frequency handover. The main counters for this scenario are as follows:

• pmInterFreqMeasCmStart, pmInterFreqMeasNoCmStart

• pmInterFreqMeasCmStop, pmInterFreqMeasNoCmStop

• pmAttNonBlindInterFreqHoCsSpeech12, pmSuccNonBlindInterFreqHoCsSpeech12

• pmFailNonBlindInterFreqHoRevertCsSpeech12, pmFailNonBlindInterFreq

HoFailRevertCsSpeech12

• pmAttNonBlindInterFreqHoCsConversational, pmSuccNonBlindInterFreq

HoCsConversational

• pmFailNonBlindInterFreqHoRevertCsConversational, pmFailNonBlindInter

FreqHoFailRevertCsConversational

• pmAttNonBlindInterFreqHoPsInteractiveLess64, pmSuccNonBlindInterFr

eqHoPsInteractiveLess64

• pmFailNonBlindInterFreqHoRevertPsInteractiveLess64, pmFailNonBlindInt

erFreqHoFailRevertPsInteractiveLess64

• pmAttNonBlindInterFreqHoPsInteractiveGreater64, pmSuccNonBlindIn

terFreqHoPsInteractiveGreater64

• pmFailNonBlindInterFreqHoRevertPsInteractiveGreater64,

• pmFailNonBlindInterFreqHoFailRevertPsInteractiveGreater64

• pmAttNonBlindInterFreqHoStreamingOther, pmSuccNonBlindInterFreqHoStreamingOther



9/26/2011 PA1

• pmFailNonBlindInterFreqHoRevertStreamingOther, pmFailNonBlindInter

FreqHoFailRevertStreamingOther

• pmNoIncomingHsHardHoAttempt, pmNoIncomingHsHardHoSuccess

• pmNoOutGoingHsHardHoAttempt, pmNoOutgoingHsHardHoSuccess

• pmNoHsHardHoReturnOldChSource, pmNoHsHardHoReturnOldChTarget

• pmNoTimesIfhoRlAddToActSet, pmNoTimesIfhoCellFailAddToActSet

• pmNoRlDeniedAdm

• pmEnableHsHhoSuccess

• pmEnableHsHhoAttempt

Other impacted counters are included in the following flowcharts, which are referenced from the inter-frequency Handover flowchart:



9/26/2011 PA1



9/26/2011 PA1

Radio Link Setup

This traffic scenario describes the setup of a radio link on request from various traffic scenarios including RAB Release, RAB Establishment, and RRC Connection Setup. The main counters for this scenario are as follows:


• pmLevelCs12RabEstablish



• pmLevelCs12Ps64RabEstablish


• pmLevelPsStr64Ps8RabEstablish

• pmLevelRrcOnlyEstablish











Note: The pmLevel<serviceType>RabEstablish and pmLevelUesWithXXRls YYRlInActSet counters are internal counters and are not visible in the output Statistical ROP file.



9/26/2011 PA1

The pmLevel<serviceType>RabEstablish counters are mapped to the related pmSum<serviceType>RabEstablish and pmSamples<serviceType>RabEstabl ish counters. The following is an example using the service type CS12 (that is, speech):

pmSumCs12RabEstablish: Sum of all sample values recorded for number of active speech 12.2–Kbit RABs

pmSamplesCs12RabEstablish: This counter is increased at every occasion when the corresponding sum counter is stepped. It is based on an internal level counter, pmLevelCs12RabEstablish, which is maintained by the RNC.

Values are read periodically, every 5 seconds, from the level counter. Each read results in the pmSamples counter being increased by one, and the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number of single CS12 RABs active at any given instant in time. The counter can be decreased or increased. The level counter is updated by various RNC traffic functions.

The pmLevelUesWithXXRlsYYRlInActSet counters are mapped to the related pmSumUesWith<x>Rls<y>RlInActSet and pmSamplesUesWith<x>Rls<y>RlIn ActSet counters. The following is an example using the number of UEs with one radio link set and two radio links in the Active Set.

pmSumUesWith1Rls2RlInActSet: Sum of all sample values recorded for number of UEs with one radio link set and two radio links in the Active Set.

pmSumUesWith1Rls2RlInActSet: This counter is increased at every occasion when the corresponding sum counter is stepped. It is based on an internal level counter, pmLevelUesWith1Rls2RlInActSet, which is maintained by the RNC. Values are read periodically, every minute, from the level counter. Each read results in the pmSamples counter being increased by one, and the actual value read from the level counter being added to the pmSum counter. The level counter maintains a snapshot of the number of UEs with one radio link set and two radio links in the Active Set at any given instant in time. The counter can be decreased or increased. The level counter is updated by various RNC traffic functions.

Other impacted counters are included in the following flowcharts, which are referenced from the Radio Link Setup flowchart:

A flowchart for the Radio Link Setup scenario is shown in Figure 42 on page 65.



9/26/2011 PA1

Radio Link Setup Scenario

Radio Link Addition

This traffic scenario describes the addition of a radio link to an existing radio connection on request from various traffic scenarios including inter-frequency handover and soft or softer handover. The main counters for this scenario are as follows:





9/26/2011 PA1
















Note: For pmLevel<serviceType>RabEstablish and pmLevelUesWithXRlsYRlIn ActSet counters, see explanation in Radio Link Setup flowchart. Other impacted counters are included in the following flowcharts that are referenced from the Radio Link Addition flowchart:



9/26/2011 PA1

Radio Link Addition Scenario

Radio Link Deletion

This traffic scenario describes the deletion of a radio link from a connection when requested by a traffic scenario. The main counters for this scenario are as follows:







9/26/2011 PA1















Note: For pmLevel<serviceType>RabEstablish and pmLevelUesWithXRlsYRlIn ActSet counters, see explanation in Radio Link Setup flowchart. Other impacted counters are included in the following flowcharts, which are referenced from the Radio Link Deletion flowchart:



9/26/2011 PA1

Radio Link Deletion Scenario

Radio Link Reconfiguration

This traffic scenario describes the reconfiguration of a radio link on request from a traffic procedure. The main counters for this scenario are as follows:







9/26/2011 PA1




Note: For pmLevel<serviceType>RabEstablish counters, see explanation in Radio Link Setup flowchart

Other impacted counters are included in the following flowcharts, which are referenced from the Radio Link Reconfiguration flowchart:

Radio Link Reconfiguration Scenario



9/26/2011 PA1

Soft Handover Addition

This traffic scenario describes the addition of a cell to the Active Set of the UE. The main counters for this scenario are as follows:

• pmNoTimesCellFailAddToActSet


• pmNoTimesRlAddToActSet





• pmNoRlDeniedAdm

• Per utranRelation:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBestCellSpeech

• Per utranCell:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBestCellSpeech

• Per utranRelation:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccess

BestCellCsConvers

• Per utranCell:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccessBestCellCsConvers

• Per utranRelation:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccess

BestCellPacketLow

• Per utranCell:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccessBestCellPacketLow

• Per utranRelation:pmRlAddAttemptsBestCellPacketHigh,

pmRlAddSuccessBestCellPacketHigh

• Per utranCell:pmRlAddAttemptsBestCellPacketHigh, pmRlAddSuccessBestCellPacketHigh

• Per utranRelation:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBestCellStream

• Per utranCell:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBestCellStream

• Per utranRelation:pmRlAddAttemptsBestCellStandAlone,

pmRlAddSuccessBestCellStandAlone



9/26/2011 PA1

• Per utranCell:pmRlAddAttemptsBestCellStandAlone, pmRlAddSuccess

BestCellStandAlone

• Per utranCell:pmNoSysRelSpeechSoHo for best cell

Other impacted counters are included in the following flowcharts, which are referenced from the Soft Handover Addition flowchart:

Soft Handover Addition Scenario



9/26/2011 PA1

Soft Handover Deletion

This traffic scenario describes the removal of a cell from the Active Set of a UE. The main counters for this scenario are as follows:


• pmNoOfTimesRlDelFrActSet

• pmNoRlDeniedAdm

Soft Handover Replacement

This traffic scenario describes the replacement of a cell in the Active Set of a UE. The main counters for this scenario are as follows:

• pmNoTimesRlRepFrActSet



9/26/2011 PA1

• pmNoRlDeniedAdm






• Per utranRelation:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBestCellSpeech

• Per utranCell:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBestCellSpeech

• Per utranRelation:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccess

BestCellCsConvers

• Per utranCell:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccessBestCellCsConvers

• Per utranRelation:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccess

BestCellPacketLow

• Per utranCell:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccessBestCellPacketLow

• Per utranRelation:pmRlAddAttemptsBestCellPacketHigh,

pmRlAddSuccessBestCellPacketHigh

• Per utranCell:pmRlAddAttemptsBestCellPacketHigh, pmRlAddSuccessBestCellPacketHigh

• Per utranRelation:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBestCellStream

• Per utranCell:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBestCellStream

• Per utranRelation:pmRlAddAttemptsBestCellStandAlone,

pmRlAddSuccessBestCellStandAlone

• Per utranCell:pmRlAddAttemptsBestCellStandAlone, pmRlAddSuccess

BestCellStandAlone

• Per utranCell:pmNoSysRelSpeechSoHo for the best cell

Other impacted counters are included in the following flowcharts, which are referenced from the Soft Handover Replacement flowchart:



9/26/2011 PA1

Soft Handover Replacement Scenario



9/26/2011 PA1

Inter-Radio Access Technology Handover, Outgoing

This traffic scenario describes inter-radio access technology handover attempts from UTRAN to GSM. The main counters for this scenario are as follows:

• pmNoDirRetryAtt, pmNoDirRetrySuccess

• pmNoFailOutIratHoSpeechGsmFailure , pmNoFailOutIrat

HoCs57GsmFailure, pmNoFailOutIratHoMultiGsmFailure ,

pmNoFailOutIratHoStandaloneGsmFailure

• pmNoAttOutIratHoSpeech, pmNoAttOutIratHoCs57, pmNoAttOutIratHoM

ulti, pmNoAttOutIratHoStandalone

• pmNoSuccessOutIratHoSpeech, pmNoSuccessOutIratHoCs57,

pmNoSuccessOutIratHoMulti, pmNoSuccessOutIratHoStandalone

• pmNoFailOutIratHoSpeechReturnOldChPhyChFail, pmNoFailOutIratHoCs

57ReturnOldChPhyChFail, pmNoFailOutIratHoMultiReturnOldChPhyChFai

l, pmNoFailOutIratHoStandaloneReturnOldChPhyChFail

• pmNoFailOutIratHoSpeechReturnOldChNotPhyChFail, pmNoFailOutIratHo

Cs57ReturnOldChNotPhyChFail, pmNoFailOutIratHoMultiReturnOldChNot

PhyChFail, pmNoFailOutIratHoStandaloneReturnOldChNotPhyChFail

• pmNoFailOutIratHoSpeechUeRejection , pmNoFailOutIratHoCs57UeRejec

tion , pmNoFailOutIratHoMultiUeRejection , pmNoFailOutIratHoStandalone

UeRejection, pmNoFailOutSbHoSpeechUeRejection

• pmNoAttOutSbHoSpeech, pmNoSuccessOutSbHoSpeech

• pmNoFailOutSbHoSpeechGsmFailure

Other impacted counters are included in the following flowcharts, which are referenced from the Inter-Radio Access Technology Handover, Outgoing flowchart:



9/26/2011 PA1

Inter-Radio Access Technology Handover, Outgoing Scenario (Part A)



9/26/2011 PA1

Inter-Radio Access Technology Handover, Outgoing Scenario (Part B)

Inter-Radio Access Technology Handover, Incoming

This traffic scenario describes the Inter-radio Access Technology Handover attempt from GSM to UTRAN. The main counters for this scenario are as follows:

• pmNoInCsIratHoAtt

• pmNoCsIratHoAdmFail

• pmNoInCsIratHoSucc

Other impacted counters are included in the following flowcharts, which are referenced from the Inter-radio Access Technology Handover, Incoming flowchart:



9/26/2011 PA1

Inter-radio Access Technology Handover, Incoming Scenario

Inter-Radio Access Technology Cell Change, Outgoing

This traffic scenario describes the inter-radio access technology cell change from UTRAN to GPRS. The main counters for this scenario are as follows:

• pmNoOutIratCcAtt

• pmNoOutIratCcReturnOldCh

• pmNoOutIratCcSuccess



9/26/2011 PA1

Inter-Radio Access Technology Cell Change, Outgoing Scenario

Inter-Radio Access Technology Cell Change, Incoming

This traffic scenario describes an inter-radio access technology cell change from GPRS to UTRAN. The main counters for this scenario are as follows:


• pmTotNoRrcConnectAttIratCcOrder

• pmTotNoRrcConnectReqSuccess

• pmTotNoRrcConnectSuccessIratCcOrder

• pmTotNoRrcConnectFailCongIratCcOrder



9/26/2011 PA1


• pmTotNoRejRrcConnMpLoadC

Inter-Radio Access Technology Cell Change, Incoming Scenario

Inter-Radio Access Technology Cell Reselection, Incoming

This traffic scenario describes an inter-radio access technology cell reselection from GPRS to UTRAN. The main counters for this scenario are as follows:




9/26/2011 PA1

• pmTotNoRrcConnectAttIratCellResel

• pmTotNoRrcConnectReqSuccess

• pmTotNoRrcConnectSuccessIratCellResel

• pmTotNoRrcConnectFailCongIratCellResel


• pmTotNoRejRrcConnMpLoadC

Inter-Radio Access Technology Cell Reselection, Incoming Scenario



9/26/2011 PA1

HS Cell Change Counters

An HS- Cell change can be triggered by the removal of an RL or change of best cell. The following counters are valid for monitoring the HS- Cell Change function. In MO Class Utran Cell

• pmNoHsCcAttempt

• pmNoHsCcSuccess

Serving HS- Cell Change Scenario



9/26/2011 PA1

CN Hard Handover on CS RAB, Source-RNC

This traffic senario describes CNHHO attempts in the source RNC.

• pmNoAttOutCnhhoSpeech

• pmNoAttOutCnhhoNonSpeech

• pmNoSuccOutCnhhoSpeech

• pmNoSuccOutCnhhoNonSpeech

Other impacted counters are included in the following flowcharts, which are referenced from the CNHHO, in the source RNC flowchart:

CN Hard Handover on CS RAB in the source RNC



9/26/2011 PA1

CN Hard Handover on CS RAB, Target-RNC

This traffic senario describes CNHHO attempts in the target RNC.

• pmNoAttIncCnhhoSpeech

• pmNoAttIncCnhhoNonSpeech

• pmNoSuccIncCnhhoSpeech

• pmNoSuccIncCnhhoNonSpeech

Other impacted counters are included in the following flowcharts, which are referenced from the CNHHO, in the target RNC flowchart:

CN Hard Handover on CS RAB in the target RNC



9/26/2011 PA1

CN Hard Handover on PS RAB, Source-RNC

This traffic senario describes CNHHO on PS in the source RNC The main counters for this senario are as follows:

• pmNoAttOutCnhhoPsConnRelease

CN Hard Handover on PS RAB in the source RNC



9/26/2011 PA1

3 Conclusion

The guideline has been made in order to assit engineer in counter analysis/KPI drive testing. It is recommended to at least follow the above steps during KPI analysis.

3G Counters Troubleshooting Guideline

Documents

Transcript of 3G Counters Troubleshooting Guideline