Performance Statistics - Flowcharts for
Counters
DESCRIPTION
103/1551-AXD 105 03/1 Uen AB
Copyright
© Ericsson AB 2008-2014 All rights reserved. No part of this document may be
reproduced in any form without the written permission of the copyright owner.
Disclaimer
The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use
of this document.
Trademark List
All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Contents
Contents
1
Introduction
1
2
Performance Management Areas
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
Accessibility
RRC Connection Setup - PS
RRC Connection Setup - CS
Iu Signalling Connection Setup
RAB Establishment
Paging
Admission Control
3
3
8
12
14
23
27
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
Retainability
Signaling Connection Release
RRC Connection Release
RAB Release
Lost Radio Connections on Dedicated Channel
Lost Radio Connections due to Layer 2 Fault
Lost Radio Connections on Common Channel
Call Reestablishment
30
31
32
36
49
51
52
53
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
Quality
Channel Switching, Common to Dedicated
Channel Switching, Dedicated to Common
Channel Switching, Upswitch Dedicated to Dedicated
Channel Switching, Downswitch Dedicated to Dedicated
Channel Switching, Common to URA_PCH
Channel Switching, Dedicated to URA_PCH
Channel Switching, URA_PCH to Dedicated
Channel Switching, URA_PCH to Common
Channel Switching to Idle
54
55
57
61
64
67
68
70
72
74
2.4
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
System Utilization
Detect Cell Congestion
Resolve DL Congestion Actions
Start Compressed Mode
Stop Compressed Mode
Cell Availability
74
75
80
83
86
86
2.5
2.5.1
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.8
2.5.9
Mobility
Procedures used during Mobility
Interfrequency Handover
Soft Handover - Radio Link Addition case
Soft Handover - Radio Link Deletion case
Soft Handover - Radio Link Replacement case
Inter-Radio Access Technology Handover, Outgoing
Inter-Radio Access Technology Handover, Incoming
Inter-Radio Access Technology Cell Change, Outgoing
Inter-Radio Access Technology Cell Change, Incoming
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
91
92
107
112
115
116
119
123
132
134
Performance Statistics - Flowcharts for Counters
2.5.10
2.5.11
2.5.12
2.5.13
2.5.14
2.5.15
2.5.16
2.5.17
2.5.18
2.5.19
2.5.20
2.5.21
Inter-Radio Access Technology Cell Reselection, Incoming
Cell Update
URA Update
RAN Information Management Update
HS Cell Change Counters
CN Hard Handover on CS RAB, Source-RNC
CN Hard Handover on CS RAB, Target-RNC
CN Hard Handover on PS RAB, Source-RNC
CN Hard Handover on PS RAB, Target-RNC
UE Positioning
Wi-Fi Mobility: UE Requesting Access to Wi-Fi
Wi-Fi Mobility: Re-estimation of UE Attached in Wi-Fi
135
137
139
141
142
143
145
147
148
149
154
155
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Introduction
1
Introduction
This Description contains flowcharts for the main traffic sequences that impact
Performance Statistics counters in the Radio Network Controller (RNC). It
should be noted that the counters presented are merely a subset of all RNC
counters. Counter types descriptions for all RNC counters and information
about RNC-specific Performance Statistics functionality and parameters is
included in Performance Statistics.
Main Symbols
Symbols used in the document are shown in Figure 1.
Start or end of funcion or subfunction
Step or action
Function or subfunction (not necessarily
described in the document)
Decision
Sequence block
Continuation of the flow
C0001348B
Figure 1
Main Symbols
All flowcharts are drawn from an RNC perspective, trying to reflect the actual
RNC implementation, but not necessarily covering complete procedures.
More detailed information on each counter is described in the Managed Object
Model (MOM), refer to Managed Object Model (MOM) RNC.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
1
Performance Statistics - Flowcharts for Counters
2
Performance Management Areas
This section describes the counter flowcharts grouped according to the
following performance management areas:
Accessibility
The ability to successfully establish a radio connection
for a requested Quality of Service (QoS).
Flowcharts for Accessibility include the setup of a
Packet-Switched (PS) and Circuit-Switched (CS) Radio
Resource Control (RRC) connection, the establishment
of a Radio Access Bearer (RAB) for each of the different
service types, and paging of the User Equipment (UE),
initiated from the Core Network (CN).
Retainability
The ability to maintain an established radio connection
until terminated normally by the user.
Flowcharts for Retainability include signaling connection
handling, which covers release of the RRC and RAB
connections due to both normal and abnormal causes;
admission control as requested from the radio link
reconfiguration, radio link setup, radio link delete,
radio link addition and compressed mode usage
traffic scenarios; and flowcharts for the loss of a radio
connection due to a variety of reasons.
Quality
The quality of a requested service as perceived by an
end-user.
Flowcharts for Quality include channel switches for
various reasons from common to dedicated channel,
from dedicated to common channel, from dedicated to
dedicated channel, and to idle mode.
System Utilization
Covers system usage and availability, channel and
code usage, and congestion situations.
Flowcharts for System Utilization include detection
of congestion situations, resolution of congestion
situations, code allocation and usage, compressed
mode usage, cell availability, and cell update.
2
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Mobility
Covers all handover types.
Flowcharts for Mobility of Ues in Cell_FACH include
Inter-frequency Handover, Intra-frequency Handover
(soft and softer), and Inter-radio Access Technology
Handover and Cell change. Mobility of UEs in
CELL_FACH includes the cell_update procedure and
mobility of Ues in URA_PCH includes the URA update
procedure.
For more information about the Performance Statistic mechanisms for
measuring the radio and transport network performance and the subscriber
perceived quality, refer to the WCDMA RAN Performance Management in
WCDMA.
Each section below describes the main traffic scenarios along with their
flowcharts that belong to a specific area.
2.1
Accessibility
This section describes the Accessibility main traffic scenarios as follows:
2.1.1
•
RRC Connection Setup – PS
•
RRC Connection Setup – CS
•
Iu Signalling Connection Setup
•
RAB Establishment
•
Paging
•
Admission Control
RRC Connection Setup - PS
This traffic scenario describes both successful and unsuccessful attempts to set
up an RRC Connection for an originating or terminating packet-switched call.
The main counters for this scenario are as follows:
•
pmTotNoRrcReq
•
pmTotNoRrcConnectReq
•
pmTotNoRrcConnectReqSucc
•
pmTotNoRrcConnectReqPs
•
pmTotNoRrcConnectReqPsSucc
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
3
Performance Statistics - Flowcharts for Counters
4
•
pmTotNoTermRrcConnectReq
•
pmTotNoTermRrcConnectReqSucc
•
pmTotNoTermRrcConnectReqPs
•
pmTotNoTermRrcConnectReqPsSucc
•
pmTotNoRrcConnectReqSubTr
•
pmTotNoUtranRejRrcConnReq
•
pmNoReqDeniedAdm
•
pmNoFailedAfterAdm
•
pmNoRejRrcConnMpLoadC
•
pmNoRejRrcConnRrcLc
•
pmNoRejRrcConnSpFlowCtrl
•
pmNoRrcReqDeniedAdm
•
pmNoRrcPsReqDeniedAdm
•
pmNoLoadSharingRrcConn
•
pmNoLoadSharingRrcConnPs
•
pmNoRrcReqDeniedAdmDlPwr
•
pmNoRrcReqDeniedAdmDlChnlCode
•
pmNoRrcReqDeniedAdmDlHw
•
pmNoRrcReqDeniedAdmUlHw
•
pmNoRrcConnReqBlockTnPs
•
pmNoRrcConnReqBlockNodePs
•
pmSrbAdmExemptRrc
•
pmTotNoRrcConnectSetup
•
pmTotNoRrcConnectUeCapability
•
pmTotNoRrcConnReqHsFach
•
pmTotNoRrcConnReqSuccHsFach
•
pmTotNoRrcConnReqPsHsFach
•
pmTotNoRrcConnReqPsSuccHsFach
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmTotNoRrcConnectReqCsfbInd
•
pmTotNoRrcConnectReqCsfbIndSucc
Other impacted counters are included in the flowchart Figure 65, which is
referenced from the RRC Connection Setup - PS flowchart.
A flowchart for the RRC Connection Setup – PS scenario is shown in Figure 2
and Figure 3.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
5
Performance Statistics - Flowcharts for Counters
RRC Connection Setup is triggered
by RRC Connection Request message
RRC Reject
due to SP Flow
Control?
YES
pmNoRejRrcConnSpFlowCtrl +
NO
pmTotNoRrcReq +
pmTotNoRrcConnectReq +
pmTotNoRrcConnectReqCsfbInd +
pmNoRejRrcConnRrcLc +
pmTotNoUtranRejRrcConnReq +
pmTotNoRrcConnectReqPs +
NO
YES
RRC Early
Reject?
NO
pmTotNoRrcConnectReqPs +
pmTotNoTermRrcConnectReq +
pmTotNoTermRrcConnectReqPs +
pmTotNoRrcConnectReqSubTr +
pmTotNoRrcConnReqHsFach +
pmTotNoRrcConnReqPsHsFach +
Load Sharing Criteria
fulfilled?
YES
pmNoLoadSharingRrcConnPs +
pmNoLoadSharingRrcConn +
Check with Load Control
NO
pmNoRejRrcConnMpLoadC +
Successful
Load Control?
RRC
CONNECTION
REQUEST
UE
SRNC
Increment pmTotNoRrcReq for every RRC Connection Request.
Increment only once, even if repeated RRC Connection
Requests: For pmTotNoRrcConnectReq, step for all
Establishment Causes. For pmTotNoRrcConnectReqCsfbInd
step when RRC CONNECTION REQUEST includes the IE
"CSFB Indication"
For pmTotNoRrcConnectReqPs, step for Establishment Cause=
Originating or Terminating Interactive/Background Call only.
For pmTotNoTermRrcConnectReq, step for cause = ‘Terminating
Conversational Call’, ‘Terminating Streaming Call’, ‘Terminating
Interactive Call’, ‘Terminating Background Call’, Terminating
High
Priority Signalling’, ‘Terminating Low Priority Signalling’ or
‘Terminating - cause unknown’.
For pmTotNoTermRrcConnectReqPs, step for cause =
‘Terminating
Interactive Call’ or ‘Terminating Background Call’.
For pmTotNoRrcConnectReqSubTr, step for cause = ‘Originating
Subscribed Traffic Call’.
For pmTotNoRrcConnReqHsFach, step for all Establishment
Causes,
if the response message is then sent on HS-FACH.
For pmTotNoRrcConnReqPsHsFach, step for cause =
‘Originating
Interactive Call’, ‘Terminating Interactive Call’, ‘Originating
Background
Call’, ‘Terminating Background Call', or 'Originating Subscribed
Traffic Call’, if the response message is then sent on HS-FACH.
YES
Successful
Admission Control?
Release of already
allocated resources
NO
1
YES
Radio Link Setup
pmTotNoUtranRejRrcConnReq +
NO
2
Successful setup?
YES
UE
RRC
CONNECTION
SETUP
RBS
RADIO LINK
RESTORE
INDICATION
SRNC
Send RRC Connection
Setup and start timer
pmTotNoRrcConnectSetup +
UE
RRC CONNECTION
SETUP COMPLETE
SRNC
SRNC
RRC Connection
Setup Complete and NBAP
Radio Link Restore Indication are
received before timer
expires?
NO
3
YES
pmTotNoRrcConnectUeCapability + *
pmSrbAdmExemptRrc + **
Increment only once
even if repeated RRC
Connection Requests
Message Sent
UE
pmTotNoRrcConnectReqSuccess +
pmTotNoTermRrcConnectReqSucc +
pmTotNoRrcConnectReqPsSucc +
pmTotNoTermRrcConnectReqPsSucc +
pmTotNoRrcConnReqSuccHsFach +
pmTotNoRrcConnReqPsSuccHsFach +
pmTotNoRrcConnectReqCsfbIndSucc +
RRC
CONNECTION
REJECT
SRNC
End RRC Connection Setup
Figure 2
6
*) Stepped for Establishment Cause =
Originating or Terminating
Conversational Call, Emergency,
Subscribed, Originating or Terminating
Interactive/Background Call.
**) Stepped only when an extra SRB is
granted by admission control.
C 00 01115Z
RRC Connection Setup - PS Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
pmNoRrcPsReqDeniedAdm +
pmNoRrcReqDeniedAdm +
pmNoReqDeniedAdm +
1
Admission
reject as a result of
load sharing?
2
YES
pmNoLoadSharingRrcConn +
pmNoLoadSharingRrcConnPs +
Release of already
allocated resources
NO
Admission reject
due to Unisaal/Sctp
congestion?
Step relevant counter(s):
pmNoReqDeniedAdm +
pmNoFailedAfterAdm +
Admission
reject due to other
reason?
NO
YES
NO
YES
Failed due
to TN block?
Step relevant counter(s):
pmNoRrcConnReqBlockTnPs +
pmNoRrcConnReqBlockNodePs +
YES
pmNoFailedRrcConnectReqHw +
pmNoFailedRrcConnectReqPsHw +
or
pmNoRrcReqDeniedAdmDlPwr +
or
pmNoRrcReqDeniedAdmDlChnlCode+
or
pmNoRrcReqDeniedAdmDlHw +
or
pmNoRrcReqDeniedAdmUlHw +
NO
3
Send RRC connection Release,
start timer, receive RRC
Connection Release
Complete/timer expires
Step relevant counter(s):
pmNoReqDeniedAdm +
pmNoFailedAfterAdm +
UE
RRC CONNECTION
RELEASE
SRNC
UE
RRC CONNECTION
RELEASE COMPLETE
SRNC
Release of already
allocated resources
If timer does not expire:
pmTotNoUtranRejRrcConnReq +
UE
RRC CONNECTION
REJECT
SRNC
Message Sent
End RRC Connection Setup
C0001466D
Figure 3
RRC Connection Setup - PS Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
7
Performance Statistics - Flowcharts for Counters
2.1.2
RRC Connection Setup - CS
This traffic scenario describes both successful and unsuccessful attempts to
set up an RRC connection for an originating or terminating circuit-switched call.
The main counters for this scenario are as follows:
8
•
pmTotNoRrcReq
•
pmTotNoRrcConnectReq
•
pmTotNoRrcConnectReqSuccess
•
pmTotNoRrcConnectReqCs
•
pmTotNoRrcConnectReqCsSucc
•
pmTotNoRrcConnReqCsHsFach
•
pmTotNoRrcConnReqCsSuccHsFach
•
pmTotNoTermRrcConnectReq
•
pmTotNoTermRrcConnectReqSucc
•
pmTotNoTermRrcConnectReqCs
•
pmTotNoTermRrcConnectReqCsSucc
•
pmTotNoRrcConnectReqSubTr
•
pmTotNoUtranRejRrcConnReq
•
pmNoReqDeniedAdm
•
pmNoFailedAfterAdm
•
pmNoRejRrcConnMpLoadC
•
pmNoRejRrcConnSpFlowCtrl
•
pmNoRrcReqDeniedAdm
•
pmNoRrcCsReqDeniedAdm
•
pmNoLoadSharingRrcConn
•
pmNoLoadSharingRrcConnCs
•
pmNoRrcReqDeniedAdmDlPwr
•
pmNoRrcReqDeniedAdmDlChnlCode
•
pmNoRrcReqDeniedAdmDlHw
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoRrcReqDeniedAdmUlHw
•
pmNoRrcConnReqBlockTnCs
•
pmNoRrcConnReqBlockNodeCs
•
pmSrbAdmExemptRrc
•
pmTotNoRrcConnectSetup
•
pmTotNoRrcConnectUeCapability
•
pmTotNoRrcConnectReqCsfbInd
•
pmTotNoRrcConnectReqCsfbIndSucc
•
pmNoLoadSharingRrcConnCsfbInd
Other impacted counters are included in the flowchart Figure 65, which is
referenced from the RRC Connection Setup - CS flowchart.
A flowchart for the RRC Connection Setup – CS scenario is shown in Figure 4
and Figure 5.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
9
Performance Statistics - Flowcharts for Counters
RRC Connection Setup is triggered
by RRC Connection Request message
pmNoRejRrcConnSpFlowCtrl +
YES
UE
Increment pmTotNoRrcReq for every RRC Connection Request.
Increment only once, even if repeated RRC Connection Requests:
For pmTotNoRrcConnectReq, step for all Establishment Causes.
For pmTotNoRrcConnectReqCsfbInd step when RRC CONNECTION
REQUEST includes the IE "CSFB Indication”.
For pmTotNoRrcConnectReqCs, step for Establishment Cause=
Emergency Call or Originating or Terminating Conversational Call.
For pmTotNoTermRrcConnectReq, step for cause = ‘Terminating
Conversational Call’, ‘Terminating Streaming Call’, ‘Terminating
Interactive Call’, ‘Terminating Background Call’, Terminating High
Priority Signalling’, ‘Terminating Low Priority Signalling’ or
‘Terminating - cause unknown’.
For pmTotNoTermRrcConnectReqCs, step for cause = ‘Terminating
Conversational Call’.
For pmTotNoRrcConnectReqSubTr, step for cause = ‘Originating
Subscribed Traffic Call’.
For pmTotNoRrcConnReqCsHsFach, step for cause = ‘Originating
Conversational Call’,‘Terminating Conversational Call’ or ‘Emergency Call’
, if the response message is then sent on HS-FACH.
pmTotNoRrcReq +
pmTotNoRrcConnectReq +
pmTotNoRrcConnectReqCsfbInd +
pmTotNoRrcConnectReqCs +
pmTotNoTermRrcConnectReq +
pmTotNoTermRrcConnectReqCs +
pmTotNoRrcConnectReqSubTr +
pmTotNoRrcConnReqCsHsFach +
Check with Load Control
Successful
Load Control?
NO
SRNC
RRC Reject
due to SP Flow Control?
NO
pmNoRejRrcConnMpLoadC +
RRC CONNECTION
REQUEST
YES
Successful
Admission Control?
Release of already
allocated resources
NO
1
YES
Radio Link Setup
NO
pmTotNoUtranRejRrcConnReq +
UE
RRC CONNECTION
SETUP
Successful setup?
2
YES
Send RRC Connection
SRNC Setup and start timer
pmTotNoRrcConnectSetup +
RBS
UE
RADIO LINK
RESTORE
INDICATION
RRC CONNECTION
SETUP COMPLETE
SRNC
RRC Connection
Setup Complete and NBAP Radio
Link Restore Indication are
received before timer
expires?
SRNC
YES
NO
3
pmTotNoRrcConnectUeCapability + *
pmSrbAdmExemptRrc + **
Increment only once
even if repeated RRC
Connection Requests
Message Sent UE
pmTotNoRrcConnectReqSuccess +
pmTotNoTermRrcConnectReqSucc +
pmTotNoRrcConnectReqCsSucc +
pmTotNoTermRrcConnectReqCsSucc +
pmTotNoRrcConnReqCsSuccHsFach +
pmTotNoRrcConnectReqCsfbIndSucc +
RRC CONNECTION
REJECT
SRNC
*) Stepped for Establishment Cause = Originating or
Terminating Conversational Call, Emergency, Subscribed,
Originating or Terminating Interactive/Background Call.
**) Stepped only when an extra SRB is granted by
admission control.
End RRC Connection Setup
C 00 01114X
Figure 4
10
RRC Connection Setup - CS Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
pmNoRrcCsReqDeniedAdm+
pmNoRrcReqDeniedAdm+
pmNoReqDeniedAdm+
1
Admission
reject as a result of
load sharing?
YES
pmNoLoadSharingRrcConn +
pmNoLoadSharingRrcConnCs +
pmNoLoadSharingRrcConnCsfbInd +
NO
Release of already
allocated resources
2
Admission reject
due to Unisaal/Sctp
congestion?
Step relevant counter(s):
pmNoReqDeniedAdm +
pmNoFailedAfterAdm +
Admission
reject due to other
reason?
NO
YES
NO
YES
Failed due
to TN block?
Step the relevant counter(s):
pmNoRrcConnReqBlockTnCs +
pmNoRrcConnReqBlockNodeCs +
YES
pmNoFailedRrcConnectReqHw +
pmNoFailedRrcConnectReqCsHw +
or
pmNoRrcReqDeniedAdmDlPwr +
or
pmNoRrcReqDeniedAdmDlChnlCode+
or
pmNoRrcReqDeniedAdmDlHw +
or
pmNoRrcReqDeniedAdmUlHw +
NO
3
Send RRC connection Release,
start timer, receive RRC
Connection Release
Complete/timer expires
Step relevant counter(s):
pmNoReqDeniedAdm +
pmNoFailedAfterAdm +
UE
RRC CONNECTION
RELEASE
SRNC
UE
RRC CONNECTION
RELEASE COMPLETE
SRNC
Release of already
allocated resources
If timer does not expire:
pmTotNoUtranRejRrcConnReq +
UE
RRC CONNECTION
REJECT
SRNC
Message Sent
End RRC Connection Setup
C0001465E
Figure 5
RRC Connection Setup - CS Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
11
Performance Statistics - Flowcharts for Counters
2.1.3
Iu Signalling Connection Setup
This traffic scenario describes both successful and unsuccessful attempts to
set up an Iu connection. See Figure 6.
The main counters for this scenario are as follows:
12
•
pmNoIuSigEstablishAttemptCs, pmNoIuSigEstablishAttemptPs
•
pmNoIuSigEstablishSuccessCs, pmNoIuSigEstablishSuccessPs
•
pmNoMocnSupportingAccessesCs, pmNoMocnSupportingAccessesPs
•
pmSpidDedicPrioEutra, pmMocnDedicPrioEutra
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
UE
Signalling Connection setup
triggered by Initial Direct
Transfer message
Initial Direct
Transfer
No
UE supports
MOCN ?
Yes
No
Chosen PLMN-id
matches CnOperator ?
Yes
pmNoMocnSupportingAccessesCs +
or
pmNoMocnSupportingAccessesPs +
pmNoIuSigEstablishAttemptPs +
or
pmNoIuSigEstablishAttemptCs +
or none
No
Yes
Succesfull SCCP
Connection Setup?
Yes
RANAP
Overload Control?
No
pmIdtDiscardedCs + *
pmIdtDiscarded +
or
pmIdtDiscardedPs + **
pmIdtDiscarded +
or
pmIdtDiscarded +
pmNoIuSigEstablishSuccessPs +
or
pmNoIuSigEstablishSuccessCs +
End Signalling
Connection setup
*) Stepped for Establisment Cause “Originated Conversational Call”
**) Stepped for Establisment Causes "Originated Interactive call",
"Originated Background Call", or "Originating Subscribed Traffic Call"
Figure 6
C 00 01317D
Iu Signalling Connection Setup scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
13
Performance Statistics - Flowcharts for Counters
RANAP Common ID received
SPID is included in
message and configured to prevent
LTE Cell Reselection to LTE?
NO
NO
Shared RAN (MOCN)
enabled?
YES
YES
pmMocnDedicPrioEutra +
pmSpidDedicPrioEutra +
End
C0002093A
Figure 7
RANAP Common ID
RANAP Direct Trasfer received
SPID is included in
message and configured to prevent
LTE Cell Reselection to LTE?
NO
YES
NO
SPID is different than
last received?
YES
pmSpidDedicPrioEutra +
End
C0002094A
Figure 8
2.1.4
RANAP Direct Transfer
RAB Establishment
This traffic scenario describes both successful and unsuccessful attempts to
set up a Radio Access Bearer for a requested service.
14
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
The main counters for this scenario are as follows:
•
pmNoNormalNasSignReleaseCs, pmNoNormalNasSignReleasePs
•
pmTotNoSbHo
•
pmNoSuccRbReconfPsIntDch, pmNoSuccRbReconfOrigPsIntDch
•
pmNoSuccRbReconfPsIntHs, pmNoSuccRbReconfOrigPsIntHs
•
pmNoSuccRbReconfPsIntEul, pmNoSuccRbReconfOrigPsIntEul
•
pmNoRabEstablishAttempts, pmNoRabEstablishSuccess
•
pmNoRabEstablishAttemptSpeech, pmNoRabEstablishSuccessSpeech
•
pmNoRabEstablishAttemptAmrNb, pmNoRabEstablishSuccessAmrNb
•
pmNoRabEstablishAttemptAmrWb, pmNoRabEstablishSuccessAmrWb
•
pmNoRabEstablishAttemptCs64, pmNoRabEstablishSuccessCs64
•
pmNoRabEstablishAttemptCs57, pmNoRabEstablishSuccessCs57
•
pmNoRabEstablishAttemptPacketInteractive, pmNoRabEstablishSucce
ssPacketInteractive
•
pmNoRabEstablishAttemptPacketStream, pmNoRabEstablishSuccessPa
cketStream
•
pmNoRabEstAttemptPsStreamHs, pmNoRabEstSuccessPsStreamHs
•
pmNoRabEstablishAttemptPacketInteractiveHs, pmNoRabEstablishSu
ccessPacketInteractiveHs
•
pmNoRabEstablishAttemptPacketInteractiveEul, pmNoRabEstablishSu
ccessPacketInteractiveEul
•
pmNoRabEstablishAttemptPacketStream128, pmNoRabEstablishSucce
ssPacketStream128
•
pmRabEstablishEcAttempt, pmRabEstablishEcSuccess
•
pmNoInvalidRabEstablishAttempts
•
pmNoRabEstablishFailureUeCapability
•
pmNoRabEstAttemptPsIntNonHs
•
pmNoRabEstSuccessPsIntNonHs
•
pmNoFailedRabEstAttemptLackDlHwBest, pmNoFailedRabEstAttemptLac
kUlHwBest
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
15
Performance Statistics - Flowcharts for Counters
16
•
pmNoFailedRabEstAttemptLackDlHw, pmNoFailedRabEstAttemptLackU
lHw
•
pmNoFailedRabEstAttemptLackDlAse, pmNoFailedRabEstAttemptLac
kUlAse
•
pmNoFailedRabEstAttemptExceedConnLimit
•
pmNoFailedRabEstAttemptLackDlChnlCode
•
pmNoFailedRabEstAttemptLackDlPwr
•
pmNoFailedRabEstAttEulRateCong
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlHls, pmCmSuccDlHls
•
pmCmStop
•
pmNoReqDeniedAdm
•
pmNoFailedAfterAdm
•
pmNoOfNonHoReqDeniedSpeech
•
pmNoOfNonHoReqDeniedCs
•
pmNoOfNonHoReqDeniedInteractive
•
pmNoOfNonHoReqDeniedPsStreaming
•
pmNoOfNonHoReqDeniedPsStr128
•
pmNoOfNonHoReqDeniedHs
•
pmNoOfNonHoReqDeniedEul
•
pmNoRabEstBlockRnPsStreamHs, pmNoRabEstBlockRnBestPsStreamHs
•
pmNoRabEstBlockTnPsStrHs, pmNoRabEstBlockTnPsStrHsBest,
pmNoRabEstBlockNodePsStrHsBest
•
pmNoRabEstBlockTnSpeech, pmNoRabEstBlockTnSpeechBest,
pmNoRabEstBlockNodeSpeechBest
•
pmNoRabEstBlockTnCs57, pmNoRabEstBlockTnCs57Best,
pmNoRabEstBlockNodeCs57Best
•
pmNoRabEstBlockTnCs64, pmNoRabEstBlockTnCs64Best,
pmNoRabEstBlockNodeCs64Best
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoRabEstBlockTnPsStrNonHs, pmNoRabEstBlockTnPsStrNonHsBest,
pmNoRabEstBlkNodePsStrNonHsBest
•
pmNoRabEstBlockTnPsIntNonHs, pmNoRabEstBlockTnPsIntNonHsBest,
pmNoRabEstBlkNodePsIntNonHsBest
•
pmNoRabEstBlockTnPsIntHs, pmNoRabEstBlockTnPsIntHsBest,
pmNoRabEstBlockNodePsIntHsBest
•
pmSrbAdmExemptRab
•
pmNoRabEstAttemptMultiPsInt
•
pmNoRabEstSuccessMultiPsInt
•
pmReconfAttSource, pmReconfSuccSource
•
pmReconfAttTarget, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmNoRabEstAttemptMultiSpeech, pmNoRabEstAttemptMultiAmrNb,
pmNoRabEstAttemptMultiAmrWb
•
pmNoRabEstSuccessMultiSpeech, pmNoRabEstSuccessMultiAmrNb,
pmNoRabEstSuccessMultiAmrWb
•
pmNoRabEstablishAttemptsCsfbInd
•
pmNoRabEstablishAttemptsCsfbDetect
•
pmNoRabEstablishSuccessCsfbInd
•
pmNoRabEstablishSuccessCsfbDetect
•
pmNoNormalNasSignReleaseCsfbInd
•
pmNoRabEstAttemptMultiSpeechUra
•
pmNoRabEstSuccessMultiSpeechUra
•
pmNoNormalNasSignReleaseMultiCsUra
Other impacted counters are included in the following flowcharts, which are
referenced from the RAB Establishment flowchart:
•
Figure 65, Figure 68
Predefined sequences used in Figure 12, Figure 13 and in Figure 14 are shown
in Figure 9 and Figure 10.
A flowchart for the RAB Establishment scenario is shown in Figure 11, Figure
12 , Figure 13 and Figure 14
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
17
Performance Statistics - Flowcharts for Counters
A1-succ / A2-succ
A1 / A2
NO
A1
A2
YES
CS already
set up ?
NO
CS already
set up ?
A1 - succ
A2 - succ
YES
pmNoRabEstAttemptMultiPsInt +
pmNoRabEstSuccessMultiPsInt +
pmNoRabEstAttemptMultiPsInt +
pmNoRabEstablishAttemptX +
pmNoRabEstablishSuccessX +
pmNoRabEstablishAttemptX +
A1 : X=PacketInteractive
A2 : X=one of PacketInteractive, PacketInteractiveHs*,
PacketStream, PacketInteractiveEul* **,
PacketStream128, PsStreamHs, PsIntNonHs
* also PacketInteractive+
** also PacketInteractiveHs+
B
B
pmNoRabEstablishAttempts +
pmReconfAttSource +
pmReconfAttTarget +
pmNoRabEstablishAttemptsCsfbInd +
pmNoRabEstablishAttemptsCsfbDetect +
B-succ
B - succ
pmNoRabEstablishAttempts +
pmReconfAttSource +
pmReconfAttTarget +
pmNoRabEstablishAttemptsCsfbInd +
pmNoRabEstablishAttemptsCsfbDetect +
pmNoRabEstablishSuccess +
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
pmNoRabEstablishSuccessCsfbInd +
pmNoRabEstablishSuccessCsfbDetect +
C 0001593B
Figure 9
18
Predefined Sequence for RAB Establishment Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
C
C
NO
PS already
set up ?
YES
pmNoRabEstAttemptMultiX+
UE originated
from URA_PCH?
NO
YES
Emergency
call?
X = one of Speech,
Speech&AmrNb,
Speech&AmrWb
YES
pmNoRabEstAttemptMultiSpeechUra +
NO
pmRabEstablishEcAttempt +
pmNoRabEstablishAttemptX +
pmNoRabEstablishAttemptSpeech +
pmNoRabEstablishAttemprsCsfbInd +
pmNoRabEstablishAttemptAmrNb +
pmNoRabEstablishAttemptsCsfbDetect +
pmNoRabEstablishAttemptsCsfbInd +
pmNoRabEstablishAttemptsCsfbDetect +
X=one of Speech,
Speech&AmrNb,
Speech&AmrWb,
CS57, CS64
C-succ
C - succ
NO
PS already
set up ?
YES
pmNoRabEstAttemptMultiX +
pmNoRabEstSuccessMultiX +
UE originated
from URA_PCH?
NO
YES
Emergency
call?
pmRabEstablishEcAttempt +
pmNoRabEstablishAttemptSpeech +
pmNoRabEstablishAttemptAmrNb +
pmRabEstablishEcSuccess +
pmNoRabEstablishSuccessSpeech +
pmNoRabEstablichSuccessAmrNb +
pmNoRabEstablishAttemptsCsfbInd +
pmNoRabEstablishAttemptsCsfbDetect +
pmNoRabEstablishSuccessCsfbInd +
pmNoRabEstablishSuccessCsfbDetect +
X = one of Speech,
Speech&AmrNb,
Speech&AmrWb
YES
pmNoRabEstAttemptMultiSpeechUra +
pmNoRabEstSuccessMultiSpeechUra +
NO
pmNoRabEstablishAttemptX +
pmNoRabEstablishSuccessX +
pmNoRabEstablishAttemptsCsfbInd +
pmNoRabEstablishAttemptsCsfbDetect +
pmNoRabEstablishSuccessCsfbInd +
pmNoRabEstablishSuccessCsfbDetect +
X=one of Speech,
Speech&AmrNb,
Speech&AmrWb,
CS57, CS64
C 0001594C
Figure 10
Predefined Sequence for RAB Establishment Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
19
Performance Statistics - Flowcharts for Counters
Start of RAB Establishment
This message triggers the
RAB Establishment process
(RANAP) RAB
ASSIGNMENT
REQUEST
Message received
Establishing
a MultiRAB Call
(CS+n*PS)?
YES
pmNoNormalNasSignReleaseMultiX+
UE originated
from URA_PCH?
NO
X = PS or CS
YES
pmNoNormalNasSignRelMultiCsUra+*
NO
* Stepped for CS only
pmNoNormalNasSignReleaseX +
* Stepped if the
pmTotNoSbHo +*
pmNoNormalNasSignReleaseCsfbInd + RAB combination
is "speech only".
This process maps the
received QoS parameters
Perform RAB mapping
onto a supported RAB type
NO
RAB mapping
successful?
pmNoInvalidRabEstablishAttempts +
YES
This process determines
if the UE can support the
requested service (RAB)
Perform UE
Capability Check
NO
Capability check
successful?
pmNoRabEstablishFailureUeCapability +
YES
YES
Directed retry?
YES
SRB-DCH, CS-Speech, Ps-Interactive_64/64,
Ps-Interactive_64/128, Ps-Interactive_64/384,
Ps-Interactive_128/64, Ps-Interactive_384/64, ADM REQ
Ps-Interactive_384/128, Ps-Interactive_128/384,
CS-Speech AMR 7950, CS-Speech AMR 5900,
Perform Admission Control
CS-Speech AMR 4750, Ps-Interactive_64/Hs,
Ps-Interactive_384/Hs, Ps-Interactive_Eul/Hs,
Ps-Interactive_128/128, Cs64,
Admission
CS-Speech + Ps_interactive_0/0, CS-Speech +
NO
Ps_interactive_64/64,
Control successful?
CS-Speech + Ps_interactive_64/128, CS-Speech +
Ps_interactive_128/64,
CS-Speech + Ps_interactive_64/384, Ps_interactive_64/64 +
YES
Ps_interactive_64/64, Ps_interactive_64/128 +
Ps_interactive_64/128,
Ps-Streaming 128/16 + Ps_interactive_8/8,
Ps-Streaming 16/128 + Ps_interactive_8/8
6
Initial RAB state?
Step any of counters:
pmNoFailedRabEstAttemptExceedConnLimit +
pmNoFailedRabEstAttemptLackDlPwr +
pmNoFailedRabEstAttemptLackDlChnlCode +
pmNoFailedRabEstAttemptLackDlAse +
pmNoFailedRabEstAttemptLackUlAse +
pmNoFailedRabEstAttemptLackDlHwBest +*
pmNoFailedRabEstAttemptLackUlHwBest +*
pmNoFailedRabEstAttemptLackDlHw +
pmNoFailedRabEstAttemptLackUlHw +
pmNoRabEstBlockRnBestPsStreamHs +
pmNoRabEstBlockRnPsStreamHs +
pmNoFailedRabEstAttEulRateCong +
* Stepped for the
best cell in the
active set.
PS-Interactive-FACH
pmNoNormalReleaseSrbOnlyHs +
The relevent counter from the following:
pmCmAttUlSf2 +, pmCmAttDlSf2 +,
pmCmAttUlHls +, pmCmAttDlHls +
Radio Link Reconfiguration
pmCmStop +
The counter to step is determined by whether the
CM method has changed or if the CM is newly
activated (if CM is UL&DL then step both UL and DL).
Radio Link Setup
Counter incremented if CM is stopped. This occurs if :
· gsmHoAllowed changes from “Allowed” to “Not Allowed”,
· or if the value of Service Handover = “Handover to GSM shall not be
· performed” for this RAB or in an earlier RAB in the case of Multi-RAB.
· ifHoAllowed = “Not Allowed”. This is for the target RAN state.
The relevent counter from the following:
pmCmSuccUlSf2 +, pmCmSuccDlSf2 +,
pmCmSuccUlHls +, pmCmSuccDlHls +
The counter to step is determined by whether the
CM method has changed or if the CM is newly
activated (if CM is UL&DL then step both UL and DL).
Radio Link Reconfiguration Commit
Failure?
YES
PS RAB
NO
CS or PS RAB
being established ?
CS RAB
20
1
2
3
4
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
C 0001220AC
Figure 11
RAB Establishment Scenario (Part A)
Performance Management Areas
1
Message sent
(RRC) RADIO BEARER SETUP
YES
Timeout or RRC
Radio Bearer Setup
Failure?
pmSrbAdmExemptRab +
NO
B
CS
PS or CS being
established ?
C
Message received
(RRC) RADIO BEARER SETUP COMPLETE
YES
Reconfiguration of existing
PS Interactive RAB?
PS
A2
(RANAP) RAB
ASSIGMENT
RESPONSE
Message sent
(indicating RAB
establishment
failure)
End of RAB Establishment
Step one of these:
pmNoSuccRbReconfPsIntDch +
pmNoSuccRbReconfOrigPsIntDch +
pmNoSuccRbReconfPsIntHs +
pmNoSuccRbReconfOrigPsIntHs +
pmNoSuccRbReconfPsIntEul +
pmNoSuccRbReconfOrigPsIntEul +
NO
Message sent
(RANAP) RAB ASSIGMENT RESPONSE
Message sent
(RRC) RADIO BEARER RECONFIGURATION
Message received
(RRC) RADIO BEARER RECONFIGURATION
COMPLETE
B - succ
CS
PS or CS being
established ?
C - succ
PS
A2 - succ
pmSrbAdmExemptRab +
step if relevant
End of RAB Establishment
Figure 12
C 0001221U
RAB Establishment Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
21
Performance Statistics - Flowcharts for Counters
2
PS
EUL/HS configuration?
NO
PS
DCH/HS configuration?
B
YES
Re-attempt on
EUL/HS?
PS
DCH/DCH configuration?
NO
YES
YES
YES
NO
6
NO
B
pmNoRabEstablishAttemptPacketInteractiveEul +
pmNoOfNonHoReqDeniedEul + *
Re-attempt on
DCH/HS?
YES
* step if relevant
6
NO
pmNoOfNonHoReqDeniedHs +
pmNoRabEstBlockTnX +
pmNoRabEstBlockTnXBest +
pmNoRabEstBlockNodeXBest +
pmNoRabEstBlockRnBestPsStreamHs+
pmNoRabEstBlockRnPsStreamHs+
pmNoRabEstablishAttemptPacketInteractiveHs+
Re-attempt on
DCH/DCH?
Step the relevant counters.
X= one of: PsIntHs or PsStreamHs
YES
YES
6
NO
Re-attempt on
RACH/FACH?
NO
YES
YES
6
NO
5
Re-attempt on
DCH/DCH?
Re-attempt on
RACH/FACH?
NO
Step the relevant counters.
X= One of: PsIntNonHs or PsStreamNonHs
pmNoRabEstBlockTnX+
pmNoRabEstBlockTnXBest+
pmNoOfNonHoReqDeniedPsStreaming+
pmNoOfNonHoReqDeniedPsStr128 +
5
C 0001456F
Figure 13
22
RAB Establishment Scenario (Part C)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
3
5
4
A1
YES
Reattempt on Multi-RAB
including PS EUL/HS
configuration ?
6
NO
pmNoOfNonHoReqDeniedInteractive +
B
pmNoReqDeniedAdm +
Re-attempt on
other configuration?
YES
6
NO
pmNoRabEstBlockTnX+
pmNoRaEstBlockTnXBest+
pmNoOfNonHoReqDeniedSpeech+
pmNoOfNonHoReqDeniedCs+
Step the relevant counters.
X= one of Speech or CS
C
pmNoReqDeniedAdm +
Message sent
(RANAP) RAB
ASSIGMENT
RESPONSE
(indicating RAB
establishment
failure)
End of RAB Establishment
C 0001468B
Figure 14
2.1.5
RAB Establishment Scenario (Part D)
Paging
This traffic scenario describes attempted, rejected, and discarded pages in
the RNC.
The main counters for this scenario are as follows:
•
pmCnInitPagingToIdleUeLa
•
pmCnInitPagingToIdleUeRa
•
pmCnInitPagingToIdleUe
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
23
Performance Statistics - Flowcharts for Counters
•
pmCnInitPagingToUraUe
•
pmNoPagingAttemptCnInitDcch
•
pmNoPagingAttemptUtranRejected
•
pmUtranInitPagingToUraUe
•
pmNoPageDiscardCmpLoadC
•
pmNoPagingType1Attempt
•
pmNoPagingType1AttemptPS
•
pmNoPagingType1AttemptCS
•
pmNoPagingType1ReplaceCs
•
pmNoPagingType1ReplaceInternal
•
pmNoPagingType1ReplacePs
If the node is a member of the cluster set up by the RNC in Pool feature, the
pmCnInitPagingToIdleUe counter is stepped on all cluster members, when
the paging is performed. So a global paging request from CN results in stepping
the pmCnInitPagingToIdleUe counter in all cluster members.
Where the LA/RA spans over both cluster members, the pmCnInitPaging
ToIdleUeLa and pmCnInitPagingToIdleUeRa counters are stepped on
both nodes.
A flowchart for the Paging scenario is shown in Figure 15 and the sub-flows for
URA are shown in Figure 16.
24
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Paging
PAGING
CRNC
CN
RNC repeated Pages
are not counted
Message Received
MP
Load Control
reject?
YES
NO
YES
End Paging
Queue reject?
PmNoPageDiscardCmpLoadC +
NO
URA_PCH
Connnected
Check UE Status
UraPaging
Idle
pmNoPagingAttemptCnInitDcch+
MP
Load Control
reject?
YES
PAGING
Message Sent
SRNC
YES
UE
TYPE 2
NO
Overload on
MP handling RANAP?
End Paging
NO
pmNoPageDiscardCmpLoadC +
YES
If Pagingarea = LA
End Paging
NO
YES
pmCnInitPagingToldleUeLA+
If Pagingarea = RA
pmCnInitPagingToldleUeRA +
NO
pmCnInitPagingToldleUE
NO
YES
MMP Flow Control show
CC-SP is overloaded?
pmNoPagingAttemptUtranRejected+
pmNoPagingType1Attempt +
pmNoPagingType1Attempt +
CS
PS
Paging Type
CS
PS
Paging Type
Check PagingType1 cause
Check PagingType1 cause
Check PagingType1 cause
Check PagingType1 cause
NO
Not possible
to decide
Term.
Conversational
Call?
YES
Term.
Interactive or Background
Call?
NO
NO
YES
CC-SP SFN
Queue full?
CRNC
pmNoPagingType1AttemptCs +
YES
Paging record
replacement
possible?
Message Sent
TYPE 1
NO
pmNoPagingType1AttemptPs +
NO
pmNoPagingAttemptUtranRejected +
End Paging
YES
End Paging
CS
Paging Type
CRNC
PS
pmNoPagingType1ReplacePs +
pmNoPagingType1ReplaceCs +
PAGING
Term.
Interactive or Background
Call?
End Paging
NO
PAGING
Term.
Conversational
Call?
YES
YES
pmNoPagingType1AttemptPs +
pmNoPagingType1AttemptCs +
Not possible
to decide
Message Sent
TYPE 1
End Paging
C 0001086K
Figure 15
Flowchart for Paging Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
25
Performance Statistics - Flowcharts for Counters
Ura Paging
YES
Overload on
MP handling RANAP?
NO
pmNoPageDiscardCmpLoadC +
End Paging
UTRAN
CN
Paging type
pmUtranInitPagingToUraUe +
pmCnInitPagingToUraUe +
pmNoPagingType1Attempt +
SFN Queue
full?
YES
NO
UE
PAGING
SRNC
Message Sent
TYPE 1
YES
End Paging
NO
Paging record
replace possible?
UTRAN
Paging type
pmNoPagingAttemptUtranRejected +
End Paging
CN
pmNoPagingType1ReplaceInternal +
CS
Paging type
pmNoPagingType1ReplaceCs +
Message Sent
PS
pmNoPagingType1ReplacePs +
SRNC
PAGING
TYPE 1
UE
End Paging
C 0001311F
Figure 16
26
URA Paging Types
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.1.6
Admission Control
This traffic scenario describes the handling of Admission Control requests from
various traffic scenarios including Radio Link Addition, Radio Link Setup, Radio
Link Deletion, Radio Link Reconfiguration and Start Compressed Mode usage.
The main counters for this scenario are as follows:
•
pmNoOfSwDownNgAdm
•
pmNoFailedAfterAdm
•
pmNoServingCellReqDeniedEul
•
pmNoServingCellReqDeniedEulTti2
•
pmNoNonServingCellReqDeniedEul
•
pmNoOfDiscardedNbapCMessages
•
pmLevelSampAseUl
•
pmLevelSampAseDl
•
pmLevelCompMode
•
pmSoftCongGbrBwUl, pmSoftCongGbrBwDl
•
pmSoftCongRbsUlHw
•
pmSamplesDlCredits
•
pmSumSqrDlCredits
•
pmSamplesUlCredits
•
pmSumSqrUlCredits
•
pmSamplesDlCode
•
pmSumSqrDlCode
•
pmDlCredits
•
pmUlCredits
•
pmSumUlCredits
•
pmSumUlCredits
•
pmSumDlCode
•
pmLevelDlCodeCnOp
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
27
Performance Statistics - Flowcharts for Counters
For more information on each counter, refer to Managed Object Model (MOM)
RNC.
The counters pmLevelSampAseUl, pmLevelSampAseDl, pmLevelCompMode,
pmLevelDlCredits, pmLevelUlcredits and pmLevelDlCodeCnOp are internal
level counters not visible in the output statistics ROP file. They are mapped to
the related counters as follows:
•
pmLevelSampAseUl is mapped to pmSumOfSampAseUl and
pmNoOfSampAseUl.
•
pmLevelSampAseDl is mapped to pmSumOfSampAseDl and
pmNoOfSampAseDl.
•
pmLevelCompMode is mapped to pmSamplesCompMode and
pmSumCompMode.
•
pmLevelDlCredits is mapped to pmDlCredits and pmLevelUlCredits is
mapped to pmUlCredits.
•
pmLevelDlCodeCnOp is mapped to pmSumDlCodeCnOp and
pmSamplesDlCodeCnOp
Other impacted counters are included in the following flowcharts, which are
referenced from the Admission Control flowchart:
•
Figure 66, Figure 68, Figure 67, Figure 65, Figure 59
A flowchart for the Admission Control scenario is shown in Figure 17 and
Figure 18.
28
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Radio Link Reconfiguration
Radio Link Setup
Radio Link Delete
The procedure Req. Admission will
-increase UL/DL ASE or
-increase DL carrier power or
-start CPM
YES
Request for cell
resources?
Request Admission
NO
Radio Link Addition
NO
The procedure inform Admission
of a reduction in used cell
resources or UL ASE adjustment
at SoHo addition or replacement
Soft congestion
triggered due to shortage
of GBR BW UL?
ASE UL change?
YES
Soft congestion
triggered due to shortage
of GBR BW DL?
NO
NO
YES
pmLevelSampAseUL +
YES
NO
pmSoftCongGbrBwUl +
The counter is incremented
/ decremented with an
amount equal to the load
increase / decrease of the
procedure
YES
ASE DL change?
pmSoftCongGbrBwDl +
Soft congestion
triggered due to shortage
of RBS UL HW?
Compressed Mode
Usage
YES
pmLevelSampAseDL +
NO
pmSoftCongRbsUlHw +
The counter is incremented
by one if CPM started or
decremented if stopped.
Admission granted?
YES
NO
YES
pmNoOfDiscardedNbapCMessages+
Stop or start of
CPM?
NO
RL
Setup and UNISAAL congested?
NO
Go to Admission
Rejected Step in Part B
YES
pmLevelCompMode +
The counter is incremented
/ decremented with an
amount equal to the load
increase / decrease of the
procedure
YES
DL codes change?
pmLevelDlCodeCnOp +
NO
1
2
C 00 01120L
Figure 17
Admission Control Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
29
Performance Statistics - Flowcharts for Counters
1
2
Load sharing evaluation is only
applied on an Admission Request
related to an RL Setup of an RRC
Connection.
Load Sharing?
A PS Interactive RAB
(non-guaranteed/non-Iur connection)
is targeted for downswitch if the
cell carries a non-guaranteed RL
with stricly lower SF than the SF
of the requested RL
YES
DL credits
consumed?
NO
NO
YES
YES
pmDlCredits +
Any non-guaranteed
traffic in the cell?
NO
YES
pmNoOfSwDownNgAdm +
Any guaranteed
traffic in the cell?
NO
Channel SwitchingDownswitching
A PS Interactive RAB is
targeted for downswitch.
YES
Eul serving Cell?
Step if relevant:
pmNoServingCellReqDeniedEul +
pmNoServingCellReqDeniedEulTti2 +
NO
Step if relevant:
pmNoNonServingCellReqDeniedEul +
Respond to calling procedure
Admission granted /
Cell load updated
Admission Rejected
Radio Link Reconfiguration
Radio Link Setup
Radio Link Delete
Radio Link Addition
Compressed Mode
Usage
C 0001323F
Figure 18
2.2
Admission Control Scenario (Part B)
Retainability
This section describes the Retainability main traffic scenarios as follows:
•
30
Signaling Connection Release
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.2.1
•
RRC Connection Release
•
Radio Access Bearer Release
•
Lost Radio Connections on DCH
•
Lost Radio Connections due to Layer 2 Faults
•
Lost Radio Connections on FACH
•
Call Reestablishment
Signaling Connection Release
This traffic scenario describes release of Signaling Connection. This procedure
may use either the RAB Release or the RRC Connection Release procedure,
depending on whether the UE has a connection to more than one CN and a
RAB towards the CN requested to be disconnected.
The main counters for this scenario are as follows:
•
pmNoNormalNasSignReleaseCs, pmNoSystemNasSignReleaseCs
•
pmNoNormalNasSignReleasePs, pmNoSystemNasSignReleasePs
•
pmNoSystemNasSignReleaseMultiCs, pmNoSystemNasSignReleaseMul
tiPs
•
pmNoNormalNasSignReleaseMultiCs, pmNoNormalNasSignReleaseMul
tiPs
•
pmNoSystemNasSignReleaseCsfbInd, pmNoNormalNasSignReleaseCsf
bInd
•
pmNoNormalNasSignRelMultiCsUra, pmNoSystemNasSignRelMultiCsUra
Other impacted counters are included in the following flowcharts:
•
Figure 23, Figure 25, Figure 20, Figure 21, Figure 22.
A flowchart for the Signaling Connection Handling scenario is shown in Figure
19.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
31
Performance Statistics - Flowcharts for Counters
Start of Signaling Connection Release
Message received
Ue connected
to 2 CN?
(RANAP) IU RELEASE
COMMAND on X
X = CS or PS
RAB to be
disconnected?
YES
NO
NO
Normal RANAP
Release? *
pmNoSystemNasSignReleaseX +
pmNoSystemNasSignReleaseCsfbInd +
YES
RAB Release
The RRC Connection is
maintained to keep the
remaining signalling
connection (and RAB, if
established to that CN)
NO
YES
pmNoNormalNasSignReleaseX +
pmNoNormalNasSignReleaseCsfbInd +
NO
Normal RANAP
Release? *
pmNoSystemNasSignReleaseX +
pmNoSystemNasSignReleaseMultiX +
pmNoSystemNasSignRelMultiCsUra+ **
YES
pmNoNormalNasSignReleaseX +
pmNoNormalNasSignReleaseMultiX+
pmNoNormalNasSignRelMultiCsUra+ **
RRC Connection
Release
*) Based on RANAP Cause. The following RANAP causes
are considered to be normal: “Normal”, “Successful
Relocation”, “Resource Optimisation Relocation”
“Release-due-to-UE-generated-signalling-connection-release”
and “User inactivity”.
**) Stepped if UE originates from state URA_PCH
End
C 0001112K
Figure 19
2.2.2
Signaling Connection Handling Scenario
RRC Connection Release
This traffic scenario describes the release of an RRC Connection due to various
causes and from different service types.
The main counters for this scenario are as follows:
32
•
pmNoNormalRabReleaseSpeech, pmNoSystemRabReleaseSpeech
•
pmNoNormalRabReleaseAmrNb, PmNoSystemRabReleaseAmrNb
•
pmNoNormalRabReleaseCs64, pmNoSystemRabReleaseCs64
•
pmNoNormalRabReleaseCsStream, pmNoSystemRabReleaseCsStream
•
pmNoNormalRabReleasePacket, pmNoSystemRabReleasePacket
•
pmNoNormalRabReleasePacketStream, pmNoSystemRabReleasePacket
Stream
•
pmNoNormalRabReleasePacketStream128, pmNoSystemRabReleasePa
cketStream128
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoNormalRabReleasePacketUra, pmNoSystemRabReleasePacketUra
•
pmNoNormalRabReleasePsStreamHs, pmNoSystemRabReleasePsStr
eamHs
•
pmNoNormalReleaseSrbOnly34, pmNoSystemReleaseSrbOnly34
•
pmNoNormalReleaseSrbOnly136, pmNoSystemReleaseSrbOnly136
•
pmNoNormalReleaseSrbOnlyHs, pmNoSystemReleaseSrbOnlyHs
•
pmNoNormalReleaseSrbOnlyEul, pmNoSystemReleaseSrbOnlyEul
•
pmNoCellDchDisconnectNormal, pmNoCellDchDisconnectAbnorm
•
pmNoSpeechDchDiscNormal, pmNoSpeechDchDiscAbnorm
•
pmNoCs64DchDiscNormal, pmNoCs64DchDiscAbnorm
•
pmNoCsStreamDchDiscNormal, pmNoCsStreamDchDiscAbnorm
•
pmNoPacketDchDiscNormal, pmNoPacketDchDiscAbnorm
•
pmNoPsStream64Ps8DchDiscNormal, pmNoPsStream64Ps8DchDiscAbn
orm
•
pmNoPsStream128Ps8DchDiscNormal, pmNoPsStream128Ps8DchDis
cAborm
•
pmNoCellFachDisconnectNormal, pmNoCellFachDisconnectAbnorm
•
pmNoCellFachDiscAbnormEulFach
•
pmRedirectAttemptsUtran, pmRedirectAttemptsEutra
•
pmNormalRelMultiSpeech, pmNormalRelMultiAmrNb, pmNormalRelMult
iAmrWb, pmNormalRelMultiPsInt
•
pmSystemRelMultiSpeech, pmSystemRelMultiAmrNb, pmSystemRelMult
iAmrWb, pmSystemRelMultiPsInt
•
pmSpidPreventRwrEutra
Other impacted counters are included in the following flowcharts which are
referenced from the RRC Connection Release flowchart:
•
Figure 67, Figure 19
Flowcharts for the RRC Connection Release scenario is shown in Figure 20,
Figure 21 andFigure 22.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
33
Performance Statistics - Flowcharts for Counters
RRC Connection Release triggered
by Signaling Connection Handling
Message Sent
RRC CONNECTION RELEASE
UE
pmRedirectAttemptsUtran +
Radio Link Deletion
NO
1
Does Ue have a
RAB established?
YES
NO
2
RABs established to
both CS and PS ?
YES
YES
NO
pmNormalRelMultiSpeech+
pmNormalRelMultiAmrNb+
pmNormalRelMultiAmrWb+
pmNormalRelMultiPsInt+
pmSystemRelMultiSpeech+
pmSystemRelMultiAmrNb+
pmSystemRelMultiAmrWb+
pmSystemRelMultiPsInt+
3
4
Figure 20
34
Normal RANAP
Release? *
C 0001111V
RRC Connection Release Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2
YES
Normal RANAP
release ?
4
3
pmNormalReleaseSource +
pmSystemReleaseSource +
UE on DCH?
UE on DCH?
YES
YES
NO
NO
UE on URA_PCH?
YES
NO
NO
UE on URA_PCH?
YES
Step relevant counters:
pmNoSystemRabReleaseSpeech +
pmNoSystemRabReleaseAmrNb +
pmNoSystemRabReleaseCs64 +
pmNoSystemRabReleaseCsStream +
pmNoSystemRabReleasePacket +
pmNoSystemRabReleasePsStreamHs +
pmNoSystemRabReleasePacketStream +
pmNoSystemRabReleasePacketStream128 +
pmNoSystemReleaseSrbOnly34 +
pmNoSystemReleaseSrbOnly136 +
pmSystemReleaseSrbOnlyHs +
pmSystemReleaseSrbOnlyEul +
Step relevant counters:
pmNoNormalRabReleaseSpeech +
pmNoNormalRabReleaseAmrNb +
pmNoNormalRabReleaseCs64 +
pmNoNormalRabReleaseCsStream +
pmNoNormalRabReleasePacket +
pmNoNormalRabReleasePsStreamHs +
pmNoNormalRabReleasePacketStream +
pmNoNormalRabReleasePacketStream128 +
pmNoNormalReleaseSrbOnly34 +
pmNoNormalReleaseSrbOnly136 +
pmNormalReleaseSrbOnlyHs +
pmNormalReleaseSrbOnlyEul +
NO
pmNoNormalRabReleasePacket +
pmNoSystemRabReleasePacket +
pmNoSystemRabReleasePacketUra +
pmNoSystemRabReleasePacket +
pmNoNormalRabReleasePacketUra +
pmNoNormalRabReleasePacket +
NO
1
SPID for UE allows
RWR to LTE?
pmSpidPreventRwrEutra +
YES
pmRedirectAttemptsEutraCnOper +
pmRedirectAttemptsEutra +
Return to calling procedure: Signaling Connection Handling
C 0001591D
Figure 21
RRC Connection Release Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
35
Performance Statistics - Flowcharts for Counters
1
YES
NO
Normal RRC
Release? *
Step if relevant, if reconfiguration attempt
caused by RAB Establishment,
RAB Release or Channel Switching fails
unrecoverable resulting in connection release
NO
pmReconfSysRelSource+
pmReconfSysRelTarget+
UE on DCH?
YES
If Signaling
Connection only,
counter
pmNoCellDchDisc...
is stepped
PS Interactive
64/64 or 64/128
orb 64/384
Going from PS
Streaming 16/64 +
PS 8/8
IDLE
pmNoCellDchDisconnectNormal +
or
(pmNoCellDchDisconnectNormal +
and
(pmNoSpeechDchDiscNormal +
or
pmNoCs64DchDiscNormal +
or
pmNoCsStreamDchDiscNormal +
or
pmNoPacketDchDiscNormal +
or
pmNoPsStream64Ps8DchDiscNormal +
or
pmNoPsStream128Ps8DchDiscNormal +))
pmNoCellFachDisconnectNormal +
NO
SPID for UE allows
RWR to LTE?
NO
YES
pmNoCellDchDisconnectAbnorm +
or
(pmNoCellDchDisconnectAbnorm +
and
(pmNoSpeechDchDiscAbnorm +
or
pmNoCs64DchDiscAbnorm +
or
pmNoCsStreamDchDiscAbnorm +
or
pmNoPacketDchDiscAbnorm +
or
pmNoPsStream64Ps8DchDiscAborm +
or
pmNoPsStream128Ps8DchDiscAborm +))
If Signaling
Connection only,
counter
pmNoCellDchDisc...
is stepped
PS Interactive
64/64 or 64/128
orb 64/384
Going from PS
Streaming 16/64 +
PS 8/8
IDLE
pmNoCellFachDisconnectAbnorm +
pmNoCellFachDiscAbnormEulFach +
YES
pmRedirectAttemptsEutraCnOper +
pmRedirectAttemptsEutra +
pmSpidPreventRwrEutra +
UE on DCH?
Step if relevant
Return to calling procedure: Signaling Connection Handling
C 0001592C
Figure 22
2.2.3
RRC Connection Release Scenario (Part C)
RAB Release
This traffic scenario describes the steps involved in RAB Release.
The main counters for this scenario are as follows:
36
•
pmNoNormalRabReleaseSpeech, pmNoSystemRabReleaseSpeech
•
pmNoNormalRabReleaseAmrNb, pmNoSystemRabReleaseAmrNb
•
pmNoNormalRabReleaseAmrWb, pmNoSystemRabReleaseAmrWb
•
pmNoNormalRabReleaseCs64, pmNoSystemRabReleaseCs64
•
pmNoNormalRabReleaseCsStream, pmNoSystemRabReleaseCsStream
•
pmNoNormalRabReleasePacket, pmNoSystemRabReleasePacket
•
pmNoNormalRabReleasePacketStream, pmNoSystemRabReleasePacket
Stream
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoNormalRbReleaseHs, pmNoSystemRbReleaseHs
•
pmNoNormalRbReleaseEul, pmNoSystemRbReleaseEul
•
pmNoNormalRabReleasePacketStream128, pmNoSystemRabReleasePa
cketStream128
•
pmNoNormalRabReleasePsStreamHs, pmNoSystemRabReleasePsStr
eamHs
•
pmNoRabReleaseAttempt, pmNoRabReleaseSuccess
•
pmNoInvalidRabReleaseAttempts
•
pmInactivityMultiPsInt
•
pmInactivityPsStreamIdle
•
pmNoSuccRbReconfPsIntDch, pmNoSuccRbReconfOrigPsIntDch
•
pmNoSuccRbReconfPsIntHs, pmNoSuccRbReconfOrigPsIntHs
•
pmNoSuccRbReconfPsIntEul, pmNoSuccRbReconfOrigPsIntEul
•
pmPsIntHsToFachAtt, pmPsIntHsToFachSucc
•
pmPsIntDchToFachAtt, pmPsIntDchToFachSucc
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmSystemReleaseSource
•
pmNormalRelMultiSpeech, pmNormalRelMultiSpeechToPsInt,
pmNormalRelMultiAmrWb, pmNormalRelMultiAmrNb
•
pmSystemRelMultiSpeech, pmSystemRelMultiSpeechToPsInt,
pmSystemRelMultiAmrWb, pmSystemRelMultiAmrNb
Other impacted counters are included in the following flowcharts:
•
Figure 65, Figure 68, Figure 19
A flowchart for the RAB Release scenario is shown in Figure 23, Figure 24,
Figure 25, Figure 26, Figure 27, Figure 28, Figure 29, Figure 30, Figure 31,
Figure 32, Figure 33, Figure 34 and Figure 35.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
37
Performance Statistics - Flowcharts for Counters
Signalling Connection
Handling
(RANAP) RAB ASSIGNMENT
REQUEST
RAB Release triggere
by RAB Assignment
PS Streaming Inactivity
Timeout
Reason = Rabs to be released
pmInactivityPsStreamIdle +
Start of RAB Release
Trigger?
Iu
Release
Command
Can be triggered by the RANAP RAB
Assignment Request message or
RANAP Iu Release Command message
(Signalling Connection Handling)
RANAP RAB Assignment Request,
Reason = Rabs to be released
Unknown RAB
ID, .....
Valid Release
Request?
NO
Error 1
YES
Message sent
(RANAP) RAB ASSIGNMENT
RESPONSE SUCCESSFUL
SRNC or DRNC?
SRNC
DRNC
C 00 01251
Figure 23
RAB Release Scenario Start
Error 2
Error 1
pmNoRabReleaseAttempts +
Logical Error Reception of
RAB Assignment,
RAB Type not supported
Reason?
RAB ID
Unknown
pmNoInvalidRabReleaseAttempts +
Message sent
End
pmNoRabReleaseAttempts +
(RANAP) IU RELEASE
REQUEST
Message sent
End
Cause = Unsuccessful Cause
CN may or may not reply
with RANAP Iu Release
Command Command.
(RANAP) RAB
ASSIGNMENT
RESPONSE
Cause = Unsuccessful
C 00 01252B
Figure 24
38
RAB Release Scenario, Error 1 and Error 2
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
SRNC
YES
RAB on DCH?
NO
Radio Link Release
Radio Link
Reconfiguration
RAB Type?
DCH RAB Type?
DCH RAB (Ps on DCH, PS Streaming
Multi RAB
CS Streaming, CS Data, (PS Streaming
(Speech +
CS Speech)
16/64 +
PS 64,
PS Interactive 8/8) Speech +
PS Streaming
multiPS,
16/128 +
multiPS)
PS Interactive 8/8
Figure 25
DSCH RAB Type
(PS on 64/HS
or 384/HS
or Eul/HS)
PS Data on
FACH
C 00 01253F
RAB Release Scenario, SRNC
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
39
Performance Statistics - Flowcharts for Counters
DCH RAB (Ps on DCH,
CS Streaming, CS Data,
CS Speech)
YES
Successful Radio
Link reconfiguration?
(RRC) RADIO
BEARER
RELEASE
Message sent
NO
Error 2
Step relevant counter:
pmPsIntDchToFachAtt +
YES
Successfull
Complete?
Step relevant counter:
pmNoSuccRbReconfOrigPsIntDch +
pmPsIntDchToFachSucc +
NO
Error 2
pmNoRabReleaseAttempts +
pmNoRabReleaseSuccess +
pmReconfAttSource+
pmReconfAttTarget+
pmReconfSuccSource+
pmReconfSuccTarget+
Normal
pmNoNormalRabReleaseX +
Cause?
X= one of Speech,
Speech&AmrNb,
Speech&AmrWb,
Packet, CsStream,
Cs64
Abnormal
pmNoSystemRabReleaseSpeechX +
pmSystemReleaseSource+
pmNormalReleaseSource+
RANAP Message?
Rab
Assignment
Request?
End
Message sent
CN
End
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause
received in Iu
Release Command
C 00 01254E
Figure 26
40
RAB Release Scenario, SRNC-DCH RAB
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
PS Streaming
NO
Successful Radio
Link reconfiguration?
Error 2
YES
Message received
(RRC) RADIO
BEARER
RELEASE COMPLETE
NO
Successfull
Complete?
Error 2
YES
Step relevant counter:
pmNoSuccRbReconfPsIntDch +
pmNoRabReleaseAttempts +
pmNoRabReleaseSuccess +
A request to release the PS Int 8/8 will
have been received earlier. The RNC
will have replied with an IU Release
Request to release the connection
(since the Streaming 16/64 cannot be
supported standalone). An IU Release
Command will than be received
leading to this branch of the release.
pmReconfAttSource+
pmReconfAttTarget+
pmReconfSuccSource+
pmReconfSuccTarget+
PS Interactive
(Release of Streaming Part)
SRB-DCH
(Release of both parts of RAB)
Abnormal
Cause?
Normal
Target State?
Abnormal
pmNoSystemRabReleasePacketStream +
pmNoSystemRabReleasePacketStream128 +
pmNoSystemRabReleasePacket +
pmNoSystemRabReleasePacketStream +
pmNoSystemRabReleasePacketStream128 +
pmNoNormalRabReleasePacketStream +
pmNoNormalRabReleasePacketStream128 +
pmSystemReleaseSource +
pmSystemReleaseSource +
Normal
pmNoNormalRabReleasePacket +
pmNoNormalRabReleasePacketStream +
pmNoNormalRabReleasePacketStream128 +
pmNormalReleaseSource +
Rab Assignment Request?
Cause?
pmNormalReleaseSource +
RANAP Message?
Message sent
End
End
CN
(RANAP) IU RELEASE
COMPLETE
RNC
cause = cause received in Iu
Release Command
C 00 01255D
Figure 27
RAB Release Scenario, SRNC-PS Streaming
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
41
Performance Statistics - Flowcharts for Counters
Multi RAB (Speech +
PS 64, Speech +
multiPS, multiPS)
YES
NO
NO
Successful Radio
Link reconfiguration?
(RRC) RADIO
Message sent
BEARER
RELEASE
Error 2
YES
Successfull
Complete?
Step relevant counter:
pmNoSuccRbReconfPsIntHs +
pmNoSuccRbReconfPsIntEul +
Error 2
pmNoRabReleaseAttempt +
pmNoRabReleaseSuccess +
pmReconfAttSource+
pmReconfAttTarget+
pmReconfSuccSource+
pmReconfSuccTarget+
CS
Normal
Cause?
pmNoNormalRabReleaseSpeech +
pmNormalRelMultiSpeech +
pmNormalRelMultiSpeechToPsInt +
pmNoNormalRabReleaseX +
pmNormalRelMultiX +
Abnormal
YES
pmNoSystemRabReleaseSpeech +
pmSystemRelMultiSpeech +
pmSystemRelMultiSpeechToPsInt +
Step if relevant
X= AmrWb
or AmrNb
PS
Target State?
Release triggered
by inactivity of one or more
PS Interactive RABs?
pmInactivityMultiPsInt +,
stepped once for each
released PS interactive RAB
NO
pmNoNormalRabReleaseX +
pmNormalRelMultiX +
Normal
Cause?
pmNormalReleaseSource +
Abnormal
pmSystemReleaseSource +
pmNoNormalRabReleasePacket +
pmNormalRelMultiPsInt +
pmNoNormalRelMultiPsIntToX +
pmNormalReleaseSource +
pmNoSystemRabReleasePacket +
pmSystemRelMultiPsInt +
Step if relevant
X= one of:
Speech
Speech&AmrWb
Speech&AmrNb
pmNoNormalRelMultiPsIntToX +
pmSystemReleaseSource +
RANAP Message?
Rab
Assignment
Request?
End
Figure 28
42
Message sent
End
CN
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause received in Iu
Release Command
C 00 01256F
RAB Release Scenario, Multi RAB SRNC (Speech + PS 64, Speech + MultiPS,
MultiPS)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
DSCH RAB Type
(PS on 64/HS
or 384/HS
or Eul/HS)
Successful
YES
Radio Link
Reconfiguration?
(RRC) RADIO BEARER
RELEASE
Message sent
NO
Error 2
Step relevant counter:
pmPsIntHsToFachAtt +
Successful
YES
Radio Bearer
Release ?
Step relevant counter:
pmNoSuccRbReconfOrigPsIntHs +
pmNoSuccRbReconfOrigPsIntEul +
pmPsIntHsToFachSucc +
NO
Error 2
pmNoRabRelaseAttempt +
pmNoRabReleaseSuccess +
pmReconfAttSource+
pmReconfAttTarget+
pmReconfSuccSource+
pmReconfSuccTarget+
Normal
pmNoNormalRbReleaseHs +
pmNoNormalRabReleasePacket +
pmNoNormalRabReleasePsStreamHs +*
Cause ?
Abnormal
pmNoSystemRbReleaseHs +
pmNoSystemRabReleasePacket +
pmNoSystemRabReleasePsStreamHs +*
* Step if relevant
pmSystemReleaseSource +
pmNormalReleaseSource +
YES
pmNoNormalRbReleaseEul +
Eul ?
Eul ?
YES
NO pmNoSystemRbReleaseEul +
NO
RANAP
Rab
Assignement
Request
Message
Message sent
End
CN
IU RELEASE
COMPLETE
RNC
End
C 00 01257G
Figure 29
RAB Release Scenario, SRNC- RAB Type
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
43
Performance Statistics - Flowcharts for Counters
PS Data on
FACH
Successful
Radio Link release?
NO
Error 2
YES
(RRC) RADIO
BEARER RELEASE
Message sent
Successful
RRC Radio Bearer
release Complete?
NO
Error 2
YES
pmNoRabReleaseAttempt +
pmNoRabReleaseSuccess +
pmReconfAttSource+
pmReconfAttTarget+
pmReconfSuccSource+
pmReconfSuccTarget+
Normal
Cause?
Abnormal
pmNoNormalRabReleasePacket +
pmNoSystemRabReleasePacket +
pmNormalReleaseSource+
pmSystemReleaseSource+
RANAP Message?
Rab
Assignment
Request?
End
Message sent
End
CN
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause
received in Iu
Release Command
C 00 01258C
Figure 30
44
RAB Release Scenario, SRNC-PS Data on FACH
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
DRNC
YES
RAB on DCH?
NO
Radio Link Release
Radio Link
Reconfiguration
DCH RAB Type?
DCH RAB
(Ps on DCH,
CS Streaming,
CS Data,
CS Speech)
Figure 31
PS Streaming
(PS Streaming
16/64 +
PS Interactive 8/8)
PS Streaming
16/128 +
PS Interactive 8/8
Speech +
PS 64
(multi RAB)
PS Data on
FACH C 00 01259C
RAB Release Scenario, DRNC
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
45
Performance Statistics - Flowcharts for Counters
DCH RAB (Ps on DCH,
CS Streaming, CS Data,
CS Speech)
YES
Successful Radio
Link reconfiguration?
(RRC) RADIO
BEARER
RELEASE
Message sent
NO
Error 2
Step relevant counter:
pmPsIntDchToFachAtt +
Successful
YES
Radio Bearer Release ?
NO
Step relevant counters:
pmNoSuccRbReconfOrigPsIntDch +
pmPsIntDchToFachSucc +
Cause?
Error 2
Abnormal
Normal
pmNoNormalRabReleaseSpeech +
or
pmNoNormalRabReleaseSpeech +
pmNoNormalRabReleaseAmrNb +
or
pmNoNormalRabReleaseSpeech +
pmNoNormalRabReleaseAmrWb +
or
pmNoNormalRabReleasePacket +
or
pmNoNormalRabReleaseCsStream +
or
pmNoNormalRabReleaseCs64 +
pmNoSystemRabReleaseSpeech +
or
pmNoSystemRabReleaseSpeech +
pmNoSystemRabReleaseAmrNb +
or
pmNoSystemRabReleaseSpeech +
pmNoSystemRabReleaseAmrWb +
or
pmNoSystemRabReleasePacket +
or
pmNoSystemRabReleaseCsStream +
or
pmNoSystemRabReleaseCs64 +
RANAP Message?
Rab
Assignment
Request?
End
Figure 32
46
Message sent
End
CN
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause
received in Iu
Release Command
C 00 01260E
RAB Release Scenario, DRNC-DCH RAB
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
PS Streaming
(PS Streaming 16/64 +
PS Interactive 8/8)
+ Streaming 16/128
NO
Successful Radio
Link reconfiguration?
Error 2
YES
Message received
(RRC) RADIO
BEARER
RELEASE COMPLETE
Successful
Radio Bearer Release ?
NO
YES
A request to release the PS Int 8/8 will
have been received earlier. The RNC
will have replied with an IU Release
Request to release the connection
(since the Streaming 16/64 cannot be
supported standalone). An IU Release
Command will than be received
leading to this branch of the release.
Error 2
Step relevant counter:
pmNoSuccRbReconfPsIntDch +
PS Interactive 64/64
(Release of Streaming Part)
Target State?
SRB-DCH
(Release of both parts of RAB)
Abnormal
Cause?
Abnormal
pmNoSystemRabReleasePacketStream +
pmNoSystemRabReleasePsStreamHs +
Cause?
pmNoSystemRabReleasePacket +
pmNoSystemRabReleasePacketStream +
pmNoSystemRabReleasePsStreamHs +
Normal
Normal
pmNoNormalRabReleasePacket +
pmNoNormalRabReleasePacketStream +
pmNoNormalRabReleasePsStreamHs +
pmNoNormalRabReleasePacketStream +
pmNoNormalRabReleasePsStreamHs +
Rab Assignment Request?
RANAP Message?
Message sent
End
End
CN
(RANAP) IU RELEASE
COMPLETE
RNC
cause = cause received in Iu
Release Command
C 00 01261D
Figure 33
RAB Release Scenario, DRNC-PS Streaming
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
47
Performance Statistics - Flowcharts for Counters
Speech + PS 64 (multi RAB)
YES
(RRC) RADIO
Message sent
BEARER
RELEASE
NO
Successful
NO
Successful Radio
Link reconfiguration?
Error 2
YES
Radio Bearer Release ?
Error 2
Step relevant counter:
pmNoSuccRbReconfPsIntHs +
pmNoSuccRbReconfPsIntEul +
CS
Normal
Cause?
pmNoNormalRabReleaseSpeech +
pmNormalRelMultiSpeech +
pmNormalRelMultiSpeechToPsInt +
pmNoNormalRabReleaseX +
pmNormalRelMultiX +
PS
Target State?
Abnormal
pmNoSystemRabReleaseSpeech +
pmSystemRelMultiSpeech +
pmSystemRelMultiSpeechToPsInt +
Step if relevant
X= AmrWb
or AmrNb
pmNoNormalRabReleaseX +
pmNormalRelMultiX +
Normal
Abnormal
Cause?
pmNoNormalRabReleasePacket +
pmNormalRelMultiPsInt +
pmNoNormalRelMultiPsIntToX +
pmNoSystemRabReleasePacket +
pmSystemRelMultiPsInt +
Step if relevant
X= one from
Speech
Speech&AmrWb
Speech&AmrNb
pmNoNormalRelMultiPsIntToX +
RANAP Message?
Message sent
Rab
Assignment
Request?
End
End
CN
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause received in Iu
Release Command
C 00 01262F
Figure 34
48
RAB Release Scenario, DRNC-Speech + PS 64
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
PS Data on
FACH
Successful
Radio Link release?
NO
Error 2
YES
Message sent
(RRC) RADIO
BEARER RELEASE
Successful
RRC Radio Bearer
release Complete?
NO
Error 2
YES
Abnormal
Cause?
Normal
pmNoNormalRabReleasePacket +
pmNoSystemRabReleasePacket +
Rab
Assignment
Request?
RANAP
Message?
Message sent
End
Figure 35
2.2.4
End
CN
(RANAP) IU
RELEASE
COMPLETE
RNC
cause = cause received
in Iu Release Command
C 00 01263
RAB Release Scenario, DRNC-PS Data on FACH
Lost Radio Connections on Dedicated Channel
This traffic scenario describes the loss of a radio connection from a dedicated
channel as detected by radio connection supervision.
The main counter for this scenario is pmNoReleaseDchRcLostT.
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the Lost Radio Connections on Dedicated Channel flowchart.
A flowchart for the Lost Radio Connections on Dedicated Channel scenario
is shown in Figure 36 and Figure 37.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
49
Performance Statistics - Flowcharts for Counters
Supervision of Radio Connections
on dedicated channels
Rnsap/Nbap
RADIO LINK
FAILURE
INDICATION
NO
Radio
Link Failure
Indication Received
with cause value
"Synchronization
Failure"?
YES
Have
all Radio Link
Sets belonging to the
connection reported loss of
synchronization?
NO
YES
Start Supervision timer: dchRcLostT
Rnsap/Nbap
RADIO LINK
RESTORE
INDICATION
Note: The Counter is
stepped in the SRNC
RL
Restore received
before expiring of
supervising
timer?
YES
Stop Supervision timer
NO
pmNoReleaseDchRcLostT +
RRC Connection Release
C 00 01095C
Figure 36
50
Lost Radio Connections on Dedicated Channel Scenario A
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Supervision of Radio Connections
on dedicated channels
Note: The Counter is
stepped in the SRNC
Rnsap/Nbap
RADIO LINK
FAILURE
INDICATION
Failure
of Radio Link
associated with
the Serving HS-DSCH?
NO
YES
Start Supervision timer: hsDschRcLostT
Rnsap/Nbap
RADIO LINK
RESTORE
INDICATION
RL
Restore received
before expiring of
supervising
timer?
YES
Stop Supervision timer
NO
NO
Connection
to CS CN
exist?
YES
pmNoReleaseDchRcLostT +
Release connection to PS CN
Release UE connection
END
Supervision of Radio Connections
on dedicated channels
C0001462B
Figure 37
2.2.5
Lost Radio Connections on Dedicated Channel Scenario B
Lost Radio Connections due to Layer 2 Fault
This traffic scenario describes the loss of a connection due to layer 2 faults, as
detected by radio connection supervision functionality.
The main counter for this scenario is pmNoRlcErrors.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
51
Performance Statistics - Flowcharts for Counters
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the Lost Radio Connections due to Layer 2 Fault flowchart.
A flowchart for the Lost Radio Connections due to Layer 2 Fault scenario
is shown in Figure 38.
Supervision on all Radio
Connections
NO
Has
an RLC
unrecoverable error
occured?
YES
pmNoRlcErrors +
Note: This counter is
stepped for errors detected
in layer 2 in the RNC
RRC Connection Release
C 00 01096B
Figure 38
2.2.6
Lost Radio Connections due to Layer 2 Fault Scenario
Lost Radio Connections on Common Channel
This traffic scenario describes the loss of a connection from a common channel
as detected by radio connection supervision functionality.
The main counter for this scenario is pmNoReleaseCchWaitCuT.
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the Lost Radio Connections on Common Channel flowchart.
A flowchart for the Lost Radio Connections on Common Channel scenario
is shown in Figure 39.
52
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Supervision of Radio Connections
on Common channels
UE on Cell_FACH
(Re) Start supervising timer: cchWaitCuT
RRC Cell Update
NO
Cell
Update received
before the expiration
of the supervision
timer
YES
pmNoReleaseCchWaitCuT +
RRC Connection Release
C 00 01097B
Figure 39
2.2.7
Lost Radio Connections on Common Channel Scenario
Call Reestablishment
This traffic scenario describes automatic reestablishment of CS connection
after a loss of DL synchronization or if RLC unrecoverable error is detected by
the UE and conveyed in a CELL UPDATE message.
The counters for this scenario are as follows:
•
pmCallReestReqCs
•
pmCallReestAttCs
•
pmCallReestSuccCs
A flowchart for the Call Reestablishment scenario is shown in Figure 40:
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
53
Performance Statistics - Flowcharts for Counters
CELL UPDATE message
is received
Cell Update cause
“RL failure” or “RLC unrecoverable
error”?
NO
Connection
Release
End
YES
T314 timer
in UE expired?
YES
NO
pmCallReestReqCs +
Radio Link Deletion
Perform Admission Control
Admission
Control successful?
NO
YES
Radio Link Setup
pmCallReestAttCs +
(RRC) Cell Update
Confirm
Message Sent/Received
Failure response
message?
YES
NO
pmCallReestSuccCs +
End of Call Reestablishment
C 0001472A
Figure 40
2.3
Call Reestablishment Scenario
Quality
This section describes the Quality main traffic scenarios as follows:
54
•
Channel Switching, Common to Dedicated
•
Channel Switching, Dedicated to Common
•
Channel Switching, upswitch Dedicated to Dedicated
•
Channel Switching, downswitch Dedicated to Dedicated
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.3.1
•
Channel Switching, Common to URA_PCH
•
Channel Switching, URA_PCH to Common
•
Channel Switching, Dedicated to URA_PCH
•
Channel Switching, URA_PCH to Dedicated
•
Channel Switching to Idle
Channel Switching, Common to Dedicated
This traffic scenario describes the switching of a channel from common to
dedicated as a result of a Channel Switching Evaluation decision based on
downlink buffer load and traffic volume measurements from the UE.
The main counters for this scenario are as follows:
•
pmLevelPsInteractive
•
pmLevelUesWith1Rls1RlInActSet
•
pmNoOfRlForNonDriftingUes
•
pmDlUpswitchAttemptHs, pmDlUpswitchSuccessHs
•
pmUlUpswitchAttemptLow, pmUlUpswitchSuccessLow
•
pmUpswitchFachHsAttempt, pmUpswitchFachHsSuccess
•
pmDlUpswitchAttemptLow, pmDlUpswitchSuccessLow
•
pmUlUpswitchAttemptEul, pmUlUpswitchSuccessEul
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
55
Performance Statistics - Flowcharts for Counters
Note:
The internal counters pmLevel<serviceType>RabEstablish and
pmLevelUesWithXRlsYRlInActSet are not visible in the output Statistics
ROP file. They are mapped to the following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceT
ype>RabEstablish
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counter pmLevelPsInteractive also is of type pmLevel<serviceT
ype>RabEstablish despite a different name syntax. This counter is
mapped to the following related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
The counter pmLevelEulMcConn also is of type pmLevel<serviceT
ype>RabEstablish despite a different name syntax. This counter is
mapped to the following related counters:
•
pmSumEulMcConn and pmSamplesEulMcConn
For a general explanation of counters of type pmLevel<serviceType>R
abEstablish and pmLevelUesWithXRlsYRlInActSet and their related
counters, see the explanation in the Radio Link Setup flowchart figure.
Other impacted counters are included in the flowcharts Figure 20, Figure 17
and Figure 18, which are referenced from the Channel Switching, Common to
Dedicated flowchart.
A flowchart for the Channel Switching, Common to Dedicated scenario is
shown in Figure 41.
56
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Channel Switching Evaluation decides
common->dedicated channel switch needed
Decision to switch if DL or
UL buffer load above a threshold
Check MP Load Control
NO
End
Load ok?
YES
Admission Control
NO
Admission granted?
pmUlUpswitchAttemptEul +
pmDlUpswitchAttemptHs +
pmUpswitchFachHsAttempt +
YES
NBAP/RNSAP: Radio Link
Setup Request
Messages Received/Sent
YES
NBAP/RNSAP: Radio Link
Setup Response
RRC: Radio Bearer
Reconfiguration
FACH to DCH
switch successful?
RRC: Radio Bearer
Reconfiguration Complete
Step relevant counters
Step relevant counters
NO
YES
pmUlUpswitchAttemptLow +
pmUlUpswitchSuccessLow +
pmUlUpswitchAttemptEul +
pmUlUpswitchSuccessEul +
pmDlUpswitchAttemptLow +
pmDlUpswitchSuccessLow +
pmDlUpswitchAttemptHs +
pmDlUpswitchSuccessHs +
pmUpswitchFachHsAttempt +
pmUpswitchFachHsSuccess +
Reattempt on
lower rate?
NO
pmUlUpswitchAttemptLow +
pmUlUpswitchAttemptEul +
pmDlUpswitchAttemptLow +
pmDlUpswitchAttemptHs +
pmUpswitchFachHsAttempt +
Possible
to revert to
FACH?
Step relevant counters
NO
Send message
YES
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
Release new resources
Stay on common channel
RRC Connection Release
pmReconfAttSource +
pmReconfAttTarget +
pmReconfAttSource +
pmReconfAttTarget +
pmReconfAttSource +
pmReconfAttTarget +
End
End
End
RANAP:
IuRelease
Request
C 0001128N
Figure 41
2.3.2
Channel Switching, Common to Dedicated Scenario
Channel Switching, Dedicated to Common
This traffic scenario describes the switching of a channel from dedicated to
common as a result of a Channel Switching Evaluation decision.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
57
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
58
•
pmNoCellUpdAttempt, pmNoCellUpdSuccess
•
pmDownSwitchAttempt, pmDownSwitchSuccess
•
pmPsIntHsToFachAtt, pmPsIntHsToFachSucc
•
pmPsIntDchToFachAtt, pmPsIntDchToFachSucc
•
pmCmStop
•
pmInterFreqMeasCmStop
•
pmInterFreqMeasNoCmStop
•
pmNoOfRlForDriftingUes
•
pmNoOfRlForDriftingUesPerDrnc
•
pmNoOfRlForNonDriftingUes
•
pmLevelPsInteractive
•
pmLevelUesWith1Rls1RlInActSet
•
pmLevelUesWith1Rls2RlInActSet
•
pmLevelUesWith1Rls3RlInActSet
•
pmLevelUesWith2Rls2RlInActSet
•
pmLevelUesWith2Rls3RlInActSet
•
pmLevelUesWith2Rls4RlInActSet
•
pmLevelUesWith3Rls3RlInActSet
•
pmLevelUesWith3Rls4RlInActSet
•
pmLevelUesWith4Rls4RlInActSet
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmOutRedirectHsIflsFach
•
pmInRedirectHsIflsFach
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Note:
The internal counters pmLevel<serviceType>RabEstablish and
pmLevelUesWithXRlsYRlInActSet are not visible in the output Statistics
ROP file. They are mapped to the following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceT
ype>RabEstablish
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counter pmLevelPsInteractive also is of type pmLevel<serviceT
ype>RabEstablish despite a different name syntax. This counter is
mapped to the following related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
The counter pmLevelEulMcConn also is of type pmLevel<serviceT
ype>RabEstablish despite a different name syntax. This counter is
mapped to the following related counters:
•
pmSumEulMcConn and pmSamplesEulMcConn
For a general explanation of counters of type pmLevel<serviceType>R
abEstablish and pmLevelUesWithXRlsYRlInActSet and their related
counters, see the explanation in the Radio Link Setup flowchart figure.
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the Channel Switching, Dedicated to Common flowchart.
A flowchart for the Channel Switching, Dedicated to Common scenario is
shown in Figure 42.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
59
Performance Statistics - Flowcharts for Counters
Decision to switch if parameter AllowSwitchToCommon=1.
Channel Evaluation decision is due to Low Throughput.
Additionally, this switch can be triggered by Congestion.
Before the switch, the UE is communicating on Cell_DCH with 1..4 cells
in the Active Set. Unless otherwise stated, all counters are stepped
for each cell in the active set before a switch to FACH takes place.
After switching to FACH, the UE is in Cell_FACH state and
communicates on one cell only.
Channel Switching Evaluation decides
dedicated-common channel switch needed
RRC: Radio Bearer
Reconfiguration
Message Sent
pmOutRedirectHsIflsFach +
Step the relevant counter:
pmPsIntHsToFachAtt +
pmPsIntDchToFachAtt +
pmDownSwitchAttempt +
pmReconfAttSource +
pmReconfAttTarget +
RRC: Radio
Bearer Reconfiguration Failure
received?
RRC: Cell Update
YES
pmNoCellUpdAttempt +
Possible to
revert to DCH?
pmInRedirectHsIflsFach +
RRC: Cell Update
Confirm
RRC Connection Release
Message Sent
YES
End
RRC: Radio Bearer
Reconfiguration Complete
NBAP/RNSAP: Radio
Link Delete Response
NO
Revert to DCH
NO
Cell Update Successful?
NBAP/RNSAP: Radio
Link Delete Request
For FACH-Cell
NO
Message Received
Abort UE
Connection
End
YES
Messages Received/Sent
NO
Reconfiguration
Successful?
Send message
YES
Step the relevant counter:
pmPsIntHsToFachSucc +
pmPsIntDchToFachSucc +
RRC Connection Release
End
pmDownSwitchSuccess +
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
Compressed mode active?
YES
pmCmStop +
NO
Meas type
Inter-Frequency?
NO
YES
Meas type
Inter-Frequency?
pmInterFreqMeasNoCmStop +
YES
pmInterFreqMeasCmStop +
NO
pmLevelPsInteractivepmLevelUesWith1Rls1RlInActSetpmLevelUesWith1Rls2RlInActSetpmLevelUesWith1Rls3RlInActSetpmLevelUesWith2Rls2RlInActSetpmLevelUesWith2Rls3RlInActSetpmLevelUesWith2Rls4RlInActSetpmLevelUesWith3Rls3RlInActSetpmLevelUesWith3Rls4RlInActSetpmLevelUesWith4Rls4RlInActSetpmNoOfRlForNonDriftingUespmNoOfRlForDriftingUes-
Step one of these only
For FACH-Cell
pmNoCellUpdAttempt +
pmNoCellUpdSuccess +
End
Figure 42
60
C 00 01129M
Channel Switching, Dedicated to Common Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.3.3
Channel Switching, Upswitch Dedicated to Dedicated
This traffic scenario describes the switching between dedicated channels as a
result of a Channel Switching Evaluation decision.
The main counters for this scenario are as follows:
•
pmUlUpswitchAttemptLow, pmUlUpswitchSuccessLow
•
pmUlUpswitchAttemptMedium, pmUlUpswitchSuccessMedium
•
pmUlUpswitchAttemptHigh, pmUlUpswitchSuccessHigh
•
pmUlUpswitchAttemptEul, pmUlUpswitchSuccessEul
•
pmDlUpswitchAttemptLow, pmDlUpswitchSuccessLow
•
pmDlUpswitchAttemptMedium, pmDlUpswitchSuccessMedium
•
pmDlUpswitchAttemptHigh, pmDlUpswitchSuccessHigh
•
pmDlUpswitchAttemptHs, pmDlUpswitchSuccessHs
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlHls, pmCmSuccDlHls
•
pmNoSuccRbReconfPsIntDch
•
pmNoSuccRbReconfPsIntHs
•
pmNoSuccRbReconfPsIntEul
•
pmCmStop
•
pmLevelPsInteractive
•
pmLevelPsEulRabEstablish
•
pmLevelPsHsAdchRabEstablish
•
pmLevelBestPsEulRabEstablish
•
pmLevelBestPsHsAdchRabEstablish
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
61
Performance Statistics - Flowcharts for Counters
Note:
The counter pmLevelPsInteractive is of type pmLevel<serviceTy
pe>RabEstablish despite a different name syntax. This counter
is mapped to the related counters pmSumPsInteractive and
pmSamplesPsInteractive.
The counter pmLevelEulMcConn also is of type pmLevel<ser
viceType>RabEstablish despite a different name syntax. This
counter is mapped to the related counters pmSumEulMcConn and
pmSamplesEulMcConn.
The internal counters pmLevel<serviceType>RabEstablish and
pmLevelBest<serviceType>RabEstablish are not visible in the output
Statistics ROP file. They are mapped to the following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceTy
pe>RabEstablishs
•
pmSumBest<serviceType>RabEstablish and pmSamplesBest<ser
viceType>RabEstablishs
For a general explanation of counters of type pmLevel<serviceType
>RabEstablish and their related counters, see the explanation in the
Radio Link Setup flowchart figure.
Other impacted counters are included in the flowcharts Figure 20, Figure 17
and Figure 18, which are referenced from the Channel Switching, upswitch
Dedicated to Dedicated flowchart.
A flowchart for the Channel Switching, upswitch Dedicated to Dedicated
scenario is shown in Figure 43 and Figure 44.
62
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Channel Switching Evaluation decides switch
between dedicated channels needed
UL Upswitch
Channel Switching Evaluation decision to switch can be due to:
Throughput (upswitch)
DL Upswitch
Trigged by?
If (DL <= 64)
pmDlUpswitchAttemptLow +
If (64 < DL < 256)
pmDlUpswitchAttemptMedium +
If (256 <= DL <HS)
pmDlUpswitchAttemptHigh +
If (DL = HS)
pmDlUpswitchAttemptHs +
If (UL <= 64)
pmUlUpswitchAttemptLow +
If (64 < UL < 256)
pmUlUpswitchAttemptMedium +
If (256 <= UL < Eul)
pmUlUpswitchAttemptHigh +
If (UL = Eul)
pmUlUpswitchAttemptEul +
pmReconfAttSource +
pmReconfAttTarget +
Check MP Load Control
NO
Load ok?
YES
Admission Control
NBAP/RNSAP: Radio Link
Reconfiguration Prepare
NO
Admission granted?
NBAP/RNSAP: Radio Link
Reconfiguration Ready
YES
NBAP/RNSAP: Radio
Link Reconfiguration Commit
End
Messages Received/Sent
RRC: Transport Channel
Reconfiguration or Radio
Bearer Reconfiguration
Reconfiguration
Successful?
NO
YES
Possible to
revert to old
rate?
pmReconfSuccSource+
pmReconfSuccTarget+
pmNormalReleaseSource+
NO
Send message
YES
NO
Change
Compressed Mode?
Revert to old data rate
RRC Connection Release
End
End
RANAP:
IuRelease
Request
YES
For the new method:
Step the relevant counter
RRC: Transport Channel
Reconfiguration Complete
or Radio Bearer
Reconfiguration Complete
pmCmAttUlSf2 +
pmCmAttUlHls +
pmCmAttDlSf2 +
pmCmAttDlHls +
Receive Message
Reconfiguration
Successful?
NO
YES
Step the relevant counter:
pmNoSuccRbReconfPsIntDch +
pmNoSuccRbReconfPsIntHs +
pmNoSuccRbReconfPsIntEul +
1
Figure 43
C 00 01318H
Channel Switching, upswitch Dedicated to Dedicated Scenario (Part 1)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
63
Performance Statistics - Flowcharts for Counters
1
UL Upswitch
Trigged by?
If (DL <= 64)
pmDlUpswitchSuccessLow +
If (64 < DL < 256)
pmDlUpswitchSuccessMedium +
If (256 <= DL <HS)
pmDlUpswitchSuccessHigh +
If (DL = HS)
pmDlUpswitchSuccessHs +
If (UL <= 64)
pmUlUpswitchSuccessLow +
If (64 < UL < 256)
pmUlUpswitchSuccessMedium +
If (256 <= UL < Eul)
pmUlUpswitchSuccessHigh +
If (UL = Eul)
pmUlUpswitchSuccessEul +
Change
Change/Stop
of Compressed Mode
Method needed?
pmCmStop +
For the new method:
Step the relevant
counter
DL Upswitch
NO
Stop
pmCmSuccUlSf2 +
pmCmSuccUlHls +
pmCmSuccDlSf2 +
pmCmSuccDlHls +
pmCmStop +
pmLevelPsInteractive +/pmLevelPsEulRabEstablish +/pmLevelPsHsAdchRabEstablish +/pmLevelBestPsEulRabEstablish +/pmLevelBestPsHsAdchRabEstablish +/-
End
Figure 44
2.3.4
C 0001457B
Channel Switching, upswitch Dedicated to Dedicated Scenario (Part 2)
Channel Switching, Downswitch Dedicated to Dedicated
This traffic scenario describes the switching between dedicated channels as a
result of a Channel Switching Evaluation decision.
The main counters for this scenario are as follows:
64
•
pmDownSwitchAttempt, pmDownSwitchSuccess
•
pmHsToDchSuccess
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlHls, pmCmSuccDlHls
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoRabDownswSoftCongPsIntEul
•
pmNoSuccRbReconfOrigPsIntDch
•
pmNoSuccRbReconfOrigPsIntHs
•
pmNoSuccRbReconfOrigPsIntEul
•
pmCmStop
•
pmLevelPsInteractive
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
Note:
The counter pmLevelPsInteractive is of type pmLevel<serviceTy
pe>RabEstablish despite a different name syntax. This counter
is mapped to the related counters pmSumPsInteractive and
pmSamplesPsInteractive.
The counter pmLevelEulMcConn also is of type pmLevel<serviceType
>RabEstablish despite a different name syntax. This counter is mapped
to the related counters pmSumEulMcConn and pmSamplesEulMcConn
For a general explanation of counters of type pmLevel<serviceType
>RabEstablish and their related counters, see the explanation in the
Radio Link Setup flowchart figure.
Other impacted counters are included in the flowcharts Figure 20, Figure 17
and Figure 18, which are referenced from the Channel Switching, downswitch
Dedicated to Dedicated flowchart.
A flowchart for the Channel Switching, downswitch Dedicated to Dedicated
scenario is shown in Figure 45.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
65
Performance Statistics - Flowcharts for Counters
Channel Switching Evaluation decides switch
between dedicated channels needed
YES
NBAP/RNSAP: Radio Link
Reconfiguration Prepare
Channel Switching Evaluation decision to switch can be due to:
Coverage (downswitch), Admission, Overload, Soft Handover,
Channel Switching Execution, Serving HS Cell Change,
Soft Congestion
Messages Received/Sent
NBAP/RNSAP: Radio Link
Reconfiguration Ready
NBAP/RNSAP: Radio
Link Reconfiguration Commit
Step the relevant counter:
pmHsToDchAttempt+
pmEulToDchAttempt+
RRC: Transport Channel
Reconfiguration or Radio
Bearer Reconfiguration
pmDownSwitchAttempt +
pmReconfAttSource +
pmReconfAttTarget +
NO
Reconfiguration
Successful?
YES
NO
Possible to
revert to old
rate?
Change
Compressed Mode?
NO
Send message
YES
YES
pmCmAttUlSf2 +
pmCmAttUlHls +
pmCmAttDlSf2 +
pmCmAttDlHls +
For the new method:
Step the relevant counter
RRC: Transport Channel
Reconfiguration Complete
or Radio Bearer
Reconfiguration Complete
RRC Connection Release
End
End
If switched from HS to DCH
pmHsToDchSuccess +
Receive Message
Reconfiguration
Successful?
Revert to old data rate
RANAP:
IuRelease
Request
NO
YES
Step the relevant counter:
pmNoSuccRbReconfOrigPsIntDch +
pmNoSuccRbReconfOrigPsIntHs +
pmNoSuccRbReconfOrigPsIntEul +
pmDownSwitchSuccess +
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
EUL 2ms TTI->10ms
TTI downswitch due to
soft congestion?
NO
YES
pmNoRabDownswSoftCongPsIntEul +
Change
Change/Stop
of Compressed Mode
Method needed?
pmCmStop +
Stop
For the new
method:
Step the
relevant
counter
Figure 45
66
pmCmSuccUlSf2 +
pmCmSuccUlHls +
pmCmSuccDlSf2 +
pmCmSuccDlHls +
NO
pmLevelPsInteractive +/-
pmCmStop +
End
C 0001245L
Channel Switching, downswitch Dedicated to Dedicated Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.3.5
Channel Switching, Common to URA_PCH
This traffic scenario describes the switching of a channel from Common
(Cell_FACH) to URA_PCH. The switch takes place as a result of the expiration
of the timer inactivityTimer.
The counters for this scenario are as follows:
•
pmChSwitchAttemptFachUra
•
pmChSwitchSuccFachUra
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmOutRedirectHsIflsUra
A flowchart for the Channel Switching, Common to URA_PCH scenario is
shown in Figure 46.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
67
Performance Statistics - Flowcharts for Counters
Timer inactivityTimer expires
Choose URA.
The existing URAs stored for the cell
will be used as candidates for the
selection.
UE
DCCH: Physical Channel
Reconfiguration
Messages Sent
pmOutRedirectHsIflsUra +
UE
DCCH: Physical Channel
Reconfiguration Complete
Messages Received
pmChSwitchAttemptFachUra +
pmReconfAttSource +
pmReconfAttTarget +
T_CH_SWITCH_6
expired
YES
NO
PHYSICAL_CHANNEL_RECONFIGURATION_FAILURE
message received
YES
NO
Logical error in
PHYSICAL_CHANNEL_RECONFIGURATION_COMPLETE
YES
NO
URA_UPDATE
received from UE as response to
PHYSICAL_CHANNEL_RECONFIGURATION
YES
NO
pmChSwitchSuccFachUra +
Signalling
Connection Release
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
End
End
C 0001309E
Figure 46
2.3.6
Channel Switching, Common to URA_PCH Scenario
Channel Switching, Dedicated to URA_PCH
This traffic scenario describes the switching of a channel from dedicated to
URA_PCH as a result of a Channel Switching Evaluation decision.
68
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
The counters for this scenario are as follows:
•
pmChSwitchAttemptDchUra
•
pmChSwitchAttemptHsUra
•
pmChSwitchAttemptEulUra
•
pmChSwitchSuccDchUra
•
pmChSwitchSuccHsUra
•
pmChSwitchSuccEulUra
•
pmCmStop
•
pmInterFreqMeasNoCmStop
•
pmInterFreqMeasCmStop
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmOutRedirectHsIflsUra
A flowchart for the Channel Switching, Dedicated to URA_PCH scenario is
shown in Figure 47
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
69
Performance Statistics - Flowcharts for Counters
Channel Switching Evaluation decides
Dedicated-URA_PCH switch needed
Choose URA.
The existing URAs stored for the cell
will be used as candidates for the
selection.
Step the relevant couter(s):
pmChSwitchAttemptDchUra +
pmChSwitchAttemptHsUra +
pmChSwitchAttemptEulUra +
pmReconfAttSource +
pmReconfAttTarget +
UE
DCCH: Physical Channel
Reconfiguration
Messages Sent
pmOutRedirectHsIflsUra +
UE
DCCH: Physical Channel
Reconfiguration Complete
Messages Received
YES
T_RRC_CH_SWITCH_1
expired
NO
RADIO_BEARER_RECONFIGURATION_FAILURE
message received
YES
NO
Logical error in
RADIO_BEARER_RECONFIGURATION_COMPLETE
YES
NO
URA_UPDATE
received from UE as response to
RADIO_BEARER_RECONFIGURATION
YES
Signalling
Connection Release
NO
Step the relevant counter(s):
pmChSwitchSuccDchUra +
pmChSwitchSuccHsUra +
pmChSwitchSuccEulUra +
End
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
(NBAP) RL Deletion
Request
(NBAP) RL Deletion
Response
Messages Sent/Received
Compressed mode active?
YES
pmCmStop +
NO
Meas type
Inter-Frequency?
NO
YES
pmInterFreqMeasNoCmStop +
Meas type
Inter-Frequency?
YES
pmInterFreqMeasCmStop +
NO
pmNoOfRlForNonDriftingUes -
End
C 00 01464C
Figure 47
2.3.7
Channel Switching, Dedicated to URA_PCH Scenario
Channel Switching, URA_PCH to Dedicated
This traffic scenario describes the switching of a channel from URA_PCH to
dedicated as a result of a Channel Switching Evaluation decision.
70
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
The counters for this scenario are as follows:
•
pmChSwitchAttemptUraDch
•
pmChSwitchAttemptUraHs
•
pmChSwitchAttemptUraEul
•
pmChSwitchSuccUraDch
•
pmChSwitchSuccUraHs
•
pmChSwitchSuccUraEul
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
A flowchart for the Channel Switching, URA_PCH to Dedicated scenario is
shown in Figure 48:
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
71
Performance Statistics - Flowcharts for Counters
Cell update received from UE
NO
MP Load Capacity
Request granted?
YES
DC SP
Resource available?
NO
YES
PDR
Resource available?
NO
YES
YES
PDR SP
Load Rejected?
NO
RBS
Successful
Admission Control?
(NBAP) Radio Link
Setup Request
NO
pmChSwitchAttemptUraDch +
pmChSwitchAttemptUraHs +
pmChSwitchAttemptUraEul +
YES
(NBAP) Radio Link
Setup Response
Step
relevant
counter
Messages Sent/Received
UE
(RRC) Cell Update
Confirm
YES
(RRC) Response
message
URA to DCH
switch successful?
Reattempt
on lower rate on
CELL_DCH
NO
YES
Step relevant counters
pmChSwitchAttemptUraDch +
pmChSwitchAttemptUraHs +
pmChSwitchAttemptUraEul +
pmChSwitchSuccUraDch +
pmChSwitchSuccUraHs +
pmChSwitchSuccUraEul +
NO
pmChSwitchAttemptUraDch +
pmChSwitchAttemptUraHs +
pmChSwitchAttemptUraEul +
Step relevant counters
End
2.3.8
NO
End
YES
1
pmReconfAttSource +
pmReconfAttTarget +
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
Figure 48
Possible to
revert to FACH?
C 00 01469E
Channel Switching, URA_PCH to Dedicated Scenario
Channel Switching, URA_PCH to Common
This traffic scenario describes the switching of a channel from URA_PCH
to Common (Cell_FACH). The switch takes place as a result of a UE in the
URA_PCH state sending a CELL UPDATE.
The counters for this scenario are as follows:
72
•
pmChSwitchAttemptUraFach
•
pmChSwitchSuccUraFach
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmReconfAttSource, pmReconfAttTarget
•
pmReconfSuccSource, pmReconfSuccTarget
•
pmNormalReleaseSource
•
pmNoCellUpdateAttMultiCs, pmNoCellUpdateSuccMultiCs
A flowchart for the Channel Switching, URA_PCH to Common scenario is
shown in Figure 49.
1
Cell update received from UE
MP Load
Capacity Request granted?
NO
YES
DC SP
Resource unavailable
YES
NO
PDR
Resource unavailable
YES
NO
PDR SP
Load Rejected
YES
NO
Failure to
establish DCCH/DTCH
NO
DCCH: Cell Update Confirmation
YES
pmChSwitchAttemptUraFach +
Messages Sent/Received
UE
DCCH: Utran Mobility Information
pmChSwitchAttemptUraFach +
pmChSwitchSuccUraFach +
pmReconfAttSource +
pmReconfAttTarget +
pmReconfSuccSource +
pmReconfSuccTarget +
pmNormalReleaseSource +
pmReconfAttSource +
pmReconfAttTarget +
NO
CS call is to
be established ?
YES
pmNoCellUpdateAttMultiCs +
YES
CS call is to
be established ?
NO
pmNoCellUpdateAttMultiCs +
pmNoCellUpdateSuccMultiCs +
End
RRC Connection
Release
End
C 0001310F
Figure 49
Channel Switching, URA_PCH to Common Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
73
Performance Statistics - Flowcharts for Counters
2.3.9
Channel Switching to Idle
This traffic scenario describes the switching from either Common Channel to
Idle, Dedicated Channel to Idle, or PS HS- to Idle.
The main counter for this scenario is pmChSwitchFachIdle (common channel
to idle).
Other impacted counters are included in the flowchart Figure 19, which is
referenced from the Channel Switching to Idle flowchart figure.
A flowchart for the Channel Switching To Idle scenario is shown in Figure 50.
Channel Switching Evaluation decides
switch to Idle needed
Switch
from?
Channel Switching Evaluation decision Common to Idle
OR
Channel Switching Evaluation decision Dedicated to Common,
if parameter AllowSwitchToCommon=0
OR
Congestion triggering Dedicated to Common,
if parameter AllowSwitchtoCommon=0
OR
Channel Switching Evaluation decision HS-DSCH to Idle
From Common Channel
pmChSwitchFachIdle +
From Dedicated Channel
Signaling Connection Release
End
Figure 50
2.4
C 0001131F
Channel Switching To Idle Scenario
System Utilization
This section describes the System Utilization main traffic scenarios as follows:
74
•
Detect Cell Congestion
•
Resolve Congestion Actions
•
Start Compressed Mode
•
Stop Compressed Mode
•
Cell Availability
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.4.1
Detect Cell Congestion
This traffic scenarios describe the detection of congestion in a cell (congestion
= overload).
The main counters for this scenario are as follows:
•
pmSumOfTimesMeasOlDl
•
pmSumOfTimesMeasOlUl
•
pmTotalTimeDlCellCong
•
pmTotalTimeUlCellCong
•
pmTotalTimeEulDchBalancing
•
pmHsdschOverloadDetection
•
pmTotalTimeHsdschOverload
For more information on each counter, refer to Managed Object Model (MOM)
RNC. Other impacted counters are included in Figure 56, Figure 57, and Figure
58 which is referenced from the Detect Cell Congestion flowcharts.
Flowcharts for the detection of Cell Congestion are shown in Figure 51, Figure
52, Figure 53, Figure 54 and Figure 55.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
75
Performance Statistics - Flowcharts for Counters
Not DL congested
RBS
C-RNC
COMMON
MEASUREMENT
REPORT
A TX carrier power measurement
report is received which indicates a power
above the DL Congestion threshold
Message received
pmSumOfTimesMeasOIDI +
A TX carrier power measurement
report is received.
Start 1 sec. timer
Measurement
report received?
Yes
Message received
C-RNC
The TX carrier power
measurement report
indicate a power
below the Congestion
threshold
No
Yes
No
COMMON
RBS
MEASUREMENT
REPORT
Still DL Congestion?
No
Timer expired?
Not DL congested
Yes
pmTotalTimeDlCellCong+
C 00 01121C
Figure 51
76
Detect Cell DL Congestion Scenario 1 (Non-HS Capable Cell)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
DL not overload
or HS overload
RBS
Non-HS power measurement
C-RNC
COMMON
report (event driven) is received
MEASUREMENT
which indicates DL DCH overload
REPORT
pmSumOfTimesMeasOIDI +
Start 1 sec. timer
No
Non-HS measurement
report (event driven)
is received?
Yes
Still DL DCH
Overload?
Yes
No
No
Timer expired?
Yes
pmTotalTimeDlCellCong +
C 00 01349A
Figure 52
Detect Cell DL Congestion Scenario 2 (HS Capable Cell)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
77
Performance Statistics - Flowcharts for Counters
DL DCH not overload or
DL DCH overload
Non-HS power and HS required
power measurement
report (periodic) are received
which indicates HS overload
COMMON
MEASUREMENT
REPORT
pmHsdschOverloadDetection +
Start 1 sec. timer
No
Non-HS power and
HS required power
measurement report
(periodic) are
received?
Yes
Still HS
Overload?
Yes
No
No
Timer expired?
Yes
pmTotalTimeHsdschOverload +
C 00 01350A
Figure 53
78
Detect Cell DL Congestion Scenario 3 (HS Capable Cell)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Not UL congested
RBS
C-RNC
COMMON
MEASUREMENT
REPORT
A UL RTWP measurement
report is received which
indicate an RTWP above
the UL Congestion threshold
Message received
pmSumOfTimesMeasOlUl+
An UL RTWP measurement
report is received.
Start 1 sec. timer
Measurement
report received?
Yes
Message received
C-RNC
The UL RTWP
measurement report
indicate a power
below the Congestion
threshold
No
Yes
No
COMMON
RBS
MEASUREMENT
REPORT
Still UL Congestion?
No
Timer expired?
Not UL congested
Yes
pmTotalTimeUlCellCong +
C 0001159D
Figure 54
Detect Cell UL Congestion Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
79
Performance Statistics - Flowcharts for Counters
Not EUL cell congested
RBS
C-RNC
COMMON
MEASUREMENT
REPORT
Measurement report is received
indicating EUL cell congestion
Message received
Measurement
report is received.
Start 1 sec. timer
Measurement
report received?
Yes
Message received
C-RNC
COMMON
RBS
MEASUREMENT
REPORT
No
Measurement report
indicating no
EUL cell congestion
Yes
No
Still EUL cell
congestion?
No
Timer expired?
Not EUL cell congested
Yes
pmTotalTimeEulDchBalancing +
C 0001474A
Figure 55
2.4.2
Detect EUL Cell Congestion Scenario
Resolve DL Congestion Actions
This traffic scenario describes the actions taken by congestion control when
congestion is detected in a cell.
The main counters for this scenario are as follows:
80
•
pmNoOfSwDownNgCong
•
pmNoOfSwDownEulCong
•
pmNoOfIurSwDownNgCong
•
pmNoOfTermSpeechCong
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoOfIurTermSpeechCong
•
pmNoOfTermCsCong
•
pmNoOfIurTermCsCong
•
pmNoOfSwDownHsCong
•
pmNoOfIurTermHsCong
Other impacted counters are included in the following flowcharts which are
referenced from the Resolve Congestion Actions flowchart:
•
Figure 20, Figure 42
A flowchart for the resolving of congestion actions scenario is shown in Figure
56, Figure 57 and Figure 58.
Detect DL DCH Overload
or HS Overload
Start timer tmInitialG
YES
Non-guaranteed
RABs in SRNC to target
is carried?
Target non-guraranteed RABs in SRNC for
release action traffic according to priority
The counter is
stepped an amount
equal to the number
of targeted (non-Iur)
RLs
NO
DL DCH
Overload
HS
Overload
pmNoOfSwDownNgCong +
pmNoOfSwDownEulCong +
Downswitch to
CELL_FACH is
initiated for UEs
associated with
RLs targeted for
downswitch
Channel Switching Downswitching
Start timer
tmCongActionNg
tmCongActionNg expires
C 0001215F
Figure 56
Resolve Congestion Actions Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
81
Performance Statistics - Flowcharts for Counters
DL DCH Overload
Yes
No
tmInitialG still running?
No
terminate
Guaranteed RABs or
RLs in DRNC (excluding HS)
to target is
carried?
Yes
Target guaranteed RABs and RLs in
DRNC (excluding HS) for release action
according to priority
Congested
Cell controlled by serving
RNC (non-Iur case)?
No
Yes
pmNoOfTermSpeechCong+
pmNoOfTermCsCong+
RAB Release
Congested Cell
controlled by drifting RNC
(Iur case)?
No
Yes
pmNoOfIurTermSpeechCong+
pmNoOfIurTermCsCong+
pmNoOfIurSwDownNgCong+
This implies that
associated users
will be released by
the S-RNC.
RL FAILURE INDICATION
sent to S-RNC
Start timer tmCongAction
tmCongAction timeout
C0001216G
Figure 57
82
Resolve Congestion Actions Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
HS Overload
Yes
No
tmInitialG still running?
No
terminate
Guaranteed RABs or
RLs in DRNC (including guaranteed
service on HS) to target
is carried?
Yes
Target guaranteed RABs and RLs in DRNC
(including guaranteed service on HS)
for release action according to priority
Congested
Cell controlled by serving
RNC (non-Iur case)?
No
Yes
pmNoOfTermSpeechCong+
pmNoOfTermCsCong+
RAB Release
The counter is stepped
an amount equal
to the number of
targeted guaranteed
RABs on HS
pmNoOfSwDownHsCong+
Congested Cell
controlled by drifting RNC
(Iur case)?
No
Yes
pmNoOfIurTermSpeechCong+
pmNoOfIurTermCsCong+
pmNoOfIurSwDownNgCong+
The counter is stepped
an amount equal to
the number of
targeted guaranteed
RABs on HS
This implies that
associated users
will be released by
the S-RNC.
pmNoOfIurTermHsCong+
RL FAILURE INDICATION
sent to S-RNC
Start timer tmCongAction
tmCongAction timeout
C0001351C
Figure 58
2.4.3
Resolve Congestion Actions Scenario (Part C)
Start Compressed Mode
This traffic scenario describes the starting of compressed mode.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
83
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlHls, pmCmSuccDlHls
Other impacted counters are included in the following flowcharts:
•
Figure 17 and Figure 18.
A flowchart for the Start Compressed Mode scenario is shown in Figure 59.
84
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Decision to Start InterFrequency or IRAT
Measurements requiring Compressed Mode
Compressed Mode Start
Select:
- Method, HLS or SF/2 as defined for RAB state
- Directions, UL/DL as required by UE capabilities
Cells in SRNC?
YES
If Admission denied
terminate the procedure.
Admission Control
NO
NO
Code Allocation/usage
SF2 in DL?
YES
Cells in DRNC?
YES
Prepare compressed mode
in RBS
(NBAP) Radio Link
Reconfiguration Prepare
RBS
Prepare compressed mode
in DRNC
(RNSAP) Radio Link
Reconfiguration Prepare
DRNC
NO
(RNSAP/NBAP) Radio Link Reconfiguration Ready
NBAP or RNSAP Response Message
Successful RL
Reconfiguration Preparation
Procedure?
NO
RBS/DRNC
Send RL Reconfiguration Cancel and terminate procedure.
YES
CM started
in UL ?
YES
pmCmAttUl<method> +
One of: pmCmAttUISf2, pmCmAttUIHIs,
stepped when cell in SRNC
pmCmAttDl<method> +
One of: pmCmAttDISf2, pmCmAttDIHIs
stepped when cell in SRNC
NO
CM started
in DL ?
YES
NO
(RRC) Physical Channel Reconfiguration
(RRC) Physical Channel Reconfiguration Complete
Prepare compressed mode in UE
Successful
preparation?
NO
UE
If no response from UE before procedure timer expires - Release connection.
For other errors - Send RL Reconf Cancel, terminate procedure.
YES
Cells in SRNC?
YES
Commit configuration
(NBAP) Radio Link
Reconfiguration Commit
RBS
NO
CM started
in UL ?
YES
pmCmSuccUl<method> +
Step pmCmSuccUISf2 or
pmCmSuccUIHIs
pmCmSuccDl<method> +
Step pmCmSuccDISf2 or
pmCmSuccDIHIs
NO
CM started
in DL ?
YES
NO
Cells in DRNC?
YES
Commit configuration
(RNSAP) Radio Link
Reconfiguration Commit
DRNC
NO
Activate configuration in UE
(RRC) Measurement Control
UE
End Procedure
C 00 01099D
Figure 59
Start of Compressed Mode Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
85
Performance Statistics - Flowcharts for Counters
2.4.4
Stop Compressed Mode
This traffic scenario describes the stopping of compressed mode.
The main counters for this scenario are as follows:
•
pmCmStop
Other impacted counters are included in the following flowcharts:
•
Figure 17 and Figure 18.
A flowchart for the Stop Compressed Mode scenario is shown in Figure 60.
Decision to Stop InterFrequency or IRAT
Measurements using Compressed Mode
Compressed Mode Stop
YES
Cells in SRNC?
NO
Release resources
Admission Control
Order stop of compressed mode
(NBAP) Compressed
Mode Command
RBS
(RNSAP) Compressed
Mode Command
DRNC
pmCmStop +
YES
Cells in DRNC?
Order stop of compressed mode
NO
Order stop of compressed
mode in UE
(RRC) Measurement Control
UE
End Procedure
C 00 01100A
Figure 60
2.4.5
Stop Compressed Mode Scenario
Cell Availability
This traffic scenario describes the scenarios for cell downtime caused by
manual and automatic intervention.
The main counters for this scenario are as follows:
86
•
pmCellDowntimeMan, pmCellDowntimeAuto
•
pmHsDowntimeMan, pmHsDowntimeAuto
•
pmEulDowntimeMan, pmEulDowntimeAuto
•
pmMbmsDowntimeMan, pmMbmsDowntimeAuto
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
A flowchart for the Cell Availability scenario is shown in Figure 61, Figure 62,
Figure 63, and Figure 64.
Check Cell availability
YES
Calling
procedures
Manual Lock
Cell/Channel
Automatic Lock
Cell/Channel
Cell Admin
State = locked?
Manual Unlock
Cell/Channel
NO
YES
Add
Cell/Channel
Any of
RACH/FACH/PCH
Admin State =
locked?
Delete
Cell/Channel
Reconfigure
Cell/Channel
NO
Start incrementing
pmCellDowntimeMan
if not already incrementing
Increment once per second
Stop incrementing
pmCellDowntimeAuto
if incrementing ongoing
Stop incrementing
pmCellDowntimeMan
if incrementing ongoing
Cell Op
State = disabled?
Operational
State Change of
Cell/Channel due to
failure or recovery
YES
NO
Any of
RACH/FACH/PCH
Op State =
disabled?
NO
Stop incrementing
pmCellDowntimeAuto if
incrementing ongoing
YES
Note: A cell and it´s
common channels are
seen as a single entity for
the purpose of setting the
downtime counters
Start incrementing
pmCellDowntimeAuto if
not already incrementing
Increment once per
second
End check Cell
availability
C 0001098D
Figure 61
Cell Availability Scenario Part A
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
87
Performance Statistics - Flowcharts for Counters
Check HSDPA
availability
Calling
procedures
Manual Lock Hsdsch
Automatic Lock Hsdsch
Is
incrementing of
pmCellDowntimeMan
ongoing?
YES
Manual Unlock Hsdsch
NO
Add Hsdsch
YES
Is Hsdsch
Admin State = locked?
Delete Hsdsch
NO
Start incrementing
pmHsDowntimeMan
if not already incrementing
Increment once per second
Stop incrementing
pmHsDowntimeMan
if incrementing ongoing
Stop incrementing
pmHsDowntimeAuto
if incrementing ongoing
Is
incrementing of
pmCellDowntimeAuto
ongoing?
Reconfigure Hsdsch
OperationalState
Change of Hsdsch
due to failure or
recovery
YES
Note: The procedure
Check HSDPA
availability can be called
by procedure check Cell
Availability.
NO
Is
Hsdsch Op State =
disabled?
NO
Stop incrementing
pmHsDowntimeAuto if
incrementing ongoing
YES
Start incrementing
pmHsDowntimeAuto
if not already incrementing
Increment once per second
End check Hsdsch
availability
C 0001200B
Figure 62
88
Cell Availability Scenario Part B
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Check MBMS
availability
Calling
procedures
Manual Lock MbmsCch
Automatic Lock MbmsCch
Is
incrementing of
pmCellDowntimeMan
ongoing?
YES
Add MbmsCch
NO
Delete MbmsCch
YES
Is MbmsCch
Admin State = locked?
Reconfigure MbmsCch
NO
Start incrementing
pmMbmsDowntimeMan
if not already incrementing
Increment once per second
Stop incrementing
pmMbmsDowntimeMan
if incrementing ongoing
Stop incrementing
pmMbmsDowntimeAuto
if incrementing ongoing
Is
incrementing of
pmCellDowntimeAuto
ongoing?
OperationalState
Change of MbmsCch
due to failure or
recovery
YES
Note: The procedure
Check MBMS
availability can be called
by procedure check Cell
Availability.
NO
Is
MbmsCch Op State =
disabled?
NO
Stop incrementing
pmMbmsDowntimeAuto if
incrementing ongoing
YES
Start incrementing
pmMbmsDowntimeAuto
if not already incrementing
Increment once per second
End check MBMS
availability
C 00 01352A
Figure 63
Cell Availability Scenario Part C
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
89
Performance Statistics - Flowcharts for Counters
Check Eul
availability
Calling
procedures
Manual Lock Eul
Automatic Lock Eul
Is
incrementing of
pmCellDowntimeMan
ongoing?
YES
Manual Unlock Eul
NO
Add Eul
Is
incrementing of
pmHsDowntimeMan
ongoing?
YES
Delete Eul
Reconfigure Eul
NO
YES
Is Eul
Admin State = locked?
OperationalState
Change of Eul
due to failure or
recovery
NO
Start incrementing
pmEulDowntimeMan
if not already incrementing
Increment once per second
Stop incrementing
pmEulDowntimeMan
if incrementing ongoing
Stop incrementing
pmEulDowntimeAuto
if incrementing ongoing
Is
incrementing of
pmCellDowntimeAuto
ongoing?
Note: The procedure
Check Eul availability
can be called by
procedure check
HSDPA Availability.
YES
NO
Is
incrementing of
pmHsDowntimeAuto
ongoing?
YES
NO
Is
Eul Op State =
disabled?
YES
NO
Stop incrementing
pmEulDowntimeAuto if
incrementing ongoing
Start incrementing
pmEulDowntimeAuto
if not already incrementing
Increment once per second
End check Eul
availability
C 0001314B
Figure 64
90
Cell Availability Scenario Part D
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.5
Mobility
This section describes the Mobility main traffic scenarios as follows:
•
Interfrequency Handover
•
Soft Handover Addition
•
Soft Handover Deletion
•
Soft Handover Replacement
•
Inter-Radio Access Technology Handover, Outgoing
•
Inter-Radio Access Technology Handover, Incoming
•
Inter-Radio Access Technology Cell Change, Outgoing
•
Inter-Radio Access Technology Cell Change, Incoming
•
Inter-Radio Access Technology Cell Reselection, Incoming
•
Cell Update
•
URA Update
•
RAN Information Management Update
•
HS Cell Change Counters
•
CN Hard Handover on CS RAB, Source-RNC
•
CN Hard Handover on CS RAB, Target-RNC
•
CN Hard Handover on PS RAB, Source-RNC
•
CN Hard Handover on PS RAB, Target-RNC
•
UE Positioning
If the RNC in Pool feature is used, the calls that are drifting internally within
the cluster, between cells belonging to different RNC nodes do not transfer
call control handling between the RNC nodes as long as the calls are in DCH
state. When a call that was initially setup in RNC cluster member A, and
so has its call control handling in RNC A, moves over to a cell controlled by
another RNC cluster member B, the call control for that call still remains with
RNC A. This includes also the stepping of counters belonging to RNC B, for
example, UtranCell counters belonging to RNC B. The pm counter collection
mechanism that runs every ROP period is extended in RNC in Pool. The
mechanism also transfers pm counter data automatically over the Iux interface
to the correct owner RNC where it is then aggregated together and output into
that RNC ROP file. This is handled automatically within the normal scheme
of pm counter data collection that occurs every ROP period. As such, the
Operator does not need to be concerned with the details of the process.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
91
Performance Statistics - Flowcharts for Counters
2.5.1
Procedures used during Mobility
This section describes procedures used during Mobility main traffic scenarios
as follows:
2.5.1.1
•
Radio Link Setup
•
Radio Link Addition
•
Radio Link Deletion
•
Radio Link Reconfiguration
Radio Link Setup
This traffic scenario describes the setup of a radio link on request from various
traffic scenarios including RAB Release, RAB Establishment, and RRC
Connection Setup.
The main counters for this scenario are as follows:
92
•
pmNoOfRlForDriftingUes
•
pmNoOfRlForNonDriftingUes
•
pmLevelCs12RabEstablish, pmLevelBestCs12RabEstablish
•
pmLevelCs57RabEstablish, pmLevelBestCs57RabEstablish
•
pmLevelCs64RabEstablish, pmLevelBestCs64RabEstablish
•
pmLevelAmr4750RabEstablish, pmLevelBestAmr4750RabEstablish
•
pmLevelAmr5900RabEstablish, pmLevelBestAmr5900RabEstablish
•
pmLevelAmr7950RabEstablish, pmLevelBestAmr7950RabEstablish
•
pmLevelAmr12200RabEstablish, pmLevelBestAmr12200RabEstablish
•
pmLevelAmrNbMmRabEstablish, pmLevelBestAmrNbMmRabEstablish
•
pmLevelAmrWbRabEstablish, pmLevelBestAmrWbRabEstablish
•
pmLevelPsStreamHsRabEst, pmLevelBestPsStreamHsRabEst
•
pmLevelPsStr64Ps8RabEstablish, pmLevelBestPsStr64Ps8RabEstablish
•
pmLevelPsEulRabEstablish, pmLevelBestPsEulRabEstablish
•
pmLevelPsHsAdchRabEstablish, pmLevelBestPsHsAdchRabEstablish
•
pmLevelBestPsEulRabEstCpc
•
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmLevelPsInteractive
•
pmLevelSrbOnly34, pmLevelBestSrbOnly34
•
pmLevelSrbOnlyHs, pmLevelBestSrbOnlyHs
•
pmLevelSrbOnlyEul, pmLevelBestSrbOnlyEul
•
pmLevelUesWith1Rls1RlInActSet
•
pmLevelUesWith1Rls2RlInActSet
•
pmLevelUesWith1Rls3RlInActSet
•
pmLevelUesWith2Rls2RlInActSet
•
pmLevelUesWith2Rls3RlInActSet
•
pmLevelUesWith2Rls4RlInActSet
•
pmLevelUesWith3Rls3RlInActSet
•
pmLevelUesWith3Rls4RlInActSet
•
pmLevelUesWith4Rls4RlInActSet
•
pmLevelMocnCsRabEstablish
•
pmLevelMocnCsRabEstCnOp
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
93
Performance Statistics - Flowcharts for Counters
Note:
The internal counters pmLevel<serviceType>RabEstablish, pmLevelBe
st<serviceType>RabEstablish and pmLevelUesWithXRlsYRlInActSet
are not visible in the output Statistics ROP file. They are mapped to the
following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceTy
pe>RabEstablishs
•
pmSumBest<serviceType>RabEstablish and pmSamplesBest<ser
viceType>RabEstablishs
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counters pmLevelPsInteractive, pmLevelEulMcConn,
pmLevelRrcOnlyEstablish pmLevelBestRrcOnlyEstablish,
pmLevelSrbOnly34, pmLevelBestSrbOnly34, pmLevelSrbOnlyHs,
pmLevelBestSrbOnlyHs, pmLevelSrbOnlyEul, pmLevelBestSrbOnlyEu
l, pmMocnCsRabEstCnOp and pmLevelMocnCsRabEstablish also
are of type pmLevel<serviceType>RabEstablish despite a different
name syntax. These particular counters are mapped to the following
related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
•
pmSumEulMcConn and pmSamplesEulMcConn
•
pmSumRrcOnlyEstablish and pmSamplesRrcOnlyEstablish
•
pmSumBestRrcOnlyEstablish, pmSamplesBestRrcOnlyEstablish
•
pmSumSrbOnly34, pmSamplesSrbOnly34
•
pmSumBestSrbOnly34, pmSamplesBestSrbOnly34
•
pmSumSrbOnlyHs, pmSamplesSrbOnlyHs
•
pmSumBestSrbOnlyHs, pmSamplesBestSrbOnlyHs
•
pmSumSrbOnlyEul, pmSamplesSrbOnlyEul
•
pmSumBestSrbOnlyEul, pmSamplesBestSrbOnlyEul
•
pmSumMocnCsRabEstablish, pmSamplesMocnCsRabEstablish
•
pmSumMocnCsRabEstCnOp, pmSamplesMocnCsRabEstCnOp
The pmLevelUesWithXXRlsYYRlInActSet counters are mapped to the related
pmSumUesWith<x>Rls<y>RlInActSet and pmSamplesUesWith<x>Rls<y>RlIn
ActSet counters. The following nine combinations of <x> and <y> are possible
for the pmSumUesWith<x>Rls<y>RlInActSet counter:
•
94
pmSumUesWith1Rls1RlInActSet
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmSumUesWith1Rls2RlInActSet
•
pmSumUesWith1Rls3RlInActSet
•
pmSumUesWith2Rls2RlInActSet
•
pmSumUesWith2Rls3RlInActSet
•
pmSumUesWith2Rls4RlInActSet
•
pmSumUesWith3Rls3RlInActSet
•
pmSumUesWith3Rls4RlInActSet
•
pmSumUesWith4Rls4RlInActSet
For more information on each counter, refer to Managed Object Model (MOM)
RNC. Other impacted counters are included in the following flowcharts, which
are referenced from the Radio Link Setup flowchart:
•
Figure 17, Figure 18, Figure 4, Figure 2, Figure 23, Figure 12, Figure 73,
Figure 75, Figure 69, Figure 72, Figure 88, Figure 89.
A flowchart for the Radio Link Setup scenario is shown in Figure 65.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
95
Performance Statistics - Flowcharts for Counters
Radio Link Setup triggered by
RAB Release
Radio Link Setup triggered by
RAB Establishment
Radio Link Setup triggered by
RRC Connection Establishment
Back to calling procedure:
unsuccessful Radio Link Setup
NO
Admission Control
Trigger = RNSAP
message?
Radio Link Setup triggered by
channel switching
NO
Radio Link Setup triggered by
soft handover
Successful?
Radio Link Setup triggered by
inter-frequency handover
Code allocation/usage
Radio Link Setup triggered by
inter-RAT handover from GSM
Successful?
YES
YES
(RNSAP)
RADIO
LINK
SETUP
FAILURE
Allocate
channelization
code
NO
Admission Control
YES
(RNSAP) RADIO LINK
SETUP REQUEST or
RADIO LINK ADDITION
REQUEST
Radio Link Setup triggered by
RNSAP message
(NBAP) RADIO LINK SETUP RESPONSE/FAILURE
(RNSAP) RADIO LINK SETUP RESPONSE or
RADIO LINK ADDITION RESPONSE
Send Response message to SRNC
pmNoOfRlForDriftingUes +
Back to calling procedure:
successful Radio Link Setup
YES
RNC acting
as DRNC
Send Radio Link
Setup Request
Radio
Link Setup
Response received
before the expiration of
the supervision
timer?
(RNSAP)
RADIO
LINK
SETUP
REQUEST
NO
Resource
release
Channelization code
deallocation
YES
Trigger = RNSAP
message?
NO
Trigger = RRC
Connection
Establishment?
YES
NO
pmLevel<RAB>establish +
pmLevelUesWith(x+1)Rls(y+1)RlInActSet +
pmNoOfRlForNonDriftingUes +
If x and y not equal to 0: pmLevelNoOfUesWithxRlsyRlInActSet C 00 01103D
Figure 65
2.5.1.2
Radio Link Setup Scenario
Radio Link Addition
This traffic scenario describes the addition of a radio link to an existing radio
connection on request from various traffic scenarios including inter-frequency
handover and soft or softer handover.
The main counters for this scenario are as follows:
•
96
pmNoOfRlForDriftingUes
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoOfRlForNonDriftingUes
•
pmLevelCs12RabEstablish, pmLevelBestCs12RabEstablish
•
pmLevelCs57RabEstablish, pmLevelBestCs57RabEstablish
•
pmLevelCs64RabEstablish, pmLevelBestCs64RabEstablish
•
pmLevelAmr4750RabEstablish, pmLevelBestAmr4750RabEstablish
•
pmLevelAmr5900RabEstablish, pmLevelBestAmr5900RabEstablish
•
pmLevelAmr7950RabEstablish, pmLevelBestAmr7950RabEstablish
•
pmLevelAmr12200RabEstablish, pmLevelBestAmr12200RabEstablish
•
pmLevelAmrNbMmRabEstablish, pmLevelBestAmrNbMmRabEstablish
•
pmLevelAmrWbRabEstablish, pmLevelBestAmrWbRabEstablish
•
pmLevelPsStr64Ps8RabEstablish, pmLevelBestPsStr64Ps8RabEstablish
•
pmLevelPsEulRabEstablish, pmLevelBestPsEulRabEstablish
•
pmLevelPsHsAdchRabEstablish, pmLevelBestPsHsAdchRabEstablish
•
pmLevelBestPsEulRabEstCpc
•
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish
•
pmLevelPsInteractive
•
pmLevelSrbOnly34, pmLevelBestSrbOnly34
•
pmLevelSrbOnlyHs, pmLevelBestSrbOnlyHs
•
pmLevelSrbOnlyEul, pmLevelBestSrbOnlyEul
•
pmLevelUesWith1Rls1RlInActSet
•
pmLevelUesWith1Rls2RlInActSet
•
pmLevelUesWith1Rls3RlInActSet
•
pmLevelUesWith2Rls2RlInActSet
•
pmLevelUesWith2Rls3RlInActSet
•
pmLevelUesWith2Rls4RlInActSet
•
pmLevelUesWith3Rls3RlInActSet
•
pmLevelUesWith3Rls4RlInActSet
•
pmLevelUesWith4Rls4RlInActSet
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
97
Performance Statistics - Flowcharts for Counters
•
pmLevelMocnCsRabEstablish
•
pmLevelMocnCsRabEstCnOp
Note:
The internal counters pmLevel<serviceType>RabEstablish, pmLevelBe
st<serviceType>RabEstablish and pmLevelUesWithXRlsYRlInActSet
are not visible in the output Statistics ROP file. They are mapped to the
following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceT
ype>RabEstablish
•
pmSumBest<serviceType>RabEstablish and pmSamplesBest<ser
viceType>RabEstablish
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counters pmLevelPsInteractive, pmLevelEulMcConn,
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish,
pmLevelSrbOnly34, pmLevelBestSrbOnly34, pmLevelSrbOnlyHs,
pmLevelBestSrbOnlyHs, pmLevelSrbOnlyEul pmLevelBestSrbOnlyEul,
pmLevelMocnCsRabEstCnOp and pmLevelMocnCsRabEstablish also
are of type pmLevel<serviceType>RabEstablish despite a different
name syntax. These particular counters are mapped to the following
related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
•
pmSumEulMcConn and pmSamplesEulMcConn
•
pmSumRrcOnlyEstablishand pmSamplesRrcOnlyEstablish
•
pmSumBestRrcOnlyEstablish, pmSamplesBestRrcOnlyEstablish
•
pmSumSrbOnly34, pmSamplesSrbOnly34
•
pmSumBestSrbOnly34, pmSamplesBestSrbOnly34
•
pmSumSrbOnlyHs, pmSamplesSrbOnlyHs
•
pmSumBestSrbOnlyHs, pmSamplesBestSrbOnlyHs
•
pmSumSrbOnlyEul, pmSamplesSrbOnlyEul
•
pmSumBestSrbOnlyEul, pmSamplesBestSrbOnlyEul
•
pmSumMocnCsRabEstablish, pmSamplesMocnCsRabEstablish
•
pmSumMocnCsRabEstCnOp, pmSamplesMocnCsRabEstCnOp
For a general explanation of counters of type pmLevel<serviceType>R
abEstablish and pmLevelUesWithXRlsYRlInActSet and their related
counters, see the explanation in the Radio Link Setup flowchart figure.
98
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Other impacted counters are included in the following flowcharts that are
referenced from the Radio Link Addition flowchart:
•
Figure 17, Figure 18, Figure 73, Figure 75, Figure 69, Figure 72.
A flowchart for the Radio Link Addition scenario is shown in Figure 66.
Radio Link Addition triggered
by RNSAP message
Radio Link Addition triggered
by inter-frequency handover
Radio Link Addition triggered
by soft/softer handover
Back to calling procedure:
unsuccessful Radio Link Addition
NO
Admission Control
Trigger = RNSAP
message?
Successful?
NO
YES
(RNSAP)
RADIO
LINK
ADDITION
FAILURE
Allocate
channelization
code
Code allocation/usage
Successful?
YES
NO
Admission Control
YES
Send Radio Link
Addition Request
Radio
Link Addition
Response received
before the expiration of
the supervision
timer?
(NBAP) RADIO LINK ADDITION
RESPONSE/FAILURE
RNC acting
as DRNC
pmNoOfRlForDriftingUes +
Send RNSAP response message
Back to calling procedure:
successful Radio Link Addition
(RNSAP)
RADIO
LINK
ADDITION
REQUEST
NO
Resource
release
Channelization code
deallocation
YES
YES
(RNSAP)
RADIO
LINK
ADDITION
RESPONSE
pmLevelUesWith1Rls1RlInActSet +
pmLevelUesWithxRlsyRlInActSet pmLevelUesWithxRls(y+1)RlInActSet +
Trigger = RNSAP
message?
NO
pmNoOfRlForNonDriftingUes +
pmLevel<RAB>establish +
Handover type?
IFHO
SOHO
C 00 01104E
Figure 66
2.5.1.3
Radio Link Addition Scenario
Radio Link Deletion
This traffic scenario describes the deletion of a radio link from a connection
when requested by a traffic scenario.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
99
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
100
•
pmNoOfRlForDriftingUes
•
pmNoOfRlForNonDriftingUes
•
pmLevelCs12RabEstablish, pmLevelBestCs12RabEstablish
•
pmLevelCs57RabEstablish, pmLevelBestCs57RabEstablish
•
pmLevelCs64RabEstablish, pmLevelBestCs64RabEstablish
•
pmLevelAmr4750RabEstablish, pmLevelBestAmr4750RabEstablish
•
pmLevelAmr5900RabEstablish, pmLevelBestAmr5900RabEstablish
•
pmLevelAmr7950RabEstablish, pmLevelBestAmr7950RabEstablish
•
pmLevelAmr12200RabEstablish, pmLevelBestAmr12200RabEstablish
•
pmLevelAmrNbMmRabEstablish, pmLevelBestAmrNbMmRabEstablish
•
pmLevelAmrWbRabEstablish, pmLevelBestAmrWbRabEstablish
•
pmLevelPsStreamHsRabEst, pmLevelBestPsStreamHsRabEst
•
pmLevelPsStr64Ps8RabEstablish, pmLevelBestPsStr64Ps8RabEstablish
•
pmLevelPsEulRabEstablish, pmLevelBestPsEulRabEstablish
•
pmLevelPsHsAdchRabEstablish, pmLevelBestPsHsAdchRabEstablish
•
pmLevelBestPsEulRabEstCpc
•
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish
•
pmLevelPsInteractive
•
pmLevelSrbOnly34, pmLevelBestSrbOnly34
•
pmLevelSrbOnlyHs, pmLevelBestSrbOnlyHs
•
pmLevelSrbOnlyEul, pmLevelBestSrbOnlyEul
•
pmLevelUesWith1Rls1RlInActSet
•
pmLevelUesWith1Rls2RlInActSet
•
pmLevelUesWith1Rls3RlInActSet
•
pmLevelUesWith2Rls2RlInActSet
•
pmLevelUesWith2Rls3RlInActSet
•
pmLevelUesWith2Rls4RlInActSet
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmLevelUesWith3Rls3RlInActSet
•
pmLevelUesWith3Rls4RlInActSet
•
pmLevelUesWith4Rls4RlInActSet
•
pmLevelMocnCsRabEstablish
•
pmLevelMocnCsRabEstCnOp
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
101
Performance Statistics - Flowcharts for Counters
Note:
The internal counters pmLevel<serviceType>RabEstablish, pmLevelBe
st<serviceType>RabEstablish and pmLevelUesWithXRlsYRlInActSet
are not visible in the output Statistics ROP file. They are mapped to the
following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceT
ype>RabEstablish
•
pmSumBest<serviceType>RabEstablish and pmSamplesBest<ser
viceType>RabEstablish
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counters pmLevelPsInteractive, pmLevelEulMcConn,
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish,
pmLevelSrbOnly34, pmLevelBestSrbOnly34, pmLevelSrbOnlyHs,
pmLevelBestSrbOnlyHs, pmLevelSrbOnlyEul, pmLevelBestSrbOnlyE
ul, pmLevelMocnCsRabEstCnOp and pmLevelMocnCsRabEstablish
also are of type pmLevel<serviceType>RabEstablish despite a different
name syntax. These particular counters are mapped to the following
related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
•
pmSumEulMcConn and pmSamplesEulMcConn
•
pmSumRrcOnlyEstablishand pmSamplesRrcOnlyEstablish
•
pmSumBestRrcOnlyEstablish, pmSamplesBestRrcOnlyEstablish
•
pmSumSrbOnly34, pmSamplesSrbOnly34
•
pmSumBestSrbOnly34, pmSamplesBestSrbOnly34
•
pmSumSrbOnlyHs, pmSamplesSrbOnlyHs
•
pmSumBestSrbOnlyHs, pmSamplesBestSrbOnlyHs
•
pmSumSrbOnlyEul, pmSamplesSrbOnlyEul
•
pmSumBestSrbOnlyEul, pmSamplesBestSrbOnlyEul
•
pmSumMocnCsRabEstablish, pmSamplesMocnCsRabEstablish
•
pmSumMocnCsRabEstCnOp, pmSamplesMocnCsRabEstCnOp
For a general explanation of counters of type pmLevel<serviceType>R
abEstablish and pmLevelUesWithXRlsYRlInActSet and their related
counters, see the explanation in the Radio Link Setup flowchart figure.
102
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Other impacted counters are included in the following flowcharts, which are
referenced from the Radio Link Deletion flowchart:
•
Figure 17, Figure 18, Figure 23, Figure 12, Figure 74, Figure 75, Figure
69, Figure 72.
A flowchart for the Radio Link Deletion scenario is shown in Figure 67.
Radio Link Deletion triggered
by Channel Switching
Radio Link Deletion triggered
by RAB Release
Radio Link Deletion triggered
by SoHo
Radio Link Deletion triggered
by RAB Establishment
Send Radio Link
Deletion Request
Radio Link Deletion triggered
by IFHo
(RNSAP) RADIO LINK
DELETION REQUEST
Wait for Radio Link Deletion
Response or supervision
timer expiry
Radio Link Deletion triggered
by IRAT Ho to GSM
Radio Link Deletion triggered
by IRAT cell change
Admission Control
Radio Link Deletion triggered
by RNSAP message
Channelization code
deallocation
Radio Link Deletion triggered
by RAB Connection Release
(RNSAP) RADIO LINK
DELETION RESPONSE
Resource release
RNC acting
as DRNC
pmNoOfRlForDriftingUes Send RNSAP response message
YES
(RNSAP) RADIO LINK
DELETION RESPONSE
Trigger = RNSAP
message?
NO
Handover type?
IFHO
SOHO
NO
Last RL within
the RLS?
pmLevelUesWithxRls(y-1)RlInActSet +
YES
If x and y different from 1: pmLevelUesWith(x-1)Rls(y-1)RlInActSet +
pmLevelUesWithxRlsyRlInActSet pmNoOfRlForNonDriftingUes pmLevel<RAB>establish -
Return to calling procedure:
successful Radio Link Deletion
C 00 01105D
Figure 67
2.5.1.4
Radio Link Deletion Scenario
Radio Link Reconfiguration
This traffic scenario describes the reconfiguration of a radio link on request
from a traffic procedure.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
103
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
104
•
pmLevelCs12RabEstablish, pmLevelBestCs12RabEstablish
•
pmLevelCs57RabEstablish, pmLevelBestCs57RabEstablish
•
pmLevelCs64RabEstablish, pmLevelBestCs64RabEstablish
•
pmLevelAmr4750RabEstablish, pmLevelBestAmr4750RabEstablish
•
pmLevelAmr5900RabEstablish, pmLevelBestAmr5900RabEstablish
•
pmLevelAmr7950RabEstablish, pmLevelBestAmr7950RabEstablish
•
pmLevelAmr12200RabEstablish, pmLevelBestAmr12200RabEstablish
•
pmLevelAmrNbMmRabEstablish, pmLevelBestAmrNbMmRabEstablish
•
pmLevelAmrWbRabEstablish, pmLevelBestAmrWbRabEstablish
•
pmLevelPsStreamHsRabEst, pmLevelBestPsStreamHsRabEst
•
pmLevelPsStr64Ps8RabEstablish, pmLevelBestPsStr64Ps8RabEstablish
•
pmLevelPsEulRabEstablish, pmLevelBestPsEulRabEstablish
•
pmLevelPsHsAdchRabEstablish, pmLevelBestPsHsAdchRabEstablish
•
pmLevelBestPsEulRabEstCpc
•
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish
•
pmLevelSrbOnly34, pmLevelBestSrbOnly34
•
pmLevelSrbOnlyHs, pmLevelBestSrbOnlyHs
•
pmLevelSrbOnlyEul, pmLevelBestSrbOnlyEul
•
pmLevelPsInteractive
•
pmLevelMocnCsRabEstablish
•
pmLevelMocnCsRabEstCnOp
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Note:
The internal counters pmLevel<serviceType>RabEstablish, pmLevelBe
st<serviceType>RabEstablish and pmLevelUesWithXRlsYRlInActSet
are not visible in the output Statistics ROP file. They are mapped to the
following related counters:
•
pmSum<serviceType>RabEstablish and pmSamples<serviceT
ype>RabEstablish
•
pmSumBest<serviceType>RabEstablish and pmSamplesBest<ser
viceType>RabEstablish
•
pmSumUesWithXRlsYRlInActSet and pmSamplesUesWithXRlsY
RlInActSet
The counters pmLevelPsInteractive, pmLevelEulMcConn,
pmLevelRrcOnlyEstablish, pmLevelBestRrcOnlyEstablish,
pmLevelSrbOnly34, pmLevelBestSrbOnly34, pmLevelSrbOnlyHs,
pmLevelBestSrbOnlyHs, pmLevelSrbOnlyEul, pmLevelBestSrbOnlyE
ul, pmLevelMocnCsRabEstCnOp and pmLevelMocnCsRabEstablish
also are of type pmLevel<serviceType>RabEstablish despite a different
name syntax. These particular counters are mapped to the following
related counters:
•
pmSumPsInteractive and pmSamplesPsInteractive
•
pmSumEulMcConn and pmSamplesEulMcConn
•
pmSumRrcOnlyEstablishand pmSamplesRrcOnlyEstablish
•
pmSumBestRrcOnlyEstablish, pmSamplesBestRrcOnlyEstablish
•
pmSumSrbOnly34, pmSamplesSrbOnly34
•
pmSumBestSrbOnly34, pmSamplesBestSrbOnly34
•
pmSumSrbOnlyHs, pmSamplesSrbOnlyHs
•
pmSumBestSrbOnlyHs, pmSamplesBestSrbOnlyHs
•
pmSumSrbOnlyEul, pmSamplesSrbOnlyEul
•
pmSumBestSrbOnlyEul, pmSamplesBestSrbOnlyEul
•
pmSumMocnCsRabEstablish, pmSamplesMocnCsRabEstablish
•
pmSumMocnCsRabEstCnOp, pmSamplesMocnCsRabEstCnOp
For a general explanation of counters of type pmLevel<serviceType>R
abEstablish and pmLevelUesWithXRlsYRlInActSet and their related
counters, see the explanation in the Radio Link Setup flowchart figure.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
105
Performance Statistics - Flowcharts for Counters
Other impacted counters are included in the following flowcharts, which are
referenced from the Radio Link Reconfiguration flowchart:
•
Figure 17, Figure 18, Figure 23, Figure 12.
A flowchart for the Radio Link Reconfiguration scenario is shown in Figure 68.
Radio Link Reconfiguration
triggered by RNSAP
message
Radio Link Reconfiguration
triggered by Channel
Switching
Radio Link Reconfiguration
triggered by RAB
Estblishment
Radio Link Reconfiguration
triggered by RAB Release
Admission Control
Back to calling
procedure: unsuccessful
Radio Link Setup
NO
Trigger= RNSAP
message?
Successful?
YES
NO
Message sent
YES
Message sent
RNSAP: Radio Link
Reconfiguration Failure
Code allocation/usage
Allocate channelization code
NBAP: Radio Link
Reconfiguration Ready
or
NBAP: Radio Link
Reconfiguration Failure
Successful?
NO
Admission Control
YES
Message sent
NBAP: Radio Link
Reconfiguration Prepare
resource
resorce release
Radio Link Reconfiguration
NO
Channelization code deallocation
Ready received before the expiration
of the supervision timer
YES
RNC acting as DRNC
RNSAP: Radio Link
Reconfiguration Commit
YES
RNSAP: Radio Link
Reconfiguration ready
Message sent
Trigger=RNSAP message?
NO
Message sent
Back to calling
procedure: successful
Radio Lnk Reconfiguration
End Radio Link
Reconfiguration
In case of an
RNC acting as a
DRNC this message
is preceded by a
RNSAP: Radio
Link Reconfiguration
Commit message
C 0001118F
Figure 68
106
Radio Link Reconfiguration Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.5.2
Interfrequency Handover
This traffic scenario describes successful and failed inter-frequency handover.
The main counters for this scenario are as follows:
•
pmAttNonBlindInterFreqHoCsSpeech12, pmSuccNonBlindInterFreqHoC
sSpeech12
•
pmFailNonBlindInterFreqHoRevertCsSpeech12, pmFailNonBlindInterFreq
HoFailRevertCsSpeech12
•
pmAttNonBlindInterFreqHoCsConversational, pmSuccNonBlindInterFreq
HoCsConversational
•
pmFailNonBlindInterFreqHoRevertCsConversational, pmFailNonBlindInter
FreqHoFailRevertCsConversational
•
pmAttNonBlindInterFreqHoPsInteractiveLess64, pmSuccNonBlindInterFr
eqHoPsInteractiveLess64
•
pmFailNonBlindInterFreqHoRevertPsInteractiveLess64, pmFailNonBlindInt
erFreqHoFailRevertPsInteractiveLess64
•
pmAttNonBlindInterFreqHoPsInteractiveGreater64, pmSuccNonBlindIn
terFreqHoPsInteractiveGreater64
•
pmFailNonBlindInterFreqHoRevertPsInteractiveGreater64,
pmFailNonBlindInterFreqHoFailRevertPsInteractiveGreater64
•
pmAttNonBlindInterFreqHoStreamingOther, pmSuccNonBlindInterFreqHo
StreamingOther
•
pmFailNonBlindInterFreqHoRevertStreamingOther, pmFailNonBlindInter
FreqHoFailRevertStreamingOther
•
pmAttNonBlindIfhoPsIntHs, pmSuccNonBlindIfhoPsIntHs
•
pmFailNonBlindIfhoRevPsIntHs, pmFailNonBlindIfhoFailRevPsIntHs
•
pmAttNonBlindIfhoPsIntEul, pmSuccNonBlindIfhoPsIntEul
•
pmFailNonBlindIfhoRevPsIntEul, pmFailNonBlindIfhoFailRevPsIntEul
•
pmAttNonBlindIfhoPsStrHs, pmSuccNonBlindIfhoPsStrHs
•
pmFailNonBlindIfhoRevPsStrHs, pmFailNonBlindIfhoFailRevPsStrHs
•
pmAttLoadbasedIfho, pmSuccLoadbasedIfho
•
pmFailLoadbasedIfhoFailRev, pmFailLoadbasedIfhoRev
•
pmNoIncomingHsHardHoAttempt, pmNoIncomingHsHardHoSuccess
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
107
Performance Statistics - Flowcharts for Counters
•
pmNoOutgoingHsHardHoAttempt, pmNoOutgoingHsHardHoSuccess
•
pmNoIncomingPsStreamHsHhoAttempt, pmNoIncomingPsStreamHsH
hoSuccess
•
pmNoOutgoingPsStreamHsHhoAttempt, pmNoOutgoingPsStreamHsH
hoSuccess
•
pmNoIncomingEulHardHoAttempt, pmNoIncomingEulHardHoSuccess
•
pmNoOutgoingEulHardHoAttempt, pmNoOutgoingEulHardHoSuccess
•
pmEnableHsHhoAttempt, pmEnableHsHhoSuccess
•
pmEnableEulHhoAttempt, pmEnableEulHhoSuccess
•
pmOutHsIflsHhoAtt, pmOutHsIflsHhoSucc
•
pmInHsIflsHhoAtt, pmInHsIflsHhoSucc
•
pmOutDchIflsHhoAtt, pmOutDchIflsHhoSucc
•
pmInDchIflsHhoAtt, pmInDchIflsHhoSucc
•
pmNoEulHardHoReturnOldChSource, pmNoEulHardHoReturnOldChTa
rget
•
pmNoPsStreamHsHhoReturnOldSource, pmNoPsStreamHsHhoReturnOl
dTarget
•
pmNoHsHardHoReturnOldChSource, pmNoHsHardHoReturnOldChTarget
•
pmNoTimesIfhoRlAddToActSet, pmNoTimesIfhoCellFailAddToActSet
•
pmInterFreqMeasCmStart, pmInterFreqMeasNoCmStart
•
pmInterFreqMeasCmStop, pmInterFreqMeasNoCmStop
•
pmNoRlDeniedAdm
•
pmIratHoGsmMeasCmStop, pmIratHoGsmMeasNoCmStop
•
pmInterfFreqMeasCmStop, pmInterFreqMeasNoCmStop
Other impacted counters are included in the following flowcharts, which are
referenced from the inter-frequency Handover flowchart:
•
Figure 59, Figure 66, Figure 65
A flowchart for the inter-frequency Handover scenario is shown in Figure 69,
Figure 70, Figure 71 andFigure 72.
108
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Decision by Handover Evaluation to
start Inter-Frequency and/or IRAT HO measurements
UE requires
compressed mode?
UE
YES
Start
Compressed Mode
NO
(RRC)
Measurement
Control
Start IFHO and/or IRAT measurements
(event 2b and/or 3a)
pmInterFreqMeasCmStart +
pmIratHoGsmMeasCmStart +
One or both of these counters
are stepped depending on which
CM patters are started.
pmInterFreqMeasNoCmStart +
pmIratHoGsmMeasNoCmStart +
Handover Evaluation
Decision to stop
IFHO or IRAT measurements
Decision to start
IFHO execution
Decision to start
IRAT HO execution
2
Execute IRAT HO
1
C 00 01315F
Figure 69
Interfrequency Handover Scenario Part A
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
109
Performance Statistics - Flowcharts for Counters
2
UE
(RRC)
Measurement
Control
Initiate Inter Frequency HO
RAB on HS?
YES
new H-RNTI allocation
NO
Stay on current
frequency and
configuration
NO
Successful
H-RNTI Allocation?
YES
PDU size evaluation
Which handover case?
Intra RNC, Intra RBS
Intra RNC, Inter RBS
Radio Link Addition
Radio Link Setup
Inter RNC, Intra RBS
Inter RNC, Inter RBS
DRNC
(RNSAP) Radio Link
Addition Request
DRNC
Setup Link in DRNC
Add Link in DRNC
NO
Successful RL
Addition/Setup?
(RNSAP) Radio Link
Setup Request
NO
Intra RNC?
YES
Handover
Evaluation
Yes
pmNoTimesIfhoRlAddToActSet +
pmNoTimesIfhoCellFailAddToActSet+
pmAttNonBlindInterFreqHo<RAB Type> + **
or
if triggered by interfrequency
load based handover:
pmAttLoadbasedIfho +
NO
Admission
failure?
Yes
pmNoRlDeniedAdm+
PDU size need to
be changeed?
NO
YES
Reconfigure UE to new frequency
Reconfigure UE to new frequency
(RRC) Radio Bearer Reconfiguration
(RRC) Physical Channel Reconfiguration
**
Inter Frequency Handover Scenario Part B
Figure 70
110
UE
UE
RAB Type is one of the defined
groups, counted for the best cell
in active set, if that is located in SRNC
C 00 01595A
Interfrequency Handover Scenario - Start IFHO
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
1
YES
CM active?
Stop
Compressed Mode
NO
YES
IF measurement
active ?
NO
YES
Stop IF Measurements
IF measurement
active ?
Stop IF Measurements
pmInterfFreqMeasNoCmStop +
NO
pmInterfFreqMeasCmStop +
YES
IRAT measurement
active ?
NO
YES
Stop IRAT Measurements
IRAT measurement
active ?
Stop IRAT Measurements
NO
Message sent
(RRC)
Measurement
Control
UE
C 00 01596A
End
Figure 71
Interfrequency Handover Scenario - Stop Measurements
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
111
Performance Statistics - Flowcharts for Counters
Inter Frequency Handover Scenario Part B
Successful RRC
Procedure?
NO
YES
pmFailNonBlindInterFreqHo
FailRevert<RAB Type> + **
or
pmFailLoadbasedIfhoFailRev+
YES
NO
if HS
Hard Handover
YES
NO
NO
Release
Connection
YES
Release Connection
NO
pmEnableHsHhoSuccess +
pmEnableHsHhoAttempt +
or
pmEnableHsHhoAttempt + *
pmEnableHsHhoSuccess + *
pmEnableEulHhoAttempt + *
pmEnableEulHhoSuccess + *
or
if triggered by HS
interfrequency loadsharing:
pmOutHsIflsHhoAtt +
pmOutHsIflsHhoSucc +
pmInHsIflsHhoAtt +
pmInHsIflsHhoSucc +
pmSuccNonBlindInterFreqHo
<RAB Type> + **
or
if triggered by interfrequency
load based handover:
pmSuccLoadbasedIfho +
if triggered by DCH
interfrequency loadsharing:
pmOutDchIflsHhoAtt +
pmOutDchIflsHhoSucc +
pmInDchIflsHhoAtt +
pmInDchIflsHhoSucc +
Failure
Cause Equals Physical
Channel or Radio
Bearer Failure?
NO
RRC Timeout?
YES
NO
PS RAB Established?
YES
pmNoHsHardHoReturnOldChSource +
pmNoHsHardHoReturnOldChTarget +
or
pmNoPsStreamHsHhoReturnOldSource +
pmNoPsStreamHsHhoReturnOldTarget +
PS RAB Established?
YES
pmNoIncomingHsHardHoAttempt +
pmNoIncomingHsHardHoSuccess +
pmNoOutgoingHsHardHoAttempt +
pmNoOutgoingHsHardHoSuccess +
or
pmNoIncomingPsStreamHsHhoAttempt +
pmNoIncomingPsStreamHsHhoSuccess +
pmNoOutgoingPsStreamHsHhoAttempt +
pmNoOutgoingPsStreamHsHhoSuccess +
Eul Enabled?
If Attempted
HS Hard Handover
Eul Enabled?
NO
YES
pmNoEulHardHoReturnOldChSource +
pmNoEulHardHoReturnOldChTarget +
NO
YES
pmNoIncomingEulHardHoAttempt +
pmNoIncomingEulHardHoSuccess +
pmNoOutgoingEulHardHoAttempt +
pmNoOutgoingEulHardHoSuccess +
pmFailNonBlindInterFreqHo
Revert<RAB Type> + **
or
pmFailLoadbasedIfhoRev +
Target Radio Links are Deleted
in SRNC, Flowchart RL Deletion
and in DRNC via RNSAP Procedure
Source Radio Links are Deleted
in SRNC, Flowchart RL Deletion
and in DRNC via RNSAP Procedure
**
Release old H-RNTI
RAB Type is one of the defined
groups, counted for the best cell
in active set, if that is located in SRNC
End Procedure
C 00 01316J
Figure 72
2.5.3
Interfrequency Handover Scenario Part B
Soft Handover - Radio Link Addition case
This traffic scenario describes the addition of a cell to the Active Set of the UE.
112
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
The main counters for this scenario are as follows:
•
pmNoTimesRlAddToActSet
•
pmNoTimesCellFailAddToActSet
•
pmNoOfRlForDriftingUesPerDrnc
•
pmNoRlDeniedAdm
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttDlHls, pmCmSuccDlHls
•
Per UtranRelation:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccess
BestCellSpeech
•
Per UtranCell:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBest
CellSpeech
•
Per UtranRelation:pmRlAddAttemptsBestCellCsConvers,
pmRlAddSuccessBestCellCsConvers
•
Per UtranCell:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccess
BestCellCsConvers
•
Per UtranRelation:pmRlAddAttemptsBestCellPacketLow,
pmRlAddSuccessBestCellPacketLow
•
Per UtranCell:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccess
BestCellPacketLow
•
Per UtranRelation:pmRlAddAttemptsBestCellPacketHigh,
pmRlAddSuccessBestCellPacketHigh
•
Per UtranCell:pmRlAddAttemptsBestCellPacketHigh, pmRlAddSuccess
BestCellPacketHigh
•
Per UtranRelation:pmRlAddAttemptsBestCellStream, pmRlAddSuccess
BestCellStream
•
Per UtranCell:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBest
CellStream
•
Per UtranRelation:pmRlAddAttemptsBestCellStandAlone,
pmRlAddSuccessBestCellStandAlone
•
Per UtranCell:pmRlAddAttemptsBestCellStandAlone, pmRlAddSuccess
BestCellStandAlone
•
Per UtranCell:pmNoSysRelSpeechSoHo for best cell
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
113
Performance Statistics - Flowcharts for Counters
Other impacted counters are included in the following flowcharts, which are
referenced from the Soft Handover - Radio Link Addition flowchart:
•
Figure 65, Figure 66.
A flowchart for the Soft Handover Addition scenario is shown in Figure 73.
114
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Decision of Ho algorithms to
add a cell to the AS of the UE
If best cell in the AS controlled by SRNS
and if cell relation defined from the best cell in the AS to the cell to be
added: pmRlAddAttemptsBestCell<Connection Type> +
Which addition case?
Intra-RNS, RLS addition
Intra-RNS, RL addition
Radio Link Setup
Radio Link Addition
Inter-RNS, Iur connection
not yet established
Inter-RNS, Iur connection
already established
Send Radio Link
Setup Request
Send Radio Link
Addition Request
This will trigger a Radio Link
Setup or Addition procedure
in the RNC acting as DRNC
(RNSAP) RADIO LINK SETUP REQUEST
(RNSAP) RADIO LINK ADDITION REQUEST
(RNSAP) RADIO LINK SETUP/ADDITION RESPONSE
or RADIO LINK SETUP/ADDITION FAILURE
Successful RL
Establishment?
NO
Admission
failure?
YES
NO
NO
YES
pmNoTimesCellFailAddToActSet+
Send Active Set Update
if CPM ongoing:
pmCmAtt<direction><method>
(RRC)
ACTIVE
SET
UPDATE
If relOnRej=true*
& RL for speech
YES
Active
pmNoSysRelSpeechSoHo +
Set Update
NO
Complete received before
the expiration of the
supervision
timer
pmNoTimesCellFailAddToActSet+
(RRC) ACTIVE SET
UPDATE COMPLETE
or ACTIVE SET
UPDATE FAILURE
YES
NO
(RRC)
ACTIVE
SET
UPDATE
*) The connection is released because
the candidate cell is at least releaseConnOffset
better than the best cell in current active set.
2.5.4
YES
Send Active Set Update
Active
Set Update
Complete received before
the expiration of the
supervision
timer
(RRC) ACTIVE SET
UPDATE COMPLETE
or ACTIVE SET
UPDATE FAILURE
YES
NO
Either release the call, trigger a downpmRlAddSuccessBestCell<Connection Type> switch
+
, trigger Radio Link Deletion for the radio link
If cell relation defined from the best cell in the AS to
that one has tried to add or send Active
the cell to be added:
Set Update to restore the active set of
pmRlAddSuccessBestCell<Connection Type> +
the UE previous to the failure depending
For the cell to be added: pmNoTimesRlAddToActSet + on what failed and on the quality of the
If CPM ongoing: pmCmSucc<direction><method> +
cell to be added
Figure 73
Radio
LinkSetup/ Addition
Response received before
the expiration of the
supervision
timer
pmNoRlDeniedAdm+
pmNoOfRlForDriftingUesPerDrnc+
End
C 00 01106G
Soft Handover - Radio Link Addition Scenario
Soft Handover - Radio Link Deletion case
This traffic scenario describes the removal of a cell from the Active Set of a UE.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
115
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmNoOfRlForDriftingUesPerDrnc
•
pmNoTimesRlDelFrActSet
Other impacted counters are included in the Figure 67 flowchart, which is
referenced from the Soft Handover - Radio Link Deletion flowchart
A flowchart for the Soft Handover Deletion scenario is shown in Figure 74.
Decision of Ho algorithms to
remove a cell from the AS of the UE
(RRC) ACTIVE
SET UPDATE
(RRC) ACTIVE SET
UPDATE COMPLETE
or ACTIVE SET
UPDATE FAILURE
Send Active Set Update
Active
Set Update
Complete received
before supervision
timer expiry?
NO
Either release the call, or do
nothing (consider that the active
set remains the same)
depending on whether the
supervision timer expired or
whether an Active Set Update
Failure was received
YES
Which deletion case?
Intra-RNS
Radio Link Deletion
Inter-RNS
Send Radio Link
Deletion Request
(RNSAP) RADIO LINK
DELETION REQUEST
Wait for Radio Link
Deletion Response or
supervision timer expiry
(RNSAP) RADIO LINK
DELETION RESPONSE
pmNoOfRlForDriftingUesPerDrnc -
pmNoTimesRlDelFrActSet +
End
C 00 01107D
Figure 74
2.5.5
Soft Handover - Radio Link Deletion Scenario
Soft Handover - Radio Link Replacement case
This traffic scenario describes the replacement of a cell in the Active Set of a
UE.
The main counters for this scenario are as follows:
116
•
pmNoTimesRlRepInActSet
•
pmNoOfRlForDriftingUesPerDrnc
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
•
pmNoRlDeniedAdm
•
pmCmAttUlSf2, pmCmSuccUlSf2
•
pmCmAttUlHls, pmCmSuccUlHls
•
pmCmAttDlSf2, pmCmSuccDlSf2
•
pmCmAttDlHls, pmCmSuccDlHls
•
Per UtranRelation:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccess
BestCellSpeech
•
Per UtranCell:pmRlAddAttemptsBestCellSpeech, pmRlAddSuccessBest
CellSpeech
•
Per UtranRelation:pmRlAddAttemptsBestCellCsConvers,
pmRlAddSuccessBestCellCsConvers
•
Per UtranCell:pmRlAddAttemptsBestCellCsConvers, pmRlAddSuccess
BestCellCsConvers
•
Per UtranRelation:pmRlAddAttemptsBestCellPacketLow,
pmRlAddSuccessBestCellPacketLow
•
Per UtranCell:pmRlAddAttemptsBestCellPacketLow, pmRlAddSuccess
BestCellPacketLow
•
Per UtranRelation:pmRlAddAttemptsBestCellPacketHigh,
pmRlAddSuccessBestCellPacketHigh
•
Per UtranCell:pmRlAddAttemptsBestCellPacketHigh, pmRlAddSuccess
BestCellPacketHigh
•
Per UtranRelation:pmRlAddAttemptsBestCellStream, pmRlAddSuccess
BestCellStream
•
Per UtranCell:pmRlAddAttemptsBestCellStream, pmRlAddSuccessBest
CellStream
•
Per UtranRelation:pmRlAddAttemptsBestCellStandAlone,
pmRlAddSuccessBestCellStandAlone
•
Per UtranCell:pmRlAddAttemptsBestCellStandAlone, pmRlAddSuccess
BestCellStandAlone
•
Per UtranCell:pmNoSysRelSpeechSoHo for the best cell
Other impacted counters are included in the following flowcharts, which are
referenced from the Soft Handover - Radio Link Replacement flowchart:
•
Figure 65, Figure 66, Figure 67
A flowchart for the Soft Handover Replacement scenario is shown in Figure 75.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
117
Performance Statistics - Flowcharts for Counters
Decision of Ho algorithms to replace a cell to the AS of the UE
If best cell in the AS controlled by SRNS
and if cell relation defined from the best cell in the AS to the cell to be
added: pmRlAddAttemptsBestCell<Connection Type> +
Which addition case?
Intra-RNS, RLS addition
Radio Link Setup
Intra-RNS, RL addition
Radio Link Addition
Inter-RNS, Iur connection
not yet established
Inter-RNS, Iur connection
already established
Send Radio Link
Setup Request
Send Radio Link
Addition Request
This will trigger a Radio Link
Setup or Addition procedure
in the RNC acting as DRNC
(RNSAP) RADIO LINK SETUP REQUEST
(RNSAP) RADIO LINK ADDITION REQUEST
(RNSAP) RADIO LINK SETUP/ADDITION RESPONSE
or RADIO LINK SETUP/ADDITION FAILURE
Successful RL
establishment?
NO
Admission
failure?
NO
YES
pmNoRlDeniedAdm+
Radio Link
Setup/ Addition
Response received before
supervision timer
expiry?
pmNoTimesCellFailAddToActSet +
YES
NO
(RRC)
ACTIVE
SET
UPDATE
Send Active Set Update
if CPM ongoing:
pmCmAtt<direction><method>
Active
Set Update
Complete received
before supervision
timer expiry?
(RRC) ACTIVE SET
UPDATE COMPLETE
or ACTIVE SET
UPDATE FAILURE
If relOnRej=true*
&
RL for speech
NO
(RRC)
ACTIVE
SET
UPDATE
YES
NO
pmNoSysRelSpeechSoHo +
NO
pmNoTimesCellFailAddToActSet +
YES
pmRlAddSuccessBestCell<Connection Type> +
If cell relation defined from the best cell in the AS to
the cell to be added:
pmRlAddSuccessBestCell<Connection Type> +
For the cell to be added: pmNoTimesRlAddToActSet +
If CPM ongoing: pmCmSucc<direction><method> +
(RRC) ACTIVE SET
UPDATE COMPLETE
or ACTIVE SET
UPDATE FAILURE
Either release the call, trigger a downswitch, trigger radio link deletion for the
radio link that one has tried to add or
send Active Set Update to restore the
active set of the UE previous to the failure
depending on what failed and on the
quality of the cell to be added
YES
Send Active Set Update
Active
Set Update
Complete received
before supervision
timer expiry?
YES
pmNoOfRlForDriftingUesPerDrnc+
Which deletion case?
Intra-RNS
Radio Link Deletion
pmNoTimesRlRepInActSet +
(incremented for the cell that is deleted
Inter-RNS
(RNSAP) RADIO LINK
DELETION REQUEST
(RNSAP) RADIO LINK
DELETION RESPONSE
Send Radio Link Deletion Request
Wait for Radio Link Deletion Response
or supervision timer expiry
pmNoOfRlForDriftingUesPerDrnc -
*) The connection is released because
the candidate cell is at least releaseConnOffset
better than the best cell in current active set.
Figure 75
118
End
C 00 01108F
Soft Handover - Radio Link Replacement Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.5.6
Inter-Radio Access Technology Handover, Outgoing
This traffic scenario describes inter-radio access technology handover attempts
from UTRAN to GSM or GAN.
The main counters for this scenario are as follows:
•
pmNoDirRetryAtt, pmNoDirRetrySuccess
•
pmNoAttOutIratHoSpeech, pmNoSuccessOutIratHoSpeech
•
pmNoAttOutIratHoCs57, pmNoSuccessOutIratHoCs57
•
pmNoAttOutIratHoMulti, pmNoSuccessOutIratHoMulti
•
pmNoAttOutIratHoStandalone, pmNoSuccessOutIratHoStandalone
•
pmNoAttOutSbHoSpeech, pmNoSuccessOutSbHoSpeech
•
pmAttLbhoSpeech, pmSuccLbhoSpeech
•
pmNoFailOutIratHoSpeechReturnOldChPhyChFail, pmNoFailOutIratHoS
peechReturnOldChNotPhyChFail
•
pmNoFailOutIratHoCs57ReturnOldChPhyChFail, pmNoFailOutIratHoCs57
ReturnOldChNotPhyChFail
•
pmNoFailOutIratHoMultiReturnOldChPhyChFail, pmNoFailOutIratHoMulti
ReturnOldChNotPhyChFail
•
pmNoFailOutIratHoStandaloneReturnOldChPhyChFail, pmNoFailOutIratH
oStandaloneReturnOldChNotPhyChFail
•
pmNoFailOutSbHoSpeechReturnOldChPhyChFail, pmNoFailOutSbHoS
peechReturnOldChNotPhyChFail
•
pmFailLbhoSpeechPhyChFailReturn, pmFailLbhoSpeechNotPhyChFail
•
pmNoFailOutIratHoSpeechGsmFailure
•
pmNoFailOutIratHoCs57GsmFailure
•
pmNoFailOutIratHoMultiGsmFailure
•
pmNoFailOutIratHoStandaloneGsmFailure
•
pmNoFailOutSbHoSpeechGsmFailure
•
pmFailLbhoSpeechGsmFailure
•
pmNoFailOutIratHoSpeechUeRejection
•
pmNoFailOutIratHoCs57UeRejection
•
pmNoFailOutIratHoMultiUeRejection
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
119
Performance Statistics - Flowcharts for Counters
•
pmNoFailOutIratHoStandaloneUeRejection
•
pmNoFailOutSbHoSpeechUeRejection
•
pmFailLbhoSpeechUeReject
•
pmNoSuccessSbHo
•
pmNoOutGanIratHoReqSpeech, pmNoOutGanIratHoReqMulti
•
pmNoOutGanIratHoAttSpeech, pmNoOutGanIratHoAttMulti
•
pmNoOutGanIratHoSuccSpeech, pmNoOutGanIratHoSuccMulti
•
pmLbhoGsmAttemptCnOp, pmLbhoGsmSuccessCnOp, pmLbhoGsmRe
leaseCnOp
Other impacted counters are included in the following flowcharts, which are
referenced from the Inter-Radio Access Technology Handover, Outgoing
flowchart:
•
Figure 12, Figure 19
A flowchart for the Inter-Radio Access Technology Handover, Outgoing
scenario is shown in Figure 76, Figure 77, Figure 78, Figure 79 and Figure 80.
Triggered by the Soft Congestion
pmLbhoGsmAttemptCnOp +
Filtered monitored set of
GSM cells is empty?
YES
NO
Compressed Mode
supervision timer for
LBHO expired ?
YES
pmLbhoGsmReleaseCnOp +
NO
4
End
C 00 01601A
Figure 76
120
Soft Congestion Triggering of Inter-Radio Access Technology
Handover
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Triggered by Handover Evaluation function for
mobility reasons, based on coverage or service
CN
Triggered by RAB Establishment function for capacity
reasons, i.e. Load Sharing via Directed Retry
4
Send RANAP Relocation Required
message and start timer
RANAP Relocation
RNC
Required
Trigger?
Connection Quality
(Coverage)
CN
Service
RANAP Relocation
Command
Relocation
Command received before
timer expires?
RANAP Relocation
Preparation Failure
UTRAN Command
pmNoOutGanIratHoReq<RAB>+
NO
Message
received or timer
expired?
YES
Send Handover from
UTRAN Command
message and start timer
RNC
Relocation
Preparation
Failure
received
Timer expired
YES
NO
UE
pmNoDirRetryAtt+
RNC
Relocation
Command
Failure?
RRC Handover from
GAN HO
RNC
OR
CN
Load
Directed Retry
(Capacity)
RANAP Relocation
CN
Cancel
RANAP Relocation
CN
Cancel Acknowledge
Send Relocation Cancel
and receive Relocation
Cancel Acknowledge
RNC
RNC
Trigger?
Connection Quality
(Coverage)
3
Directed Retry
(Capacity)
Load
Service
GAN HO
pmNoAttOutSbHoSpeech+
CN
RANAP Iu Release
Command
RNC
RBS
NBAP Radio Link
Restore Indication
RNC
UE
RRC Handover from
UTRAN Failure
pmNoOutGanIratHoAtt<RAB>+
pmAttLbhoSpeech+
pmNoAttOutIratHo<RAB>+
Iu Release Command
with cause ’Normal Release’ or ’Successful
relocation’ received before
timer expires?
YES
RNC
NO
Message
received or timer
expired?
Trigger?
Connection Quality
(Coverage)
Service
pmNoSuccessOutIratHo<RAB>+
Directed Retry
(Capacity)
Load
pmSuccLbhoSpeech+
Timer expired
GAN HO
pmNoOutGanIratHoSucc<RAB>+
Handover from UTRAN
Failure
pmLbhoGsmSuccessCnOp+
pmNoSuccessOutSbHoSpeech+
1
pmNoDirRetrySuccess+
pmNoSuccessSbHo+
Signalling
Connection
Handling
Figure 77
Release
resources
C 00 01134F
Inter-Radio Access Technology Handover, Outgoing Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
121
Performance Statistics - Flowcharts for Counters
1
Trigger?
Connection Quality
(Coverage)
Directed Retry
(Capacity)
Load
Service
Failure cause?
Physical channel failure
Configuration unacceptable
pmFailLbhoSpeechPhyChFailReturn +
Any other cause than
Physical Channel failure or
Configuration unacceptable
pmFailLbhoSpeechNotPhyChFail +
pmFailLbhoSpeechUeReject +
Failure cause?
Any other cause than
Physical Channel failure or
Configuration unacceptable
Configuration unacceptable
Physical channel
failure
pmNoFailOutSbHoSpeechReturnOldChPhyChFail +
pmNoFailOutSbHoSpeechReturnOldChNotPhyChFail +
pmNoFailOutSbHoSpeechUeRejection +
Failure cause?
Physical channel failure
Configuration unacceptable
pmNoFailOutIratHo<RAB>ReturnOldChPhyChFail +
Any other cause than
Physical Channel failure or
Configuration unacceptable
pmNoFailOutIratHo<RAB>ReturnOldChNotPhyChFail +
pmNoFailOutIratHo<RAB>UeRejection +
2
C 00 01135C
Figure 78
122
Inter-Radio Access Technology Handover, Outgoing Scenario (Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2
CN
RANAP Relocation
Cancel
RNC
CN
RANAP Relocation
Cancel Acknowledge
RNC
Send Relocation Cancel and
receive Relocation Cancel
Acknowledge
Trigger?
Directed Retry
(Capacity)
Connection Quality
(Coverage)
Service
Load
RAB
Establishment
Wait for another
Radio Bearer
Assignment Request
from CS CN
Handover Evaluation
C 00 01450A
Figure 79
Inter-Radio Access Technology Handover, Outgoing Scenario (Part C)
3
Directed Retry
(Capacity)
Trigger?
Connection Quality
(Coverage)
Service
Load
pmNoFailOutSbHoSpeechGsmFailure+
pmNoFailOutIratHo<RAB>GsmFailure+
RAB
Establishment
Wait for another
Radio Bearer
Assignment
Request from CS CN
pmFailLbhoSpeechGsmFailure+
Handover Evaluation
C 00 01449A
Figure 80
2.5.7
Inter-Radio Access Technology Handover, Outgoing Scenario (Part D)
Inter-Radio Access Technology Handover, Incoming
This section describes the Inter-Radio Access Technology Handover attempt
from GSM to UTRAN and from LTE to UTRAN.
2.5.7.1
Inter-Radio Access Technology Handover from GSM or LTE(SRVCC-CS)
This traffic scenario describes the Inter-Radio Access Technology Handover
attempt from GSM or LTE(SRVCC-CS) to UTRAN.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
123
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmNoInCsIratHoAtt
•
pmNoInCsIratHoSuccess
•
pmNoInCsIratHoAdmFail
•
pmOffloadAttCs, pmOffloadSuccCs
•
pmOffloadDedicPrioEutra, pmMocnDedicPrioEutra
Other impacted counters are included in the following flowcharts, which are
referenced from the Inter-Radio Access Technology Handover from GSM,
Incoming flowchart:
•
Figure 65, Figure 19
A flowchart for the scenario is shown in Figure 81.
124
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
IRAT Handover is triggered by
RANAP Relocation Request message
pmNoInCsIratHoAtt +
Offload indication
is detected in Relocation
Request message?
NO
YES
pmOffloadAttCs +
Check for logical error,
target cell not found,
CS Data Service Handover
not supported
Successful
resource allocation?
NO
YES
Radio Link Setup
YES
NO
Successful
setup?
Admission
reject?
NO
YES
CN
RANAP
Relocation
Acknowledge
RL Restore
RNC
Send RANAP Relocation
Acknowledge message
and start timer
pmNoCsIratHoAdmFail +
Send RANAP Relocation
Failure message
RL Restore
Indication (NBAP)
Indication and Handover
to UTRAN Command messages
Handover to UTRAN
received before
RNC
UE
timeout?
Complete (RRC)
RBS
RNC
YES
pmNoInCsIratHoSucc +
Offload indication
is detected in Relocation
Request message?
YES
pmOffloadSuccCs +
pmOffloadDedicPrioEutra +
RNC
NO
Signaling Connection
Handling
Signaling Connection
Handling
NO
MOCN enabled?
2.5.7.2
CN
Release
resources
Release
resources
NO
YES
pmMocnDedicPrioEutra +
End
Figure 81
RANAP
Relocation
Failure
C 00 01133F
Inter-Radio Access Technology Handover from GSM, Incoming Scenario
Inter-Radio Access Technology Handover from LTE
This traffic scenario describes the Inter-Radio Access Technology Handover
attempt from LTE to UTRAN.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
125
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmInIratHoAttPs,
•
pmInIratHoSuccPs
•
pmInIratHoAttAckPs
•
pmNoInIratHoAttPsStr, pmNoInIratHoSuccPsStr
•
pmNoInIratHoAttPsStr128, pmNoInIratHoSuccPsStr128
•
pmNoInIratHoAttPsStrHs, pmNoInIratHoSuccPsStrHs
•
pmNoInIratHoAttPsInt, pmNoInIratHoSuccPsInt
•
pmNoInIratHoAttPsIntHs, pmNoInIratHoSuccPsIntHs
•
pmNoInIratHoAttPsIntEul, pmNoInIratHoSuccPsIntEul
•
pmNoInIratHoAttPsIntNonHs, pmNoInIratHoSuccPsIntNonHs
•
pmOffloadAttPs, pmOffloadSuccPs
Other impacted counters are included in the following flowcharts, which are
referenced from the Inter-Radio Access Technology Handover from LTE,
Incoming flowchart:
•
Figure 65, Figure 19
Predefined sequences used in Figure 84 and in Figure 85 are shown in Figure
82 and Figure 83.
A flowchart for the Inter-Radio Access Technology Handover from LTE scenario
is shown in Figure 84 and Figure 85.
126
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
A
Is PS interactive
RAB configured ?
NO
YES
For each PS interactive RAB :
pmNoInIratHoAttPsInt +
pmNoInIratHoSuccPsInt +
pmNoInIratHoAttPsIntHS +
pmNoInIratHoSuccPsIntHS +
pmNoInIratHoAttPsIntEUL +
pmNoInIratHoSuccPsIntEUL +
pmNoInIratHoAttPsIntNonHS +
pmNoInIratHoSuccPsIntNonHS +
PS streaming
RAB configured?
Step relevant counters
NO
YES
For each PS interactive RAB :
pmNoInIratHoAttPsStrHS +
pmNoInIratHoSuccPsStrHS +
pmNoInIratHoAttPsStr128 +
pmNoInIratHoSuccPsStr128 +
pmNoInIratHoAttPsStr +
pmNoInIratHoSuccPsStr +
Step relevant counters
End
C 0001597B
Figure 82
Predefined Sequence for Inter-Radio Access Technology Handover from LTE
(Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
127
Performance Statistics - Flowcharts for Counters
B
Is PS interactive
RAB configured ?
NO
YES
For each PS interactive RAB :
pmNoInIratHoAttPsInt +
pmNoInIratHoAttPsIntHS +
pmNoInIratHoAttPsIntEUL +
pmNoInIratHoAttPsIntNonHS +
PS streaming
RAB configured?
Step relevant counters
NO
YES
For each PS interactive RAB :
pmNoInIratHoAttPsStrHS +
pmNoInIratHoAttPsStr128 +
pmNoInIratHoAttPsStr +
Step relevant counters
End
C 0001598B
Figure 83
128
Predefined Sequence for Inter-Radio Access Technology Handover from LTE
(Part B)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
IRAT Handover is triggered by
RANAP Relocation Request message
Perform RAB mapping
YES
NO
RAB mapping
successful ?
pmInIratHoAttPs +
Offload indication
is detected in Relocation
Request message?
NO
Send RANAP Relocation
Failure message to CN
RNC
RANAP
Relocation
Failure
CN
YES
Signaling Connection
Handling
pmOffloadAttPs +
Release
resources
1
Perform Admission Control
YES
Offload indication
is detected in Relocation
Request message?
YES
Admission
reject?
NO
NO
Radio Link Setup
2
Successful
setup?
NO
2
YES
Send RANAP Relocation
Acknowledge message
and start timer
CN
RANAP
Relocation
Acknowledge
RL Restore
RNC
pmNoIratHoAttAckPs +
RL Restore
Indication and Handover
to UTRAN Command messages
Handover to UTRAN
received before
RNC
UE
timeout?
Complete (RRC)
RBS
Indication (NBAP)
RNC
YES
pmInIratHoSuccPs +
NO
Signaling Connection
Handling
Release
resources
B
Offload indication
is detected in Relocation
Request message?
NO
YES
pmOffloadSuccPs +
A
C 0001599B
Figure 84
Inter-Radio Access Technology Handover from LTE, Incoming Scenario (Part A)
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
129
Performance Statistics - Flowcharts for Counters
2
NO
PS EUL/HS
configuration ?
PS DCH/HS
configuration ?
YES
YES
YES
Re-attempt on
EUL/HS ?
1
YES
NO
1
YES
Re-attempt on
DCH/DCH ?
NO
Re-attempt on
DCH/HS ?
NO
NO
B
C 0001600A
Figure 85
2.5.7.3
Inter-Radio Access Technology Handover from LTE, Incoming Scenario (Part B)
Inter-Radio Access Technology Handover from LTE (SRVCC for Voice
and Data)
This traffic scenario describes the Inter-Radio Access Technology Handover
attempt from LTE (SRVCC for Voice and Data) to UTRAN.
The main counters for this scenario are as follows:
•
pmInIratHoAttMulti, pmInIratHoSuccMulti
•
pmInIratHoAttAckMulti
•
pmNoInIratHoAttSpeech, pmNoInIratHoSuccSpeech
•
pmNoInIratHoAttAmrNb, pmNoInIratHoSuccAmrNb
•
pmNoInIratHoAttAmrWb, pmNoInIratHoSuccAmrWb
•
pmOffloadAttMulti, pmOffloadSuccMulti
Other impacted counters are included in the following flowcharts:
•
Figure 65, Figure 19, Figure 82, Figure 83, Figure 84 Figure 85.
In the context of this traffic scenario, the Multi RAB case includes both the CS
RAB and the PS RABs. A flowchart for the scenario is shown in Figure 86
130
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
RNC receives RANAP Relocation Request
when the IE “Number of Iu Instances” is set to two
pmInIratHoAttAckMulti +
pmOffloadAttMulti +
Increment once for two RANAP
‘Relocation Request’ messages
with same NAS ID
pmNoInIratHoAttSpeech +
Step if RNC receives RANAP
Relocation Request from CS CN
pmNoInIratHoAttAmrWb +
pmNoInIratHoAttAmrNb +
Step relevant
NO
Both of the relocation requests
for CS and PS are received?
YES
RANAP
Send two RANAP
Relocation Failure messages
RNC
Relocation
Failure
CN
Signaling Connection
Handling
Perform RAB mapping.
Select target configuration
and capability handling.
Last retry for CS part
Radio Link Setup
Last retry to establish
only the CS part?
YES
Successful retry
for CS part
Send two RANAP
Relocation Failure messages
YES
NO
NO
NO
Successful setup for
CS and PS RABs?
Signaling Connection
Handling
Send one RANAP Relocation
Acknowledge message to MSC
RNC
Send one RANAP Relocation
Failure message to SGSN
RNC
RANAP
Relocation
Allocation
RNC
RANAP
Relocation
Allocation
MSC
Release
Resources
MSC
YES
CN
RANAP
RNC
Relocation
Acknowledge
Two Relocation Request Acknowledge
messages are sent for a Multi RAB
(including both CS RAB and PS RAB)
pmInIratHoAttAckMulti +
RBS
UE
RANAP
Relocation
Failure
Signaling Connection
Handling
Release PS
Resources
Signaling Connection
Handling
Release
Resources
SGSN
RL Restore
Indication (NBAP)
Handover to UTRAN
Complete (RRC)
RNC
RNC
RL Restore
Indication and Handover
to UTRAN Command messages
received before
timeout?
NO
YES
pmInIratHoSuccMulti +
pmNoInIratHoSuccSpeech +
pmNoInIratHoSuccAmrNb +
pmNoInIratHoSuccAmrWb +
pmOffloadSuccMulti +
Incremented once for the
entire RAB combination
if sucessful setting up a multi-RAB
Step relevant if RNC receives RANAP
Relocation Request from CS CN
Incremented once for the entire RAB
combinationif sucessful setting up a multi-RAB
for an IRAT offload request from E-UTRAN
End
C0002148A
Figure 86
Inter-Radio Access Technology Handover from LTE (SRVCC for
Voice and Data), Incoming Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
131
Performance Statistics - Flowcharts for Counters
2.5.8
Inter-Radio Access Technology Cell Change, Outgoing
This traffic scenario describes the inter-radio access technology cell change
from UTRAN to GPRS or GAN.
The main counters for this scenario are as follows:
•
pmNoOutIratCcAtt, pmNoOutIratCcAttHs, pmNoOutIratCcAttEul
•
pmNoOutIratCcSuccess, pmNoOutIratCcSuccessHs, pmNoOutIratCcSuc
cessEul
•
pmNoOutIratCcReturnOldCh, pmNoOutIratCcReturnOldChHs,
pmNoOutIratCcReturnOldChEul
•
pmNoOutGanIratCcAtt, pmNoOutGanIratCcSucc
•
pmNoOutGanIratCcAttHs, pmNoOutGanIratCcSuccHs
•
pmNoOutGanIratCcAttEul, pmNoOutGanIratCcSuccEul
Other impacted counters are included in the flowchart Figure 19, which is
referenced from the Inter-Radio Access Technology Cell Change, Outgoing
flowchart.
A flowchart for the Inter-Radio Access Technology Cell Change scenario is
shown in Figure 87.
132
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
RRC Measurement Report Event 3a received.
HO Algortihm evaluates the MR and trigger a
IRAT CC if it is accepted.
Handover Evaluation
Start evaluation of MR 3a
Start Outgoing Inter
Radio Access
Technology Cell Change
UE
RRC Cell Change
Order from UTRAN
SRNC
Send message
Start timer waiting for Iu
Release command from
PS CN
pmNoOutIratCcX +
or
pmNoOutGanIratCcX +
UE
RRC Cell Change
Order from UTRAN
Failure
SRNC
Receive message
X = One of: Att, Att & AttHs, Att & AttHs & AttEul
SRNC
Iu Release Command
PS CN
Stop timer waiting for Iu
Release command from
PS CN
Configure SP to resume
DL traffic
Cell Change
order from
UTRAN Failure
Iu Release
Command
X = One of: Success, Success & SuccessHs,
Success & SuccessHs & SuccessEul
Y = One of: Succ, Succ & SuccHs,
Succ & SuccHs & SuccEul
Is SP
reconfiguration
successful?
NO
Which
message is
received?
pmNoOutIratCcX +
or
pmNoOutIratGanCcY +
YES
pmNoOutIratCcReturnOldX +
X = One of: Ch, Ch & ChHs, Ch & ChHs & ChEul
Signaling
Connection
Handling
End Outgoing Inter Radio
Access Technology Cell
Change
C 00 01123E
Figure 87
Inter-Radio Access Technology Cell Change, Outgoing Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
133
Performance Statistics - Flowcharts for Counters
2.5.9
Inter-Radio Access Technology Cell Change, Incoming
This traffic scenario describes an inter-radio access technology cell change
from GPRS or GAN to UTRAN.
The main counters for this scenario are as follows:
•
pmTotNoRrcConnectAttIratCcOrder
•
pmTotNoRrcConnectSuccessIratCcOrder
•
pmTotNoRrcConnectFailCongIratCcOrder
•
pmTotNoRrcConnectReq
•
pmTotNoRrcConnectReqSuccess
•
pmNoRejRrcConnMpLoadC
•
pmTotNoUtranRejRrcConnReq
Other impacted counters are included in the flowchart Figure 65, which is
referenced from the Inter-Radio Access Technology Cell Change, Incoming
flowchart
A flowchart for the Inter-Radio Access Technology Cell Change, Incoming
scenario is shown in Figure 88.
134
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
RRC connection request
UE
SRNC
(cause: Inter-RAT Cell Change Order)
RRC connection establishment
is triggered byRRC connection
request message
Increment only once even if repeated RRC
connection requests
pmTotNoRcrConnectReq +
pmTotNoRcrConnectAttIratCcOrder +
Radio Link Setup
NO
Successful setup?
YES
UE
RRC connection setup
SRNC
Unsuccessful due
to Congestion?
Send RRC connection setup
and start timer
NO
YES
pmTotNoRcrConnectFailCongIratCcOrder +
Radio link restore
Indication
RBS
UE
Radio connection setup
complete
UE
RRC connection Release
UE
Radio connection Release
complete
SRNC
RRC connection setup
complete and NBAP Radio link
restore indication are received
before timer expires
SRNC
YES
SRNC
NO
Send RRC connection release,
start timer, receive RRC connection
release comoplete/timer expires
SRNC
Release of already allocated resources
Increment only once even if
repeated RRCconnection requests
pmTotNoRcrConnectReqSuccess +
pmTotNoRcrConnectSuccessIratCcOrder +
pmTotNoUtranRejRrcConnReq +
NO
Unsuccessful
Load control
YES
pmNoRejRrcConnMpLoadC +
End RRC connection setup
C 0001124D
Figure 88
2.5.10
Inter-Radio Access Technology Cell Change, Incoming Scenario
Inter-Radio Access Technology Cell Reselection, Incoming
This traffic scenario describes an inter-radio access technology cell reselection
from GPRS to UTRAN.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
135
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmTotNoRrcConnectAttIratCellResel
•
pmTotNoRrcConnectSuccessIratCellResel
•
pmTotNoRrcConnectFailCongIratCellResel
•
pmTotNoRrcConnectReq
•
pmTotNoRrcConnectReqSuccess
•
pmNoRejRrcConnMpLoadC
•
pmTotNoUtranRejRrcConnReq
Other impacted counters are included in the flowchart Figure 65, which is
referenced from the Inter-Radio Access Technology Cell Change, Incoming
flowchart
A flowchart for the Inter-Radio Access Technology Cell Reselection scenario
is shown in Figure 89.
136
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
RRC Connection Establishment
is triggered by RRC Connection
Request message
UE RRC Connection Request
SRNC
(cause: Inter-RAT Cell Reselection)
Increment only once even if repeated RRC
Connection Requests
pmTotNoRrcConnectReq +
pmTotNoRrcConnectAttIratCellResel +
Radio Link Setup
NO
Successful setup?
YES
RRC Connection Setup
UE
SRNC
Unsuccessful due
to Congestion?
Send RRC Connection Setup
and start timer
NO
YES
pmTotNoRrcConnectFailCongIratCellResel +
RBS
Radio Link Restore
Indication
SRNC
UE
Radio Connection Setup
Complete
SRNC
UE
RRC Connection Release
SRNC
RRC
Connection Setup
Complete and NBAP Radio Link
Restore Indication are received
before timer expires
YES
UE
Radio Connection Release
Complete
NO
Send RRC Connection Release,
start timer, receive RRC Connection
Release Complete/timer expires
SRNC
Release of already allocated resources
Increment only once even if repeated
RRC Connection Requests
pmTotNoRrcConnectReqSuccess +
pmTotNoRrcConnectSuccessIratCellResel +
pmTotNoUtranRejRrcConnReq +
NO
Unsuccessful
Load Control
YES
pmNoRejRrcConnMpLoadC +
End RRC Connection Setup
C 00 01125F
Figure 89
2.5.11
Inter-Radio Access Technology Cell Reselection, Incoming Scenario
Cell Update
This traffic scenario describes Cell Update situations in the RNC.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
137
Performance Statistics - Flowcharts for Counters
The main counters for this scenario are as follows:
•
pmNoCellUpdAttempt, pmNoCellUpdSuccess
•
pmSamplesActiveUesBestCell, pmSumActiveUesBestCell
•
pmSamplesActiveDriftUesBestCell, pmSumActiveDriftUesBestCell
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the Cell Update flowchart.
A flowchart figure for the Cell Update scenario is shown in Figure 90.
138
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Cell Update is received
correctly in the SRNC
1
If the SRNTI part of the URNTI cannot
be identified the connection is released.
No counter stepped.
2
Unknown
SRNTI?
1
UE is in CELL_FACH
Known
Not stepped if:
- CU contains the cause code
- ’RLC Unrecoverable error’
- CU contains the IE ’Failure cause’
- UE is considered to be in DCH state
2
RRC Connection Release
pmNoCellUpdAttempt +
YES
Error?
3
3
NO
This error check can consist of one of
the following:
- CU contains the cause code
- ’RLC Unrecoverable error’
- CU contains the IE ’AM-RLC error’
- CU contains the IE ’Failure cause’
NO
YES
New Cell?
YES
Cause Cell
Reselection?
Assign CRNTI
Get Cell Params
Set up new MAC-C
Delete old MAC-C
NO
UE
RRC: Cell Update Confirm
SRNC
4
Send message
Address the Ue with URNTI
Reassign the same CRNTI
pmNoCellUpdSuccess +
This check can fail for one of the
following reasons:
- C-RNTI cannot be assigned
- The UE cannot be added to the
- common channels
YES
End
OK?
4
NO
RRC Connection Release
UE
RRC: Cell Update Confirm
SRNC
Send message. Set timer.
Wait for response
Timeout?
YES
NO
UE
RRC: Utran Mobility Information Confirm
SRNC
Receive message
Resume data transfer
End
Stop timer
pmNoCellUpdSuccess +
End
Figure 90
2.5.12
C 00 01127F
Cell Update Scenario
URA Update
This section describes the URA update scenarios in the RNC.
The main counters for this scenario are as follows:
•
pmNoUraUpdAttempt
•
pmNoUraUpdSuccess
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
139
Performance Statistics - Flowcharts for Counters
•
pmLevelRabUra
Note:
pmLevelRabUra is an internal counter, not visible in the output
Statistics ROP file. It is mapped to related counters pmSumRabUra
and pmSamplesRabUra.
Other impacted counters are included in the flowchart Figure 20, which is
referenced from the URA Update flowchart.
A flowchart figure for the URA Update scenario is shown in Figure 91.
URA Update is received
correctly in the SRNC
URNTI?
Unknown
Known
Load
Granted
NO
YES
pmNoUraUpdAttempt +
Cell
without URA?
YES
NO
NO
Periodic Update
New URA?
Keep Old URA
RRC Connection Release
YES
Change of URA
URA Reselection
Ack of
DCCH fails?
YES
NO
UE
DCCH: URA Update Confirm
SRNC
Signalling
Connection Release
Send message
pmNoUraUpdSuccess +
UE in
new URA?
YES
pmLevelRabUra +
NO
End
C 00 01313B
Figure 91
140
URA Update Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.5.13
RAN Information Management Update
RAN Information Management (RIM) support for System Information transfer to
LTE facilitates faster call setup in WCDMA by updating an eNB with information
about external UTRAN cells. This section describes sending an SI information
update to all defined associations triggered by changes in the cell’s system
information.
The counters for this scenario are as follows:
•
pmRimUtraSiUpdates
•
pmRimUtraSiSuccDeliveries
•
pmRimUtraSiUnsuccDeliveries
A flowchart for the RIM update scenario is shown in Figure 92:
SI change triggers
RIM update
pmRimUtraSiUpdates + *
Send RIM update
for each association
Wait for timeout or
acknowledgement
NO
Update for an
association
acknowledged?
YES
Message sequence
number matches most
recent update?
YES
NO
pmRimUtraSiSuccDeliveries +
Retry message
NO
Retransmission
attempted rimUtraSiRetries
times?
End
YES
pmRimUtraSiUnsuccDeliveries +
End
Figure 92
*) One SI update for RIM in cell increments this counter once
but generates one RIM message per association.
C 0001473A
RAN Information Management Update Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
141
Performance Statistics - Flowcharts for Counters
2.5.14
HS Cell Change Counters
An HS Cell change can be triggered by the removal of an RL or change of
best cell. The following counters are valid for monitoring the HS Cell Change
function.
In MO Class UtranCell:
•
pmNoHsCcAttempt, pmNoHsCcSuccess
•
pmNoEulCcAttempt, pmNoEulCcSuccess
•
pmNoPsStreamHsCcAttempt, pmNoPsStreamHsCcSuccess
A flowchart for the Serving HS- Cell Change scenario is shown in Figure 93.
142
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Decision to perform an
intra-frequency HS-DSCH
Cell Change
Admission Control (always granted)
Serving HS Cell Change preparations
No
Successful?
Yes
RRC Physical Channel Reconfiguration
Eul Enabled?
Yes
No
pmNoEulCcAttempt +
pmNoHsCcAttempt +
pmNoPsStreamHsCcAttempt +
Timeout
Or RRC Physical
Channel Reconfiguration
Failure?
Yes
No
RRC Physical Channel Reconfiguration Complete
Eul Enabled?
No
Yes
pmNoEulCcSuccess +
pmNoHsCcSuccess +
pmNoPsStreamHsCcSuccess +
Clean-up and return
Clean-up and return
C 00 01199F
Figure 93
2.5.15
Serving HS- Cell Change Scenario
CN Hard Handover on CS RAB, Source-RNC
This traffic scenario describes CNHHO attempts in the source RNC.
•
pmNoAttOutCnhhoSpeech
•
pmNoAttOutCnhhoCsNonSpeech
•
pmNoAttOutLoadbasedCnhho
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
143
Performance Statistics - Flowcharts for Counters
•
pmNoSuccOutCnhhoSpeech
•
pmNoSuccOutCnhhoCsNonSpeech
•
pmNoSuccOutLoadbasedCnhho
Other impacted counters are included in the following flowcharts, which are
referenced from the CNHHO, in the source RNC flowchart:
•
Figure 12, Figure 4
A flowchart for the CNHHO, in the source RNC scenario is shown in Figure 94.
144
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Triggered by Handover
evaluation function for mobility reasons
RRC Measurement Report Event 1a, 1c or 1d, or 2b
is received. Ho Evaluation triggers CNHHO if the
target Cell is a"Non-Iur External UTRAN CCH"
CN
RANAP
Send RANAP Relocation Required
message and start timer
RNC
Relocation Required
CN
RANAP Relocation
Command
RNC
Relocation
Command Receives before
timer expires?
RNC
OR
CN
RANAP Relocation
Preparation Failure
NO
Message
received or timer
expired?
YES
Relocation
Command
Failure?
Timer expired
CN
NO
RRC Radio Bearer
RNC
UE
YES
Reconfiguration
Send RRC Radio Bearer
and start timer
CN
RANAP Relocation
Cancel
RANAP Relocation
Cancel Acknowledge
RANAP Iu Release
Command
NBAP Radio Link
Restore Indication
RBS
UE
RRC Radio Bearer
Reconfiguration Failure
Handover Evaluation
Iu
Release Command
with cause ’Normal Release’ or ’Successful
relocation’ received before
timer expires?
RNC
RNC
RNC
RNC
Relocation
Preparation
Failure
received
Send Relocation Cancel
and receive Relocation
Cancel Acknowledge
pmNoAttOutCnho<Speech/CsNonSpeech> +
or
pmNoAttOutLoadbasedCnhho +
CN
RNC
NO
Message
received or timer
expired?
YES
Timer expired
pmNoSuccOutCnhho<Speech/CsNonSpeech> +
or
pmNoSuccOutLoadbasedCnhho +
Radio Bearer Reconfiguration failure
Signaling
Connection
Handling
CN
CN
Release
resources
RANAP Relocation
Cancel
RANAP Relocation
Cancel Acknowledge
RNC
Send Relocation Cancel
and receive Relocation
Cancel Acknowledge
RNC
Handover Evaluation
C 00 01241B
Figure 94
2.5.16
CN Hard Handover on CS RAB in the source RNC
CN Hard Handover on CS RAB, Target-RNC
This traffic scenario describes CNHHO attempts in the target RNC.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
145
Performance Statistics - Flowcharts for Counters
•
pmNoAttIncCnhhoSpeech
•
pmNoAttIncCnhhoCsNonSpeech
•
pmNoSuccIncCnhhoSpeech
•
pmNoSuccIncCnhhoCsNonSpeech
•
pmSpidDedicPrioEutra
•
pmMocnDedicPrioEutra
Other impacted counters are included in the following flowcharts, which are
referenced from the CNHHO, in the target RNC flowchart:
•
Figure 12, Figure 4
A flowchart for the CNHHO, in the target RNC scenario is shown in Figure 95.
146
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Core Network Hard Handover is triggered by
RANAP Relocation Request message
Check for logical error,
target cell not found,
CS Data Service Handover
not supported
Successful
resource allocation?
NO
YES
Radio Link Setup
YES
NO
Successful
Setup?
pmNoAttIncCnhho<Speech/CsNonSpeech>+
CN
RBS
RANAP
RNC
Relocation
Acknowledge
RL Restore
Send RANAP Relocation
Acknowledge message
and start timer
Send RANAP Relocation
Failure message
RNC
RL Restore
Indication (NBAP)
NO
Indication and Radio Bearer
Reconfiguration Complete messages
received before
RRC Radio Bearer
timeout?
UE
RNC
Reconfiguration
Complete
YES
Signallling Connection
Handling
RNC
Signallling Connection
Handling
RANAP
Relocation
Failure
CN
Release
resources
Release
resources
pmNoSuccIncCnhho<Speech/CsNonSpeech>+
SPID included in
RANAP Relocation
Request?
YES
pmSpidDedicPrioEutra +
NO
MOCN enabled?
NO
YES
pmMocnDedicPrioEutra +
End
C 00 01242D
Figure 95
2.5.17
CN Hard Handover on CS RAB in the target RNC
CN Hard Handover on PS RAB, Source-RNC
This traffic scenario describes CNHHO on PS in the source RNC
The main counters for this scenario are as follows:
•
pmNoAttOutCnhhoPsConnRelease
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
147
Performance Statistics - Flowcharts for Counters
Other impacted counters are included in the following flowcharts, which are
referenced from the CNHHO, in the source RNC flowchart:
•
Figure 12 , Figure 2
A flowchart for the CNHHO, in the source RNC scenario is shown in Figure 96.
Triggered by Handover
evaluation function for mobility reasons
RRC Measurement Report Event 1a, 1c or 1d, or 2b
is received. Ho Evaluation triggers CNHHO if the
target Cell is a"Non-Iur External UTRAN CCH"
Handover Evaluation
Start evaluation of MR
UE
RRC Connection Release
Change Order from UTRAN
Cause Directed Signaling
Connection Re-establish
RNC
Signalling Connection Handling
Start timer waiting for Iu
Release command from
PS CN
pmNoAttOutCnhhoPsConnRelease+
Receive message
SRNC
Iu Release Command
PS CN
Stop timer waiting for Iu
Release command from
PS CN
Iu Release
Command
Signalling
Connection
Handling
End
C 00 01243B
Figure 96
2.5.18
CN Hard Handover on PS RAB in the source RNC
CN Hard Handover on PS RAB, Target-RNC
There is no specific CNHHO on PS-RAB, in the target RNC. It is handled as in
Figure 2 and Figure 11.
148
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
2.5.19
UE Positioning
This traffic scenario describes the pm counter handling within UE Positioning.
The main counters for this scenario are as follows:
•
pmCellIdAttempt
•
pmCellIdSuccQosOk
•
pmCellIdSuccQosNotOk
•
pmRttAttempt
•
pmRttSuccQosOk
•
pmRttSuccQosNotOk
•
pmAgpsAttempt
•
pmAgpsSuccQosOk
•
pmAgpsSuccQosNotOk
The Pcap counters are as follows:
•
pmNoPcapPosIniReq
Note:
•
pmNoPcapPosIniResp
Note:
•
The counter is stepped when a POSITION INITIATION RESPONSE
message is received by the RNC over Pcap.
pmNoPcapPosActReq
Note:
•
The counter is stepped when a POSITION INITIATION REQUEST
message is sent from the RNC to SAS.
The counter is stepped when a POSITION ACTIVATION
REQUEST message is received by the RNC.
pmNoPcapPosActResp
Note:
The counter is stepped when a POSITION ACTIVATION
RESPONSE message is sent by the RNC to SAS.
A flowchart for the UE Positioning scenario is shown in Figure 97, Figure 98,
Figure 99, and Figure 100.
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
149
Performance Statistics - Flowcharts for Counters
Start of
UE Positioning
(RANAP) LOCATION REPORTING CONTROL
Message received
Determine Positioning Service Classes
based on IE "Client Type" in the RANAP.
Choose the correct instance of MOC
PositioningServiceClass to apply the counters
Select the method for the
first positioning attempt
cell_Id
Method for
first attempt?
A-GPS
RTT
UE Positioning
scenario 1
Figure 97
150
UE Positioning
scenario 2
UE Positioning
scenario 3
C 0001376B
UE Positioning - Main Scenario
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
UE Positioning
Main scenario
pmCellIdAttempt +
Perform CellId and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmCellIdSuccQosOk +
No
pmCellIdSuccQosNok +
END
Select the method for the
second positioning attempt
Method for
second attempt?
RTT
A-GPS
None
END
pmRttAttempt +
pmAgpsAttempt +
Perform RTT and
evaluate the accuracy
Perform A-GPS and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmRttSuccQosOk +
No
pmAgpsSuccQosOk +
pmRttSuccQosNok +
END
Select the method for the
third positioning attempt
Method for
third attempt?
Method for
third attempt?
None
END
No
pmAgpsSuccQosNok +
END
Select the method for the
third positioning attempt
None
Required
accuracy fulfilled?
Yes
END
A-GPS
RTT
pmAgpsAttempt +
pmRttAttempt +
Perform A-GPS and
evaluate the accuracy
Perform RTT and
evaluate the accuracy
Required
accuracy fulfilled?
No
pmAgpsSuccQosNok +
Yes
pmRttSuccQosNok +
END
Yes
pmRttSuccQosOk +
pmAgpsSuccQosOk +
END
Required
accuracy fulfilled?
No
END
END
C 00 01377A
Figure 98
UE Positioning - Scenario 1
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
151
Performance Statistics - Flowcharts for Counters
UE Positioning
Main scenario
pmRttAttempt +
Perform RTT and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmRttSuccQosOk +
No
pmRttSuccQosNok +
END
Select the method for the
second positioning attempt
Method for
second attempt?
cell_id
A-GPS
None
END
pmCellIdAttempt +
pmAgpsAttempt +
Perform CellId and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmCellIdSuccQosOk +
pmAgpsSuccQosOk +
No
No
pmAgpsSuccQosNok +
END
Select the method for the
third positioning attempt
Select the method for the
third positioning attempt
Method for
third attempt?
None
Required
accuracy fulfilled?
Yes
pmCellIdSuccQosNok +
END
Perform A-GPS and
evaluate the accuracy
Method for
third attempt?
None
END
END
A-GPS
cell_id
pmAgpsAttempt +
pmCellIdAttempt +
Perform A-GPS and
evaluate the accuracy
Perform CellId and
evaluate the accuracy
Required
accuracy fulfilled?
No
pmAgpsSuccQosNok +
Yes
pmCellIdSuccQosNok +
END
Yes
pmCellIdSuccQosOk +
pmAgpsSuccQosOk +
END
Required
accuracy fulfilled?
No
END
END
C 00 01378A
Figure 99
152
UE Positioning - Scenario 2
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
UE Positioning
Main scenario
pmAgpsAttempt +
Perform A-GPS and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmAgpsSuccQosOk +
No
pmAgpsSuccQosNok +
END
Select the method for the
second positioning attempt
Method for
second attempt?
cell_id
RTT
None
END
pmCellIdAttempt +
pmRttAttempt +
Perform CellId and
evaluate the accuracy
Perform RTT and
evaluate the accuracy
Required
accuracy fulfilled?
Yes
pmCellIdSuccQosOk +
pmRttSuccQosOk +
No
pmCellIdSuccQosNok +
END
No
pmRttSuccQosNok +
END
Select the method for the
third positioning attempt
Select the method for the
third positioning attempt
Method for
third attempt?
None
Required
accuracy fulfilled?
Yes
Method for
third attempt?
None
END
END
RTT
cell_id
pmRttAttempt +
pmCellIdAttempt +
Perform RTT and
evaluate the accuracy
Perform CellId and
evaluate the accuracy
Required
accuracy fulfilled?
No
pmRttSuccQosNok +
Yes
pmCellIdSuccQosNok +
END
Yes
pmCellIdSuccQosOk +
pmRttSuccQosOk +
END
Required
accuracy fulfilled?
No
END
END
C 00 01379A
Figure 100
UE Positioning - Scenario 3
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
153
Performance Statistics - Flowcharts for Counters
2.5.20
Wi-Fi Mobility: UE Requesting Access to Wi-Fi
This traffic scenario describes the pm counter handling when estimating
throughput and evaluating to admit a UE attempting access to Wi-Fi.
The main counters for the AttachRequest scenario are as follows:
•
pmWifiUeNotRegisteredAtt
•
pmWifiAccessReq
•
pmWifiAccessRsp
•
pmWifiAdm
•
pmWifiUraAtt
•
pmWifiFachAdm
•
pmWifiFachAtt
•
pmWifiFachRej
•
pmWifiHsAdm
•
pmWifiHsAtt
•
pmWifiHsRej
•
pmWifiR99Adm
•
pmWifiR99Att
•
pmWifiR99NoDecision
•
pmWifiR99Rej
A flowchart for the UE requesting access to Wi-Fi scenario is shown in Figure
101.
154
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
Performance Management Areas
Start at any state
WIC
Receive message
pmWifiAccessReq +
U2:RACP:
Access Request
Admit after general checks?
for example
WiFi thp > typical cell thp
Yes
No
Determine UE state and
cells related to the WiFi AP
pmWifiHsAtt+
pmWifiR99Att+
pmWifiFachAtt+
pmWifiURAAtt +
pmWifiUeNotRegisteredAtt+
Step relevant
Evaluate UE state, cell-list and throughput.
Decide to Admit or Reject, UE in Wifi
or to let WIC decide (no decision)
Yes
No
Admit?
No decision
Step relevant
pmWifiHsAdm+
pmWifiFachAdm+
pmWifiR99NoDecision+
pmWifiR99Adm+
Send response message
pmWifiAccessRsp+
pmWifiAdm+ (if admitted)
pmWifiHsRej+
pmWifiFachRej+
pmWifiR99Rej+
U2:RACP:
Access Response
Step relevant
WIC
C0002145A
Figure 101
2.5.21
UE Throughput-based Mobility to Wi-Fi - Scenario 1
Wi-Fi Mobility: Re-estimation of UE Attached in Wi-Fi
This traffic scenario describes the pm counter handling when estimating
throughput for a UE attached in Wi-Fi.
The main counters for the Estimate Request scenario are as follows:
•
pmWifiUeNotRegisteredEstReq
•
pmWifiEstimateReq
•
pmWifiEstimateRsp
•
pmWifiUraEstReq
103/1551-AXD 105 03/1 Uen AB | 2014-05-19
155
Performance Statistics - Flowcharts for Counters
•
pmWifiFachEstReq
•
pmWifiHsEstReq
•
pmWifiHsEstReq
A flowchart for the re-estimation of UE attached in Wi-Fi scenario is shown in
Figure 102.
Start at any state
WIC
U2:RACP:
Estimate Request
Receive message
pmWifiEstimateReq +
Determine UE state and
cells related to the WiFi AP
pmWifiHsEstReq+
pmWifiEstReq+
pmWifiFachEstReq+
pmWifiURAEstReq+
pmWifiUeNotRegisteredEstReq+
Step relevant
Evaluate UE state, cell-list
and estimate throughput
Send response message
pmWifiEstimateRsp+
U2:RACP:
Estimate Response
WIC
C0002146A
Figure 102
156
UE Throughput-based Mobility to Wi-Fi - Scenario 2
103/1551-AXD 105 03/1 Uen AB | 2014-05-19