3G RAN KPIs and Counters 20091216 p2

3G RAN
Counters and Signaling

Introduction
Internal
1 © Nokia Siemens Networks
Objectives
• The session will give an overview of the counters and

signaling
• Focus more on RRC/RAB Setup and Access
Internal
Contents
• 3G KPI Overview
• 3G RAN KPI Classification
• Focus on Accessibility KPI
Internal
3G KPI Overview
Field Measurement KPI RAN KPI Core Network KPI
BS
GPRS GGSN Firewall Internet
Backbone
PS data
FMT 3G SGSN server
CS data
RNC 3G MSC Modem server
PSTN
End-to-End KPI
Different Scopes : Different Classifications of RAN KPI :

• End-to-end KPI • Accessibility
• Core Network KPI • Retainability
• Field Measurement KPI • Usage
• RAN KPI • Mobility
Internal
Classification of RAN KPI
SRNC
Relocation
SRNC
Accessibility: RNC
RNC
RRC Setup & Access
Rate
RAB Setup & Access
Usage:
Rate
Cell Availability
Call Setup Success Rate
Ave. Uplink Load
Ave. Downlink Load
X
BTS2 Pre-emption
UE
BTS1
X
Retainability: Mobility:
RRC Drop Rate SHO Success
RAB Drop Rate Rate
SHO Overhead
Internal
List of Measurement Tables
TABLE COUNTERS
Cell resource M1000Cx
Service level M1001Cx
Traffic M1002Cx
L3 signalling at Iu M1003Cx
L3 signalling at Iur M1004Cx
L3 signalling at Iub M1005Cx
RRC signalling M1006Cx
Soft handover M1007Cx
Intra-system hard handover M1008Cx
L3 relocation signalling M1009Cx
Inter-system handover M1010Cx
Location services M1011Cx
Service area broadcast M1012Cx
RCPM RLC M1017Cx
AAL2 Resource Reservation M800Cx
AAL2 Path CAC Resource M550Cx
Internal
HSDPA in WBTS M5000Cx
Performance Measurement Counters
SGSN MGW
RCPM OLPC MSC/HLR
SGSN
Inter System Handover (M1016)
SABC
DSP
(M1010)
(M613)
Packet Call measurements RNC L3 signalling on Iu interface
RCPM RLC (M1003)
(M1022)
(M1017) Traffic
RNC
Cell Throughput measurements (M1002) ATM Virtual Channel
L3 signalling on Iub interface
(M1023) (M530)
(M1005)
AAL2 Resource ReservationAAL2 Path CAC Resource
Service Level (M8000) (M550)
HSDPA in WBTS
(M1001)
(M5000) Soft Handover
Cell Resource (M1007) Location Services
Intra System Handover
(M1000) (M1008) (M1011)
Service Area Broadcast
Updated for RAS06 RRC Signalling
(M1012)
(M1006)
New for RAS6
Internal
Service Level Measurements (M1001)
• The service level measurement is carried out in the serving RNC (SRNC)
• The object of the measurement is the WBTS/WCELL, which is the best active set
cell of the SRNC (having the biggest CPICH Ec/No value in the last ‘RRC:
Measurement Report’ message) i.e. so called reference cell or main cell
•In anchoring case, all active set cells belong to the drift RNC and the serving RNC is
not aware of their identifications
– Therefore, this measurement is forced to use the special WBTS/WCELL object
identifier WBTS-0/WCELL-0
• The best active set cell may change during the call, thus, the object of the
measurement can be different for connection establishment and release counters
• In RAS05.1 new counters added to count the changes of reference cells
– RAB can be established and released in two separate measurement intervals:
connection establishment and release counters of the same call are updated during
different measurement intervals
– If a failure, which leads to RRC connection release, occurs during any RAB active
phase, both RRC active and RAB failure counters are updated with an appropriate
cause
Internal
Traffic Measurement (M1002)
• Measures Radio Network Performance from the SRNCs perspective

• Measures DCH requests versus allocations and durations
• Different Request/allocations: Signalling, CS and PS with QoS definitions
(PS Interactive 64kbps and HS-DSCH)
• Signalling link DCH allocations occur at RRC Setup
– When UE moves from idle mode to RRC connected mode
• User plane DCH allocations may be initiated when the UE is in either idle
or RRC connected mode
– Measurements carried out in Both SRNC and DRNC
• No knowledge of RAB parameters in the DRNC so definition of the
counters is limited to:
– CS voice
– Signalling
– Data
Internal
Counters and Signalling
• RRC Performance
– RRC Setup Phase
– RRC Access Phase
– RRC Active Phase
• RAB Establishment
– RAB Setup
– RAB Active
Internal
RRC and RAB Phases
Phase: Setup Access Active
Setup Access Active

complete Complete Complete
Success
Access Active
Release
Active
Attempts Failures RRC Drop
Access Fails
All the counters of the Service Level

Table are incremented only for the
Setups Failures, Blocking reference cell
Internal
RRC Connection Setup Phase
UE Node B RNC
This phase starts when UE sends [RACH] RRC:RRC Connection Request
the ‘RRC CONNECTION NBAP: RL Setup Request
REQUEST’ message using the Start

TX/RX
PRACH channel and it is NBAP: RL Setup Response

ALCAP:ERQ
completed when RNC, after ALCAP:ECF
reserving all the necessary [FACH] RRC: RRC Connection Setup
Start
resources for the RRC TX/RX
Connection (RNC, BTS, Radio L1 Synchronisation
and Transmission), replies with NBAP: Synchronisation Indication
DL ‘RRC CONNECTION SETUP’ [DCH] RRC: RRC Connection Setup Complete
message, carried over S-CCPCH

