2 - KPI Presentation Ver 1-8 Serv Lev

WCDMA RAN
Service level MEASUREMENT
RAN 1.5.2 ED2
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

Service Level Measurement
• The service level measurement is carried out in the serving RNC (SRNC)
• The object of the measurement is the WBTS/WCELL, which is the
reference cell
• In anchoring case, all active set cells belong to the drift RNC and the
serving RNC is not aware of their identifications.
• The best active set cell may change during the call: the object of the
measurement can be different for connection establishment and release
counters
• 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.

RRC and RAB Phases
Phase: Setup Access Active
Setup Access Active

complete Complete Complete
Succes
Access Active
Release
Active
Attempts Failures RRC Drop
Access Fails
Setups Failures, Blocking All the counters of the Sevice

Level Tabel are incremented only
for the reference cell

RRC Phases
UE RNC CORE
RRC Connection Request Event 1: RRC_CONN_STP_ATT
Event 1 incremented
Setup Phase Event 2: RRC_CONN_STP_COMP

RRC incremented
RRC Connection Setup
setup Event 2 Event 3: RRC_CONN_ACC_COMP
time incremented
Access Phase
Event 4: RRC_CONN_ACT_COMP
RRC Connection Setup Complete incremented
Event 3
Active Phase
Event 4 IU Release Command

H RRC Connection Counters
Failure Case:
RRC Connection Setup fails
RNC CN Due to
UE BTS Triggers:
1001C2 Handover control
RRC: Connection Request 1001C3 Admission control
Correctly Received message 1001C4 BTS
RRC Connection Setup Starts 1001C5 Transmission network
Triggers: 1001C6 RNC internal reason
1001C0 RRC Connection Attempt 1001C7 Frozen BTS
RRC Connection Setup phase
Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup Failure Case:
RRC Connection setup completed RRC Connection Access fails
Triggers: Due to
1001C1 RRC Con Setup Compl Triggers:
1001C9 L1 synchronization in BTS
RRC Connection Access phase 1001C10 UU interface
RNC waits reply from UE 1001C11 RNC internal reason
RRC: RRC Connection Setup Complete
RRC Connection Access completed Failure Case:
Triggers: RRC Connection Active fails
1001C8 RRC Con Acc Comp Due to
RRC: Initial Direct Transfer Triggers:
1001C15 Iu interface
RANAP: Initial UE Message
1001C16 Radio interface
1001C17 BTS
1001C18 Iur interface
RRC Connection Active phase 1001C19 Ciphering failure
UE-CN Signaling 1001C20 Integrity check
1001C21 RNC internal rea
RANAP: Iu Release Command
Special Reason:
RRC Connection Active completed RRC Connection Active
Triggers: Release Due to
1001C12 RRC Con Active Comp Triggers:
1001C13 SRNC Relocat
1001C14 Pre-emption

RRM algorithms in implementation - introduction 1/5
• “RRM” is divided between RNC, BTS and UE

• RNC (AC, PS, LC, RM, PC, HC, mapping of RAB QoS to RB QoS(L1/L2
parameters) )
• BTS (PC, reporting)
• UE (PC, reporting, mapping of application needs to UMTS QoS profile)
• We can also divide RRM in a cell and a connection specific
functions. There is many to many interaction between “call” and
“cell”.
• One call can be linked with many BTS/cells.
• One BTS/cell can be linked with many calls.
• HC and PC are connection specific
• AC, PS and LC are cell specific but they also have connection specific part
• RM (code tree management) is cell specific
Cell
• In the RNC RRM is implemented in the following PRBs:“Call”
RRUSEB(BRMPRB)
• AC,PS,LC,RM –cell specific
RRUSEB(HA3PRB)
• HC –connection specific
L3TSEB(RRCPRB/MCC-hand)
• AC,PS –connection specific
P2SEB(OLFTOR)
• PC (UL outer loop) - connection
specific
• SP5SEB (OLPC-entity) PC (UL outer loop) – DCH specific
• This presentation will concentrate mainly on HA3 and BRM.
RRM algorithms in implementation - introduction
Cell 1&2
4/5
LC,AC
MRC
(UL) PC NBAP-C
and RM
(UL) BRM-d
(BTS1)
L2
BTS1 HA3-d
NBAP-d
RRC/
MCC
CRNC,
DRNC
Connection
RNSAP
specific HC
RRC RRC
Cell 3 RRC/
RRC-d
LC,AC,P
S and HA3-d
PC MRC RM
UE (DL) (DL)
NBAP-C BRM-d RRC/
(BTS2) MCC
Connection
MDC = Macro diversity Combining BTS2 specificCN
AC
RANAP
MRC = Maximal Ratio Combining NBAP-d and PS
PC = Power Control
HA3-d = Handover Control
BRM = Base Station Resource Manager MDC PC L2 CRNC,
MCC = "Mobile Connection Control" MRC PC
(UL) (UL) (UL) SRNC
RRC-d = RRC protocol entity (UL)

RRM algorithms in implementation – RRUSEB and L3TSEB 1/3
MS
BTS/cell specific hand
Call specific hand
ICSU #n
ICSU #2
Uu
ICSU #1
RRUSEB L3TSEB Iu signalling function block
BTS radio resource manager function RANAP protocol management
block(BRMFB) program block
BTS radio resource manager Iu CN
UU signalling & connection management RANAP RANAP-d
program block (BRMPRB) function block master
BRM RRC protocol & connection
master
management program block
(RRCPRB) Iub signalling function block
BRM-d RRC NBAP protocol management
MCC
master program block
NBAP Iub BS
master
RRC-d RRC-C NBAP-C NBAP-d
Handover control function block (HA3FB)
RRC-S
Handover control program block Iur signalling function block
(HA3PRB)
RNSAP protocol
HA3PRB HA3-d management program
master
block Iur DRNC
RNSAP-d RNSAP
master
OMU DMCU RRMU

ATCSEB
WCDMA L2, L1 and Outer loop Signalling connection control
RNC-NEMU power control services function block
Performance
Measurement
Interconnector
RLC MAC Signalling
connection control
program block
AGSSEB (RC3)
Statistics Outer Loop

measurement Power Control
program block
(PMIPRB)

RRM algorithms in implementation – RRC
RRCPRB
• The RRCPRB offers signaling connections towards the MS and call control functionality.
• The RRCPRB is located in ICSU.
• The program block is divided into four parts:
• MS Connection Control,
• RRC Common for idle mode,
• RRC Dedicated for connected mode,
• RRC System information for scheduling and segmentation of the system information to be
broadcasted.
MS Connection Control (MCC) controls the connection between MS , RNC, and CN. MS Connection
Control composes the transport channel parameters and controls the packet transfer states according
to the inactivity indication from MAC-layer. MS Connection Control also requests the capacity from
RRM and controls admission decision procedure in active set level. MS Connection Control produces
the RLC parameters needed in L1/L2 services/RLC. There will be one MS Connection Control per MS in
SRNC. In DRNC there will be another MS Connection Control, which controls the RL procedures in
DRNC.
The DRNC's MS Connection Control does not have an RRC connection (RRC-D).
RRC-C handles the RACH/FACH signaling towards the MS when there is no RRC connection. There will
be one RRC-C per cell and it is created when RACH/FACH is created.
RRC-D handles the signaling procedures when the mobile has the RRC connection. There will be one
RRC-D per MS in SRNC and it is created every time MS makes the connection establishment and it is
released when connection is released.
RRC-S handles the system information scheduling, segmentation, and broadcasting. There will be one
RRC-S per cell and it is created at the time of RACH/FACH creation.
RRM algorithms in implementation – L3TSEB 1/xx
IUVPRB
The IUVRB offers signaling connections to the CN. The IUVPRB program block is located in ICSU.
The program block handles the RANAP procedures, e.g. Bearer setup, Bearer reconfiguration and
Bearer release towards the CN. There will be one RANAP per MS per one CN.
IURPRB
The IURPRB offers signaling connections between RNCs. The IURPRB is located in ICSU. The
program
block handles the RNSAP procedures towards the other RNC. There will be one or more RNSAP per
one MS, depending on the number of neighbor RNCs. Thus, there will be one RNSAP per one MS per
neighbor RNC.
NBAPRB
The NBAPRB offers signaling connections to the BS. The NBAPRB program block is located in ICSU.
The program block is divided into two parts NBAP Common and NBAP Dedicated.
NBAP-C offers common procedures of NBAP L3 signaling protocol towards BS, e.g. RL setup,
Broadcast information, and BS configuration procedures. There will be one NBAP-C per one BS.
NBAP-D on the other hand, offers dedicated procedures of NPAB L3 signaling protocol towards BS,
e.g. RL reconfiguration and release procedures. There will be one NBAP-D per one BS traffic
termination point (TTP).

