RN3158 RANKPI Training – RU40

Paging and Radio Resource Control Connection

1 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Agenda

• QoS architecture overview

• Paging Procedure
• CBS procedure – new in RU40
• RRC Connection – Setup Phase
• AAL2 Resource Reservation in Iub
• RRC Access Phase
• Traffic counters for RRC setup and access
• Analysis or RRC Connection Setup Complete message
• RRC Active Phase
• Common Channel Set Up
• M1006 RRC Measurements (State Transition Counters new in RU40)
• Fast Dormancy (Fast Dormancy Profiling new in RU40)

2 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 QoS architecture overview

3 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Quality of Service (3GPP 23.107/23.207)

UMTS

TE MT UTRAN CN Iu CN TE
EDGE Gateway
NODE

End-to-End Service

TE/MT Local External Bearer

Bearer Service
UMTS Bearer Service Service

Radio Access Bearer CN Bearer

Service Service

Radio Bearer Iu Bearer Backbone

Service Bearer Service
Service

4 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAB and RRC connection

Radio Access Bearer

Signalling Connection

RRC Connection Iu Connection

RRC

Radio Bearer Iu Bearer

UE UTRAN CN
Uu (RNC) Iu

5 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection and RAB phases

The Service Level measurements provide RRC and RAB connection-related

information.
With this purpose, RRC connection and RAB have been divided into three
phases:
Setup Phase

Access Phase

Active Phase

Thus, for each phase, a success/failure rate KPI can be defined, both for RRC
connection and for each RAB type.

6 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection and RAB phases
Moreover, if a failure happens during any RAB phase, typically both RRC
active and RAB (setup, access or active) failure counters are updated with
the appropriate cause.

X
Radio Access Bearer

XRNC
RRC Connection

UE CN

Uu Iu
In addition to the KPIs presented in the slide before, these measurements provide
also the following KPIs:
– RAB holding time
– DCH holding time per NRT RAB type
– RRC and RAB setup time
7 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
 Paging Procedure

8 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging Types Counters
The Core Network Paging Attempt Type 1 provides an indication of the number of core
network originated paging type 1 messages sent by the RNC. These paging messages are
broadcast across an entire location area or an entire routing area.
UE RNC CORE
Event 1: PAGING_TYPE_1_ATT_CN_ORIG
UE is in RRC IDLE Mode incremented
Paging
Paging Type 1
Event 1

The RNC Paging Attempt Type 1 provides an indication of the number of RNC originated
paging type 1 messages sent by the RNC. These paging messages are broadcast across
either a single cell or a UTRAN registration area.
UE RNC CORE
Event 1: PAGING_TYPE_1_ATT_RNC_ORIG
UE is in CELL_PCH or URA PCH incremented
Paging
Paging Type 1
Event 1

The Paging Attempt Type 2 provides an indication of the number of paging type 2 messages
sent by the RNC. These paging messages are transmitted across only the cells to which the
UE is currently connected. The counter is incremented for the cells to which the UE are
connected.
UE RNC CORE
Event 1: PAGING_TYPE_2_ATT
UE is in CELL_DCH or CELL_FACH incremented
Paging
Paging Type 2
Event 1

9 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging for UEs in RRC IDLE state

When RNC receives paging message RANAP:

UE BTS RNC Paging from the CN, counter: M1003C36
CN
REC_PAG_MSG is incremented
UE In Idle mode
RANAP: PAGING
1 PICH
(FP/AAL2/PCCH/PCH/S-CCPCH) : PAGING TYPE 1

RRC connection establishment

If RNC cannot process the paging messages and
Paging response
forward those to the UE due to ICSU/RRMU overload,
counters M1003C47/C48
DEL_PAG_MSG_ICSU/RRMU_OVERLOAD are
incremented

When RNC sends Paging Type 1 through cells,

counter M1006C25
PAGING_TYPE_1_ATT_CN_ORIG is
incremented.

10 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging for UEs in CELL_PCH or URA_PCH

Triggers M1003C36 and

MM MM Idle M1006C155 PAGING_OCCASION_CELL_PCH or
2 Connected M1006C159 PAGING_OCCASION_URA_PCH
UE BTS RNC CN1 CN2

UE has signalling connection to CN1

UE is in URA_PCH or CELL_PCH state
RANAP:PAGING
PICH
(FP/AAL2/PCCH/PCH/S-CCPCH) : PAGING TYPE 1
(RACH) RRC Cell Update : Paging Response
Triggers M1006C25 and
M1006C156 PAGING_MESSAGES_CELL_PCH
Paging response to CN 2 or
M1006C160PAGING_MESSAGES_URA_PCH

When there is no repsonse within 2 sec

Triggers M1006C37 CELL_UPD_ATT_PAGING_RESP and M1006C158
M1006C157CELL_UPD_AFTER_PAG_CELL_PCH FAIL_PAG_NO_RESP_CELL_PCH or
or M1006C162
M1006C161CELL_UPD_AFTER_PAG_URA_PCH FAIL_PAG_NO_RESP_URA_PCH
are triggered

11 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging for UEs in CELL/URA_PCH due to arriving data
packet from SGSN

UE RNC SGSN
The MAC-d (RLC) in RNC
indicates that there is downlink A number of RNC originated paging type 1
3 user data in RLC buffers then
the RRC signaling entity
1.PDP PDU
attempts (UE in PCH/URA substate).
initiates the paging procedure
When RNC sends Paging Type 1 through a cell,
counter M1006C26
2. Paging Request (P-TMSI)
PAGING_TYPE_1_ATT_RNC_ORIG is
RRC: PAGING TYPE 1 with PICH BTS -> UE incremented.
MM Cell Update
(RACH) RRC Cell Update : Paging Response

12 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging for UEs in CELL_DCH or CELL_FACH

MM MM Idle
4 Connected
UE BTS RNC CN1 CN2

UE has signalling connection to CN1

UE is in CELL_DCH/FACH state
RANAP:PAGING
PICH
(FP/AAL2/PCCH/PCH/S-CCPCH) : PAGING TYPE 2
(RACH) RRC Cell Update : Paging Response

Paging response to CN 2

Triggers M1006C27 PAGING_TYPE_2_ATT

13 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Paging Counters

M1006C251 LOW PRIORITY PAGING DROP

Description: The number of low priority paging messages dropped in L2 scheduling.
Updated: When the L2 entity of RNC drops low priority paging message due to
congestion.
Logical type: Sum; Trigger type: Event; Unit: Integer number

M1006C252 HIGH PRIORITY PAGING DROP

Description: The number of high priority paging messages dropped in L2 scheduling.
Updated: When the L2 entity of RNC drops high priority paging message due to
congestion.
Logical type: Sum; Trigger type: Event; Unit: Integer number

14 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 CBS procedure – RU40

15 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2704: 3GPP Rel8 CBS ETWS Support – 1/3
new in RU40
• introduces ETWS (Earthquake and Tsunami Warning Service) for CBS (Cell Broadcast
Service)
• is used to broadcast emergency information such as earthquake and tsunami warnings to
as many mobile terminals and as quickly as possible
• in some countries this is to be a governmental requirement

16 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2704: 3GPP Rel8 CBS ETWS Support 2/3
new in RU40
Warning Notification is classified into two types depending on the purpose and urgency of the
notification:
• primary notification – delivers the most important information of the threat that is approaching to
users (e.g.: the imminent occurrence of earthquake or tsunami) – it is delivered to the users as soon as
possible
• secondary notification – delivers additional information, such as instructions on what to do/where to
get help, as long as the emergency lasts

Functional description
• new ETWS parameters are added to service area broadcast protocol (SABP) messages
• RNC triggers sending of PICH and paging message (or system information change message) to all
UEs including ETWS warning and ETWS PRIMARY NOTIFICATION WITH SECURITY message to all
Cell_DCH state Ues
• CBC (Cell Broadcast Center) can indicate that no CTCH data at all by including "Broadcast Message
Content Validity Indicator" IE into the Write-Replace message
• SAB can be enabled in the cell only if it has either two or three secondary common control physical
channels
• SAB support with one secondary common control physical channel is not allowed

17 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 RAN2704: 3GPP Rel8 CBS ETWS Support 3/3
new in RU40
CBC SGSN RNC NodeB U
E
1. Write Relpace
2. Paging Type1

4 sec. 3. BMC Schedule Message

4. BMC CBS Message

5. Report Success

1. CBC initiates the procedure by sending a WRITE-REPLACE message to the RNC that includes disaster type (for
example earthquake or tsunami)
2. The RNC sends ETWS PRIMARY NOTIFICATION WITH SECURITY IE, PAGING TYPE1 IE or SYSTEM
INFORMATION CHANGE INDICATION IE to all UEs.
3. The RNC sends a BMC SCHEDULE MESSAGE IE to provide DRX information of cell broadcast data at the UE
4. The RNC sends a BMC CBS MESSAGE IE which carries the actual cell broadcast data.
5. The RNC sends a BMC REPORT-SUCCESS IE in return of Write-Replace
New Counters
M1012C13 WRITE-REPLACE ETWS MSG FROM CBC Service Area Broadcast (RNC)
M1012C14 WRITE-REPLACE COMPLETE ETWS MSG TO CBC Service Area Broadcast (RNC)

18 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Connection – Setup Phase

19 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection - RACH UE distance detection
NetAct diagnostics
- detected at OSS within cell/BTS levels PRACH delay classes
For PRACH Delay Range = 60 km
Range 60 km (this is fixed in RAS06)
bin 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
from(m) 0 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076
PROP_DELAY (from) 0 1 2 4 5 7 9 13 17 21 26 30 34 43 64 85 107 128 149 171 214
to(m) 234 468 936 1170 1638 2106 3042 3978 4914 6084 7020 7956 10062 14976 19890 25038 29952 34866 40014 50076 infinite
PROP_DELAY (to) 0 1 3 4 6 8 12 16 20 25 29 33 42 63 84 106 127 148 170 213

bin size(m) 234 234 468 234 468 468 936 936 936 1170 936 936 2106 4914 4914 5148 4914 4914 5148 10062

1 PD step at Iub =
78 m x 3 = 234 m distance
P-RACH

Remember !
Multipath delays due to multipath propagation (1 Distance (PD with 3 chip resolution)
s  300 m path difference). Components with
delay separation more than 1 chip (0.260 s = 78 PRACH propagation delay statistics is
m) can be separated and combined. presented using a distribution consisting of 21
Via interface Iub PD is given with 3 chip counters M1006C128-M1006C148
resolution only.

20 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection - RACH UE distance detection
RRC connection setup phase analysis
- Random access (propagation delay)
Counter id Counter name Distance [meters]
M1006C128 PRACH_DELAY_CLASS_0 0...234
RAN1127 M1006C129 PRACH_DELAY_CLASS_1 234...468
Extended Cell (180 km) extends M1006C130 PRACH_DELAY_CLASS_2 468...936
M1006C131 PRACH_DELAY_CLASS_3 936...1170
the theoretical maximum cell range M1006C132 PRACH_DELAY_CLASS_4 1170...1638
from 20 km to 180 km M1006C133 PRACH_DELAY_CLASS_5 1638...2106
M1006C134 PRACH_DELAY_CLASS_6 2106...3042
New counters in RRC M1006C135 PRACH_DELAY_CLASS_7 3042...3978
measurements (M1006) M1006C136 PRACH_DELAY_CLASS_8 3978...4914
M1006C137 PRACH_DELAY_CLASS_9 4914...6084
Example: 60 km cell range M1006C138 PRACH_DELAY_CLASS_10 6084...7020
M1006C139 PRACH_DELAY_CLASS_11 7020...7956
M1006C140 PRACH_DELAY_CLASS_12 7956...10062
M1006C141 PRACH_DELAY_CLASS_13 10062...14976
M1006C142 PRACH_DELAY_CLASS_14 14976...19890
M1006C143 PRACH_DELAY_CLASS_15 19890...25038
M1006C144 PRACH_DELAY_CLASS_16 25038...29952
M1006C145 PRACH_DELAY_CLASS_17 29952...34866
PRACH M1006C146 PRACH_DELAY_CLASS_18 34866...40014
Preambles (UL) M1006C147 PRACH_DELAY_CLASS_19 40014...50076
M1006C148 PRACH_DELAY_CLASS_20 greater than 50076
Node B Distance (PD) 3 chips at Iub
measurement reporting interval

21 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection - RACH UE distance detection
New counters in RRC measurements M1006 or probing with higher granularity of
PD distribution can be used to evaluate how far UEs are from the cell

It should be verified, whether

cells showing distant access
have fragmented dominance
outside the intended cell area
(introduced e.g. by reflection
due to the hilly terrain).
RT/NRT services monitored at Iub
Furthermore it should be
proved, whether with a higher
setting of the open loop power
control parameter PRACH
Required Received C/I (default
= -25 dB) shift to -20 dB
unwanted distant access will be TOO
avoided. early
Access

22 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Performance – Signaling and Trigger points positive
UE Node B RNC
[RACH] RRC:RRC Connection Request
M1001C0
AC to check to accept
or reject RRC
Connection Request

RRC Connection Setup NBAP: RL Setup Request

Allocation of UTRAN
phase Start TX/RX

NBAP: RL Setup Response

resources
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection Setup

M1001C1
Start TX/RX

L1 Synchronisation
RRC Connection Access
NBAP: Synchronisation Indication Waiting for UE reply
phase

[DCH] RRC: RRC Connection Setup Complete

M1001C8
RRC Connection Active phase

RRC active complete drop Pre-Emption SRNS Relocation

23 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RRC Connection Setup & Access and Active negative

UE BTS RNC CN

RRC: RRC connection Request

RRC SETUP fails if some of the needed resources (RNC, BTS, AIR,
RRC SETUP phase Transport) are not available. When an RRC setup failure occurs the RNC
sends an RRC: RRC CONNECTION REJECT message to UE
RRC Setup time

(Resource Reservation in RNC, BTS,

Transport)
RRC: RRC connection Setup
RRC ACCESS fails if the UE does not reply to RRC: RRC CONNECTION
RRC ACCESS phase
SETUP message with the RRC: RRC CONNECTION SETUP COMPLETE
(RNC waits for Reply from UE) message in given time, if the BTS reports a radio link synchronisation failure
RRC: RRC connection Setup Complete or in an RNC internal failure occurs
RRC ACTIVE phase

RRC: Initial Direct Transfer RRC ACTIVE fails when an interface related (Iu, Iur , Iub, or Radio) or RNC
internal failure occurs, and the failure causes the release of the RRC
RANAP: Initial UE Message Connection. When an RRC active failure occurs, the RRC send a RANAP: IU
RELEASE REQUEST to all involved CNs and waits for RANAP: IU
UE-CN Signalling
RELEASE COMMAND message (s)
(E.g. RAB Establishment and Release)

RANAP: Iu Release Command

RRC ACTIVE release cause can be either ISHO, IFHO, SRSN relocation
RRC: RRC connection Release
or pre-emption
RRC: RRC connection Release Complete

Release RRC resources in RNC, BTS,

Transport

24 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected ICSU can not process the call

No processing power on ICSU (Interface Control and Signaling Unit) unit

Incoming call request can not be handled due to lack of ICSU processing
“No hand free” is RNC internal clear code.

UE BS RNC

RRC Connection Request ICSU overload

RRC Connection Reject

Cause: congestion

Failure Counter M1001C618

25 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected Start of Handover Control fails

UE BS RNC

RRC Connection Request HC setup failure

RRC Connection Reject

Cause: congestion

In that case the RRC set up failed without involving the BS, transmission, and UE. The RRC request is
soon rejected because Handover Control process cannot be setup.
Handover Control is a major Process supporting all the handover types available in NSN Nokia RAS.

Failure Counter M1001C2

26 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected Air interface (UL/DL) overload (1/2)
Admission Control rejects air interface resource allocation due to air i/f overload (low
priority Establishment causes only)
UL interference [dB] DL cell power [dBm]

overload state overload state

PrxOffset PtxOffset
marginal load state marginal load state
PrxTarget PtxTarget
feasible load state feasible load state
current NC load

load load
If current non-controllable cell load is If current non-controllable cell load is
higher than or equal to PrxTarget higher than or equal to PtxTarget

Failure Counter M1001C3

load

27 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected Air interface (UL/DL) overload (2/2)

Failure Counter M1002C1 Failure Counter M1002C2

DCH_REQ_LINK_REJ_UL_SRNC DCH_REQ_LINK_REJ_DL_SRNC
Check TRAFFIC for more details (M1002)

Only relevant for:

Originating/Terminating Conversational Call
Originating/Terminating Streaming Call
Originating/Terminating Interactive Call
Originating/Terminating Background Call
Originating Subscribed traffic Call
Originating/Terminating Low Priority Signalling
Call reestablishment
Terminating – cause unknown

28 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection setup
Admission Control admits the call
Traffic counters (M1002) count number of
• SRB allocation requests
• SRB successful allocations
• SRB durations
depending on allocated SRB bit rate 3.4 or 13.6 (1.7 not supported in NSN Nokia RAN)
Requests:
(M1002C3) DCH_REQ_RRC_CONN_SRNC : includes state transitions and RRC Connections
(M1002C0) DCH_REQ_LINK_SRNC : includes SHO, HHOs, state transitions and RRC Connections

Successful AC decision triggers:

(M1002C7) DCH_ALLO_LINK_3_4_SRNC or
(M1002C8) DCH_ALLO_LINK_13_6_SRNC (NOTE counters incremented only in case BTS setup and AAL2
reservation are ok)

And starts the duration counters (sampled continuously with 1s interval)

(M1002C10) DCH_ALLO_DURA_LINK_3_4_SRNC or
(M1002C11) DCH_ALLO_DURA_LINK_13_6_SRNC (NOTE counters started only in case BTS setup and AAL2
reservation are ok)

29 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up
Frozen WBTS
• If RRC requests can not be handled due to resource shortage or
ongoing pre-emption procedure, they are queued
• If queue is full (30 requests max.) further requests are rejected
right away, these trigger this counter
• RNC sets WBTS status to frozen (no new requests are processed
to setup high priority call)
• No RL setup request, no further counters triggered

Failure Counter M1001C7

30 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up
Frozen WBTS – data from RAS05.1 network

RRC_CONN_STP_FAIL_RNTI_ALLO (Servlev)
RRC_CONN_STP_FAIL_IUB_AAL2 (Servlev)

rrc_conn_stp_fail_frozbs (Servlev)
rrc_conn_stp_fail_bts (Servlev)
rrc_conn_stp_fail_ac (Servlev)
rrc_conn_stp_comp (Servlev)
rrc_conn_stp_att (Servlev)
3G Network

Time

Somewhere 30.01.2008 00:00 0 0 2835 2828 3 3 0

Somewhere 30.01.2008 01:00 0 0 2109 2106 3 0 0
Somewhere 30.01.2008 02:00 0 0 1938 1938 0 0 0
Somewhere 30.01.2008 03:00 0 0 1641 1641 0 0 0
Somewhere 30.01.2008 04:00 0 0 1619 1619 0 0 0
Somewhere 30.01.2008 05:00 0 0 1862 1862 0 0 0
Somewhere 30.01.2008 06:00 0 0 2285 2285 0 0 0
Somewhere 30.01.2008 07:00 0 0 3977 3977 0 0 0
Somewhere 30.01.2008 08:00 0 0 5477 5475 1 1 0
Somewhere 30.01.2008 09:00 0 0 7197 7160 0 37 0
Somewhere 30.01.2008 10:00 0 0 7906 7839 1 66 0
Somewhere 30.01.2008 11:00 1 0 9846 9730 8 104 0
Somewhere 30.01.2008 12:00 1 0 10827 10501 60 263 0
Somewhere 30.01.2008 13:00 0 0 10523 10296 0 223 0
Somewhere 30.01.2008 14:00 0 0 11008 10613 13 382 0
Somewhere 30.01.2008 15:00 0 0 9733 9426 8 299 0
Somewhere 30.01.2008 16:00 0 0 11281 9758 8 1512 0
Somewhere 30.01.2008 17:00 0 0 13589 9183 0 4405 0
Somewhere 30.01.2008 18:00 0 0 9513 8773 1 738 0
Somewhere 30.01.2008 19:00 1 0 8683 7549 59 1074 0
Somewhere 30.01.2008 20:00 0 0 8838 6848 119 1531 340
Somewhere 30.01.2008 21:00 0 0 14684 4673 20 8639 1352
Somewhere 30.01.2008 22:00 0 0 12082 4580 228 6266 1008

31 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected RNTI cannot be allocated
Due to processing capacity constraints, RNC can not allocate RNTI
and UL Scrambling Code
Uplink Scrambling Code Number
150001 16 = 1376257 10

Radio Network Temporary Identifier

B0BF 16 = 45247 10
Failure Counter M1001C247

32 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected WBTS reports problem setting up Radio Link

NBAP Radio Link Setup procedure is initiated to setup radio link

between RNC and WBTS

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Failure

Check L3 IuB for more

details (M1005), see
next slides

Failure Counter M1001C4

33 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Radio Link Setup Counters

Radio link setup is requested from RNC at call establishment (RRC

connection setup) and for soft/hard handover (not for softer handover,
in this case it would be Radio Link Addition).
Radio link setup procedure is used to establish radio link and
simultaneously initiate the creation of a new Node B communication
context.
Thus, there might be 4 reasons for sending Radio Link Setup Request
message to Node B:
• Setup the first link (for RRC Connection Setup)
• Setup a link for SHO
• Setup a link for HHO
• RRC state transition from Cell_FACH to Cell_DCH

34 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Radio Link Setup Counters

The RL SETUP ATTEMPT counters (first link/SHO/HHO) are incremented by

the RNC whenever it sends an NBAP: RADIO LINK SETUP REQUEST
message.

The RL SETUP SUCCESS counters (first link/SHO/HHO) are incremented by

the RNC whenever it receives an NBAP: RADIO LINK SETUP RESPONSE
message.

The Radio Link Setup Success Ratio KPI provides an indication of the
percentage of successful radio link setups.

Node B RNC

Radio Link Setup Request RL_SETUP_ATT

incremented
Radio Link Setup Response
RL_SETUP_SUCC
incremented

35 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 Radio Link Setup Counters first radio link or state
transition Cell_FACH  Cell_DCH
There are specific counters for Radio Link Setup procedure at RRC setup phase:
− attempt M1005C0 RL_SETUP_ATT_FOR_FIRST_RL

− success
− 5 failure reasons
M1005C5 RL_SETUP_SUCC_FOR_FIRST_RL

M1005C14 SETUP_FAIL_RL_BTS_NOT_RESP
Node B RNC
Radio Link Setup Request RL_SETUP_ATT
incremented M1005C176 SETUP_FAIL_FIRST_RL_RNL
Radio Link Setup Response
e.g. RL_SETUP_SUCC
incremented
M1005C177 SETUP_FAIL_FIRST_RL_TNL

M1005C178 SETUP_FAIL_FIRST_RL_PROT

M1005C179 SETUP_FAIL_FIRST_RL_MISC

36 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

KPI: Radio Link Setup for first radio link Success rate

RL_SETUP_SUCC_FOR_FIRST_RL
First _ Link _ Setup _ Succ _ Rate  100[%]
RL_SETUP_ATT_FOR_FIRST_RL

M1005C5/M1005C0

Difference from attempts and successes should be equal to

the number of RRC setup failure due to BTS
(RRC_CONN_STP_FAIL_BTS ) from Service Level.

The KPI normally dominated by lack of processing capacity

in the WBTS.

37 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Success Rate for 1st Radio Link
(data from RAN04 release – German Network early 2006)
First Radio link is used for RRC connection or after state transition from Cell_FACH to
Cell_DCH

date rl_setup_att_for_first_rl setup_fail_rl_not_enough_res

worse case: 22.01.2006 921490 149263

Max. blocking due to lack of WBTS Baseband capacity ~ 16 %

38 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected Any other failure detected

UE BS RNC

RRC Connection Request RRC Connection reject

RRC Connection Reject

Cause: congestion

If RNC decides to reject the RRC Connection Establishment (setup) at any given time (due
to reasons other than specifically counted by other counters), counter M1001C6
RRC_CONN_STP_FAIL_RNC is incremented

Failure Counter M1001C6

39 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection set up failure
RRC Connection is rejected by DL Connection Admission Control (CAC)

UE Node B RNC
[RACH] RRC:RRC Connection Request

AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request

Start TX/RX

NBAP: RL Setup Response

DL CAC reject because
ALCAP:ERQ
of ATM
ALCAP:ECF

[FACH] RRC: RRC Connection Setup

Start TX/RX

L1 Synchronisation

NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete Failure Counter M1001C530

RRC Connection Active phase
40 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RRC connection set up failure
RRC Connection is rejected by UL Connection Admission Control (CAC)

UE Node B RNC
[RACH] RRC:RRC Connection Request

AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request

Start TX/RX

NBAP: RL Setup Response

ALCAP:ERQ
ALCAP:RLC UL CAC reject from
WBTS
[FACH] RRC: RRC Connection Setup

Start TX/RX

L1 Synchronisation

NBAP: Synchronisation Indication

Failure Counter M1001C5

[DCH] RRC: RRC Connection Setup Complete

RRC Connection Active phase

41 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
 AAL2 Resource Reservation in Iub

42 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

What is AAL2 CAC ?

The AAL2 CAC controls the admission of

AAL2 connections into the ATM VCC Delay requirement
making sure that network has enough VCC PCR Loss tolerance
resources to guarantee the QOS for both
existing & new connections requests.
In Iub there are three such algorithms: Input
• RNC CAC for downlink
(complicated)
• BTS CAC for uplink (simple) Reservation
• AXC CAC for uplink in case of for existing
AAL2 multiplexing (simple) connections
So the AAL2 CAC is guarding the entrance
of the outgoing AAL2 VCC CAC Algorithm
The ALC parameters define for each bearer: Output
• Maximum bitrate
• Maximum packet size
• Average bitrate
• Average packet size

43 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Resource Reservation in Iub (similar with Iu-CS, IuR)

BTS (WAM or FTM) RNC

UE AAL2 SIG CAC CAC AAL2SIG ATM RM RRC
RRC: connection request

RNC internal transport 1

resource reservation

AAL2 connection establishment ERQ (SUGR) 2

WBTS internal transport

resource reservation 3

1 After the RNC internal

Response to ERQ; ECF or RLC (cause)
reservation is successfully done,
counter RES_SUCCEEDED (M800C0) is updated. AAL2 conn. estab. confirmation
4
RRC:connection setup

44 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Resource Reservation in Iub (similar with IuR)

BTS (WAM) RNC

UE AAL2 SIG CAC CAC AAL2SIG ATM RM RRC
RRC: connection request

1
RNC internal transport
resource reservation
AAL2 connection establishment ERQ (SUGR) 2

WBTS internal transport

resource reservation 3

Response to ERQ; ECF or RLC (cause)

2 If the RNC internal reservation fails one of the following counters is updated
AAL2 conn. estab. confirmation
‐ RES_EXT_CAP (M800C1): Not enough bandwidth in external ATM VCC. 4
‐ RES_INT_CAP (M800C2): Not enough
RRC:connection capacity available inside RNC to
setup
terminate the connection
‐ RES_OTHER (M800C3): Any other RNC internal reason.

45 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Resource Reservation in Iub (similar with IuR)

BTS (WAM) RNC

UE AAL2 SIG CAC CAC AAL2SIG ATM RM RRC
RRC: connection request

3 There are detailed counters for AAL2 signaling in measurement

“AAL2 signalling protocol at UNI” (M548), refer to description of 1
that measurement for details RNC internal transport
resource reservation
AAL2 connection establishment ERQ (SUGR) 2

WBTS internal transport

resource reservation 3

Response to ERQ; ECF or RLC (cause)

AAL2 conn. estab. confirmation

4
RRC:connection setup

46 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Resource Reservation in Iub (similar with IuR)

BTS (WAM) RNC

UE AAL2 SIG CAC CAC AAL2SIG ATM RM RRC
RRC: connection request
4 Depending of the result of AAL2 signaling with BTS or AXC, following
counters are updated.
‐ AAL2_SUCCEEDED (M800C4) 1
RNC internal transport
‐ AAL2_REJECTED (M800C5) resource reservation
For shared HSDPA AAL2
AAL2 allocation
connection there is
establishment dedicated
ERQ (SUGR) signaling counter. 2
‐ AAL2_SUCCEEDED_HSDPA (M800C6)
WBTS internal transport
resource reservation 3

Response to ERQ; ECF or RLC (cause)

AAL2 conn. estab. confirmation

4
RRC:connection setup

47 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Resource Reservation (M800)

RNC_602a: AAL2 connection reservation success rate

• The transport resource request success ratio [%]. This KPI describes the
average success rate of the transport resource reservation attempts for AAL2
type connections.
100 *(sum(AAL2_SUCCEEDED)/
sum(AAL2_SUCCEEDED+AAL2_REJECTED+RES_EXT_CAP+RES_INT_CAP+RES_OTHER))%

100 *(sum(M800C4)/sum(M800C4+M800C5+M800C1+M800C2+M800C3))%

M800C0 Successful reserved resource requests in RNC

M800C4 AAL2 signaling requests which have been successfully executed in A2SP
M800C5 AAL2 signaling requests which have failed for any reason. E.g. signaling failed or UL:CAC reject.
M800C1 Transport resources requests which are rejected by DL:CAC since there is not enough capacity in the
external AAL2 path.
M800C2 Resource reservations which are rejected by DL:CAC since there are no RNC-internal AAL2 processing
resources available.
M800C3 Resource reservations which have failed for any other reason than CAC or signaling (for example route
analysis, parameter or DSP resource allocation problem).

48 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

AAL2 Path CAC Resource Measurement (M550)

• AAL2 connections are allocated and released by ATM Resource

Management which will check AAL2 reservation using CAC.
• M550 measurement reports RNC CAC resource usage for Iub
AAL2 user plane traffic downlink per VCC
• Counters for configured and reserved bandwidth, as well as
maximum and minimum reserved bandwidth are available
• Useful for monitoring Iub (DL) and Iucs (UL) and Iur load
• Feature 1214 removes the limit on number of objects that can be
measured at the same time!

49 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Connection Setup KPIs (Network point of view)

These KPI does not necessarily represent the UE perception of RRC connection success rate.

In case of Layer 3 failure, UE will retransmit RRC CONNECTION REQUEST message, as

defined by the parameters N300 and T300.

On the other side, if PRACH coverage is inadequate, the RNC may not even receive the RRC
CONNECTION REQUEST message. The UE attempt would then fail without the RNC having
any knowledge.

RRC Conn Setup Succ Rate =

100*sum([RRC_CONN_STP_COMP]) / sum([RRC_CONN_STP_ATT] +
[RRC_CONN_SETUP_COMP_AFT_DIR] - [RRC_CON_SETUP_COMP_DIRECTED])

KPI Formula: RNC_20b = 100*sum([M1001C1]) / sum([M1001C0] + [M1001C259] - [M1001C260])

50 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 RRC Performance – Signaling and Trigger points positive
UE Node B RNC
[RACH] RRC:RRC Connection Request
M1001C0
AC to check to accept
or reject RRC
Connection Request

RRC Connection Setup NBAP: RL Setup Request

Allocation of UTRAN
phase Start TX/RX

NBAP: RL Setup Response

resources
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection Setup We are here

M1001C1
Start TX/RX

L1 Synchronisation
RRC Connection Access
NBAP: Synchronisation Indication Waiting for UE reply
phase

[DCH] RRC: RRC Connection Setup Complete

M1001C8
RRC Connection Active phase

RRC active complete drop Pre-Emption SRNS Relocation

51 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
 RRC Access Phase

52 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access phase
UE side Network side

Time
UE initiates physical dedicated channel establishment
before sending e.g. RRC Connection Setup Complete –
message on DPDCH

Timer T312 started

N312 L1 “in sync”

indicators received in DL

L1 Synchronization
established, T312 stopped
and reset

UE starts to send UL DPCCH, PC premable &

WBTS starts to receive “in-sync” indicators.
SRB-delay amount of DPCCH frames
Receiving N_INSYNC_IND indicators on L1
within 40 ms, L1 synchronization is
considered established

BTS sends NBAP: SYNCHRONIZATION INDICATION

PC preamble & SRB-delay amount of DPCCH to RNC after another 80 ms of maintained
frames sent by UE synchronisation

RRC Connection Setup Complete –message

SENT after PC preamble & SRB delay TSLs from
DL sync is achieved RNC receives RRC
Connection Setup Complete –
message ->
53 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RRC Setup & Access Phase
In case UE is not able to establish synchronization within timer T312 it
stops Tx on the DCH
In case BTS is not able to establish synchronization it does not send
NBAP:Synchronization Indication –message to RNC
The BTS tries to establish synchronization until RNC sends NBAP:Radio
Link Deletion -message