(FACH sub-channel)
Internal
RRC Setup Phase (1) • If RNC correctly received the message,
M1001C0 RRC_CONN_STP_ATT, is update
•Specific ‘RRC:RRC Connection Request’ counters with

UE Node B RNC establishment cause is incremented as indicated by UE,
[RACH] RRC:RRC Connection Request M1006C0 CONN_REQ_MOC_ESTAB_CONV_CALL
M1006C19 RRC_CONN_REQ_CALL_RE_ESTAB
HC Entity
• RNC allocates resources from Handover Control (HC).
AC Entity • When the RNC decides to reject the ‘RRC:RRC connection
request’ because the handover control entity reports a failure
NBAP: RL Setup Request M1001C2 RRC_CONN_STP_FAIL_HC
Start Tx/Rx • In RAN04, the RNC allocates RNTI for the RRC Connection
• When the RNC decides to reject the ‘RRC connection
Request’ due to RNTI allocation failure caused by RRMU
NBAP: RL Setup Response overload
M1001C247 RRC CONN SETUP FAIL DUE TO RNTI ALLO
ALCAP:ERQ FAIL
ALCAP:ECF
• After this, the RNC sends an ‘RRC: RRC CONNECTION
[FACH] RRC: RRC Connection Setup REJECT’ message to the UE.
(This counter is updated also in case of incoming SRNS
relocations, inter-system handovers, and inter-RNC hard
Start Tx/Rx handovers)
• If RNC decides to reject the RRC Connection Establishment
(Setup) at any given time (due to reasons other than
specifically counted by other counters),
M1001C6 RRC_CONN_STP_FAIL_RNC
• If ‘RRC Connection Request’ is rejected, the RNC will send

“RRC: RRC Connection Reject’ message to the UE
M1006C21 RRC_CONN_REJECT
Internal

HC Entity
• DCH Requests
AC Entity M1002C3 DCH_REQ_RRC_CONN_SRNC
(includes state transitions and RRC connections)
NBAP: RL Setup Request M1002C0 DCH_REQ_LINK_SRNC
M1002C238 DCH_REQ_RRC_CONN_DRNC
Start Tx/Rx (includes SHO, HHOs, state transitions and RRC
connections)
NBAP: RL Setup Response • In case the UL load (measured PrxTotal) exceeds
PrxTraget + PrxOffset OR Prx_nc exceeds PrxTarget
ALCAP:ERQ M1002C1 DCH_REQ_LINK_REJ_UL_SRNC
M1002C239 DCH_REQ_SIG_LINK_UL_DRNC
ALCAP:ECF
• DCH allocation rejection triggers:
[FACH] RRC: RRC Connection Setup M1001C3 RRC_CONN_STP_FAIL_AC

Start Tx/Rx “RRC: RRC Connection Reject’ message to the UE
Internal
UL and DL Load
Internal

HC Entity
• DCH Requests
connections)
NBAP: RL Setup Response • In case the DL load (measured PtxTotal) exceeds PtxTraget
+ PtxOffset or Ptx_nc exceeds the PtxTarget
ALCAP:ERQ M1002C2 CH_REQ_LINK_REJ_DL_SRNC
M1002C240 DCH_REQ_SIG_LINK_DL_DRNC
ALCAP:ECF (mistake in counter update in softer HO case : counter NOT
updated in case softer HO rejection, corrected RAS05 E5,
[FACH] RRC: RRC Connection Setup causes M1002C1+M1002C2 < M1002C5)
• DCH allocation rejection triggers:

Start Tx/Rx M1001C3 RRC_CONN_STP_FAIL_AC

Internal

HC Entity
• DCH Requests
connections)
NBAP: RL Setup Response
• DCH allocation rejection triggers, in case the RRC
ALCAP:ERQ Connection setup fails due to channelisation codes not
available
ALCAP:ECF M1001C3 RRC_CONN_STP_FAIL_AC
[FACH] RRC: RRC Connection Setup • If ‘RRC Connection Request’ is rejected, the RNC will send
Start Tx/Rx
Internal
RRC Setup Phase (5.1) • If RNC correctly received the message,

HC Entity
• DCH Requests
NBAP: RL Setup Request
M1002C0 DCH_REQ_LINK_SRNC
Start Tx/Rx M1002C238 DCH_REQ_RRC_CONN_DRNC
(includes SHO, HHOs, state transitions and RRC
NBAP: RL Setup Response connections)
• Successful AC decision triggers
ALCAP:ERQ M1002C7 DCH_ALLO_LINK_3_4_SRNC
M1002C8 DCH_ALLO_LINK_13_6_SRNC
ALCAP:ECF (incremented only in case BTS setup and AAL2 reservation
are ok)
[FACH] RRC: RRC Connection Setup • Starts the duration counters (sampled continuously with 1s
interval RN2.0 GCD3 onwards)
M1002C10 DCH_ALLO_DURA_LINK_3_4_SRNC
Start Tx/Rx M1002C11 DCH_ALLO_DURA_LINK_13_6_SRNC
(started only in case BTS setup and AAL2 reservation are
ok)
• RL Setup Request
M1005C0 RL_SETUP_ATT_FOR_FIRST_RL
(includes RRC connection setups and state transitions,
cell_FACH => cell_DCH)
Internal
• In RAS05, RL Setup Failure
RRC Setup Phase (5.2) M1005C176 SETUP_FAIL_FIRST_RL_RNL
M1005C177 SETUP_FAIL_FIRST_RL_TRL
M1005C178 SETUP_FAIL_FIRST_RL_PROT
M1005C179 SETUP_FAIL_FIRST_RL_MISC
UE Node B RNC (Counters are incremented in case of RRC Connection Setup
or state transition to Cell_DCH)
[RACH] RRC:RRC Connection Request
• In RAS05.1, RL Setup Failure
HC Entity M1005C14 SETUP_FAIL_RL_BTS_NOT_RESP
(incremented in case BTS does not respond and supervision
AC Entity timer in RNC expires)
NBAP: RL Setup Request • In case the BTS rejects the attempt
DCH_ALLO_DURA_xxx (not incremented)
Start Tx/Rx DCH_ALLO_xxx are (not incremented)
NBAP: RL Setup Response • RL allocation rejection triggers:

M1001C4 RRC_CONN_STP_FAIL_BTS
ALCAP:ERQ
ALCAP:ECF “RRC: RRC Connection Reject’ message to the UE
[FACH] RRC: RRC Connection Setup
Start Tx/Rx
Internal
RL Setup Failure Causes, Typical
• Radio Network Layer Cause:

– Combining not supported
– Combining Resources not available
– Requested Tx Diversity Mode not supported
– Number of DL codes not supported
– Number of UL codes not supported
– UL SF not supported
– DL SF not supported
– Dedicated Transport Channel Type not supported
– Downlink Shared Channel Type not supported
– Uplink Shared Channel Type not supported
– CM not supported
– DPC mode change not supported
– Delayed Activation not supported
• Transport Layer Cause:
– Transport Resources Unavailable
• Miscellaneous Cause:
– O&M Intervention
– Control processing overload
– HW failures
Internal
RRC Setup Phase (6) • RL Setup Request
• RL Setup Response
UE Node B RNC M1005C5 RL_SETUP_SUCC_FOR_FIRST_RL
[RACH] RRC:RRC Connection Request • In RAN04, when the RNC CAC decides to reject the ‘RRC
Connection Request’ due to Iub transport resource shortage
HC Entity between the RNC and the WBTS
M1001C399 RRC SETUP FAIL DUE TO IUB AAL2 TRANS
AC Entity (also incremented in case of inter-system handovers, and
inter-RNC hard handovers)
NBAP: RL Setup Request • No ALCAP ERQ is sent as the rejection happens before
establishment request is sent
Start Tx/Rx • In RAS05 onwards, it is replaced by
M1001C530 RRC_CONN_STP_FAIL_IUB_AAL2
NBAP: RL Setup Response (also incremented in case of inter-system handovers, and
ALCAP:ERQ
• M800 and M550 provide more detailed information.
ALCAP:ECF
• In case the CAC rejects the attempt
DCH_ALLO_xxx are (not incremented)

Start Tx/Rx Connection setup fails due to Iub not available
M1001C5 RRC_CONN_STP_FAIL_TRANS

Internal
RRC Setup Phase (7) • RL Setup Request
• RL Setup Response
UE Node B RNC M1005C5 RL_SETUP_SUCC_FOR_FIRST_RL
[RACH] RRC:RRC Connection Request • In RAN04, when the RNC CAC decides to reject the ‘RRC
Connection Request’ due to Iub transport resource shortage
HC Entity between the RNC and the WBTS
M1001C399 RRC SETUP FAIL DUE TO IUB AAL2 TRANS
AC Entity (also incremented in case of inter-system handovers, and
NBAP: RL Setup Request • No ALCAP ERQ is sent as the rejection happens before
establishment request is sent
Start Tx/Rx • In RAS05 onwards, it is replaced by
M1001C530 RRC_CONN_STP_FAIL_IUB_AAL2
NBAP: RL Setup Response (also incremented in case of inter-system handovers, and
ALCAP:ERQ
ALCAP:ECF
Connection setup fails due to Iub not available
M1001C5 RRC_CONN_STP_FAIL_TRANS

Start Tx/Rx
• In case the Iub reservation rejection,

Internal
RRC Setup Phase (8)
UE Node B RNC
HC Entity
AC Entity
Start Tx/Rx
ALCAP:ERQ
ALCAP:ECF • When RRC Connection Setup was established

M1006C22 RRC_CONN_SETUP
(includes also repeated sendings of the message due to
RNC internal timer expiry or due to a new ‘RRC Connection
Request’ from the UE)
Start Tx/Rx
• RRC Connection Setup Complete
M1001C1 RRC_CONN_STP_COMP
Internal
RRC Setup Phase (9)
UE Node B RNC
HC Entity
AC Entity
Start Tx/Rx
ALCAP:ERQ • In case the RNC receives new ‘RRC Connection Request’

from the same UE before ‘RRC Connection Setup Complete’
ALCAP:ECF and before RRCconnRepTimer1 expires, RNC sends new
RRC Connection Setup before RRCconnRepTimer1 expires.
M1006C100 RRC_SETUP_RETRANS_TRIG_BY_UE
• If RRC Connection Setup Complete is not received in the
time defined in RRCconnRepTimer2
M1006C101 RRC_SETUP_RETRANS_TRIG_TIMER
Start Tx/Rx
Internal
Percentage, %
25
Internal
0%
20%
40%
60%
80%
100%
11/1/2009
RNCname RNC_MALANG
11/2/2009
11/3/2009
Data
11/4/2009
© Nokia Siemens Networks

11/5/2009
11/6/2009
11/7/2009
Sum of RrcStp_Fail_HC_#
11/8/2009
11/9/2009
11/10/2009
RRC Setup Failures
11/11/2009
Sum of RrcStp_Fail_AC_#
11/12/2009
11/13/2009
11/14/2009
11/15/2009
RRC Setup Failures
Date-Time
11/16/2009
Sum of RrcStp_Fail_BTS_#
11/17/2009
11/18/2009
11/19/2009
11/20/2009
11/21/2009
Sum of RrcStp_Fail_RNC_#
11/22/2009
11/23/2009
11/24/2009
11/25/2009
11/27/2009
Sum of RrcStp_Fail_FrznBts_#
11/28/2009
11/29/2009
11/30/2009
RRC Access Phase (1)
UE Node B RNC
It begins when RNC sends DL [RACH] RRC:RRC Connection Request
“RRC CONNECTION SETUP” NBAP: RL Setup Request
message to UE and it is Start

TX/RX
successfully completed upon NBAP: RL Setup Response

ALCAP:ERQ
receiving UL “RRC ALCAP:ECF
CONNECTION SETUP [FACH] RRC: RRC Connection Setup
COMPLETE” message UE Start

TX/RX
transmits using the established L1 Synchronisation
dedicated channel NBAP: Synchronisation Indication
[DCH] RRC: RRC Connection Setup Complete
This procedure can be quite

critical since it includes both UL
and DL L1 synchronization of the
signaling dedicated channel to be
setup
Internal
UE Node B RNC
HC Entity
AC Entity • Failure in receiving the ‘RRC Connection Setup Complete’

NBAP: RL Setup Request message and missing ‘NBAP Synchronisation Indication’
M1001C9 RRC_CONN_ACC_FAIL_RADIO
Start Tx/Rx •The RRC Access Failures are typically caused by the radio
failures which can be limited by improving the acquiring the
NBAP: RL Setup Response sych (make it faster i.e. reduce the N312 i.e. in synch
samples needed for the DL synch decision by the UE – it
ALCAP:ERQ should be noted that the recommended value is 1 sample,
parameter value 2) or increase the max DL power by
ALCAP:ECF decreasing the CPICHtoRefRABOffset

X
Start Tx/Rx
L1 Synchronisation
X
NBAP: Synchronisation Indication

X
Internal
UE Node B RNC
HC Entity
AC Entity • Failure in receiving the ‘RRC Connection Setup Complete’

NBAP: RL Setup Request message and ‘NBAP Synchronisation Indication’ is received
M1001C10 RRC_CONN_ACC_FAIL_MS
Start Tx/Rx
ALCAP:ERQ
ALCAP:ECF

X
Start Tx/Rx
L1 Synchronisation
X

X
Internal
UE Node B RNC
HC Entity
AC Entity
• RRC Connection Setup Complete
NBAP: RL Setup Request M1001C1 RRC_CONN_STP_COMP
Start Tx/Rx • If RNC has internal failure before ‘RRC Connection Setup
Complete’ has been received then the counter
NBAP: RL Setup Response M1001C11 RRC_CONN_ACC_FAIL_RNC
ALCAP:ERQ
ALCAP:ECF
Start Tx/Rx
L1 Synchronisation

X
Internal
• Received RRC Connection Setup Complete –message
RRC Access Phase (5) triggers:
M1001C8 RRC_CONN_ACC_COMP
M1006C23 RRC_CONN_SETUP_COMPL_SENT
UE Node B RNC • The number of RRC connection establishments by UEs by

category
HS-DSCH classes
HC Entity M1001C548 UE_SUPP_HSDSCH_CLASS_1_6
M1001C549 UE_SUPP_HSDSCH_CLASS_7_8
AC Entity M1001C550 UE_SUPP_HSDSCH_CLASS_9_10
M1001C551 UE_SUPP_HSDSCH_CLASS_11_12
M1001C389 UE_SUPPORT_FOR_IPHC
Start Tx/Rx (RFC2507 IP header compression)
M1001C404 ACCESS_STRATUM_REL_IND_4
(release indicator release 4)
(release indicator release 99)
ALCAP:ERQ M1001C406 UE_SUPPORT_GSM
(GSM)
ALCAP:ECF M1001C407 UE_SUPPORT_MULTICARRIER_CDMA
(multi-carrier CDMA)
[FACH] RRC: RRC Connection Setup M1001C408 UE_RXTX_POSITION_CAPAB_2
(RX-TX time difference positioning capability type 2)
Start Tx/Rx (access stratum release indicator release 5)
L1 Synchronisation (access stratum release indicator release 6)
M1001C641 UE_SUPPORT_GANHO
NBAP: Synchronisation Indication (Generic Access Network, GAN)
DSCH Classes
[DCH] RRC: RRC Connection Setup Complete M1001C610 UE_SUPP_EDCH_CATEGORY_1
M1001C611 UE_SUPP_EDCH_CATEGORY_2
Internal M1001C614 UE_SUPP_EDCH_CATEGORY_5
30 © Nokia Siemens Networks M1001C615 UE_SUPP_EDCH_CATEGORY_6
Percentage, %
31
Internal
0%
20%
40%
60%
80%
100%
11/1/2009
RNCname RNC_MALANG
11/2/2009
11/3/2009
11/4/2009
© Nokia Siemens Networks

11/5/2009
11/6/2009
11/7/2009
Data
11/8/2009
11/9/2009
11/10/2009
11/11/2009
RRC Access Failures
11/12/2009
Sum of RrcAccess_Fail_Radio_#
11/13/2009
11/14/2009
11/15/2009
RRC Access Failures
Date-Time
11/16/2009
11/17/2009
Sum of RrcAccess_Fail_Uu_#
11/18/2009
11/19/2009
11/20/2009
11/21/2009
11/22/2009
Sum of RrcAccess_Fail_RNC_#
11/23/2009
11/24/2009
11/25/2009
11/27/2009
11/28/2009
11/29/2009
11/30/2009
RRC Active Phase • If the RNC receives ‘RRC status’ message during ‘RRC
Connection’
UE Node B RNC M1006C102 RRC_STATUS_MS
(indicating some mismatch in RRC states between RNC and
[RACH] RRC:RRC Connection Request UE or some mismatch in the parameters)
HC Entity • If ‘RRC Status’ message is received with IE ‘Received
message type’ value PAGING TYPE 2 and with IE ‘Protocol
AC Entity error information’ set to the value of the variable
PROTOCOL_ERROR_INFORMATION,
NBAP: RL Setup Request M1006C103 RRC_STATUS_INVALID_PAGING2
Start Tx/Rx • If ‘RRC Status’ message is received with IE ‘Received
message type’ value SIGNALLING CONNECTION
NBAP: RL Setup Response RELEASE and IE ‘Protocol error information’ with value
‘Message not compatible with receiver state’,
ALCAP:ERQ M1006C104 RRC_STATUS_INVALID_CONFIG
ALCAP:ECF • If ‘RRC Status’ message is received with the IE ‘Protocol

error information’ containing IE ‘Protocol error cause’ set to
[FACH] RRC: RRC Connection Setup value ‘ASN.1 violation or encoding error’
M1006C105 RRC_STATUS_ASN1_VIOL_ENC_ERR
Start Tx/Rx
L1 Synchronisation
RRC Setup and Access
DCH] RRC: RRC Status

Internal
RAB Setup for CS (1)
• RANAP: RAB Assignment Request
M1003C8 RAB_ASS_REQ_BY_CN
UE Node B RNC MGW
• RAB Setup Attempts
RANAP: RAB Assignment Request M1001C66 RAB_STP_ATT_CS_VOICE
M1001C67 RAB_STP_ATT_CS_CONV
AC Entity • If the RNC rejects the CS Voice ‘RAB Assignment

Request’ due to AMR capacity license exceeded
M1001C619 RAB_STP_FAIL_CS_VOICE_LIC
NBAP: RL Reconfiguration Prepare
• In RAN04, when the CS RAB setup attempt is
NBAP: RL Reconfiguration Ready not started due to requested parameters not
supported by the UE or RNC, the ‘RAB Setup Attempt’
counters are not updated
M1001C256 RAB_STP_FAIL_CS_UE_CAPA
M1001C255 RAB_STP_FAIL_CS_NOT_SUPP_PAR
RANAP: RAB Assignment Response
Internal
UE Node B RNC MGW
AC Entity • ‘RAB Assignment Request’ Counters

M1002C12 REQ_CS_VOICE_IN_SRNC
M1002C50 REQ_CS_DATA_CONV_SRNC
(includes SHO, HHO and RAB setups for CS voice/CS
data)
NBAP: RL Reconfiguration Ready M1002C15 RT_DCH_INIT_VOICE_SRNC
M1002C56 RT REQ_CS_STREAM_REJ_UL_SRNC
(includes RAB setups for CS voice/CS data)
M1002C16 REQ_CS_VOICE_SRNC
M1002C58 RT DCH DHO REQ FOR CS DATA CALL
RANAP: RAB Assignment Response CONV CLASS IN SRNC
(includes DCH request only for RAB Voice/CS data
SHO)
• Separate for CS Voice and CS Conversational

• Separate for SRNC and DRNC
• In case the UL load (measured PrxTotal) exceeds

PrxTarget + PrxOffset or Prx_nc + Prx_nc exceeds
PrxTarget
M1002C13 REQ_CS_VOICE_REJ_UL_SRNC
M1002C52 REQ_CS_CONV_REJ_UL_SRNC
• In case the RAB assignment fails due to AC

M1003C13 RAB_ASS_NONSUCC_RNL
M1001C80 RAB_STP_FAIL_CS_VOICE_AC
M1001C85 RAB_STP_FAIL_CS_CONV_AC
Internal
UE Node B RNC MGW

data)
SHO)