RRM algorithms in implementation – BRM 1/3
BRMPRB (Base station Resource Manager)

Main functionality of BRM are:
• Load Control
• Admission Control,
• Packet Scheduler,
• Code Management
There is one BRM hand (BRM-d) for each BTS, and this hand controls all cells under the BTS. +
Interfaces (8):
• NBAP-C: start of BRM-d, Radio resource indication (RRI), creation, modification and
release of RACH/FACH/PCH
• NBAP-d: radio link measurement reporting
• MCC: resource allocations/modifications/release
• MAC-c: BRM indicates to MAC if common channels can/can’t be used for data transfer in DL
• REKOVE: informs the cell activity state to BRMPRB
• RAKTOR: RNW parameters
• RAILIB: RNW parameters
• PMIPRB: counters
Measurements
• Radio resource indication (RRI), period 100ms-2s
• Radio link measurement, period 0,5 s

RRM algorithms in implementation – HA3 1/3
HA3PRB (Handover Algorithm)

There is one HA3 hand (HA3-d) for each call.
Interfaces (7):
• MCC : start/release of HA3-d,start of handovers, iur-dedicated measurement reports
• RRC-d : RRC:measurement reports, measurement control
• NBAP-d : radio link sync/failure indications, radio link reports
• RAKTOR : RNW parameters
• RAILIB : RNW parameters
• PMIPRB (DI5STA) : counters
• OLFTOR : UL quality deterioration report
Measurements in RN1.5 (ED2):
• RRC: INTRA-FREQUENCY MEASUREMENT, CPICH EcNo (1a,1b,1c), event triggered

• RRC: INTER-FREQUENCY MEASUREMENT, periodical
• RRC: INTER-RAT MEASUREMENT. Periodical
• RRC: INTRA-FREQUENCY MEASUREMENT, CPICH EcNo (1e,1f) , event triggered
• RRC: UE INTERNAL MEASUREMENT, Rx<>Tx difference, event triggered
• RRC: UE INTERNAL MEASUREMENT, TxPwr, event triggered
• RRC: INTRA-FREQUENCY MEASUREMENT, CPICH RSCP (1e,1f) , event triggered
• NBAP:RADIO LINK MEASUREMET
• RNSAP:DEDICATED MEASUREMENT (radio link)

RRM algorithms in implementation – NRM
NRMPRB (Transport Resource Manager)
NRM handles the transport resource reservation, modification and releasing in
applications level in RNC.
It provides an interface between radio releted applications (e.g. MC Connection
Controller and Radio Resource Controller) and the transport related applications
provided by the switching platform

RRC Setup Phase
• This phase starts when UE sends the “RRC
CONNECTION REQUEST” message using the
PRACH channel and it is completed when RNC,
after reserving all the necessary resources for the Node B
RRC Connection (RNC, BTS, Radio and UE RNC
Transmission), replies with DL “RRC RRC: RRC Connection Request (RACH)
CONNECTION SETUP” message, carried over S- NBAP: Radio Link Setup Request
CCPCH (FACH sub-channel). NBAP: Radio Link Setup Response
• This procedure is not affected bu UE’s behavoiur, ALCAP: Establish Request

provided that RACH has been detected by RNC.
ALCAP: Establish Confirm
• New counter in ED2: RRC Conn Setup Att
Repeats: FP: Downlink Sync
• The number of RRC Connection Request

