04 RN31584EN10GLA0 Paging+RRC Connection

RN3158 RANKPI Training
Paging and Radio Resource Control Connection

1
Nokia Siemens Networks
RANKPI /BAs / 05.05.2009
Agenda
QoS architecture overview
Radio Resource Control (RRC) connection setup
Theory Signaling Flow
Trigger Points
KPIs
RANKPI /BAs / 05.05.2009
Quality of Service (3GPP 23.107/23.207)

UMTS
TE
MT
UTRAN
CN Iu
EDGE
NODE
CN
Gateway
TE
End-to-End Service
TE/MT Local
Bearer Service
UMTS Bearer Service

Radio Access Bearer
Service
Radio Bearer
Service
RANKPI /BAs / 05.05.2009
Iu Bearer
Service
CN Bearer
Service
Backbone
Bearer
Service
External Bearer
Service
RAB and RRC connection
Radio Access Bearer

Signalling Connection
RRC Connection
Iu Connection
RRC
Radio Bearer
UE
4
UTRAN
Iu Bearer
Uu (RNC) Iu
RANKPI /BAs / 05.05.2009
CN
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.
RANKPI /BAs / 05.05.2009
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.
Radio Access Bearer
XRNC
RRC Connection
UE
Uu
CN
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
6
RANKPI /BAs / 05.05.2009
Paging Procedure
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
incremented
UE is in RRC IDLE Mode

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
incremented
UE is in CELL_PCH or URA PCH

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
UE is in CELL_DCH or CELL_FACH
Paging
Paging Type 2
Event 1
RANKPI /BAs / 05.05.2009
Event 1: PAGING_TYPE_2_ATT
incremented
Paging for UEs in RRC IDLE state
BTS
UE
RNC
UE In Idle mode
CN
When RNC receives paging message

RANAP: Paging from the CN, counter:
M1003C36 REC_PAG_MSG is incremented
RANAP: PAGING
PICH
(FP/AAL2/PCCH/PCH/S-CCPCH) : PAGING TYPE 1
RRC connection establishment
Paging response
If RNC cannot process the paging messages and

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.
RANKPI /BAs / 05.05.2009
Paging for UEs in CELL_PCH or URA_PCH

MM
Connected
2
UE
BTS
RNC
CN1
MM Idle
CN2
Triggers M1003C36 and

M1006C155 PAGING_OCCASION_CELL_PCH
or
M1006C159 PAGING_OCCASION_URA_PCH
UE has signalling connection to CN1

UE is in URA_PCH or CELL_PCH state
RANAP:PAGING
PICH
(RACH) RRC Cell Update : Paging Response
Paging response to CN 2
Triggers M1006C37 CELL_UPD_ATT_PAGING_RESP and

M1006C157CELL_UPD_AFTER_PAG_CELL_PCH
or
M1006C161CELL_UPD_AFTER_PAG_URA_PCH
10
RANKPI /BAs / 05.05.2009
Triggers M1006C25 and

M1006C156 PAGING_MESSAGES_CELL_PCH
or
M1006C160PAGING_MESSAGES_URA_PCH
When there is no repsonse within 2 sec

M1006C158
FAIL_PAG_NO_RESP_CELL_PCH or
M1006C162
FAIL_PAG_NO_RESP_URA_PCH
are triggered
Paging for UEs in CELL_DCH or CELL_FACH
MM
Connected
4
UE
BTS
RNC
CN1
MM Idle
CN2
UE has signalling connection to CN1

UE is in CELL_DCH/FACH state
RANAP:PAGING
PICH
Paging response to CN 2
Triggers M1006C27 PAGING_TYPE_2_ATT
11
RANKPI /BAs / 05.05.2009
Paging for UEs in CELL/URA_PCH due to arriving

data packet from SGSN.
UE
RNC
The
The MAC-d (RLC) in RNC
indicates
indicates that
that there
there is
is
downlink
downlink user data in RLC
buffers
buffers then
then the
the RRC
RRC
signaling
signaling entity
entity initiates
initiates the
the
paging
paging procedure
procedure
SGSN
1.PDP PDU
2. Paging Request (P-TMSI)

RRC: PAGING TYPE 1 with PICH BTS -> UE
MM Cell Update
12
RANKPI /BAs / 05.05.2009
A number of RNC originated paging type 1