• In case the DL load (measured PtxTotal) exceeds

PtxTarget + PtxOffset or Ptx_nc + Ptx_nc exceeds
PtxTarget
M1002C14 REQ_CS_VOICE_REJ_DL_SRNC
• In case the RAB assignment fails due to AC M1002C53 REQ_CS_CONV_REJ_dL_SRNC is
M1003C13 RAB_ASS_NONSUCC_RNL (includes SHO and RAB requests)
M1002C17 REQ_CS_VOICE_REJ_SRNC
M1001C80 RAB_STP_FAIL_CS_VOICE_AC M1002C61 RT_REQ_DATA_STREAM_REJ_SRNC
M1001C85 RAB_STP_FAIL_CS_CONV_AC (includes SHO only)
Internal
UE Node B RNC MGW

data)
SHO)


• Blocking Counters
M1000C81 NO_CODES_AVAILABLE_SF128
(AMR 12.2kbps)
M1000C79 NO_CODES_AVAILABLE_SF32
(CS CONV 64kbps)
Internal
UE Node B RNC MGW

data)
SHO)

• Duration counters are initialised • For successful AC in UL and DL (includes SHO)

(sampled continuously with 1s interval RN2.0 GCD3 M1002C18 ALLO_FOR_AMR_xx_UL_IN_SRNC
onwards) M1002C33 ALLO_FOR_AMR_xx_DL_IN_SRNC
M1002C34 DUR_FOR_AMR_xx_UL_IN_SRNC • For different bit rates in UL and DL (includes SHO)
M1002C49 DUR_FOR_AMR_xx_DL_IN_SRNC M1002C62 ALLO_TRAN_CS_CONV_xx_SRNC
M1002C66 ALLO_DUR_CS_CONV_UL_IN_SRNC M1002C65 ALLO_TRAN_CS_CONV_xx_SRNC
M1002C69 ALLO_DUR_CS_CONV_DL_IN_SRNC (incremented only in case BTS setup and AAL2
(incremented only in case BTS setup and AAL2 reservation are ok)
reservation are ok)
Internal
UE Node B RNC MGW
RANAP: RAB Assignment Request
AC Entity • AMR Codec Mode Set on SF128 {5.9, 4.75}

Selection for incoming call
NBAP: RL Reconfiguration Prepare M1002C561 AMR_LOWER_CODEC_SF128_INC
(This does not mean that SF128 would really be taken
into use but is just a proposal from the load control
NBAP: RL Reconfiguration Ready entity of a single cell in UEs active set.)
• AMR Codec Mode Set on SF256 {5.9, 4.75}

Selection for incoming call
M1002C561 AMR_LOWER_CODEC_SF256_INC
RANAP: RAB Assignment Response (This does not mean that SF256 would really be taken
into use but is just a proposal from the load control
entity of a single cell in UEs active set.)
Internal
RAB Setup for CS (6) • When RNC starts existing RL modification procedure
(to modify the RL set up for SRB and add the
requested service)
UE Node B RNC MGW M1005C78 RECONF_PREP_DCH_ADD_SRNC
M1005C79 RECONF_PREP_DCH_MOD_SRNC
RANAP: RAB Assignment Request M1005C132 REC_PREP_SRNC
• In case of Voice (AMR) call the

AC Entity M1005C78 RECONF_PREP_DCH_ADD_SRNC
(incremented by 3 as there are 3 individual RBs added
into the RL, for AMR class A, class B and class C bits)
M1005C79 RECONF_PREP_DCH_MOD_SRNC
(incremented even the SRB was setup as 3.4kbps)
NBAP: RL Reconfiguration Ready M1005C132 REC_PREP_SRNC
(incremented once)
Internal
• RL Reconfiguration Failure
UE Node B RNC MGW In RAS05 and WN3.0 onwards, SRNC
M1005C212 RECONF_ADD_FAIL_SRNC_RNL
RANAP: RAB Assignment Request M1005C213 RECONF_ADD_FAIL_SRNC_TRL
M1005C214 RECONF_ADD_FAIL_SRNC_PROT
M1005C215 RECONF_ADD_FAIL_SRNC_MISC
AC Entity In RAS05 and WN3.0 onwards, DRNC
M1005C216 RECONF_ADD_FAIL_DRNC_RNL
M1005C217 RECONF_ADD_FAIL_DRNC_TRL
M1005C218 RECONF_ADD_FAIL_DRNC_PROT
M1005C219 RECONF_ADD_FAIL_DRNC_MISC
NBAP: RL Reconfiguration Ready
In RAS5.1ED and RAS06
M1005C94 RECONF_ADD_FAIL_SRNC_BTS_NR
M1005C112 RECONF_ADD_FAIL_DRNC_BTS_NR
(incremented in case BTS does not respond in time
RANAP: RAB Assignment Response and response supervision timer expires in RNC)
• In case the BTS rejects the attempt,


Internal
• In case of successful resource reservation at the
UE Node B RNC MGW BTS the BTS sends ‘NBAP: RL Reconfiguration
Ready’ message
M1005C135 REC_PREP_SRNC_READY
RANAP: RAB Assignment Request
(counts all READY messages)
M1005C84 RECONF_DCH_ADD_SRNC_RDY
(counts only the READY messages due to ADD
AC Entity
requests)
M1005C85 RECONF_DCH_MOD_SRNC_RDY
NBAP: RL Reconfiguration Prepare (counts only the READY messages due to MOD
requests)
M1005C86 RECONF_DCH_DEL_SRNC_RDY
(counts only the READY messages due to DEL
requests)
• In case of voice calls the

M1005C84 RECONF_DCH_ADD_SRNC_RDY
(incremented 3 times, once for each added RB)
M1005C85 RECONF_DCH_MOD_SRNC_RDY
(incremented for modified SRB)
M1005C135 REC_PREP_SRNC_READY
(incremented once)
Internal
RAB Setup for CS (9) • Failure in AAL2 connection setups triggers ‘NBAP:RL
Reconfiguration Cancel’ message
M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
(incremented in ALL the BTSs in AS, even only one
UE Node B RNC MGW BTS Iub is having the problem)
RANAP:RAB Assignment Request • Blocking in AAL2 connection triggers

M1001C400 RAB SETUP FAILURES DUE TO IUB
AAL2 TRANS FOR CS VOICE
AC Entity (SPARE_2_SERVICELEVEL),
NBAP: RL Reconfiguration Prepare AAL2 TRANS FOR CS DATA CONV
(SPARE_3_SERVICELEVEL)
AAL2 TRANS FOR CS DATA STREAM
(SPARE_4_SERVICELEVEL),
ALCAP:ERQ
• When the RNC decides to reject the CS voice RAB
ALCAP:ECF request due to Iub transport resource shortage
between RNC and WBTS
NBAP: RL Reconfiguration Cancel • The number of RAB setup failures caused by Iub
AAL2 transport resource shortage due to RNC CAC
M1001C531 RAB_STP_FAIL_CS_V_IUB_AAL2,
RANAP:RAB Assignment Response
M1001C532 RAB_STP_FAIL_CS_CO_IUB_AAL2
M1001C533 RAB_STP_FAIL_CS_ST_IUB_AAL2
(replaces the RAN04 counters M1001C400,
M1001C401 and M1001C402 respectively)
• Failures in CS Voice RAB Setup due to Iur Transport • In case the AAL2 reservation failure or AAL2 setup
M1001C621RAB_STP_FAIL_CS_VOICE_IUR_TR failure
M1001C622RAB_STP_FAIL_CS_CONV_IUR_TR DUR_xxx counters (not incremented)
M1001C82 ALLO_xxx counters (not incremented)
M1001C87
• Failures in CS Voice RAB Setup due to Iu-CS
transport resource • In case the RAB assignment fails due to Iub
M1001C625 RAB_STP_FAIL_CS_VOICE_IU_CS M1003C14 RAB_ASS_NONSUCC_TRL
M1001C626 RAB_STP_FAIL_CS_CONV_IU_CS
Internal
M1001C82 M1001C82 RAB_STP_FAIL_CS_VOICE_TRANS
M1001C87 M1001C87 RAB_STP_FAIL_CS_CONV_TRANS
• AAL2 Setup Time Counter
UE Node B M1006C194SUM_TIME_AAL2_SETUP
RNC MGW
(difference between ‘ALCAP: Establishment Request’
and ‘ALCAP: Establishment Confirm’ messages
RANAP:RAB Assignment Request M1006C195DENOM_TIME_AAL2_SETUP
(denominator for M1006C194, used for average
calculation, updated by value 1, then the measured
AC Entity time is updated to counter M1006C194)
NBAP: RL Reconfiguration Prepare • After successful AAL2 connection setup ‘NBAP: RL

Reconfiguration Commit’ message is sent and new RL
NBAP: RL Reconfiguration Ready is taken into use
M1005C126 REC_COMM_SYNCH_SRNC
ALCAP:ERQ (counts all the RL Reconfiguration Commits (ADD,
MOD and DEL) )
ALCAP:ECF
• After successful ‘RL Reconfiguration Commit’, the
RNC tells the UE about the new DCH by sending
NBAP: RL Reconfiguration Commit
RRC: Radio Bearer Setup message
M1006C28 RB_SETUP
[DCH] RRC: Radio Bearer Setup
M1001C73 RAB_STP_COMP_CS_VOICE
[DCH] RRC: Radio Bearer Setup Failure M1001C74 RAB_STP_COMP_CS_CONV
RANAP:RAB Assignment Response • In case there is no ‘RRC: Radio Bearer Setup

Complete’ message received from the UE or UE
sends ‘RRC: Radio Bearer Setup Failure’ message
M1001C122 RAB_ACC_FAIL_CS_VOICE_MS
M1001C124 RAB_ACC_FAIL_CS_CONV_MS
Internal
UE Node B RNC MGW
• If at any instance during ‘RAB Assignment’
procedure, the RNC decides to reject the RAB setup c
RANAP:RAB Assignment Request M1001C83 RAB_STP_FAIL_CS_CONV_RNC
M1001C84 RAB_STP_FAIL_CS_VOICE_RNC
AC Entity
ALCAP:ERQ
ALCAP:ECF • In case of successful RAB Assignment counters:

M1003C11 RAB_ASS_SUCC
NBAP: RL Reconfiguration Commit M1001C115 RAB_ACC_COMP_CS_VOICE
M1001C116 RAB_ACC_COMP_CS_CONV
[DCH] RRC: Radio Bearer Setup M1006C29 RB_SETUP_COMPL
[DCH] RRC: Radio Bearer Setup Failure • RAB Setup Timer Counter
M1001C604 RAB_SETUP_TIME_MAX_CS_VOICE
RANAP:RAB Assignment Response M1001C605 RAB_SETUP_TIME_MAX_CS_CONV
M1001C606 RAB_SETUP_TIME_MAX_CS_STR
(amount of time that passed between a ‘RANAP: RAB
Assignment Request’ message and a ‘RANAP: RAB
Assignment Response’ message during an RAB
establishment
Internal
• AMR Codec Mode Downgrade to set {5.9, 4.75} on
RAB Setup for CS (11) SF128
M1002C563 LOAD_AMR_DGR_SF128_SUCCESS
(when RNC receives ‘RRC: Transport Channel
Reconfiguration Complete’ message from the UE
UE Node B RNC MGW indicating a successful AMR codec downgrade and
updated only for the cell that triggered the codec
downgrade)
RANAP:RAB Assignment Request
• AMR Code Mode Upgrade due to load thresholds

AC Entity M1002C565 LOAD_AMR_UPGRADE_SUCCESS
(when the RNC receives RRC: Transport Channel
NBAP: RL Reconfiguration Prepare indicating a successful AMR codec upgrade and
updated only for the cell that triggered the upgrade
NBAP: RL Reconfiguration Ready procedure)
ALCAP:ERQ
• AMR Codec Mode Downgrade to set {5.9, 4.75} on
ALCAP:ECF SF256
M1002C564 LOAD_AMR_DGR_SF256_SUCCESS
(when RNC receives ‘RRC: Transport Channel
NBAP: RL Reconfiguration Commit
indicating a successful AMR codec downgrade and
[DCH] RRC: Transport Channel Reconfiguration updated only for the cell that triggered the codec
[DCH] RRC: Transport Channel Reconfiguration Complete downgrade)
• AMR Codec Change Fail due to ICSU unit load

M1002C566 AMR_CODEC_CHANGE_FAIL_ICSU
(number of AMR codec changes prevented by the
ICSU unit load)
• AMR Codec Change Fail due to other reasons
M1002C567 AMR_CODEC_CHANGE_FAIL_OTHER
(number of AMR codec changes that failed due to
RANAP:RAB Assignment Response other reason than one of the following: ICSU load,
other active set cells do not have the needed AMR
mode set enabled, other active set cells are not in
underload state, the active set has changed during the
Internal last five seconds or another parallel procedure is
45 © Nokia Siemens Networks ongoing for the same UE)
RAB Setup Failures
RNCname RNC_BATAM1
RAB Setup Failures for CS Voice
100%
80%
60%
Percentage, %
40%
20%
0%
11/1/2009
11/2/2009
11/3/2009
11/4/2009
11/5/2009
11/6/2009
11/7/2009
11/8/2009
11/9/2009
11/10/2009
11/11/2009
11/12/2009
11/13/2009
11/14/2009
11/15/2009
11/16/2009
11/17/2009
11/18/2009
11/19/2009
11/20/2009
11/21/2009
11/22/2009
11/23/2009
11/24/2009
11/25/2009
11/27/2009
11/28/2009
11/29/2009
11/30/2009
Data
Sum of RabStp_Fail_AC_CsVoice_# Sum of RabStp_Fail_BTS_CsVoice_# Sum of RabStp_Fail_TRANS_CsVoice_# Sum of RabStp_Fail_RNC_CsVoice_# Sum of RabStp_Fail_FrznBts_CsVoice_#
Date-Time
Internal

3G RAN KPIs and Counters 20091216 p2

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3G RAN KPIs and Counters 20091216 p2

Enviado por

Direitos autorais:

Formatos disponíveis

3G RAN

Counters and Signaling

• The session will give an overview of the counters and

Different Scopes : Different Classifications of RAN KPI :

• Measures Radio Network Performance from the SRNCs perspective

Setup Access Active

All the counters of the Service Level

the ‘RRC CONNECTION NBAP: RL Setup Request

REQUEST’ message using the Start

PRACH channel and it is NBAP: RL Setup Response

completed when RNC, after ALCAP:ECF

reserving all the necessary [FACH] RRC: RRC Connection Setup

Connection (RNC, BTS, Radio L1 Synchronisation

and Transmission), replies with NBAP: Synchronisation Indication

DL ‘RRC CONNECTION SETUP’ [DCH] RRC: RRC Connection Setup Complete

message, carried over S-CCPCH

•Specific ‘RRC:RRC Connection Request’ counters with

• If ‘RRC Connection Request’ is rejected, the RNC will send

•Specific ‘RRC:RRC Connection Request’ counters with

• If ‘RRC Connection Request’ is rejected, the RNC will send

•Specific ‘RRC:RRC Connection Request’ counters with

• DCH allocation rejection triggers:

• If ‘RRC Connection Request’ is rejected, the RNC will send

•Specific ‘RRC:RRC Connection Request’ counters with

•Specific ‘RRC:RRC Connection Request’ counters with

NBAP: RL Setup Response • RL allocation rejection triggers:

• Radio Network Layer Cause:

• DCH allocation rejection triggers, in case the RRC

• If ‘RRC Connection Request’ is rejected, the RNC will send

• M800 and M548 provide more detailed information.

• If ‘RRC Connection Request’ is rejected, the RNC will send

NBAP: RL Setup Request

NBAP: RL Setup Response

ALCAP:ECF • When RRC Connection Setup was established

NBAP: RL Setup Request

NBAP: RL Setup Response

ALCAP:ERQ • In case the RNC receives new ‘RRC Connection Request’

© Nokia Siemens Networks

“RRC CONNECTION SETUP” NBAP: RL Setup Request

message to UE and it is Start

successfully completed upon NBAP: RL Setup Response

receiving UL “RRC ALCAP:ECF

CONNECTION SETUP [FACH] RRC: RRC Connection Setup

COMPLETE” message UE Start

transmits using the established L1 Synchronisation

dedicated channel NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete

This procedure can be quite

AC Entity • Failure in receiving the ‘RRC Connection Setup Complete’

[FACH] RRC: RRC Connection Setup

[DCH] RRC: RRC Connection Setup Complete

AC Entity • Failure in receiving the ‘RRC Connection Setup Complete’

NBAP: RL Setup Response

[FACH] RRC: RRC Connection Setup

[DCH] RRC: RRC Connection Setup Complete

[FACH] RRC: RRC Connection Setup

NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete

UE Node B RNC • The number of RRC connection establishments by UEs by

© Nokia Siemens Networks

ALCAP:ECF • If ‘RRC Status’ message is received with the IE ‘Protocol

NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete

RRC Setup and Access