UE Node B RNC
[RACH] RRC:RRC Connection Request

NBAP: RL Setup Request

Start
TX/RX
NBAP: RL Setup Response
ALCAP:ERQ

ALCAP:ECF

[FACH] RRC: RRC Connection Setup

Start
TX/RX

L1 Synchronisation

54 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

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 UE Node B RNC
COMPLETE” message UE transmits using
the established dedicated channel [RACH] RRC:RRC Connection Request

NBAP: RL Setup Request

This procedure can be quite critical since it
Start
includes both UL and DL L1 synchronization TX/RX
of the signaling dedicated channel to be NBAP: RL Setup Response
setup ALCAP:ERQ

It ends with RRCC Setup Complete or after 6 ALCAP:ECF

seconds (as failure) [FACH] RRC: RRC Connection Setup

Start
TX/RX

L1 Synchronisation

NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete

55 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access Phase
UE Node B RNC
[RACH] RRC:RRC Connection
Request
AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request Sent RRC Connection Setup –message triggers:
RNC_327a=(M1001C1) RRC_CONN_STP_COMP
Start TX/RX
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection

Setup
Start TX/RX

L1 Synchronisation
NBAP: Synchronisation Indication
X • Failure in receiving the RRC Connection Setup
Complete and missing NBAP Synchronisation
Indication: RNC_335a = (M1001C9)
RRC_CONN_ACC_FAIL_RADIO is updated
X
[DCH] RRC: RRC Connection Setup Complete

56 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access Phase
UE Node B RNC
[RACH] RRC:RRC Connection
Request
AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request Sent RRC Connection Setup –message triggers:
RNC_327a=(M1001C1) RRC_CONN_STP_COMP
Start TX/RX
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection

Setup
Start TX/RX

L1 Synchronisation

NBAP: Synchronisation Indication

• Failure in receiving the RRC Connection Setup
Complete and NBAP Synchronisation Indication is
received : RNC_336a = (M1001C10)

X
[DCH] RRC: RRC Connection Setup Complete RRC_CONN_ACC_FAIL_MS

57 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access Phase

UE Node B RNC
[RACH] RRC:RRC Connection
Request
AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request Sent RRC Connection Setup –message triggers:
RNC_327a=(M1001C1) RRC_CONN_STP_COMP
Start TX/RX
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection

Setup
Start TX/RX

L1 Synchronisation

NBAP: Synchronisation Indication

If RNC has internal failure before RRC Connection Setup
Complete has been received then the counter RNC_337a =
[DCH] RRC: RRC Connection Setup Complete M1001C11 RRC_CONN_ACC_FAIL_RNC is incremented

58 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (1/10)

Call flow improvement:

1001C9 L1 synchronization in BTS

Node B
phases of initial
UE RNC
setup/RRC CN/SGSN

RRC setup RRC connection access phase

RRC: RRC Connection Setup (FACH)
Access phase

RRC
Connection

UE reply
period
connection access RRC setup
L1 Synchronisation
RRC

completed
and access
NBAP: Synchronisation Indication
Triggers: complete
1001C8 RRC ratio [%]
Access Complete
[DCH] RRC: RRC Connection
Start UE
Setup Complete

Failure Case: RRC Connection Access fails, due to Triggers:

1001C9 L1 synchronization in BTS
1001C10 air interface (path loss UL/DL)
1001C11 RNC internal reason

59 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (2/10)
In case of good link quality
- quicker access to NW
- post verification of L1 synch. improves initial setup time by 70 ms

Node B
UE transmits at T 1
Serving cell
Node B T0
Non serving cell T1
Good link quality

60 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (3/10)

Standard 3GPP handling

UE checks link QoS 70 ms
Node B starts UE starts
UE listing 1st in-sync 2nd 3nd UE starts DCH transmitting
transmitting receiving 4nd
on FACH primitive

10 ms radio
frames 40 ms window
40 ms window
Delay while UE
receives RRC 40 ms window
Connection Setup 40 ms window
message on the UE transmits at T 1
FACH UE L1 collects 40 ms of
quality measurements Node B

Serving cell
Node B T0
Non serving cell T1
T 2 fails
UE transmission
(no in-sync) T 2
Good link quality,
but we waste time
61 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RRC Access L1 synchronization - (4/10)

Improved (introduced in RU20) handling

Node B starts
transmitting Post verification no failure due to in-sync
UE starts
transmitting at T1

40 ms window
10 ms
frames
UE starts listing on DCH

RRC Connection
Setup send still on Node B
FACH
But now UE enters UE transmits at T 1
DCH
Serving cell
Node B T0
Non serving cell T1

62 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (5/10)

In-sync evaluation
In Sync and Out of Sync on DL
DPCCH quality check
DPDCH CRC

Node B
UE transmits at T 1
Serving cell
Node B T0
Non serving cell T1
UE transmission
fails (no in-sync) T 2

63 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (6/10)

In-sync evaluation In Sync and Out of Sync on DL DPCCH

quality check DPDCH CRC
At least one TB in the last radio
in sync indication 20 last TBs received
frame received with correct CRC
with incorrect CRC

AND
DPCCH_Ec/Io OR out of sync indication
160 ms

Qin

160 ms Qout

time
Toff Ton

3GPP TS25.101 V5
UE shuts power off UE shuts power on

64 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (7/10)

In-sync evaluation
A UE must check the synchronisation When a physical dedicated channel
status of every radio frame of downlink establishment is initiated by the UE, the UE shall
dedicated channels. The synchronisation start a timer T312 and wait for layer 1 to indicate
status is reported to the higher layer. N312 "in sync" indications. On receiving N312
"in sync" indications, the physical channel is
The reporting criteria split in two phases: considered established and the timer T312 is
Phase 1: Physical channel establishment stopped and reset.
During the first 160 ms after the If the timer T312 expires before the physical
establishment of a dedicated physical channel is established, the UE shall consider
downlink channel this as a "physical channel failure".
If the DPCCH quality from measurements >
Qin over a period of 40 ms -
In-sync messages are sent to the higher
layers

65 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (8/10)

Improved handling Less access failure Than RRC connection setup

due to radio reason complete still missing
More access failure due to
MS reason
Node B starts
transmitting UE stops transmitting if
UE starts
transmitting verification check fails (still no in-sync at T 2)

40 ms window
10 ms
frames Post verification
UE starts listing on DCH

RRC Connection UE transmits at T 1

Setup send still on Node B
FACH
But now UE enters
DCH
Serving cell
Node B T0
Non serving cell T1
T2
UE transmission
fails (no in-sync) T 2

66 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (9/10)

UE starts transmitting
without
The total delay before UE starts UL
transmission is reduced by 70 ms. Post Verification

40 ms window
[DCH] RRC Setup Complete
40 ms window
RRC Connection Access phase
40 ms window
50 ms window
Node B starts transmitting
40 ms window

FACH: RRC Connection Setup UE starts transmitting UE stops transmitting if

with Post Verification verification check fails

10 ms radio
frames
40 ms window
UE starts receiving,
mobile is listing on DCH Post verification
UE L1 collects 40 ms
check
of quality
measurements

67 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access L1 synchronization - (10/10)

L1 synchronization improvement in BTS at counter 1001C9

UE Node B RNC
phases of initial RRC setup
Counter A
RACH: AC checks to accept/reject
RRC RRC connection request
Connection
Request

resources
RRC Connection

Allocation
NBAP: RL Setup Request
Setup phase Start TX/RX

of
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF

FACH: RRC Connection Setup

Start NB Counter B
RRC Connection
UE KPI: ratio counter C / B
Access phase L1 Synchronisation
NBAP: Synchronisation Indication
reply Success of L1
Improvement of period Synchronisation
L1 synch.
DCH: RRC Connection
Start UE Counter C
RRC Connection Setup Complete
Active phase

68 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access failures, distribution

L1 Synchronisation
NBAP: Synchronisation Indication

RRC: RRC Conn Setup Complete X

UE
X RNC
BTS

RRC Access Failures RADIO (for L1 synchronization)

RRC Access Failures due to MS

Cell Reselections (not a failure)

L1 Synchronisation
NBAP: Synchronisation Indication

RRC: RRC Conn Setup Complete

UE
X RNC
BTS

69 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

No RRC Conn Setup Complete received
Possible reason: Cell Reselection

M1001C0 RRC_CONN_STP_ATT (A)=1

M1001C1 RRC_CONN_STP_COMP (A)=1
M1001C8 RRC_CONN_ACC_COMP (A)=0

UE RNC
RRC Connection Request
Cell A
M1001C0 RRC_CONN_STP_ATT (B)=1
RRC Connection Setup
Cell A
M1001C1 RRC_CONN_STP_COMP (B)=1
M1001C8 RRC_CONN_ACC_COMP (B)=1
RRC Connection Request
Cell B
RRC Connection Setup M1001C241 RRC_CONN_ACC_REL_RESEL (A)=1
Cell B

RRC Conn Setup Complete

Cell B

CELL A COUNTS RESELECTION (WITHIN 6 SECONDS after RRCC

SETUP) AS THE REASON FOR ACCESS FAILURE
70 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
Directed RRC Connection Setup

• Within two cells of one sector Directed RRCC Setup is possible for load or
service reasons. This is reflected in counters and KPIs
M1001C0 RRC_CONN_STP_ATT (A)=1
M1001C260 RRC_CONN_STP_COMP_AND_REDIR (A)=1
M1001C259 RRC_CONN_STP_COMP_AFT_REDIR (A)=0
UE RNC M1001C8 RRC_CONN_ACC_COMP (A)=0
RRC Connection Request
Cell A, f1

RRC Connection Setup Cell A, f1

UE directed to f2

RRC Connection Setup Complete

Cell B, f2

M1001C0 RRC_CONN_STP_ATT (B)=0

M1001C260 RRC_CONN_STP_COMP_AND_REDIR (B)=0
M1001C259 RRC_CONN_STP_COMP_AFT_REDIR (B)=1
M1001C8 RRC_CONN_ACC_COMP (B)=1

71 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Exercise

• Using the KPI documentation, prove that the KPIs for RRC Setup
and Access Complete show correct values on cell and RNC level
• Disregard M1001C617 for this exercise

72 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Setup Time KPI

This KPI represents the average time to successfully establish an RRC connection.

UE RNC
RRC Connection Request

/ 100s 
RRC Connection Setup
AVE _ RRC _ SETUP _ TM
RRC Connection Setup Complete
DENOM _ RRC _ SETUP _ TM
X
Updating
point
M1001C221/M1001C222

AVG_RRC_SETUP_TM sums the times for all the successful RRC Conn 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.

73 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Drop Rate KPI

 RRC _ CONN _ ACT _ FAIL _ xxx

100 *
all _ failures
%
RRC _ CONN _ ACT _ COMP  RRC _ CONN _ ACT _ REL _ P _ EMP 
RRC _ CONN _ ACT _ REL _ SRNC   RRC _ CONN _ ACT _ FAIL _ xxx
all _ failures

•Successful RRC Setup ->

RRC_CONN_ACC_COMP is •RRC Drop here causes
updated RRC_CONN_ACT_FAIL_xx to be
incremented,
RRC_CONN_ACT_COMP is not
incremented

The denominator and nominator are incremented in SAME cells therefore no

problems with mobility
However all the failures might not be captured by RRC_CONN_ACT_FAIL_xxx
counters (error is quite marginal)
The KPI is meaningful for cluster/cell level and on day/hour basis
74 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
Traffic counters for RRC setup and access

75 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Traffic measurements
Introduction

TRAFFIC MEASUREMENTS provide information on transport channel DCH

requests and allocations, and on compressed mode requests and allocations.

The measurement is carried out in the controlling RNC (CRNC) that, from the
user plane point of view, may be either the SRNC or the DRNC.

For SRB and every RAB type (CS voice, CS video, PS Inter, PS Back, PS Str)
the following KPIs can be defined:
– DCH REJ RATE (UL and DL)
– DCH ALLOCATION RATE
– DCH ALLOCATION DURATION

76 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Access Phase
RRC Connection Request triggers M1002 request
UE Node B RNC counters
[RACH] RRC:RRC Connection Request

AC to check to accept
or reject RRC
Connection Request
NBAP: RL Setup Request
M1002 reject counters are triggered by AC, if there
Start TX/RX are not enough air interface resources
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF

[FACH] RRC: RRC Connection

Setup
Start TX/RX RRC Connection Setup Complete triggers M1002
allocation counters
L1 Synchronisation

NBAP: Synchronisation Indication

[DCH] RRC: RRC Connection Setup Complete

77 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Traffic Table: DCH request for Signalling

M1002C1 DCH_REQ_LINK_REJ_UL_SRNC UL DCH Reject

M1002C0
DCH_REQ_LINK_SRNC
DCH request for RRC M1002C2 DCH_REQ_LINK_REJ_DL_SRNC  DL DCH Reject
Connection, SHO, HHO and
state transition CELL_FACH 
CELL_DCH

= M1002C10 DCH_ALLO_LINK_3_4_SRNC
M1002C11 DCH_ALLO_13_6_SRNC
M1002C3
DCH_REQ_RRC_CONN_SRNC
DCH request only for
RRC Connection

+
M1002C4
DCH_DHO_REQ_LINK_SRNC M1002C5 DCH_DHO_REQ_LINK_REJ_SRNC
DCH request only for
SHO

+
M1002C339
DCH_HHO_REQ_LINK_SRNC M1002C340 DCH_HHO_REQ_LINK_REJ_SRNC
DCH request only for
HHO

The term DHO (diversity handover)

is used in the counter names as a synonym for SHO.
78 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
UL/DL DCH blocking Sign Link PIs

This set of KPIs is useful to understand if blocking at RRC level is due to UL AC or DL

AC.

100%
DCH_REQ_LINK_REJ_UL_SRNC
UL DCH Reject Rate Sign 
DCH_REQ_LINK_SRNC

100%
DCH_REQ_LINK_REJ_DL_SRNC
DL DCH Reject Rate Sign 
DCH_REQ_LINK_SRNC

79 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

DCH allocation duration Signalling Link PI

DCH_ALLO_DURA_LINK_3_4_SRNC  DCH_ALLO_DURA_LINK_13_6_SRNC
DCH Duration Sign  s
100

Counter Unit=10ms.
Counter value updated every s
Upon release, M1002 duration counters are updated with the (sub-
second) time since latest update.
This update goes to all cells in AS that are affected by the release

80 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Analysis or RRC Connection Setup Complete message

81 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection setup complete information
analysis (1/3)
UE capability information in RRC Connection Setup Complete

UE capability carries information for:

• IP Header Compression algorithms

• IFHO/ISHO measurements (CM/DR)
• Packet Scheduler bitrates supported
• Location Measurements (RTT/GPS)
• Physical channels supported
• High Speed Packet Access Capabilities
• IS-NACC

82 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC connection setup complete info analysis (2/3)
PM counters available for analyzing the information elements in RRC connection setup complete
message: UE CAPABILITIES

The number RRC connection establishments by UEs that support:

M1001C389 UE_SUPPORT_FOR_IPHC - RFC2507 IP header compression

M1001C390 UE_SUPPORT_FOR_ROHC - RFC 3095 (robust HC)
M1001C404 ACCESS_STRATUM_REL_IND_4 - 3GPP Release indicator release 4
M1001C405 ACCESS_STRATUM_REL_IND_99 - 3GPP Release indicator release 99
M1001C406 UE_SUPPORT_GSM – GSM
M1001C407 UE_SUPPORT_MULTICARRIER_CDMA - Multi-carrier CDMA
M1001C408 UE_RXTX_POSITION_CAPAB_2 - UE RX-TX time difference positioning capability type 2
M1001C552 ACCESS_STRATUM_REL_IND_5 - 3GPP Release indicator release 5
M1001C616 ACCESS-STRATUM_REL_IND_6 - 3GPP Release indicator release 6
M1001C595 UE support for Network Assisted GPS
M1001C709* ACCESS STRATUM RELEASE INDICATOR RELEASE 9
M1001C715 EUTRA CAPABILITY FDD
M1001C716 EUTRA CAPABILITY TDD

* these counters are currently not supported

83 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009
RRC connection setup complete info analysis (3/3)
HSPA capability information:
The number of RRC connection establishments by UEs supporting HS-DSCH
classes:
< UE category >
1,2,3,4,5 or 6 M1001C548 UE_SUPP_HSDSCH_CLASS_1_6
7 or 8 M1001C549 UE_SUPP_HSDSCH_CLASS_7_8
9 or 10 M1001C550 UE_SUPP_HSDSCH_CLASS_9_10
11 or 12 M1001C551 UE_SUPP_HSDSCH_CLASS_11_12

The number of RRC connection establishments by UEs supporting E-DCH

classes:
< UE category >
1 M1001C610 UE SUPPORT FOR CATEGORY 1
2 M1001C611 UE SUPPORT FOR CATEGORY 2
3 M1001C612 UE SUPPORT FOR CATEGORY 3
4 M1001C613 UE SUPPORT FOR CATEGORY 4
5 M1001C614 UE SUPPORT FOR CATEGORY 5
6 M1001C615 UE SUPPORT FOR CATEGORY 6

84 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC counters per Establishment Cause: Attempts and
Failures, M1001C22-61

85 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Active Phase

86 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC active phase

• There are also counters to follow up events in RRC active phase

• M1001C12 for normal completion
• Further counters for releases and failures

UE RNC CORE
RRC Connection Request

Setup Phase
RRC Connection Setup

Access Phase
RRC Connection Setup Complete

Active Phase
IU Release Command

87 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC active phase counters

RRCC complete
M1001C12 RRC_CONN_ACT_COMP

RRCC releases RRCC failures

M1001C13 ff. triggered by: M1001C15 ff. triggered by:
Relocation Iu Interface failure
Pre-Emption Radio Interface failure
CN unspecified error BTS
Inactivity in URA/Cell_PCH Iur Interface failure
RNC HW shortage Ciphering
Directed Retry RNC internal failure
IS/GAN HO UE
Inter-RNC Inter-/Intra-F HHO

88 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Further important RRC Active failure counters

• M1001C391 RRC_CONN_ACT_FAIL_UE
• Updated in case of:
• UE is not responding to an RRC message within a given time
• UE is responding with such failure message (e.g. configuration unsupported) that
the connection must be released
• M1001C21 RRC_CONN_ACT_FAIL_RNC
• Updated in case of:
• RNC internal reasons
• Transmission failure
• FP synchronisation loss

89 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Usage/Request KPI – new in RU40
RNC_5448a NAS BHCA:
• Busy Hour Call Allocation attempts for non Radio Access Bearer related RRC
Connection Establishment request causes
• Measurement 1001: Service Level

KPI formula: KPI formula with short names

sum([M1001C42]+ [M1001C44]+ sum([INTR_RAT_CELL_RE_SEL_ATTS]+ [CELL_CHNG_ORD_ATTS]+
[M1001C46]+ [M1001C48]+ [REGISTRATION_ATTS]+ [DETACH_ATTS]+
[M1001C50]+ [M1001C52]+ [MOC_HIGH_PRIOR_SIGN_ATTS]+ [MTC_HIGH_PRIOR_SIGN_ATTS]+
[M1001C54]+ [M1001C56]+ [MOC_LOW_PRIOR_SIGN_ATTS]+ [MTC_LOW_PRIOR_SIGN_ATTS]+
[M1001C60]+ [M1001C30]) [MTC_CAUSE_UNKNOWN_ATTS]+ [MOC_SUBSC_TRAF_CALL_ATTS])

KPI class: Usage/Requested Capacity

Unit: Integer number
Object summary levels: Network, City, Area, RNC, Cluster of cells, Cell
Time summary levels: Total; week; weeklyBH; day; dailyBH; hour

90 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Common Channel Set Up

91 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Common Channel Setup
Mobility requirements
- Common Channel entry - no directed RRC

Directed RRC Connection Setup

RRC Idle Cell_PCH f3, HSDPA&HSUPA
Cell_DCH • UE’s cell known
• no UE Location • DCH allocated • UE to be paged
Information • UE’s cell known Layering supported, if
(DRX functionality
in UTRAN  PICH)
• only LAI / RAI
afterwards transition
in CN
• no data transfer Cell_FACH to Cell_DCH
f2, HSDPA
possible
(HSDPA) triggered
• RRC Connection
establishment via
Cell_FACH URA_PCH
RACH/FACH • common channel • similar to Cell_PCH
signaling allocated (FACH, UE Rel-6 •capability C
no Cell Update,
New RACH, CPCH, DSCH) but URA Update
No directed RRC
Establish • UE’s cell known
/ Release UE Rel5/6 & B f1, R´
R´99
Connection HSDPA
mode capability
(f1 to f2) RRC
Connection
Any other UE A

Concept: Booking of
resources/load within CCH first,
no direct shift of load to other
layer (Directed RRC)

92 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Common Channel Setup

M1001

M1001C678 RRC SETUP ATTEMPT CCH

M1001C679 RRC ACCESS COMPLETE CCH
M1001C680 RRC ACCESS RELEASE DUE TO CELL RESELECTION CCH
M1001C681 RRC SETUP ATTEMPT REPEATS CCH

93 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 M1006 RRC Measurements

94 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RRC Signaling Measurements
M1006C200 INACTIVE HSPA UP RELESE DUE TO PREVENTIVE OVERLOAD
The number of inactive HSPA user plane releases due to preventive overload control
• when an RRC signalling entity receives an RRC: RADIO BEARER
RECONFIGURATION COMPLETE message after successful HSPA user plane release
to Cell-FACH or DCH 0/0 due to preventive overload control
M1006C201 CAPACITY REQ FOR RELESED HSPA DUE TO PREVENTIVE
OVERLOAD
The number of times when UL or DL capacity request is received for a user within 10
seconds of user plane release due to preventive overload control
• when either UL or DL capacity request is received for a radio bearer whose HSPA user
plane has been released within previous 10 seconds due to preventive overload control
M1006C202 RADIO BEARER CONFIGURED FOR FLEXIBLE RLC
The number of radio bearer setups and reconfigurations to use Flexible-RLC
• when the UE replies with RRC: RADIO BEARER SETUP COMPLETE or RRC: RADIO
BEARER RECONFIGURATION COMPLETE indicating a successful configuration of
Flexible-RLC and Flexible RLC was not in use before the reconfiguration.

95 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009 *) feature in RU20EP

RRC Signaling Measurements
Related to Packet Data Transfer States
M1006C253 CELL UPDATE ATT DUE TO CS CALL
Description: The number of started Cell Update procedures with establishment cause "Originating
Conversational Call", "Terminating Conversational Call", or "Emergency Call". "Establishment cause"
is an optional IE in the Cell Update message introduced by 3GPP Rel5. Also one of the basic Cell
Update counters M1006C34-M1006C40 is updated along with this counter depending on the "Cell
update cause" IE used by the UE.
Updated: When the RNC receives RRC: CELL UPDATE message with cause "Originating
Conversational Call", "Terminating Conversational Call", or "Emergency Call". Logical type: Sum
Trigger type: Event; Unit: Integer number

M1006C254 CELL UPDATE SUCCESS DUE TO CS CALL

Description: The number of successful Cell Update procedures with establishment cause
"Originating Conversational Call", "Terminating Conversational Call", or "Emergency Call".
"Establishment cause" is an optional IE in the Cell Update message introduced by 3GPP Rel5. Also
one of the basic Cell Update counters M1006C34-M1006C40 is updated along with this counter
depending on the "Cell update cause" IE used by the UE.
Updated: When the UE responds with Radio Bearer Reconfiguration Complete or UTRAN Mobility
Information Confirm after the RNC has sent Cell Update Confirm as a response to Cell Update with
the mentioned causes. Logical type: Sum Trigger type: Event; Unit: Integer number

96 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2167 State Transition Counters – new in RU40 1/2
• adds new counters at the cell level to receive more detailed statistics of UE state transitions.
• complete the existing counter set, therefore, enhance monitoring capabilities
• introduces "from and to" Cell_FACH, Cell_DCH, E-DCH, PCH transitions and transition attempts
• operator benefits from monitoring activities related to:
• an increase of bursty data activities sites for which the base transceiver station (BTS) experiences
excessive signaling because of lack of fine tuning on the inactivity timers
• fast dormancy phenomena (indirect)
• low connection establishment success rates
on RRC-connection level
M1006C223 CELL_FACH TO IDLE
(not separately for each RAB )
M1006C224 CELL_FACH TO CELL_DCH ATTEMPTS on RRC-connection level
M1006C225 CELL_DCH TO CELL_FACH ATTEMPTS on RRC-connection level
M1006C226 CELL_FACH TO PCH ATTEMPTS on RRC-connection level
M1006C227 PCH TO CELL_FACH ATTEMPTS on RRC-connection level
M1006C228 CELL_DCH TO PCH ATTEMPTS on RRC-connection level
M1006C229 PCH TO CELL_DCH ATTEMPTS on RRC-connection level
M1006C230 CELL_FACH TO HS-DSCH/E-DCH ATTEMPTS for each RAB
M1006C231 HS-DSCH/E-DCH TO CELL FACH ATTEMPTS for each RAB
M1006C232 FACH TO HS-DSCH/E-DCH SUCCESSFUL for each RAB

97 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2167 State Transition Counters – new in RU40 2/2

Related counters:

M1006C45 CELL DCH STATE TO CELL FACH

M1006C46 CELL FACH STATE TO CELL DCH
M1006C170 STATE TRANSITION TIME PCH TO FACH
M1006C171 DENOMINATOR FOR STATE TRANSITION TIME PCH TO FACH
M1006C180 STATE TRANSITION TIME FACH TO PCH
M1006C181 DENOMINATOR FOR STATE TRANSITION TIME FACH TO PCH

98 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RNC_5446a Number of State Transition – new in RU40
Number of state transitions KPI
• the sum of all state transitions excluding when coming from idle to CELL-DCH or when going to idle
from any state.

KPI formula (Counters): KPI formula (counters name):

sum([M1006C171]+ sum([DENOM_ST_TRANS_TIME_PCH_FACH]+
[M1006C173]+ [DENOM_ST_TRANS_TIME_FACH_DCH]+
[M1006C175]+ [DENOM_ST_TRANS_TIME_PCH_DCH]+
[DENOM_ST_TRANS_TIME_DCH_FACH]+
[M1006C177]+
[DENOM_ST_TRANS_TIME_DCH_PCH]+
[M1006C179]+
[DENOM_ST_TRANS_TIME_FACH_PCH])
[M1006C181])

Object summary levels Network, City, Area, RNC, Cluster of cells, Cell
Time summary levels Total; week; weekly BH; day; daily BH; hour

99 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2494 Fast Cell_PCH Switching – new in RU40
• reduces the state transition time from Cell_PCH and Cell_FACH
• decreasing state transition time to Cell_DCH state and thus improving the end-user experience in
case e.g. of web browsing

Functionality:
• RNC transmitts smaller message size and subsequently shorter overall state transition time
• RRC signaling is started in parallel with reservation of RNC L2 resources, which reduces state
transition time.
• optimization of UE message is applied mainly in cases where newly allocated configuration is the
same as previous configuration already stored at the UE.

Related counters (existent):

M1006C174 STATE TRANSITION TIME PCH TO DCH
M1006C175 DENOMINATOR FOR STATE TRANSITION TIME PCH TO DCH

100 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RNC_5456a HS-FACH session attempts – new in RU40
• HS-FACH session attempts.
• Measurement 1006: RRC signalling

KPI formula: KPI formula with short names:

sum([M1006C249]) sum([RB_CONFIG_HSFACH_DL])

• HS-FACH session attempts – only HS-FACH DL configuration counter is taken into

account in this KPI.

KPI class: Usage/Requested Capacity

Unit: Integer number
Object summary levels: Network, City, Area, RNC, Cluster of cells, Cell
Time summary levels: Total; week; weeklyBH; day; dailyBH; hour

101 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RNC_5459a HS-FACH Setup Success Ratio – new in RU40
• success ratio of transitions from CELL_DCH or CELL_PCH to Enhanced CELL_FACH.
• Measurement 1006: RRC signalling

KPI Formula:
100*sum([M1006C216] + [M1006C220]) / sum([M1006C215] + [M1006C219])
KPI formula with short names:
100*sum([SUCC_DCH_TO_EFACH] + [SUCC_PCH_TO_EFACH])

/
sum([ATT_DCH_TO_EFACH] + [ATT_PCH_TO_EFACH])

KPI class: Accessibility

Unit: %
Object summary levels: Network; City; Area; RNC; WBTS; Cluster of cells; Cell
Time summary levels: Total; week; weeklyBH; day; dailyBH; hour

102 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RNC_5476a HS-FACH Success Ratio – new in RU40
• success ratio of transitions from Enhanced CELL_FACH to CELL_DCH or CELL_PCH.
• Measurement 1006: RRC signalling

KPI formula:

100*sum([M1006C218] + [M1006C222]) / sum([M1006C217] + [M1006C221])

KPI formula with short names:
100*sum([SUCC_EFACH_TO_DCH] + [SUCC_EFACH_TO_PCH])
/
sum([ATT_EFACH_TO_DCH] + [ATT_EFACH_TO_PCH])

KPI class: Accessibility

Unit: %
Object summary levels: Network; City; Area; RNC; WBTS; Cluster of cells; Cell
Time summary levels: Total; week; weeklyBH; day; dailyBH; hour

103 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

 Fast Dormancy

104 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2136: Fast Dormancy – RU30

Fast Dormancy (On Top)

- it is an 3GPP Rel.8 feature optional for UEs
- to reduce the signaling load between the 3G network and the UE and to save the UE’s battery life
- UE informs the network when a PS data transmission ends
- the network changes the UE state directly to Cell_PCH or URA_PCH state, which lowers the UE
battery consumption considerably, instead of staying in Cell_DCH or Cell_FACH state.

If the UE needs to send or receive data the required signaling from Cell/URA_PCH state is only a
fraction of the signaling needed in starting from IDLE mode

This feature does not require activation. Fast Dormancy is active by default.

105 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Fast Dormancy UEs – RU20 and RU30
Fast Dormancy
• UE requests from network to be shifted to state of low battery power consumption
because data session ended
• UE sends signaling connection release indication, “simulating” this way signaling
connection failure
RU20
• RRC connection is released, i.e. UE shifted to idle state
• RRC connection, RAB and radio bearer have to be re-established, if new data shall be
sent
• High signaling load introduced by UEs frequently transmitting small amount of data
RU30
• RNC tries to shift UE to Cell_PCH, i.e. to keep the RRC connection and the RAB
• No “ping-pong” between release and reestablishment, if new data shall be sent

106 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Fast Dormancy – Smart Phone Handling
• UE sends signaling connection release indication with cause UE requested PS
data session end (fast dormancy request)
→ not shifted to idle mode, but to Cell_PCH
• To prevent too much such request, new timer T323 introduced
→ minimum time between last user data transmission and request or between
consecutive requests
T323
RNC
0,5,10,20,30,60,90,120 s
Default 0 s

Last user data or signaling

UE connection release indication T323 RNC

signaling connection
release indication

107 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Fast Dormancy and Type of RAB in RU30
• The reaction of the RNC due to a fast dormancy request depends on the current type
of (multi)RAB
UE RAB single or multiple PS Single or multiple PS CS RAB
RAB + CS RAB RAB

PS resources are PS resources are Fast Dormancy

State after message released released not supported
“UE Request PS
data session end” UE stays in UE goes to cell_PCH or
cell_DCH URA_PCH

Counter related to the feature

M1006C243 SIG CONN REL IND DUE PS SESSION END
Description: The number of RRC: Signalling Connection Release Indication messages received from
the UE with cause "UE Requested PS Data session end". Also M1006C58 is updated along with this
counter. M1006C58 includes all Signalling Connection Release Indications with or without the cause IE.
Updated: When the RNC receives RRC: Signalling Connection Release Indication message from the
UE, with value "UE Requested PS Data session end" in IE "Signalling Connection Release Indication
Cause".

108 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

RAN2451: Fast Dormancy Profiling – new in RU40
• Fast Dormancy Profiling
 Identify Legacy Fast Dormancy (LFD) phones which cause unnecessary signaling load
 Identified smartphones are moved to Cell_PCH with shorter timers to avoid signaling
connection release
 In addition the data threshold for common channel use is higher, to avoid Cell_DCH
setup just for a keep-alive message
 Stored IMSI gives possibility to faster usage of higher traffic volume thresholds

Counters:
M1006C255 UE IDENTIFIED AS LFDPHONE
M1006C256 LFDPHONE FACH OR DCH TO PCH SUCCESS
M1006C257 LFDPHONE PCH TO FACH OR DCH SUCCESS

109 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009

Thank You !

110 © Nokia Siemens Networks RANKPI /BAs / 05.05.2009