attempts (UE in PCH/URA substate).
When RNC sends Paging Type 1 through a
cell, counter M1006C26
PAGING_TYPE_1_ATT_RNC_ORIG is
incremented.
RRC Connection
13
RANKPI /BAs / 05.05.2009
Capacity Areas in UTRAN

During call set-up [RRC, RAB] several resource areas are checked and
physical / logical resources allocated.
Air Interface
WBTS HW Resources Transport
UL interference
DL transmisson power
DL Codes
DSP processing
RLC/MAC
IuB
FSP/ WSP capacity
14
RANKPI /BAs / 05.05.2009
(N*) E1 capacity / AAL2
RNC
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
NBAP: RL Setup Request
RRC Connection
Setup phase
Allocation of UTRAN
Start
Start TX/RX
TX/RX
resources
NBAP: RL Setup Response
ALCAP:ERQ
ALCAP:ECF
[FACH] RRC: RRC Connection Setup
M1001C1
Start TX/RX
L1 Synchronisation
RRC Connection
Access phase
Waiting for UE reply
NBAP: Synchronisation Indication
[DCH] RRC: RRC Connection Setup Complete
M1001C8
RRC Connection Active phase
RRC active complete
15
drop
Pre-Emption
RANKPI /BAs / 05.05.2009
SRNS Relocation
RRC Connection Setup & Access and Active

UE
RNC
BTS
negative
CN
RRC: RRC connection Request

RRC SETUP phase
RRC Setup time
(Resource Reservation in RNC, BTS,

Transport)
RRC: RRC connection Setup
RRC ACCESS phase
(RNC waits for Reply from UE)
RRC: RRC connection Setup Complete
RRC ACTIVE phase
RRC: Initial Direct Transfer
RANAP: Initial UE Message
UE-CN Signalling
(E.g. RAB Establishment and Release)
RRC SETUP fails if some of the needed resources (RNC, BTS,

AIR, Transport) are not available. When an RRC setup failure
occurs the RNC sends an RRC: RRC CONNECTION REJECT
message to UE
RRC ACCESS fails if the UE does not reply to RRC: RRC
CONNECTION SETUP message with the RRC: RRC CONNECTION
SETUP COMPLETE message in given time, if the BTS reports a
radio link synchronisation failure or in an RNC internal failure
occurs
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 Connection. When an RRC active failure
occurs, the RRC send a RANAP: IU RELEASE REQUEST to all
involved CNs and waits for RANAP: IU RELEASE COMMAND
message (s)
RANAP: Iu Release Command

RRC: RRC connection Release
RRC: RRC connection Release Complete
Release RRC resources in RNC,
BTS, Transport
16
RANKPI /BAs / 05.05.2009
RRC ACTIVE release cause can be either ISHO, IFHO, SRSN

relocation or pre-emption
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.
BS
UE
RRC Connection Request
RNC
ICSU overload
RRC Connection Reject

Cause: congestion
Failure Counter
17
RANKPI /BAs / 05.05.2009
M1001C618
RRC Connection is rejected Start of Handover Control fails

BS
UE
RNC
HC setup failure

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
18
RANKPI /BAs / 05.05.2009
M1001C2
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
PrxOffset
marginal load state
overload state
PtxOffset
marginal load state

PrxTarget
feasible load state
PtxTarget
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
19
RANKPI /BAs / 05.05.2009
load
M1001C3

RRC Connection is rejected Air interface (UL/DL) overload (2/2)
Failure Counter
M1002C1
Failure Counter
DCH_REQ_LINK_REJ_UL_SRNC
M1002C2
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
20
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)
21
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
22
RANKPI /BAs / 05.05.2009
M1001C7
RRC connection set up
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
Somewhere
23
30.01.2008 00:00
30.01.2008 01:00
30.01.2008 02:00
30.01.2008 03:00
30.01.2008 04:00
30.01.2008 05:00
30.01.2008 06:00
30.01.2008 07:00
30.01.2008 08:00
30.01.2008 09:00
30.01.2008 10:00
30.01.2008 11:00
30.01.2008 12:00
30.01.2008 13:00
30.01.2008 14:00
30.01.2008 15:00
30.01.2008 16:00
30.01.2008 17:00
30.01.2008 18:00
30.01.2008 19:00
30.01.2008 20:00
30.01.2008 21:00
30.01.2008 22:00
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
RANKPI /BAs / 05.05.2009
2835
2109
1938
1641
1619
1862
2285
3977
5477
7197
7906
9846
10827
10523
11008
9733
11281
13589
9513
8683
8838
14684
12082
2828
2106
1938
1641
1619
1862
2285
3977
5475
7160
7839
9730
10501
10296
10613
9426
9758
9183
8773
7549
6848
4673
4580
3
3
0
0
0
0
0
0
1
0
1
8
60
0
13
8
8
0
1
59
119
20
228
3
0
0
0
0
0
0
0
1
37
66
104
263
223
382
299
1512
4405
738
1074
1531
8639
6266
rrc _ c o n n _ s tp _ fa il_ fro z b s (S e rv le v )
rrc _ c o n n _ s tp _ fa il_ b ts (S e rv le v )
rrc _ c o n n _ s tp _ fa il_ a c (S e rv le v )
rrc _ c o n n _ s tp _ c o m p (S e rv le v )
rrc _ c o n n _ s tp _ a tt (S e rv le v )
R R C _ C O N N _ S T P _ F A IL _ R N T I_ A L L O (S e rv le v )
R R C _ C O N N _ S T P _ F A IL _ IU B _ A A L 2 (S e rv le v )
T im e
3 G N e tw o rk
Frozen WBTS data from RAS05.1 network
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
340
1352
1008
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
24
RANKPI /BAs / 05.05.2009
M1001C247
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
25
RANKPI /BAs / 05.05.2009
M1001C4
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:
26
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
RANKPI /BAs / 05.05.2009

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

Radio Link Setup Response
RL_SETUP_ATT
incremented
RL_SETUP_SUCC
incremented
27
RANKPI /BAs / 05.05.2009

first radio link or state transition Cell_FACH Cell_DCH
There are specific counters for Radio Link Setup procedure at RRC setup
phase:
M1005C0 RL_SETUP_ATT_FOR_FIRST_RL
attempt
success
5 failure reasons
Node B
M1005C14 SETUP_FAIL_RL_BTS_NOT_RESP
RNC
Radio Link Setup Request

Radio Link Setup Response
M1005C5 RL_SETUP_SUCC_FOR_FIRST_RL
RL_SETUP_ATT
incremented
e.g. RL_SETUP_SUCC
incremented
M1005C176 SETUP_FAIL_FIRST_RL_RNL
M1005C177 SETUP_FAIL_FIRST_RL_TNL
M1005C178 SETUP_FAIL_FIRST_RL_PROT
M1005C179 SETUP_FAIL_FIRST_RL_MISC
28
RANKPI /BAs / 05.05.2009
KPI: Radio Link Setup for first radio link Success rate
RL_SETUP_S
UCC_FOR_FI
RST_RL
RL_SETUP_S
UCC_FOR_FI
RST_RL 100[%]
First
_
Link
_
Setup
_
Succ
_
Rate
First _ Link _ Setup _ Succ _ Rate

100[%]
RL_SETUP_A
RL_SETUP_ATT_FOR_FIR
TT_FOR_FIRST_RL
ST_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.
29
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
22.01.2006
worse case:
rl_setup_att_for_first_rl
921490
setup_fail_rl_not_enough_res
149263
Max. blocking due to lack of WBTS Baseband capacity ~ 16 %

30
RANKPI /BAs / 05.05.2009
RRC Connection is rejected Any other failure detected

BS
UE
RNC
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
31
RANKPI /BAs / 05.05.2009
M1001C6
RRC Connection is rejected by DL Connection Admission Control (CAC)

UE
Node B
RNC
AC to check to
Connection Request
Start
Start TX/RX
TX/RX
ALCAP:ERQ
ALCAP:ECF
DL CAC reject
because of ATM

Start TX/RX
L1 Synchronisation
32
RANKPI /BAs / 05.05.2009
Failure Counter
M1001C530
RRC Connection is rejected by UL Connection Admission Control (CAC)

UE
Node B
RNC
AC to check to
Connection Request
Start
Start TX/RX
TX/RX
ALCAP:ERQ
ALCAP:RLC
UL CAC reject from

WBTS
Start TX/RX
L1 Synchronisation

33
RANKPI /BAs / 05.05.2009
Failure Counter
M1001C5
What is AAL2 CAC ?

The AAL2 CAC controls the admission of
AAL2 connections into the ATM VCC
making sure that network has enough
resources to guarantee the QOS for both
existing & new connections requests.
In Iub there are three such algorithms:
RNC CAC for downlink
(complicated)
BTS CAC for uplink (simple)
AXC CAC for uplink in case of
AAL2 multiplexing (simple)
So the AAL2 CAC is guarding the entrance
of the outgoing AAL2 VCC
The ALC parameters define for each bearer:
34
Maximum bitrate
Maximum packet size
Average bitrate
Average packet size
RANKPI /BAs / 05.05.2009
ALC Parameters
ALC Set (for DCCH)
Add/remove connection
Delay
requirement
VCC PCR
Loss tolerance
Input
Reservation
for existing
connections
CAC Algorithm
Output
AAL2 Resource Reservation in Iub
(similar with Iu-CS, IuR)
RNC
BTS (WAM or FTM)

U
E
AAL2 SIG
CAC
RRC: connection request
CAC
AAL2SIG
ATM RM
RRC
RNC internal transport

resource reservation
AAL2 connection establishment ERQ (SUGR)
WBTS internal
transport resource
reservation
1 After the RNC internal

Response to ERQ; ECF or RLC (cause)
reservation is successfully done,
counter RES_SUCCEEDED (M800C0) is updated.

RRC:connection setup
35
RANKPI /BAs / 05.05.2009
AAL2 conn. estab. confirmation
AAL2 Resource Reservation in Iub (similar with IuR)

RNC
BTS (WAM)
U
E
AAL2 SIG
CAC
CAC
AAL2SIG
ATM RM RRC
RNC internal transport

resource reservation
WBTS internal
transport resource
reservation
2 If the RNC internal reservation fails one of the following counters is

updated
36
RES_EXT_CAP (M800C1):
Not enough bandwidth in external ATM
VCC.
RES_INT_CAP (M800C2): Not enough capacity available inside

RNC to terminate the connection
RES_OTHER (M800C3): Any other RNC internal reason.
RANKPI /BAs / 05.05.2009

RNC
BTS (WAM)
U
E
AAL2 SIG
CAC
CAC
AAL2SIG
ATM RM RRC
3 There are detailed counters for AAL2 signaling in measurement
AAL2 signalling protocol at UNI (M548), refer

to internal
RNC
description of that measurement for detailstransport resource
reservation
WBTS internal
transport resource
reservation

37
RANKPI /BAs / 05.05.2009

RNC
BTS (WAM)
U
E
AAL2 SIG
CAC
CAC
AAL2SIG
ATM RM RRC
4 Depending of the result of AAL2 signaling with BTS or AXC,
following counters are updated.
AAL2_SUCCEEDED (M800C4)
AAL2_REJECTED (M800C5)
RNC internal
transport resource
reservation
For shared HSDPA

AAL2
allocation
thereERQ
is dedicated
signaling
AAL2
connection
establishment
(SUGR)
counter.
WBTS
AAL2_SUCCEEDED_HSDPA
(M800C6)
internal
transport resource
reservation

38
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).
39
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!
40
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.
(M1001C1)
(M1001C1)RRC_CONN_S
RRC_CONN_STP_COMP
TP_COMP
RRC
Conn
Setup
Succ
Rate
RRC Conn Setup Succ Rate (M1001C0) RRC_CONN_STP_ATT **100

100 %
%
(M1001C0) RRC_CONN_STP_ATT
41
RANKPI /BAs / 05.05.2009
RRC Performance Signaling and Trigger points

positive
Node B
UE
RNC
M1001C0
AC to check to
Connection Request
RRC Connection
Setup phase
Start
Start TX/RX
TX/RX
!
!
Allocation ofeUTRAN
n
o
resources
D
ALCAP:ERQ
ALCAP:ECF
M1001C1
We are here
Start TX/RX
L1 Synchronisation
RRC Connection
Access phase
Waiting for UE reply
M1001C8
RRC active complete
42
drop
Pre-Emption
RANKPI /BAs / 05.05.2009
SRNS Relocation
RRC Access phase

UE initiates physical dedicated channel
establishment before sending e.g. RRC
Connection Setup Complete message on DPDCH
Time
UE side
Network side
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 &
SRB-delay amount of DPCCH frames
PC preamble & SRB-delay amount of DPCCH

frames sent by UE
RRC Connection Setup Complete message
SENT after PC preamble & SRB delay TSLs
from DL sync is achieved
43
RANKPI /BAs / 05.05.2009
WBTS starts to receive in-sync

indicators.
Receiving N_INSYNC_IND indicators on L1
within 40 ms, L1 synchronization is
considered established
BTS sends NBAP: SYNCHRONIZATION INDICATION
to RNC after another 80 ms of maintained
synchronisation
RNC receives RRC Connection Setup Complete

message ->
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

Start
Start
TX/RX
TX/RX
ALCAP:ERQ
ALCAP:ECF
Start
Start
TX/RX
TX/RX
L1 Synchronisation
44
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 COMPLETE message UE
transmits using the established dedicated
channel
This procedure can be quite critical since
it includes both UL and DL L1
synchronization
of
the
signaling
dedicated channel to be setup
It ends with RRCC Setup Complete or
after 6 seconds (as failure)
UE
Node B
RNC

Start
Start
TX/RX
TX/RX
ALCAP:ERQ
ALCAP:ECF
Start
Start
TX/RX
TX/RX
L1 Synchronisation
45
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
Start TX/RX
Sent RRC Connection Setup message triggers:

RNC_327a=(M1001C1) RRC_CONN_STP_COMP

ALCAP:ERQ
ALCAP:ECF
[FACH] RRC: RRC Connection
Setup
Start
TX/RX
L1 Synchronisation
X
X
[DCH] RRC: RRC Connection Setup

Complete
46
RANKPI /BAs / 05.05.2009
Failure in receiving the RRC Connection Setup

Complete and missing NBAP Synchronisation
Indication: RNC_335a = (M1001C9)
RRC_CONN_ACC_FAIL_RADIO is updated
RRC Access Phase

UE
Node B
RNC

Request
AC to check to
accept or reject
RRC Connection
Request

Start TX/RX
ALCAP:ERQ
ALCAP:EC
F
Setup
Start
TX/RX
L1 Synchronisation
NBAP: Synchronisation
Indication

Complete
47
RANKPI /BAs / 05.05.2009
Failure in receiving the RRC Connection Setup

Complete and NBAP Synchronisation Indication is
received : RNC_336a = (M1001C10)
RRC_CONN_ACC_FAIL_MS
RRC Access Phase

UE
Node B
RNC

Request
AC to check to
accept or reject
RRC Connection
Request
Start TX/RX


ALCAP:ERQ
ALCAP:EC
F
Setup
Start TX/RX
L1 Synchronisation
Indication
Complete
48
RANKPI /BAs / 05.05.2009
If RNC has internal failure before RRC Connection

Setup Complete has been received then the counter
RNC_337a = M1001C11
RRC_CONN_ACC_FAIL_RNC is incremented
RRC Access failures, distribution
L1 Synchronisation
RRC: RRC Conn Setup Complete
UE
BTS
X
X
RNC
RRC
RRCAccess
AccessFailures
FailuresRADIO
RADIO(for
(forL1
L1synchronization)
synchronization)
RRC
RRCAccess
AccessFailures
Failuresdue
duetotoMS
MS
Cell
CellReselections
Reselections(not
(notaafailure)
failure)
L1 Synchronisation
RRC: RRC Conn Setup Complete
UE
49
RANKPI /BAs / 05.05.2009
BTS
RNC
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
Cell A
RRC Connection Setup
Cell A
M1001C0 RRC_CONN_STP_ATT (B)=1

M1001C1 RRC_CONN_STP_COMP (B)=1
M1001C8 RRC_CONN_ACC_COMP (B)=1
Cell B
Cell B
RRC Conn Setup Complete
M1001C241 RRC_CONN_ACC_REL_RESEL (A)=1
Cell B
CELL A COUNTS RESELECTION (WITHIN 6 SECONDS after

RRCC SETUP) AS THE REASON FOR ACCESS FAILURE
50
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
RNC M1001C8 RRC_CONN_ACC_COMP (A)=0
UE
Cell A, f1

UE directed to f2
Cell A, f1
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
51
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
52
RANKPI /BAs / 05.05.2009
RRC Setup Time KPI

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

XUpdatin
g point
AVE
AVE __RRC
RRC__SETUP
SETUP__TM
TM / 100 s
/ 100 s
DENOM
DENOM __RRC
RRC__SETUP
SETUP__TM
TM
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 Nokias 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.
53
RANKPI /BAs / 05.05.2009
RRC Drop Rate KPI

RRC
RRC__CONN
CONN__ACT
ACT__FAIL
FAIL__xxx
xxx
all _ failures
100
%
100**RRC _ CONN _ ACTall__ failures
%
RRC _ CONN _ ACT _COMP
COMPRRC
RRC__CONN
CONN__ACT
ACT__REL
REL__PP__EMP
EMP
RRC
RRC__CONN
CONN__ACT
ACT__REL
REL__SRNC
SRNC RRC
RRC__CONN
CONN__ACT
ACT__FAIL
FAIL__xxx
xxx
allall__failures
failures
Successful
SuccessfulRRC
RRCSetup
Setup->->
RRC_CONN_ACC_COMP
RRC_CONN_ACC_COMP
isisupdated
updated
RRC
RRCDrop
Drophere
herecauses
causes
RRC_CONN_ACT_FAIL_xx
RRC_CONN_ACT_FAIL_xxtotobe
be
incremented,
incremented,
RRC_CONN_ACT_COMP
RRC_CONN_ACT_COMPisisnot
not
incremented
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
54
RANKPI /BAs / 05.05.2009
Traffic counters for RRC setup and access
55
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
56
RANKPI /BAs / 05.05.2009
RRC Access Phase

UE
Node B
RNC
RRC Connection Request triggers M1002 request

counters

AC to check to
accept or reject
RRC Connection
Request
Start TX/RX
M1002 reject counters are triggered by AC, if there are

not enough air interface resources

ALCAP:ERQ
ALCAP:EC
F
Setup
Start TX/RX
L1 Synchronisation
Indication
Complete
57
RANKPI /BAs / 05.05.2009
RRC Connection Setup Complete triggers M1002

allocation counters
Traffic Table: DCH request for Signalling

M1002C1 DCH_REQ_LINK_REJ_UL_SRNC
M1002C0
DCH_REQ_LINK_SRNC
DCH request for RRC
Connection, SHO, HHO and
state transition CELL_FACH
CELL_DCH
M1002C2 DCH_REQ_LINK_REJ_DL_SRNC
+
M1002C4
DCH_DHO_REQ_LINK_SRNC
DCH request only for
SHO
M1002C5 DCH_DHO_REQ_LINK_REJ_SRNC
+
M1002C340 DCH_HHO_REQ_LINK_REJ_SRNC
The term DHO (diversity handover)

is used in the counter names as a synonym for SHO.
58
DL DCH
Reject
M1002C10 DCH_ALLO_LINK_3_4_SRNC
M1002C11 DCH_ALLO_13_6_SRNC
M1002C3
DCH_REQ_RRC_CONN_SRNC
RRC Connection
M1002C339
DCH_HHO_REQ_LINK_SRNC
HHO
UL DCH
Reject
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.
DCH_REQ_LI
DCH_REQ_LINK_REJ_UL_
NK_REJ_UL_SRNC
SRNC 100 %
UL
DCH
Reject
Rate
Sign
UL DCH Reject Rate Sign

100 %
DCH_REQ_LI
NK_SRNC
DCH_REQ_LINK_SRNC
DCH_REQ_LI
DCH_REQ_LINK_REJ_DL_
NK_REJ_DL_SRNC
SRNC100 %
DL
DCH
Reject
Rate
Sign
DL DCH Reject Rate Sign

100 %
DCH_REQ_LI
NK_SRNC
DCH_REQ_LINK_SRNC
59
RANKPI /BAs / 05.05.2009
DCH allocation duration Signaling Link PI
DCH_ALLO_D
DCH_ALLO_DURA_LINK_3
URA_LINK_3_4_SRNC
_4_SRNCDCH_ALLO_D
DCH_ALLO_DURA_LINK_1
URA_LINK_13_6_SRNC
3_6_SRNC s
DCH
Duration
Sign
DCH Duration Sign

s
100
100
Counter Unit=10ms.
Counter value updated every s
Upon release, M1002 duration counters are updated with the (subsecond) time since latest update.
This update goes to all cells in AS that are affected by the release
60
RANKPI /BAs / 05.05.2009
Analysis or RRC Connection Setup Complete

message
61
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
62
RANKPI /BAs / 05.05.2009

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 RFC2507 IP header compression UE_SUPPORT_FOR_IPHC
M1001C390 RFC 3095 UE_SUPPORT_FOR_ROHC
3GPP Release indicator release 99 - M1001C405
ACCESS_STRATUM_REL_IND_99
3GPP Release indicator release 4 - M1001C404 ACCESS_STRATUM_REL_IND_4
3GPP Release indicator release 5 M1001C552 ACCESS_STRATUM_REL_IND_5
3GPP Release indicator release 6 M1001C616 ACCESS-STRATUM_REL_IND_6
GSM - M1001C406 UE_SUPPORT_GSM
Multi-carrier CDMA - M1001C407 UE_SUPPORT_MULTICARRIER_CDMA
UE RX-TX time difference positioning capability type 2 - M1001C408
UE_RXTX_POSITION_CAPAB_2
UE support for Network Assisted GPS M1001C595
63
RANKPI /BAs / 05.05.2009

analysis (3/3)
HSPA capability information:
The number of RRC connection establishments by UEs supporting HSDSCH classes:
< UE category >
1,2,3,4,5 or 6
7 or 8
9 or 10
11 or 12
M1001C548 UE_SUPP_HSDSCH_CLASS_1_6
The number of RRC connection establishments by UEs supporting EDCH classes:

< UE category >
1
2
3
4
5
6
64
M1001C610 UE SUPPORT FOR CATEGORY 1

RANKPI /BAs / 05.05.2009
RRC counters per Establishment Cause: Attempts

and Failures, M1001C22-61
65
RANKPI /BAs / 05.05.2009
RRC Active Phase
66
RANKPI /BAs / 05.05.2009
RRC active phase
RU10 also contains counters to follow up events in RRC

active phase
M1001C12 for normal completion
Further counters for releases and failures
UE
RNC
CORE

Setup Phase
Access Phase
Active Phase
IU Release Command
67
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
68
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
69
Updated in case of:

RNC internal reasons
Transmission failure
FP synchronisation loss
RANKPI /BAs / 05.05.2009
Thank You !
70
RANKPI /BAs / 05.05.2009

04 RN31584EN10GLA0 Paging+RRC Connection

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

04 RN31584EN10GLA0 Paging+RRC Connection

Загружено:

Авторское право:

Доступные форматы

RN3158 RANKPI Training

Paging and Radio Resource Control Connection

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Quality of Service (3GPP 23.107/23.207)

UMTS Bearer Service

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

RAB and RRC connection

Radio Access Bearer

Nokia Siemens Networks

RRC connection and RAB phases

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Moreover, if a failure happens during any RAB phase, typically both

Radio Access Bearer

In addition to the KPIs presented in the slide before, these measurements

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Paging Types Counters

UE is in RRC IDLE Mode

UE is in CELL_PCH or URA PCH

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Paging for UEs in RRC IDLE state

When RNC receives paging message

If RNC cannot process the paging messages and

When RNC sends Paging Type 1 through

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Paging for UEs in CELL_PCH or URA_PCH

Triggers M1003C36 and

UE has signalling connection to CN1

Triggers M1006C37 CELL_UPD_ATT_PAGING_RESP and

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Triggers M1006C25 and

When there is no repsonse within 2 sec

Paging for UEs in CELL_DCH or CELL_FACH

UE has signalling connection to CN1

Triggers M1006C27 PAGING_TYPE_2_ATT

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Paging for UEs in CELL/URA_PCH due to arriving

2. Paging Request (P-TMSI)

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

A number of RNC originated paging type 1

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

Capacity Areas in UTRAN

WBTS HW Resources Transport

Nokia Siemens Networks

RANKPI /BAs / 05.05.2009

(N*) E1 capacity / AAL2

RRC Performance Signaling and Trigger points

[RACH] RRC:RRC Connection Request

NBAP: RL Setup Response

Waiting for UE reply