FP: Uplink Sync
retransmissions (successfully received by the RNC) RRC: RRC Connection Setup (FACH)
from the same UE if the RRC Connection Request is
rejected due to unsuccessful resource reservation L1 Synchronisation
attempt in RNC. NBAP: Synchronisation Indication
• UPDATED: When a repeated RRC CONNECTION RRC: RRC Connection Setup Complete (DCH)
REQUEST is received from the same UE as the first
RRC CONNECTION REQUEST during UE-ID
buffering time (UEIDBuffTime='Wait
Time'+N300+T300) after RRC CONNECTION
REJECT has been sent to this UE

RRC Setup Failures
• RRC Setup Failure for HC
• RRC Setup Failure for AC
• RRC Setup Failure for BTS
• RRC Setup Failure for Transmission
• RRC Setup Failure for BTS frozen
• RRC Setup Failure for RNC internal reason

RRC Setup Failures HC
• RRC Setup Failure for HC
• HA3 is the first program block
• HA3 master doesn't recognise cell when it is asked to start handover
control in RRC setup.
• Failure for HC due to "wcel_not_exist“ from PM ticket anlaysis
(start_ho_control_nack): in one ICSU the BTS was not existing for some
problems in RACKTOR process (ICSU restart).

RRC Setup Failures AC
• RRC Setup Failure for AC:
• AC control can block the call at RRC level if Target + Offset is exceeded (overload area)
• UL or DL blocking? Check Cell Resource counters (prx/ptx total)
• In general it’s possible to check the AC blocking in rrc setup phase by checking the Traffic counters:
• DCH_REQ_LINK_REJ_UL_SRNC
• DCH_REQ_LINK_REJ_DL_SRNC
even if the numbers are not comparable because traffic counters include requests
for SHO
• Preemption works at this level (check counter for rrc release due to preemption
(RRC_CONN_ACT_REL_P_EMP)
• Main failure reasons from PM ticket analysis:
• rrc_conn_req_nack (Cell ovelrad)
• pre_emption_failure (no cell found) no more in ED2

RRC Setup Failures BTS
• RRC Setup Failure for BTS:
• main failure reasons from PM tickets:
• rl_setup_failure (hardware_overload) migth be some WSP problems
• This failure should be mapped into Iub Table counters related to the Radio Link setup
failure :
• SETUP_FAIL_RL_NOT_ENOUGH_RES
• From PM Ticket:
• Reason: rl_setup_failure_c
• Detailed reason: not_enough_resources_c
Node B
UE RNC
RRC: RRC Connection Request (RACH)
NBAP: Radio Link Setup Request
NBAP: Radio Link Setup Response
ALCAP: Establish Request
FP: Downlink Sync
FP: Uplink Sync

RRC: RRC Connection Setup (FACH)
L1 Synchronisation
NBAP: Synchronisation Indication

RRC: RRC Connection Setup Complete (DCH)

RRC Setup Failures Trans
• RRC Setup Failure for Transmission:
• Main failure reason from PM ticekt is serv_req_nack_from_nrm meaning some
problem in setting up AAL2 transmission resources in Iub
• NRM is in-charged of Iub capacity
• After cpacity check, there is AAL2 signalling starts
• Counter is incremented if:
• No Iub capacity
• AAL2 setup fails

AAL2 Setup over Iub
• The resource reservation is performed in such order that all CAC reservations for RNC
internal and external (AAL2 path) resources are done before signaling.
• If the CAC actions are successfully completed, the signaling is started and RNC asks
BTS to arrange its resources accordingly.
• If the CAC actions fail, the signaling phase is not started at all and the signaling counters
are not aware of the connections rejected due to RNC AAL2 layer CAC.
AAL2 user plane setup over Iub (MOC)
BTS (WAM) RNC
UE AAL2 SIG CAC RRC: connection request
CAC AAL2SIG ATM RM RRC
Transport res. reserv. req.

resource reservation
Possible NACK
ERQ (SUGR) AAL2 connection establishement
resource reservation
Possible NACK
ECF
AAL2 conn. estab. confirmation
RRC:connection setup
1 © NOKIA
Others RRC Setup Failures
• RRC Setup Failure Frozen BTS: the AC blocks RL establishment to setup
emergency call and in case of pre-emption / when BTS is frozen no new
RRC connection are allowed)
• RRC Setup Failure for RNC internal reason: all other failure reanos (e.g.
parameter mismatch, timer expiry)

RRC Access Phase
• It begins when RNC sends DL “RRC
CONNECTION SETUP” message to UE and
it is successfully completed upon receiving UL
“RRC CONNECTION SETUP COMPLETE” Node B
UE RNC
message UE transmits using the established
RRC: RRC Connection Request (RACH)
dedicated channel.
NBAP: Radio Link Setup Request
• This procedure can be quite critical since it
includes both UL and DL L1 synchronization NBAP: Radio Link Setup Response
of the signalling dedicated channel to be ALCAP: Establish Request

setup
• New Counter: RRC Conn Acc Relase due to
cell reselection FP: Downlink Sync
• The number of RRC Connection Access

FP: Uplink Sync
releases due to cell reselection. This is the case
RRC: RRC Connection Setup (FACH)
when the UE has sent a new RRC connection
request to the new cell while the RRC L1 Synchronisation
connection setup phase is still ongoing in the
old cell. The RNC releases resources for the NBAP: Synchronisation Indication
old RRC connection attempt. RRC: RRC Connection Setup Complete (DCH)
• UPDATED: When the RRC Connection attempt
is released before the RRC Connection Setup
Complete is received from the UE due to a new
RRC Connection Request to another cell.

RRC Access Failures
• RRC Access Failures for L1 synchronization
• RRC Access Failures for UU interface
• RRC Access Failures for RNC internal reasons

RRC Access Failures L1 Synch
• The counter RRC_CONN_ACC_FAIL_RADIO is updated if the timer
T_RRC_Resp_CCH expires (6 seconds) without receiving the RRC CONNECTION
SETUP COMPLETE and RNC has not received SYNCHRONIZATION INDICATION
message from Node B yet.
• This can happen in the following scenarios:
• UE does not receive the RRC CONNECTION SETUP (for poor coverage, DL
interference, cell reselection)
• UE correctly receives RRC CONNECTION SETUP message but it is not able to establish
DL L1 synchronization ( a new RRC CONNECTION REQUEST will be submitted)
• Registration attempt by roaming
• UE is successful in establishing the dedicated physical channel for signalling purposes
and after sending some UL frames for UL synchro purposes (default is 14) but the BTS is
not able to get UL synchronization so it does not send NBAP “SYNCHRONIZATION
INDICATION” to RNC
L1 Synchronisation

X
UE BTS
X RNC

RRC Access Failures MS
• The counter RRC_CONN_ACC_FAIL_MS is updated if the BTS succeeds
in establishinf L1 synchro (SYNCHRONIZATION INDICATION is sent to
RNC) but RNC does not receive UL RRC CONNECTION SETUP
COMPLETE within timer T_RRC_Resp_CCH (default is 6 s from the
establishment of Radio Link resources on Iub)
L1 Synchronisation
UE BTS
X RNC

L RRC Setup Time KPI
• The result represents the average time to successfully establish an RRC
connection. A successful RRC connection is defined as one for which the RNC
receives the uplink RRC CONNECTION SETUP COMPLETE message.
UE RNC
/ 100s 
RRC Connection Request AVE _ RRC _ SETUP _ TM
RRC Connection Setup DENOM _ RRC _ SETUP _ TM
RRC Connection Setup Complete
X Triggering Point
• The AVG_RRC_SETUP_TM counter records the time between the RNC receiving
the RRC CONNECTION REQUEST message and receiving the RRC
CONNECTION SETUP COMPLETE message:
• The counter sums the times for all successful RRC connection
establishments.
• The DENOM_RRC_SETUP_TM is incremented by 1 after every successful RRC
connection establishment.
• The factor of 100 appearing within the KPI calculation is a result of Nokia’s
internal representation of the counter value. Nokia uses a 10 ms unit for the
AVG_RRC_SETUP_TM counter.
• The KPI is meaningful only for cell level and on hour basis

RRC Active Failures
• RRC Active Failures for Iu interface
• RRC Active Failures for Radio interface
• RRC Active Failures for BTS
• RRC Active Failures for Iur interface
• RRC Active Failures for Ciphering failure
• RRC Active Failures for Integrity check
• RRC Active Failures for RNC internal
reason
• Most of the failures are:

• RNC internal
• Radio
• IU
The cause of the RANAP: IU RELEASE
COMMAND message does not have any
effect on counter updates
If the CN starts the release of the Iu
signalling connection the RNC always
updates the RRC active complete counter
The faiulre counters are update if the RNC
sends RANAP: IU RELEASE REQUEST

RRC Active Failure for IU
• RRC_CONN_ACT_FAIL_IU : number of active RRC connection failures
caused by Iu interface-related problems (for example the signalling
connection fails between the RNC and CN)
• For example due to wrong parameter setting in MSC (INFO IN SCCP C-
REF MESSAGE SUPPORTED was enable), this counter was
incremented during the detach procedure nevertheless the detach was
successfully
• From PM ticket there are some IU failure due to “radio_link_failure RRC ACT FAIL IU
(timer_expired): need further investigations 2000 100
1800 90
1600 80
1400 70
RRC FAIL IU
1200 60
RRC COMP
RRC ACC COMPLETE

1000 50
RRC ACT FAIL IU
800 40
600 30
400 20
200 10
0 0
01.Oct
02.Oct
03.Oct
04.Oct
05.Oct
06.Oct
07.Oct
08.Oct
09.Oct
13.Oct
14.Oct
15.Oct
16.Oct
17.Oct
18.Oct
19.Oct
20.Oct
21.Oct
22.Oct
23.Oct
24.Oct
25.Oct
27.Oct
28.Oct
DAY

Network KPI: RRC Active Failure IU
• From benchmarking poor performance in RRC Abnormal release
RRC_CONN_ACT_FAIL_IU
50% 4th of March

45%
40%
35%
30%
25%
20%
15%
10%
5%
0%
20040201
20040203
20040205
20040207
20040209
20040211
20040213
20040215
20040217
20040219
20040221
20040223
20040225
20040227
20040229
20040302
20040304
20040307
20040309
20040311
20040313
20040315
20040317
20040319
20040321
20040323
From PMI Tickets
RRC Active Failure for

IU reason is triggered
during the detach
procedure

Log for Detach Procedure
RRC Connection Request

for detach

Iu release
Release command for

IU does not specify
any reason
rrcprb
d8ad iuv_iu_release_command_s
rrcprb
d8ad iuv_iu_release_command_s No release
rrcprb
d4f5 rrc_connection_release_req_s
reason
rrcprb specified
rrcprb

RRC release
Release command for

RRC is: “unspecified”
rrcprb
rrcprb
rrcprb
rrcprb
rrcprb

Failure Reason
RRC Active Failure due

to IU is incremented even
if the detach procedure
is successfull.
Solution:
MSC parameter: “INFO
IN SCCP CREF-MESSAGE
SUPPORTED” has been
changed from "NO" to
“yes” (4th of March)
due to upload of
BSSAP default
parameter on MSC
RRC Active Failure for Radio
• RRC_CONN_ACT_FAIL_RADIO : from PM ticket the main reason are:
• “radio_link_failure” (radio_conn_los) due to the loss of UL

sinchronisation of the BTS (the BTS sends RADIO LINK FAILURE
message to the RNC)
• “no_resp_from_rlc”

Example of Radio Link Failure
RRC Connection Request for Registration

with good RF condition EcNo=-4
11:34:13.14

Initial synchronisation is ok
RRC Setup Complete
11:34:14.05

Radio Link Failure

(11:34:18.03)
Periodic message T_arlf= 5 s
11:34:23.04
No L1 sync re-establishment 
Iu release request after
T_L1_Sync_ReEstab_Wait = 6s
(11:34:24:54)

Phase: RRC Active Failure

Failure: Radio Interface
Reason: Radio Link Failure

Example of “no response from rlc”
RRC Connection Setup in bad

coverage area:
SC = 110
EcNo= -13.5

Pilot Pollution area:

SC 110EcNo=-17.5 dB
SC 258EcNo =-14.5 dB

Radio link failure

11:42:44,07
Synchronisatio re-
establishment before
timer expires
11:42:44.09
Iu Release Request
cause unspecific failure
11:42:48,32 upper
layer failure

RRC Connection
Active Failure
Radio Interface
No response from rlc

RRC Connection KPIs
UE RNC CN
BTS
RRC: Connection Request
Correctly Received message
RRC Connection Setup Starts
Triggers:
1001C0 RRC Connection Attempt RRC Setup Complete Ratio [%]
RRC Connection Setup phase
Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup RRC Setup and
RRC Connection setup completed
Triggers: Access Complete Ratio [%]
1001C1 RRC Con Setup Compl
RRC Connection Access phase
RNC waits reply from UE Special Reason:
RRC Connection Active
RRC: RRC Connection Completed Release Due to
RRC Connection Access completed Triggers:
Triggers: 1001C13 SRNC Relocation
1001C8 RRC Con Acc Comp 1001C14 Pre-emption
RRC: Initial Direct Transfer
RRC Connection Active phase RRC Drop Ratio [%]

UE-CN Signaling
RRC Connection Active completed

Triggers:
1001C12 RRC Con Active Comp

H RRC Connection Setup and Access KPIs
• This KPI does not necessarily represent the UE perception of RRC
connection success rate.
• If PRACH coverage is inadequate the RNC may not receive the RRC
CONNECTION REQUEST message. The RRC connection attempt would
then fail without the RNC having any knowledge of the attempt.
• In case of failure Layer 3 of the UE will re-attempt failed RRC connections as
defined by the parameters N300 and T300
*100%
RRC _ CONN _ STP _ CMP
RRC _ Setup _ Comp _ Rate 
RRC _ CONN _ STP _ ATT
*100%
RRC _ CONN _ ACC _ CMP
RRC _ Estab _ Comp _ Rate 
• The KPI is meaningful for cluster/cell level and on day/hour basis

RRC CONN REQ HANDLING – CD3
• SCENARIO2:
• Mobile sends 4 RRC CONNECTION REQUEST msg and RNC

answers 4 times (N300=3) with RRC CONNECTION REJECT (e.g.
due to congestion)
UE RNC
RRC Connection Request M1001C0 RRC_CONN_STP_ATT=4
M1001C1 RRC_CONN_STP_COMP=0
RRC Connection Reject M1001C8 RRC_CONN_ACC_COMP=0
RRC Connection Reject M1001C242 RRC_CONN_STP_ATT_REPET=3

RRC Connection Reject

THE USER PERCEIVES 4-3=1 FAILURE ONLY
RRC Connection Reject

RRC CONN REQ HANDLING – CD3
• SCENARIO3: CELL RESELECTION
NEW COUNTER HAS
IMPACT ON RRC ACCESS M1001C0 RRC_CONN_STP_ATT (A)=1
M1001C1 RRC_CONN_STP_COMP (A)=1
UE RNC M1001C8 RRC_CONN_ACC_COMP (A)=0
Cell A
M1001C0 RRC_CONN_STP_ATT (B)=1
RRC Connection Setup M1001C1 RRC_CONN_STP_COMP (B)=1
Cell A
M1001C8 RRC_CONN_ACC_COMP (B)=1
Cell B
RRC Connection Setup M1001C241 RRC_CONN_ACC_REL_RESEL (A)=1
Cell B
RRC Conn Setup Complete

Cell B
NO PROBLEM FOR THE USER AND CELL B; CELL A COUNTS 1 RESELECTION

New (CD03) RC Connection Setup and
Access KPIs
• After CD03 new RRC counters are implemented:
• RRC Connection Setup repetition
• RRC Connection Access for cell reselection
• New formula for KPIs:

*100%
RRC _ Setup _ Comp _ Rate _ user 
RRC _ CONN _ STP _ ATT  RRC _ SETUP _ ATT _ REPEAT
*100%
RRC _ Setup _ Comp _ Rate _ network 
*100%
RRC _ Estab _ Comp _ Rate _ user 
RRC _ CONN _ STP _ ATT  RRC _ SETUP _ ATT _ REPEAT 
RRC _ CONN _ ACC _ REL _ CELL _ RES
*100%
RRC _ Estab _ Comp _ Rate _ netw 
RRC _ CONN _ STP _ ATT  RRC _ CONN _ ACC _ REL _ CELL _ RES

H RRC Drop Rate KPI
• There are two formulas for RRC Drop Rate: Drop migth be due to problems
in the traget cell e.g. SHO failure
Nromal RRC releases are taken into account
RRC _ CONN _ ACT _ COMP  RRC _ CONN _ ACT _ REL _ P _ EMP  RRC _ CONN _ ACT _ REL _ SRNC
100  100 * %
RRC _ CONN _ ACC _ COMP
• UE mobility may cause this KPI to exceed 100 % or become negative i.e. a UE
establishes its RRC connection in one cell and then releases it in a different cell.
RRC rlease failures are taken into account
 RRC _ CONN _ ACT _ FAIL _ xxx

100 *
all _ failures
%
RRC _ CONN _ ACT _ COMP   RRC _ CONN _ ACT _ FAIL _ xxx
all _ failures
• Some of the failures might not be counted


RRC drop formula comparison
• RNC level
RRC Drop
12.00%
10.00%
Drop Rate [%]
8.00% RRC Drop RRC Act

Compl
6.00%
RRC Drop with
4.00% failures
2.00%
0.00%
20040517
20040518
20040519
20040520
20040521
20040522
20040523
20040524
Day

H RRC Connection by Attempt Cause
RRC Connection Setup
due to Cause
Triggers:
UE RNC CN
BTS 1001C22 MOC conv call att
1001C24 MOC stream call att
RRC: Connection Request 1001C26 MOC interac call att
1001C28 MOC backgr call att
Correctly Received message 1001C30 MOC subscribed call att
Triggers: 1001C32 MTC conv call att
1001C0 RRC Connection Attempt 1001C34 MTC stream call att
1001C36 MTC interac call att
RRC Connection Setup phase 1001C38 MTC backgr call att
Resource Reservation in RNC, BTS, Transmission 1001C40 Emergency call att
RRC: RRC Connection Request Setup 1001C42 Inter RAT cell reselection
RRC Connection setup completed 1001C44 Inter RAT cell chng ord
Triggers: 1001C46 Registration attempt
1001C1 RRC Con Setup Compl 1001C48 Detach attempt
1001C50 MOC high prior signaling
RRC Connection Access phase 1001C52 MTC high prior signaling
RNC waits reply from UE 1001C54 MOC low prior signaling
RRC: RRC Connection Completed 1001C56 MTC high prior signaling
1001C58 Call re establishment att
RRC Connection Access completed 1001C60 Terminating cause
Triggers: unknown
1001C8 RRC Con Acc Comp
RRC: Initial Direct Transfer
RRC Connection Active phase

UE-CN Signaling

Triggers:

H RRC Connection Failures by Attempt Cause
Only Setup and
UE RNC CN Access Phases
BTS
RRC: Connection Request
Correctly Received message Failures by RRC Connection
Triggers: Setup Causes
1001C0 RRC Connection Attempt Triggers:
1001C23 MOC conv call failure
RRC Connection Setup phase 1001C25 MOC stream call failure
Resource Reservation in RNC, BTS, Transmission 1001C27 MOC interac call failure
1001C29 MOC backgr call failure
RRC: RRC Connection Request Setup 1001C31 MOC subscribed call fail
RRC Connection setup completed 1001C33 MTC conv call failure
Triggers: 1001C35 MTC stream call failure
1001C1 RRC Con Setup Compl 1001C37 MTC interac call failure
1001C39 MTC backgr call failure
RRC Connection Access phase 1001C41 Emergency call failure
RNC waits reply from UE
1001C43 Inter RAT cell reselec fail
RRC: RRC Connection Completed 1001C45 Inter RAT cell chng ord fail
RRC Connection Access completed 1001C47 Registration attempt fai
Triggers: 1001C49 Detach attempt failure
1001C8 RRC Con Acc Comp 1001C51 MOC high prior sig failure
RRC: Initial Direct Transfer 1001C53 MTC high prior sig failure
1001C55 MOC low prior sig failure
1001C57 MTC high prior sig failure
1001C59 Call re establishment fail
1001C61 Terminating cause
RRC Connection Active phase unknown failure
UE-CN Signaling

Triggers:

M RRC Establishment KPI by attempt Cause
RRC _ Conn _ Failure _ cs _ conv

RRC _ Establisment _ Succ _ Rate _ cs _ conv  1 
RRC _ Conn _ Att _ cs _ conv
• This KPI considers only the RRC Connection Establishment Procedures

due to a Voice or a CS/PS Conversational Call.
• At the moment it is not possible to measure the RRC Connection
Establishment Failure Rate for Background and Interactive services.
• In fact when the mobile tries to make a PS call, the RRC Connection
can be attempted with several causes and so it is difficult to identify
which counters have to be considered at the denominator of the
formula.

H Registration Success Rate
• Typically registration success rate shows worse results than other RRC
resons this is due to bad UEs in roaming.
REGISTRATI ON _ FAILS
Re gistration _ Succ _ Rate  1 
REGISTRATI ON _ ATTS
RRC Success Rate & Reg attempts Success Rate
300000 100.0
99.0
250000
98.0
97 97
97 97 97
97
RRC & Reg. Attempts
200000 97 97 97 97.0
97 97 97 97 RRC_Setup_attempts
96.0 Registration_attempts
150000 RRC_Setup_succ
95
95.0 RRC_Setup_and_Access
Registration_Success
100000 94.0
93.0
50000
92.0
0 91.0
4
8
/2
/2
/2
/2
/2
/2
/0
/0
/0
/0
/0
/0
/0
/0
02
02
02
02
02
02
03
03
03
03
03
03
03
03
/
/
04
04
04
04
04
04
04
04
04
04
04
04
04
04
• The KPI is meaningful for cluster/cell level
20
20
20
20
20
20
20
20
20
20
20
20
20
20
Date and on day/hour basis
HOW MANY SYNCHRO FAIL DURING REGISTRATION?

• FILTERING THAT SUBSCRIBER SEVERAL ATTEMPTS CAN BE SEEN

VERY CLOSE TO EACH OTHER
SUSPICIOUS ARISES
?????

FIRST ATTEMPT
RRC CONNECTION SETUP IS SENT TO UE.....

No new RRC Conn Req after T300 The UE receives the message
...BUT NO UL SYNCHRO INDICATION IS RECEIVED WITHIN T_RRC_RESP_CCH (6 seconds)
COUNTER RRC_CONN_ACC_FAIL_RADIO IS INCREMENTED

FIRST ATTEMPT
WHO IS TRYING TO
ACCESS VF-IT
NETWORK?

RRC CONNECTION REQUEST with ICSU
EcNo=-[(48-28)/2]-0.5= -10.5 dB
EST CAUSE
RRC CONNECTION REQUEST
CELL ID

RRC CONNECTION REQUEST with ICSU
TMSI=25 11 30 37
LAI = MCC + MNC + stored LAC = 222 99 10202
3 ITALY SUBSCRIBER roaming in VF Network

SECOND ATTEMPT
ACCESS PHASE IS COMPLETED NOW BUT.....

SECOND ATTEMPT
...H3G USER CAN NOT GET REGISTRATION !!!

LOCATION UPDATING REJECT
When the MS is informed that an LA is

forbidden, the LA is added to a list of
"forbidden LAs for roaming"
which is stored in the MS. This list is
deleted when the MS is switched off or
when the SIM is removed.
05=0000 0101 =Mobility Management (from TS 24.007,11.2.3.1.1)

04=0000 0100 =LOCATION UPDATING REJECT (from TS24.008,10.4)
0D=0000 1101 =Roaming not allowed in this location area (from TS 24.007, 10.5.3.6)

H RAB Phases
UE RNC CORE
RAB Assignment Request (setup) Event 1: RAB_STP_ATT_xxx

Event 1 incremented
setup Event 2: RAB_STP_COMP_xxx
Radio Bearer Setup incremented
Event 2
Radio Bearer Setup Complete Event 3: RAB_ACC_COMP_xxx
incremented
acces
s Event 4: RAB_ACT_COMP_xxx
RAB Assignment Response incremented
Event 3
active
Event 4 RAB Assignment Request (release)

Iu Release Command
RAB Assignment Response
Iu Release Request

H RAB Setup & Access phases RAB Setup starts
Depending on RAB Type
Triggers:
1001C66 RAB setup att for CS Voice
UE BTS RNC CN 1001C67 RAB setup att for CS Data conv clas
1001C68 RAB setup att for CS Data stream c
1001C69 RAB setup att for PS Data conv clas
RRC Connection Active phase 1001C70 RAB setup att for PS Data stream c
UE-CN Signaling 1001C71 RAB setup att for PS Data intera cla
RANAP: RAB Assignment Request 1001C72 RAB setup att for PS Data backgr c
RAB Setup Completed

Depending on RAB Type
RAB Setup phase Triggers:
Resource Reservation in RNC, BTS, Transmission 1001C73 RAB setup comp for CS Voice
1001C74 RAB setup comp for CS Data conv class
RRC: Radio Bearer Setup 1001C75 RAB setup comp for CS Data stream clas
1001C76 RAB setup comp for PS Data conv class
RAB Connection Access phase 1001C77 RAB setup comp for PS Data stream class
RNC waits reply from UE 1001C78 RAB setup comp for PS Data intera class
RRC: Radio Bearer Setup Completed 1001C79 RAB setup comp for PS Data backgr class
RANAP: RAB Assignment Response RAB Access Completed

Triggers:
1001C115 RAB setup for CS Voice
1001C116 RAB setup for CS Data conv class
1001C117 RAB setup for CS Data stream cla
RAB Active phase
1001C118 RAB setup for PS Data conv class
User Plane Data Transfer
1001C119 RAB setup for PS Data stream cla
Failure Case: 1001C120 RAB setup for PS Data intera clas
RAB ACT FAIL FOR CS VOICE CALL 1001C121 RAB setup for PS Data backgr cla
DUE TO
Triggers: Failure Case:
1001C145 Iu Interface Failure Case: CS RAB Setup for Voice fails Due to
1001C146 RADIO Interface CS RAB Access for Voice fails Due to Triggers:
1001C147 BTS Reasons Triggers: 1001C80 Admission control
1001C148 Iur Interface 1001C122 UE 1001C81 BTS
1001C149 INTEGRITY Check 1001C123 RNC internal 1001C82 Transmission network
1001C150 RNC Internal Note: Each RAB type has 1001C83 RNC internal reason
Note: Each RAB type has identical failure counters 1001C84 Frozen BTS
identical failure counters Note: Each RAB type has
identical failure counters
H RAB Active Phase Special Reason:
RAB Active Release Due to
Triggers:
1001C143 SRNC Relocation for CS Voic
1001C144 Pre-emption for CS Voice
UE BTS RNC CN
RAB Active phase
User Plane Data Transfer
RANAP: RAB Assignment Request, with IE: RAB reconfiguration
RAB Reconfiguration Attempt

RAB Reconfiguration Triggers:
Resource Reconfigured in RNC, BTS, Transmission 1001C197 RAB reconf Att
For all types of RABs
RRC: Radio Bearer Reconfiguration
RAB Reconfiguration Failure
RRC: Radio Bearer Reconfiguration Complete Triggers:
1001C198 RAB reconf Fail
RANAP: RAB Assignment Response For all types of RABs
RANAP: RAB Assignment Request, with IE: RAB Release

RAB Active Completed
RRC: Radio Bearer Release Depending on RAB Type
Triggers:
RRC: Radio Bearer Reconfiguration Complete 1001C136 RAB Act Comp for CS Voice
1001C137 RAB Act Comp for CS Data conv clas
RANAP: RAB Assignment Response 1001C138 RAB Act Comp for CS Data stream c
1001C139 RAB Act Comp for PS Data conv clas
RAB Release 1001C140 RAB Act Comp for PS Data stream c
Resource Released in RNC, BTS, Transmission
1001C141 RAB Act Comp for PS Data intera cla
1001C142 RAB Act Comp for PS Data backgr c

H RAB Connection KPI
UE BTS RNC CN
RANAP: RAB Assignment Request
RAB Setup phase RAB Setup Complete Ratio [%]

Resource Reservation in RNC, BTS, Transmission 100*[Sum(1001C73…79)/Sum(1001C66…72
RRC: Radio Bearer Setup
RAB Setup and
RAB Connection Access phase Access Complete Ratio [%]
RNC waits reply from UE 100*[Sum(1001C115..121)/Sum(1001C66…72
RRC: Radio Bearer Setup Completed

RANAP: RAB Assignment Response
RANAP: RAB Assignment Request, with IE: RAB Release
RRC: Radio Bearer Release RAB Drop Ratio [%]

100-100*[Sum(1001C115…121+1001C51
+1001C66)/Sum(1001C36…42)]
RRC: Radio Bearer Reconfiguration Complete
RANAP: RAB Assignment Response
SHO not possible during

RAB Esatblishment

RAB Setup Failures
• Admission Control: different behaviour according to the
RAB type
• BTS: only for RT RAB there is allocation of BTS resourceRNC CN
• Transmission: during the radio link reconfiguration RANAP:RAB Assignment Request
• RNC internal
Required bearer
• Anchoring (NRT) : NRT RAB is not allowed during not available
anchoring
• Frozen BTS (Admidssion Control blocks RL setup to RANAP:Assignment Response(
cause)
ensure the setup of emergency call
CN may send a new RAB Assignment
Request to establish a new bearer or
RNC sends RANAP: RAB ASSIGNEMENT RESPONSE to Iu release Command to release all
reserved resources.
the CN with an appropriate failure cause.

RAB Setup Failure for AC
• Mainly for voice and conversational data.
• BRM rejects RT DCH request:
• There is interference congestion in cell .
• No available Code in code tree.
• Bts capability check: max rl bitrate.
• Nrt queue is full
• DyLO: check that the new rl init power stay lower than DyLO threshold (rl_max_pwr -
dylo_offset) that start downgrade algorithm.
• Check with Traffic table counters if the reason is UL or DL

• In general if AC blocks only the RAB is due to DL load

Example of RRC/RAB Setup Failures AC
OUT PHASE OUT PROCESSOUT FAIL SOURCE OUT REASON OUT DETAILED REASON Comments
rrc_conn_setup_c brm_c admission_control_c rrc_conn_req_nack_c cell_overload_c Uplink
rrc_conn_setup_c brm_c admission_control_c rrc_conn_req_nack_c cell_overload_c Uplink Cell_overload = UL
rrc_conn_setup_c
rrc_conn_setup_c
brm_c
brm_c
admission_control_c
admission_control_c
rrc_conn_req_nack_c
rrc_conn_req_nack_c
cell_overload_c
cell_overload_c
Uplink
Uplink
blocking
rrc_conn_setup_c brm_c admission_control_c rrc_conn_req_nack_c cell_overload_c Uplink
rrc_conn_setup_c brm_c admission_control_c rrc_conn_req_nack_c rr_ind_failure_c Deno_Code_Cap=118 at 9:00 for cells 58033
rrc_conn_setup_c brm_c admission_control_c rrc_conn_req_nack_c rr_ind_failure_c Deno_Code_Cap=118 at 9:00 for cells 58033 Problem in cell
rrc_conn_setup_c
rrc_conn_setup_c
brm_c
brm_c
admission_control_c
admission_control_c
rrc_conn_req_nack_c
rrc_conn_req_nack_c
rr_ind_failure_c
rr_ind_failure_c
Deno_Code_Cap=118 at 9:00 for cells 58033
Deno_Code_Cap=118 at 9:00 for cells 58033
availablity
rab_setup_c
rab_active_c
brm_c
mcc_c
admission_control_c
admission_control_c
rt_dch_request_nack_c
cell_op_block_c
no_capacity_c
cell_op_block_c
AC DL on Supreme No_capacity = DL
rab_setup_c brm_c admission_control_c rt_dch_request_nack_c no_capacity_c AC DL on Supreme blocking
OUT PHASE OUT PROCESSOUT FAIL SOURCE OUT REASON OUT DETAILED REASON Commets
rrc_conn_setup_c
rrc_conn_setup_c
mcc_c
mcc_c
admission_control_c
admission_control_c
no_resp_from_brm_c
no_resp_from_brm_c
timer_expired_c
timer_expired_c
This BTS experienced "BTS Operations degraded" alarm
Problem in BRM
rrc_conn_setup_c
rrc_conn_setup_c
mcc_c
mcc_c
admission_control_c
admission_control_c
no_resp_from_brm_c
no_resp_from_brm_c
timer_expired_c
timer_expired_c
program block
rrc_conn_setup_c mcc_c admission_control_c no_resp_from_brm_c timer_expired_c This BTS experienced "BTS Operations degraded" alarm
rrc_conn_setup_c mcc_c admission_control_c no_resp_from_brm_c timer_expired_c This BTS experienced "BTS Operations degraded" alarm traffic counters are
rrc_conn_setup_c mcc_c admission_control_c no_resp_from_brm_c timer_expired_c This BTS experienced "BTS Operations degraded" alarm
not updated
rab_setup_c brm_c admission_control_c rt_dch_request_nack_c cell_overload_c AC UL: High UL interference is experienced on this site (PrxTotal equal -77 dBm
rab_setup_c brm_c admission_control_c rt_dch_request_nack_c cell_overload_c AC UL: High UL interference is experienced on this site (PrxTotal equal -77 dBm)

RAB setup failure BTS
• Only for RT
• Failure during the Radio Link Reconfiguration
Preparation:
• Equipment failure
• HW overload
• BTS sends RADIO LINK RECONFIGURATION FAILURE
FAILURE
• Check with Iub counters (Radio Link
Reconfiguration Failures)

RAB Setup Failure Transmission
• In case of failure in AAL2 setup (Iub, Iur and
Iu) the RADIO LINK RECONFIGURATION
CANCEL message is sent
• RAB setup failure is incremented not only
for Iub but for Iur and Iu as well
• No capacity
• The counter is incremented even if there is • AAL2 Failure
Iub capacity but AAL2 setup fails CANC
EL
• Counter in Iub Table are incremented as
well:
• CANC_SRNC_TRAN_STP_FAIL or
• CANCH_DRNC_TRAN_STP_FAIL

RAB Setup Failure Anchoring
• When all radio links are under other than serving RNC, and SRNS
relocation is not possible to perform, the establishment of NRT RABs is not
possible.
• The RANAP entity sends RANAP:RAB ASSIGNMENT RESPONSE/failure
message with cause value "No Resource Available".

RAB Access Failure
• RAB access fails if the UE sends
RRC: RADIO BEARER SETUP
FAILURE or the connection cannot be
established in a given time.
• RNC sends RANAP: RAB SHO not possible during
RAB Esatblishment
ASSIGNEMENT RESPONSE with the UE RNC CORE
specific failure reason and after RAB Assignment Request (setup)
RANAP: IU RELEASE REQUEST and
waits for RANAP: IU RELEASE
COMMAND from the CN. Radio Bearer Setup
• Failure due to UE :(e.g. to use a Radio BearerSetup Failure
or T_RRC_Resp_DCH/CCH
frequency, code or QoS that it is not Timer expiry
capable)
• Failure for RNC Internal RAB Assignment Response (failure)
Iu Release Request
• The timer (6s) is set when RNC
initiates a RRC procedure in Iu Release Command
Cell_DCH state. The timer is
stopped when RNC has received a
response message from MS related Chek RRC Table counters for RAB
to ongoing RRC procedure.
Setup Success Rate
RAB Active
• RAB active failure reasons:
• RNC Internal UE RNC CORE

• BTS RAB Assignment Request (setup)
• Radio Interface
• Iur
Radio Bearer Setup
• Iu
Radio BearerSetupComplete
• RAB normal release: RAB Assignment Response
• RAB active complete

• Pre-emption RAB Assignment Request (release)
• SRNC Relocation Iu Release Command
RAB Assignment Response
Iu Release Request

Example of PS RAB Active Failure due to
Radio
• UE not supporting the CELL_PCH state lead to RAB Active Failure due to Radio Interface
during the transition CELL_FACHCELL_PCH
• Anytime the RNC commands the MS to move to Cell_PCH upon expiry of the inactivity timers
the MS responds with a failure and moves to idle but the PDP context remains active as in a
normal state transition.
• This failure is not perceived by the user
AM DATA FACH RAB PS Success Rate

RAB FTP Success rate
physicalChannelReconfiguration
100%
rrc-StateIndicator |cell-PCH 90%
80%
AM DATA RACH
70%
physicalChannelReconfigurationFailure 60%
failureCause 50%
configurationUnsupported 40%
(RANAP) initiatingMessage (= initiatingMessage) 30%
20%
procedureCode |id-Iu-ReleaseRequest Upgrade to ED2 De-activation of
10% Cell_PCH state
id-Cause.. 0%
Mon Tue Wed Thu Fri Sat Sun Mon Tue Wed Thu Fri Sat Sun
radioNetwork |failure-in-the-radio-interface-proce| 07.Jun 08.Jun 09.Jun 10.Jun 11.Jun 12.Jun 13.Jun 14.Jun 15.Jun 16.Jun 17.Jun 18.Jun 19.Jun 20.Jun

Cell_PCH not supported by the UE in CD03
Transition cell_dchcell_fach
UL_DL activation timer expires
Transition cell_fachcell_pch
Failure due to Cell_PCH not supported
No failure counter
is incremented in
CD03

H RAB Drop Rate KPI
• For each RAB type there are two formulas for RAB Drop Rate (e.g. voice):
Drop migth be due to problems
Nromal RAB releases are taken into account in the traget cell e.g. SHO failure
RRC _ ACT _ COMP _ CS _ VOICE  RAB _ ACT _ REL _ CS _ VOICE _ P _ EMP  RAB _ ACT _ REL _ CS _ VOICE _ SRNC
100  100 *
RAB _ ACC _ COMP _ CS _ VOICE
For PS interactive and backgroung RAB there are no release

due to pre-emption
• UE mobility may cause this KPI to exceed 100 % or become negative i.e. a UE
establishes its RAB in one cell and then releases it in a different cell.
RAB rlease failures are taken into account
 RAB _ ACT _ FAIL _ CS _ VOICE _ xxx

100 *
all _ failures
%
RAB _ ACT _ COMP _ CS _ VOICE   RAB _ ACT _ FAIL _ CS _ VOICE _ xxx
all _ failures
• Some of the failures might not be counted

RAB Drop Rate
RAB drop Voice
10%
8%
6%
4%
Drop Rate
Normal Release
2%
Failures
0%
1
10
13
16
19
22
25
28
31
34
-2%
-4%
-6%

M Traffic Mix KPIs
• The KPI provides an indication of the percentage of CS voice, CD data, PS data
RAB establishment attempts relative to the total number of RAB establishment
attempts.
• These KPI are intended to provide a high level indication of the traffic profile
loading the network:
Traffic Mix
• CS_VOICE
• CS_CONV Same KPI using
CS_STREA
ATT_CS_VOICE •RAB_STP_AT
16%
RAB
T_CS_CONV RAB_STP_ATT_CS_STREA  RAB_STP_ATT_PS_CONV RAB_STP_ATT_PS_STREA ACC
 RAB_STP_ATT_PS
COMP
• PS_CONV
• PS_STREA Voice
51% Data Conv

• PS_INTER PS Inter
• PS_BACKG 32% PS Backg
1%
• Example for CS_VOICE:

RAB _ STP _ CS _ VOICE
RAB _ STP _ CS _ VOICE  RAB _ STP _ CS _ CONV  RAB _ STP _ CS _ STREA  RAB _ STP _ PS _ INTER  RAB _ STP _ PS _ BACKG
It’s better to use the duration counters

because for PS there might be many attempts
L RAB Setup Time KPI
• The result represents the average time to successfully establish a CS voice RAB.
A successful RAB is defined as one for which the RNC sends a positive RANAP:
RAB ASSIGNMENT RESPONSE message.
UE RNC CORE
RAB Assignment Request
Radio Bearer Setup AVE _ RAB _ SETUP _ TM _ CS _ VOICE

/ 100( s)
Radio BearerSetupComplete DENOM _ RAB _ SETUP _ TM _ CS _ VOICE
Triggering PointRAB
X Assignment Response
• The AVG_RAB_SETUP_TM_CS_VOICE counter records the time between the

RNC receiving a RANAP: RAB ASSIGNMENT REQUEST and sending a positive
RANAP: RAB ASSIGNMENT RESPONSE. The counter sums the times for all
successful RAB assignments. The DENOM_ RAB_SETUP_TM_CS_VOICE is
incremented by 1 after every successful RAB assignment.
• The factor of 100 appearing within the KPI calculation is a result of Nokia’s
internal representation of the counter value. Nokia uses a 10 ms unit for the
AVG_RAB_SETUP_TM counter.
• Same counters and formula is possible for any RAB (CS_VOICE, CS_CONV,
PS_INTER, PS_BACKG)
86
• ThePresentation_Name.PPT
© NOKIA
KPI is meaningful for cell level
/ DD-MM-YYYY / Initials
and on hour basis
Company Confidential
M RAB and DCH Holding Time
• For each traffic class there are counters for RAB Holding time (incremented when the RAB
is released only on the cell that was the reference when the RAB is released and in the
hour in which it was released!!!): from RAB Assignment Response to RAB Assignment
Response for release (or Iu Release command) Denom is
• RAB duration for PS interactive class: incremented
For each when the RAB is
AVG _ RAB _ HLD _ TM _ PS _ INTER Traffic Class
/ 100( s) released
DENOM _ RAB _ HLD _ TM _ PS _ INTER
• For NRT traffic classes (inter and backg) there are also counters for DCH Holding time
(incremented when the RAB is released onlyon the cell that was the reference when the
RAB is released and in the hour in which it was released!!!):
AVG _ DCH _ HLD _ TM _ PS _ INTER KPI not

/ 100( s) Only for
DENOM _ DCH _ HLD _ TM _ PS _ INTER working before
ED2 NRT Traffic Class
RAB Holding Time [s] DCH Holding Time [s]
20
20
40
40
60
60
80
80
100
100
120 120 Data from
140 140
160
ED2
160
180 180
200 200
More More

M Cell-DCH/Cell-Fach Time
DCH Time %
• Percentage of time in cell dch: 10%
20%
30%
AVG _ DCH _ HLD _ TM _ PS _ INTER
100% 40%
AVG _ RAB _ HLD _ TM _ PS _ INTER 50%
60%
70%
80%
90%
KPI not working before ED2 Data from
100%
ED2
More
CELL_FACH CELL_DCH CELL_FACH
Uplink DCH
Downlink DCH
NRT RB data transfer active Radio link & Iub AAL2 setup
NRT RB inactivity timer running Radio link & Iub AAL2 release

H Erlang for CS services
AVG _ RAB _ HLD _ TM _ CS _ VOICE Global KPI not usefull

( Erl )
100  60  60 for optimisation
• The KPI should be generated on a daily and cluster basis (due to the
triggering rules of the RAB holding time)
• Same KPI for each CS traffic class:
• CS_CONV
• CS_STREA

M Average Time between drop
• The KPI represents the average time between abnormal RAB releases that
a CS voice RAB is active.
AVG _ RAB _ HLD _ TM _ CS _ VOICE
100  60 (min) Global KPI not usefull
 RAB _ ACT _ FAIL _ CS _ VOICE _ xxx
all _ failures
for optimisation
• The KPI should be generated on a daily and cluster basis (due to the
triggering rules of the RAB holding time)
• Same KPI for each traffic class:
• CS_CONV
• CS_STREA
• PS_INTER
• PS BACKG

H Call Setup Success Rate (CSSR)
• The Call Setup Success Rate (CSSR) indicator aims to measure how
many of the RRC Connection Attempts for a particular RAB end with the
correct establishment of the RAB.
• It could be obtained considering the ratio between the number of
RANAP: RAB ASSIGNMENT RESPONSE messages sent by the RNC
to the CN that indicates a successful RAB establishment and the
number of RRC Connection Setup Requests received by the RNC for
the considered RAB type:
RAB _ Assignment _ Response _ Succesfully _ Established (Voice _ CS _ Conv) _ or _( PS _ Inter _ Back )
RRC _ Connection _ Setup _ Re quest (Voice _ CS _ Conv) _ or _( PS _ Inter _ Back )
• At the moment it’s possible only for CS Conversational call:

SUM(RAB_ACC_COMP_CS_VOICE+RAB_ACC_COMP_CS_CONV)/(SUM(MOC
_CONV_CALL_ATTS+MTC_CONV_CALL_ATTS))

H Call Complete Success Rate (CCSR)
• The Call Complete Success Rate (CCSR) indicator measures how many
of the RRC Connection Attempts for a particular RAB end with the
normal release of the RAB.
• It could be obtained as the ratio between the number of RANAP: RAB
ASSIGNMENT RESPONSE messages sent by the RNC to the CN that
indicates a successful RAB release and the number of RRC Connection
Setup Requests received by the RNC for the considered RAB type:
RAB _ Normal _ Re lease (Voice _ CS _ Conv) _ or _( PS _ Inter _ Back )

RRC _ Connection _ Setup _ Re quest (Voice _ CS _ Conv) _ or _( PS _ Inter _ Back )
• At the moment it’s possible only for CS Conversational call:

SUM(RAB_ACT_COMP_CS_VOICE+RAB_ACT_COMP_CS_CONV)/(SUM(MOC_
CONV_CALL_ATTS+MTC_CONV_CALL_ATTS))

Alternative CSSR and CCSR
• In order to take into account MultiRab, the following formula for CSSR is
under evaluation (in this case it’s possible to distinguish between AMR and
CS conv. but only in the RAB part while the RRC is including all the
reasons):
RRC _ Establ _ Succ _ Rate  RAB _ Establ _ Succ _ Rate
• Drop during RRC active and before RAB Assignement Request

• In order to take into account MultiRab, the following formula for CCSR is
under evaluation:
CSSR  (1  RAB _ Drop _ Rate)

2 - KPI Presentation Ver 1-8 Serv Lev

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2 - KPI Presentation Ver 1-8 Serv Lev

Uploaded by

Copyright:

Available Formats

WCDMA RAN

Service level MEASUREMENT

RAN 1.5.2 ED2

1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

2 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

Setup Access Active

Setups Failures, Blocking All the counters of the Sevice

3 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

Setup Phase Event 2: RRC_CONN_STP_COMP

Event 4 IU Release Command

4 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

5 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

• “RRM” is divided between RNC, BTS and UE

7 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

OMU DMCU RRMU

Statistics Outer Loop

8 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

10 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

BRMPRB (Base station Resource Manager)

11 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

HA3PRB (Handover Algorithm)

• RRC: INTRA-FREQUENCY MEASUREMENT, CPICH EcNo (1a,1b,1c), event triggered

12 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

13 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

Transmission), replies with DL “RRC RRC: RRC Connection Request (RACH)

CCPCH (FACH sub-channel). NBAP: Radio Link Setup Response

• This procedure is not affected bu UE’s behavoiur, ALCAP: Establish Request

• The number of RRC Connection Request

14 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

15 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

16 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

17 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

RRC: RRC Connection Request (RACH)

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

ALCAP: Establish Request

ALCAP: Establish Confirm

FP: Downlink Sync

FP: Uplink Sync

NBAP: Synchronisation Indication

19 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

20 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

Transport res. reserv. req.

ERQ (SUGR) AAL2 connection establishement

AAL2 conn. estab. confirmation

22 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

of the signalling dedicated channel to be ALCAP: Establish Request

• The number of RRC Connection Access

23 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

24 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

RRC: RRC Connection Setup Complete (DCH)

25 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

NBAP: Synchronisation Indication

RRC: RRC Connection Setup Complete (DCH)

26 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

27 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

• Most of the failures are:

28 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

RRC ACC COMPLETE

29 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential

50% 4th of March

RRC Active Failure for

31 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential