Ericsson Internal

OPERAT. GUIDELINES 1 (239)

Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMCN Performance Indicators

Abstract

This document covers IMS performance indicators intended for PM reports

supporting IP Multimedia Core Network (IMCN) .
 Ericsson Internal
OPERAT. GUIDELINES 2 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Contents
1 Revision history ...................................................................................... 5
2 Introduction ........................................................................................... 18
2.1 Purpose ..................................................................................... 18
2.2 Scope ........................................................................................ 18
2.3 General information .................................................................. 19
3 IMCN R-KPIs for VoLTE........................................................................ 22
4 IMS CSCF ............................................................................................... 24
4.1 Access Type tokens for Access Aware R-KPIs........................ 24
4.2 IMS CSCF Registration Accessibility........................................ 24
4.3 IMS CSCF Registration Retainability........................................ 27
4.4 IMS CSCF Dropped Registrations Ratio .................................. 32
4.5 IMS CSCF Session Setup Accessibility ................................... 33
4.6 IMS CSCF Session Retainability .............................................. 44
4.7 IMS CSCF Dropped Sessions Ratio......................................... 45
4.8 IMS CSCF Session Set-up Integrity ......................................... 46
4.9 IMS CSCF Charging Accessibility ............................................ 52
4.10 Traffic Indicators........................................................................ 53
4.11 IMS Active Users ...................................................................... 64
5 PSTN Interworking and Transit ........................................................... 67
5.1 IMS PSTN Interworking and Transit Accessibility .................... 67
5.2 Traffic Indicator ......................................................................... 68
6 IMS MTAS ............................................................................................... 69
6.1 IMS MTAS Registration Accessibility ....................................... 69
6.2 IMS MTAS Registration Retainability ....................................... 71
6.3 IMS MMTEL AS Session Setup Accessibility........................... 72
6.4 IMS MTAS (MMTel AS and SCC AS) Session Retainability ... 85
6.5 IMS MMTEL AS Hold/Resume Service Accessibility ............... 95
6.6 IMS MMTEL AS Communication Diversion Service
Accessibility............................................................................... 96
6.7 IMS MMTEL AS Conference Service Accessibility .................. 97
6.8 IMS Conference AS Scheduled Conference Accessibility ....... 98
6.9 IMS MTAS Conference Service Retainability........................... 99
6.10 IMS MMTEL AS Calling Name Identification Presentation
(CNIP) Services Accessibility ................................................. 100
6.11 IMS MMTEL AS Announcement Service Accessibility .......... 101
6.12 IMS MMTEL AS Abbreviated Dialing Service Accessibility ... 102
6.13 IMS MMTEL AS Dial Tone Management Service Accessibility103
6.14 IMS MMTEL AS Communication Waiting Service Accessibility103
6.15 IMS MMTEL AS Advice of Charge Service Accessibility ....... 104
6.16 IMS MMTEL AS Third Party (3PTY) Call Creation Accessibility106
6.17 IMS MMTEL AS Third Party (3PTY) Call Creation Retainability106
6.18 IMS MMTEL AS Communication Completion Service
Accessibility............................................................................. 107
6.19 IMS MMTEL AS Flexible Communication Distribution Service
Accessibility............................................................................. 108
6.20 IMS MMTEL AS Short Number Dialing Accessibility ............. 109
6.21 IMS SCC AS Centralization and Continuity (SCC) Accessibility110
6.22 IMS SCC AS Centralization and Continuity (SCC) - SRVCC 121
 Ericsson Internal
OPERAT. GUIDELINES 3 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.23 IMS MMTEL AS Customized Alerting Tones Service

Accessibility............................................................................. 127
6.24 IMS MMTEL AS Session Transfer to Own Device Service
Accessibility............................................................................. 128
6.25 IMS MMTEL AS Parlay-X Service Accessibility ..................... 130
6.26 IMS MMTEL AS Polling of Calling Name Information
Accessibility............................................................................. 131
6.27 IMS MMTEL AS Call Return (CR) Service Accessibility ........ 132
6.28 IMS MMTEL AS Generic Supplementary Service Code
Invocation Service Accessibility.............................................. 133
6.29 IMS MMTEL AS Operator Controlled Transfer (OCT) Service
Accessibility............................................................................. 134
6.30 IMS MMTEL AS MtasPriorityCall Accessibility....................... 135
6.31 IMS MMTel AS Ring Back Tone Accessibility ........................ 137
6.32 IMS SCC AS CAMEL Application Part (CAP) Accessibility ... 137
6.33 IMS MMTel AS Closed User Group (CUG) Accessibility ....... 138
6.34 IMS ST AS Session Setup Accessibility ................................. 139
6.35 IMS MMTel AS H.248 MRFP Request Accessibility .............. 142
6.36 IMS MMTel AS Charging Request Accessibility .................... 144
6.37 IMS MMTel AS Sh Request Accessibility ............................... 146
6.38 IMS MMTel AS Subscribe Session Accessibility.................... 149
6.39 IMS Network AS Precondition IWF Service Accessibility ...... 151
6.40 Traffic Indicators...................................................................... 153
7 Gateway Functions ............................................................................. 158
7.1 IMS MGC................................................................................. 158
7.2 IMS SBG ................................................................................. 162
7.3 IMS MRS ................................................................................. 194
8 Enriched Messaging (vEMe) .............................................................. 194
8.1 IMS EMe SMSoIP Transport Interworking Accessibility ........ 194
9 IMS SIP Signaling................................................................................ 197
9.1 IMS CSCF SIP Accessibility ................................................... 197
9.2 IMS MGC SIP Signaling Accessibility .................................... 199
9.3 IMS SBG SIP Signaling Accessibility ..................................... 200
9.4 IMS JavaSIP Accessibility ...................................................... 200
10 IMS Overload and Load Regulation .................................................. 202
10.1 IMS CSCF SIP Load Regulation Rejection Ratio................... 202
10.2 IMS JavaSIP Overload Rejection ........................................... 203
10.3 MGC Overload Rejection ........................................................ 203
10.4 SBG Overload Rejection......................................................... 204
10.5 MTAS ...................................................................................... 205
10.6 TSP and vDicos Diameter ...................................................... 210
10.7 TSP SS7 and SS7 CAF .......................................................... 212
11 Diameter and SS7 signaling failures ................................................ 216
11.1 CSCF and MTAS Diameter Signaling Failure Rate ............... 216
11.2 SBG Diameter Rx, Rf, Rq or e2 Signaling.............................. 219
11.3 SBG Diameter Rx NPLI Signaling .......................................... 220
11.4 TSP SS7 Signaling MTP-L3 Link Unavailability ..................... 221
11.5 SS7 CAF Signaling M3UA Link Unavailability and Errors ..... 221
12 vDicos NIC , TIPC Link and BGFv Media Interface ......................... 223
 Ericsson Internal
OPERAT. GUIDELINES 4 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

12.1 vDicos NIC Perfomance Indicators........................................ 223

12.2 vDicos TIPC Link Performance Indicators.............................. 225
12.3 vBGF Media IP Interface Performance Indicators ................ 226
13 References ........................................................................................... 230
 Ericsson Internal
OPERAT. GUIDELINES 5 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

1 Revision history

Rev. Date Responsible Description

A 2016-09-09 etxjhje MTAS:

Equation 177 IMS MMTel AS Dialog
Event Notifier Subscribe Setup
Success Ratio,
Equation 183 IMS MMTel AS Number
of Simultaneous Sessions, added.
Equation 181 IMS MMTel AS Number
of Cached Public User Identity
Records, formula name changed, to
reflect counter,
Equation 184 IMS MMTel AS Number
of Mobile Service Simultaneous
Sessions updated to reflect average,
Equation 199 IMS MMTel AS Carried
Load [kErlang] formulas updated for
kErlang.
CSCF:
Equation 51 IMS CSCF Carried Load
[kErlang] updated for kErlang
SBG:
Equation 296 IMS SBG Initiated
Session Release [per second],
Equation 300 IMS SBG Session
Release Media Stop [per second]
added.

A1 2016-10-24 Etxjhje Equation 4 IMS CSCF Reregistration

and Deregistration Success Ratio
formula updated for response codes.

Equation 277 IMS SBG Simultaneous

MultiMedia Sessions in Busy Hour
(kErlang) updated to reflect kErlang.
Section 18 IMS S-CSCF Session
Setup per Media Type Performance
Indicators, note added for enabling of
corresponding counters.
Key change:
Equation 2 IMS CSCF Third Party
Registration Success Ratio

Equation 20 IMS CSCF Originating

Sessions Set-up Time [milliseconds]
and Equation 21 IMS CSCF
 Ericsson Internal
OPERAT. GUIDELINES 6 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Terminating Sessions Set-up Time

[milliseconds] updated to include key.

A2 2016-10-30 Etxjhje Section 8.34 IMS ST AS Session

Setup Accessibility rewritten, formulas
modified and added.
Equation 162 IMS ST AS Originating
Session Setup Success Ratio per PBX
and
Equation 163 IMS ST AS Terminating
Session Setup Success Ratio per PBX
modified.
Equation 164 IMS ST AS Originating
Session Setup Success Ratio,
Equation 165 IMS ST AS Terminating
Session Setup Success Ratio,
Equation 168 IMS ST AS Failed
Originating Sessions, per PBX,
Equation 169 IMS ST AS Failed
Terminating Sessions, per PBX,
Equation 191 IMS ST AS Number of
SIP Trunking Simultaneous Originating
Sessions per PBX,
Equation 192 IMS ST AS Number of
SIP Trunking Simultaneous
Terminating Sessions per PBX added.
Equation 175 IMS MMTel AS Sh
Notification Request Success Ratio
added.
Section 4.5 IMS CSCF Session
Retainability, SMM rule updated.

B 2016-11-17 etxjhje Equation 92 IMS MMTEL AS

Originating Session Set-up Success
Ratio
Equation 93 IMS MMTEL AS
Terminating Session Set-up Success
Ratio updated for cancel early dialog
and formula reworked.
Equation 145 IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
Active Session Access Transfer
Success Ratio,
Equation 146 IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
Alerting Access Transfer Success
Ratio,
Equation 147 IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
pre-Alerting Access Transfer Success
Ratio modified.
 Ericsson Internal
OPERAT. GUIDELINES 7 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 148 IMS SCC AS Single

Radio Voice Call Continuity (SRVCC)
Mid Call Access Transfer Success
Ratio added added.
Equation 193 IMS MMTel AS
Originating Sessions Duration
[Seconds],
Equation 194 IMS MMTel AS
Terminating Sessions Duration
[Seconds],
Equation 195 IMS MMTel AS
Originating Mean Holding Time
[Seconds],
Equation 196 IMS MMTel AS
Terminating Mean Holding Time
[Seconds] modified, covers registered
and unregistered user sessions.
Equation 197 IMS MMTel AS
Originating Service Duration
[Seconds],
Equation 197 IMS MMTel AS
Originating Service Duration [Seconds]
added.

B1 2016-12-05 etxjhje From 1/15443-HSC 11306 A1. Porting

SBG formulas.
Equation 298 IMS SBG Dialog Release
Request Timeout [per second] updated
to include SBGv formula.
Equation 305 IMS SBG transaction
timeouts [per second] removed, was
duplicate of previous formula.
Equation 369 IMS SBG SIP Core
Overload Rejection Ratio corrected.

C 2017-01-05 Etxjhje Document restructured. Clean CSCF

section created (without MTAS and
SBG), per access type and per media
type KPIs moved to CSCF section
which impiles that sections IMS S-
CSCF Access Aware Performance
Indicators, ref. 17 and IMS S-CSCF
Session Setup per Media Type
Performance Indicators, ref. 18 are
removed from document.

Deleted duplicates:
Equation 4. IMS SBG Initial
Registration Success Ratio
Equation 9. IMS SBG Incoming
Session Set-up Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 8 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 10. IMS SBG Outgoing

Session Set-up Success Ratio
Equation 26. IMS SBG Incoming
Sessions Set-up Time [milliseconds]
Equation 27. IMS SBG Outgoing
Sessions Set-up Time [milliseconds]
Equation 54. IMS CSCF Mean
Sessions Utilization
Equation 13. IMS MMTel AS
Orginating Session Completion Ratio
Equation 14. IMS MMTel AS
Terminating Session Completion Ratio
Equation 19. IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
Access Transfer Success Ratio

Moved to SBG section:

Equation 7.Equation 6. IMS SBG
Reregstration and Deregistration
Success Ratio
Equation 8. IMS SBG Initial
Registration Time [milliseconds]
Equation 12. IMS SBG Incomimg
Session Answer to Seizure Ratio
Equation 13. IMS SBG Outgoing
Session Answer to Seizure Ratio
Equation 17. IMS SBG Completion
Ratio
Equation 19. IMS SBG SRVCC Access
Transfer Success Ratio
Equation 22. IMS SBG Dropped
Sessions Ratio
Equation 54. IMS SBG Incoming
Session Duration [Seconds]
Equation 55. IMS SBG Outgoing
Session Duration [Seconds]
Equation 56. IMS SBG Mean Holding
Time [Seconds]

Moved to MTAS section:

Equation 15. IMS SCC AS Orginating
CS Session Completion Ratio
Equation 16. IMS SCC AS Terminating
CS Session Completion Ratio
Equation 17. IMS SCC AS Orginating
PS Session Completion Ratio
Equation 18. IMS SCC AS Terminating
PS Session Completion Ratio
Equation 96. IMS MMTel AS
Orginating Session Completion Ratio
Equation 97. IMS MMTel AS
Terminating Session Completion Ratio.
 Ericsson Internal
OPERAT. GUIDELINES 9 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 1. IMS CSCF Registration

Success Ratio deleted.
Equation 3. IMS CSCF Re-registration
Success Ratio moved to CSCF
Retainability section.

Equation 52 IMS CSCF Average

Reporting OC value,
Equation 53 IMS CSCF Peak
Reporting OC value,
Equation 144 IMS SCC AS Enhanced
Single Radio Voice Call Continuity
(SRVCC) Access Transfer Success
Ratio,
Equation 210 IMS MTAS Overload
Control Duration [Seconds],
Equation 211 IMS MTAS Overload
Control Periods,
Equation 212 IMS MTAS Overload
Control Values Average,
Equation 213 IMS MTAS Overload
Control Values Peak added.

Equation 168 IMS ST AS Failed

Originating Sessions, per PBX,
Equation 169 IMS ST AS Failed
Terminating Sessions, per PBX
modified after review, pbxId added as
index.

C1 2017-01-18 Etxjhje Equation 369 IMS TIPC Send

Requests [Packets per second],
Equation 370 IMS TIPC Receive
Requests [Packets per second]
corrected.

Added equations:

Equation 254 IMS SBG Incoming

S8HR Session Answer to Seizure
Ratio,
Equation 255 IMS SBG Outgoing
S8HR Session Answer to Seizure
Ratio.

Restructuring part 2.

SBG:

Traffic formulas moved to IMCN

Signaling Traffic Performance
 Ericsson Internal
OPERAT. GUIDELINES 10 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Indicators document which implies the

following formulas are deleted from
this document.
Equation 274. IMS ASBG Registered
Users,
Equation 275. IMS ASBG IMS AKA
Registered Users,
Equation 276. IMS ASBG Emergency
Registered Users,
Equation 277. IMS ASBG Initial
Registration Attempts [per second],
Equation 278. IMS ASBG
Reregistrations and Deregistrations
Attempts [per second],
Equation 279. IMS ASBG Initial
Emergency Registration Attempts [per
second],
Equation 280. IMS SBG Simultaneous
MultiMedia Sessions in Busy Hour
(kErlang),
Equation 281. IMS SBG Incoming
Session Duration [Seconds],
Equation 282. IMS SBG Outgoing
Session Duration [Seconds],
Equation 283. IMS SBG Mean Holding
Time [Seconds],
Equation 284. IMS SBG Incoming SIP
Session Set-up Attempts [per second],
Equation 285. IMS SBG Outgoing SIP
Session Set-up Attempts ,
Equation 286. IMS SBG Emergency
Session Set-up Attempts [per second],
Equation 287. IMS SBG Incoming
Priority Session Set-up Attempts [per
second],
Equation 288. IMS SBG Outgoing
Priority Session Set-up Attempts [per
second],
Equation 306. IMS SBG Simultaneous
Subscribe Sessions,
Equation 307. IMS SBG SIP Subscribe
Set-up Attempts [per second],
Equation 308. IMS SBG SIP Notify
Request Attempts [per second],
Equation 309. IMS SBG Incoming SIP
requests [per second],
Equation 310. IMS SBG Outgoing SIP
requests [per second],
Equation 312. IMS SBG Active BGF
Calls (Contexts),
Equation 313. IMS SBG BGF Call
 Ericsson Internal
OPERAT. GUIDELINES 11 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Attempts [per second]

CSCF:

Equation 27. IMS CSCF Initial

Registration Attempts [per second],
Equation 28. IMS CSCF Re-
registration Attempts [per second],
Equation 29. IMS CSCF Ue De-
registration Attempts [per second],
Equation 30. IMS HSS Cx De-register
Attempts [per second],
Equation 37. IMS CSCF Originating
Sessions Set-up Attemts [per second],
Equation 38. IMS CSCF Terminating
Sessions Set-up Attempts [per
second].

MTAS:

Equation 185. IMS MMTel AS

Originating Sessions Duration
[Seconds],
Equation 186. IMS MMTel AS
Terminating Sessions Duration
[Seconds],
Equation 187. IMS MMTel AS
Originating Mean Holding Time
[Seconds],
Equation 188. IMS MMTel AS
Terminating Mean Holding Time
[Seconds],
Equation 189. IMS MMTel AS
Originating Service Duration
[Seconds],
Equation 190. IMS MMTel AS
Terminating Service Duration
[Seconds],
Equation 191. IMS MMTel AS Carried
Load [kErlang],
Equation 192. IMS MMTel AS Mean
Originating Parlay-X Session Duration,
Equation 193. IMS MMTel AS Mean
Terminating Parlay-X Session
Duration,
Equation 196. IMS MMTel AS Mean
Conference Time,
Equation 197. IMS MMTel AS Mean
Conference Time per Participant,
Equation 200. IMS MMTel AS Mean
Third Party Call Time.
 Ericsson Internal
OPERAT. GUIDELINES 12 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

C2 2017-01-19 Etxjhje Added description to:

Equation 74 IMS CSCF PSTN
Interworking Originating Session Set-
up Success Ratio,
Equation 75 IMS CSCF PSTN
Interworking Terminating Session Set-
up Success Ratio.

D 2017-03-10 Etxjhje Equation 93 IMS MTAS DNS Failover

[per second],
Equation 360 IMS Diameter
Unsuccessful Received Requests
Ratio,
Equation 361 IMS Diameter
Unsuccessful Sent Requests Ratio
keys added.
Equation 362 IMS Diameter Malformed
Received Requests Ratio,
Equation 363 IMS Diameter Protcol
Errors and Permanent Failures Ratio
added.
Equation 8 IMS CSCF Originating
Session Set-up Success Ratio and
Equation 9 IMS CSCF Terminating
Session Set-up Success Ratio
corrected.
Equation 247 IMS SBG SRVCC
Access Transfer Success Ratio, SBGv
specific formula added.

Document restructuring: Following

formulas moved to IMCN Signaling
Traffic Performance Indicators.
Equation 185 IMS MMTel AS
Originating Sessions Duration
[Seconds],
Equation 186 IMS MMTel AS
Terminating Sessions Duration
[Seconds],
Equation 187 IMS MMTel AS
Originating Mean Holding Time
[Seconds],
Equation 188 IMS MMTel AS
Terminating Mean Holding Time
[Seconds],
Equation 189 IMS MMTel AS
Originating Service Duration
[Seconds],
Equation 190 IMS MMTel AS
Terminating Service Duration
[Seconds],
 Ericsson Internal
OPERAT. GUIDELINES 13 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 191 IMS MMTel AS Carried

Load [kErlang],
Equation 192 IMS MMTel AS Mean
Originating Parlay-X Session Duration,
Equation 193 IMS MMTel AS Mean
Terminating Parlay-X Session
Duration,
Equation 196 IMS MMTel AS Mean
Conference Time,
Equation 197 IMS MMTel AS Mean
Conference Time per Participant,
Equation 200 IMS MMTel AS Mean
Third Party Call Time removed.
Equation 8 IMS CSCF Originating
Session Set-up Success Ratio and
Equation 9 IMS CSCF Terminating
Session Set-up Success Ratio
updated, now excluding ‘User
cancelled in early dialog’ factors.

D1 2017-04-06 etxjhje Equation 114 IMS MMTEL AS Advice

of Charge Start (AoC-S) Success Ratio
Equation 115 IMS MMTEL AS Advice
of Charge During (AoC-D) Success
Ratio,
Equation 116 IMS MMTEL AS Advice
of Charge End (AoC-E) Success Ratio
and
Equation 135 IMS SCC AS Session
Setup from CS using CAP Registered
and Unregistered Users Success
Ratio,
Equation 230 IMS A-SBG Initial
Registration Success Ratio native part
corrected.

E 2017-05-10 etxjhje Equation 92 IMS MMTEL AS Call

Released No Credit,
Equation 149 IMS MMTEL AS Call
Return Erasure Procedure Success
Ratio,
Equation 152 IMS MMTel AS GETS
Priority Service Successfully Setup
Ratio added.
New sections SBG Diameter Signaling
15.2 and
SBG Rx interface 17 added.
Equation 110 IMS MMTEL AS Calling
Name Identification Presentation
(CNIP) Success Ratio corrected (TR
HV82830.
 Ericsson Internal
OPERAT. GUIDELINES 14 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

E1 2017-06-21 etxjhje Equation 12 IMS CSCF Originating

Session Set-up Success Ratio per
Media Type and
Equation 13 IMS CSCF Terminating
Session Set-up Success Ratio per
Media Type corrected for counter
names.
Equation 136 IMS SCC AS Session
Setup from CS using CAP Registered
and Unregistered Users Success Ratio
formula name changed.
Equation 142 IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
Mid Call Access Transfer Success
Ratio corrected and formula name
changed.
Sections 14.8 TSP and vDicos
Diameter and 15.1 HSS, CSCF and
MTAS Diameter Signaling Failure Rate
differentiated for TSP and vDicos,
since counter naming is not the same.

F 2017-10-16 Etxjhje Equation 8 IMS CSCF Originating

Session Set-up Success Ratio and
Equation 9 IMS CSCF Terminating
Session Set-up Success Ratio
corrected, Redirection (181) subtracted
and Cancel before early dialog added
as success factors.
Equation 22 IMS S-CSCF Originating
Session Duration per Access Type
[Seconds] corrected.
Equation 44 IMS CSCF Registerd
Users Redistributed,
Equation 45 IMS CSCF Unregisterd
Users Redistributed added.
Equation 179 IMS MTAS Number of
Registered IMS Users formula updated
for new counter.
Section 9.3.8 IMS SBG Message
Accessibility added.
Equation 8 IMS CSCF Originating
Session Set-up Success Ratio and
Equation 9 IMS CSCF Terminating
Session Set-up Success Ratio
corrected, Redirection (181) subtracted
and Cancel before early dialog added
as success factors.
Equation 235 IMS A-SBG Initial
Registration Success Ratio,
 Ericsson Internal
OPERAT. GUIDELINES 15 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 237 IMS A-SBG

Reregistration and Deregistration
Success Ratio,
Equation 238 IMS A-SBG Re-
registration Success Ratio modified
SBGv specific equation removed, since
SBGv now has feature parity for the
registrations counters.

G 2017-12-12 Etxjhje Equation 8 IMS CSCF Originating

Session Set-up Success Ratio and
Equation 9 IMS CSCF Terminating
Session Set-up Success Ratio,
Equation 10 IMS CSCF Originating
Session Set-up Success Ratio per
Access Type,
Equation 11 IMS CSCF Terminating
Session Set-up Success Ratio per
Access Type,
Equation 12 IMS CSCF Originating
Session Set-up Success Ratio per
Media Type,
Equation 13 IMS CSCF Terminating
Session Set-up Success Ratio per
Media Type updated, user factors
removed.
Equation 29 IMS CSCF Registered
Users,
Equation 30 IMS CSCF Registered
User Profiles,
Equation 31 IMS CSCF Unregistered
User Profiles formula names updated.
Equation 43 IMS ESCF Emergency
Session Setup Failures [per second],
Equation 44 IMS CSCF EATF SRVCC
Emergency Access Transfer Failures
[per second] added.
Equation 65 IMS MMTEL AS
Originating Session Set-up Success
Ratio and
Equation 66 IMS MMTEL AS
Terminating Session Set-up Success
Ratio updated to reflect ‘Session Setup
Counters in MMTel AS’
requirement105 65-0334/42413.
Equation 68 IMS MMTEL AS
Terminating Answer to Seizure Ratio
(ASR) updated to reflect counter name
change.
Equation 69 IMS MMTEL AS Failed
Originating Sessions [per second],
 Ericsson Internal
OPERAT. GUIDELINES 16 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 70 IMS MMTEL AS Failed

Terminating Sessions [per second]
modified to contain unregistered
failures and per second.
Equation 92 IMS MMTEL AS Failed
Originating Sessions for unregistered
PUI, per cause code
Equation 93 IMS MMTEL AS Failed
Terminating Sessions for unregistered
PUI, per cause code removed.
Equation 71 IMS MMTEL AS User
Rejected Originating Sessions [per
second],
Equation 72 IMS MMTEL AS User
Rejected Terminating Sessions [per
second],
Equation 73 IMS MMTEL AS Network
Rejected Originating Sessions [per
second],
Equation 74 IMS MMTEL AS Network
Rejected Terminating Sessions [per
second],
Equation 75 IMS MMTEL AS Service
Logic Rejected Originating Sessions
[per second],
Equation 76 IMS MMTEL AS Service
Logic Rejected Terminating Sessions
[per second],
Equation 77 IMS MMTEL AS External
Support Node Rejected Originating
Sessions [per second],
Equation 78 IMS MMTEL AS External
Support Node Rejected Terminating
Sessions [per second] added for
‘Session Setup Counters in MMTel AS’
requirement105 65-0334/42413.
Equation 79 IMS MMTEL AS Call
Released No Credit [per second],
Equation 80 IMS MMTEL AS Rejected
Parlay-X requests, per cause code [per
second] modified to be per second.
Equation 86 IMS SCC AS Originating
CS Session Completion Ratio,
Equation 88 IMS SCC AS Originating
PS Session Completion Ratio formula
names corrected.
Equation 90 IMS MMTEL AS Failed
Originating Session completion [per ,
Equation 91 IMS MMTEL AS Failed
Terminating Sessions completion,
Equation 92 IMS SCC AS Failed
 Ericsson Internal
OPERAT. GUIDELINES 17 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Originating CS Session completion,

Equation 93 IMS SCC AS Failed
Terminating CS Sessions completion,
Equation 94 IMS SCC AS Failed
Originating PS Session completion,
Equation 95 IMS SCC AS Failed
Terminating PS Sessions completion
added.
Equation 139 IMS SCC AS Single
Radio Voice Call Continuity (SRVCC)
Access Transfer Success Ratio
formula removed.
Equation 130 IMS SCC AS SR-VCC
Access Transfer Success Ratio
modified to cover Rel-10 SRVCC.
Equation 185 IMS SCC AS Number of
Simultaneous Sessions added.
Equation 229 IMS SBG Session
Completion Ratio, formula name
corrected.
Equation 231 IMS SBG SRVCC
Access Transfer Success Ratio
modified, no specific SBGv version.
Equation 217 IMS A-SBG De-
registration Success Ratio,
Equation 272 IMS SBG Hanging BGF
Termination Events,
Equation 272 IMS SBG Hanging BGF
Termination Events [per second]
added.
Equation 306 IMS MTAS SIP Orig
Requests Overload Rejection Ratio,
Equation 307 IMS MTAS SIP Term
Requests Overload Rejection Ratio
modified, unregisterd factors added.
Equation 328 IMS SBG Diameter
Permanent Failures [per second],
Equation 329 IMS SBG Diameter
Transient Failures [per second],
Equation 330 IMS SBG Diameter
Protocol Errors [per second] added.
Equation 331 IMS SBG Diameter Rx
NPLI Success Ratio corrected for SBG.

Section 8 Enriched Messaging (vEMe)

updated to cover vEMe, was EMe.

Section 4.9 IMS CSCF Charging

Accessibility,
Sections 9.4 IMS JavaSIP
Accessibility,
10.7.2 SS7 CAF Signaling M3UA
 Ericsson Internal
OPERAT. GUIDELINES 18 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Congestion,
11.5 SS7 CAF Signaling M3UA Link
Unavailability and Errors,
12.3 vBGF Media IP Interface
Performance Indicators added.

Equation 308 IMS MTAS SIP Unreg

Term Requests Overload Rejection
Ratio removed.

Service Uptake (HSS), Presence

(PGM) ENUM/DNS, IMS MGW and
BCE sections removed.

2 Introduction
2.1 Purpose

This document defines performance measures and formulas, R-KPI:s, based

on available counters in IMS with the intention to support the making of PM
reports for IP Multimedia Core Network (IMCN) system and nodes.

2.2 Scope

Performance management is the process to produce, transfer, collect, store

and present data, which can be used to verify the physical and logical
configuration of the network and to locate potential problems as early as
possible. Performance management is also used for monitoring of the
network characteristics so that Quality of Service (QoS) and Service Level
Agreements (SLA) may be supervised. The performance management for
IMS provides measurement data for the IMS domain contribution to end to
end service management in the form of Resource Service Key Performance
Indicators (R-KPI). The R-KPI concept and R-KPIs themselves are defined in
Key Performance Indicators for IMS System, ref. [8]. Another source for
selection of KPIs to be supported is TS 32.454 V11.0.0 Key Performance
Indicators (KPI) for the IP Multimedia Subsystem (IMS), ref. [5] and
corresponding measurement definitions TS 32.409 IMS performance
measurements, ref. [4]).

The following performance management areas are supported:

• Quality of service; accessibility and retainability of IMS services, ref.

ITU-T E.800, ref. [9], Key Performance Indicators for IMS System, ref.
[8].

• Service uptake; Number of IMS subscribers, number of registered IMS

subscribers, number of active users per mobile IMS service
 Ericsson Internal
OPERAT. GUIDELINES 19 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Thus IMS and Node Key Performance Indicators (KPI) and Performance
Indicators (PI) are listed in the document.

This document covers the Multi Media Telephony (MMTel) service. Support
functions like signal interworking and media gateway control functions (MGC),
and IP-IP Network-to-Network (NNI) and access gateway function are also
covered.

The signaling traffic aspects of performance management support for IMS is

published in an own document, IMCN Signaling Traffic Performance
Indicators, ref. [11], this document covers the areas:

• Licensing based on capacity parameters. Performance Indicators for

monitoring of capacity based licenses.

• Resource utilization; CPU, Memory and Disk utilization

• Signaling traffic; Signaling traffic performance indicators and formulas

are reported to support the dimensioning process

2.3 General information

2.3.1 Concepts

The concepts are defined in Key Performance Indicators for IMS System, ref.
[8]. The concepts used in this document are referenced below.

2.3.1.1 S-KPI - System Key Performance Indicator

S-KPIs are selected based on end user expectations to define the quality of
e.g. a voice call experience end to end. An S-KPI is used to define the Quality
of System Service (QoSS). The QoSS is a combination of the network
performance and the performance of the resources involved when delivering
the service end-to-end. Example of resource is IMCN network.

2.3.1.2 Resource Service

A Resource Service is a functional part of the realization structure. The

combination of several Resource Services builds a system that can deliver a
System Service. In this document, IMS system is defined as one of the
Resources needed to deliver a number of defined System Services.

Resource Services are implementation dependent.

2.3.1.3 R-KPI – Resource Service Key Performance Indicator.

An R-KPI describes the quality of a Resource Service e.g. accessibility,

retainability and integrity. This is the equivalent measure to an S-KPI but valid
for Resource Service. R-KPIs may be used to calculate S-KPIs, represent
performance of part of the e2e system and serve as basis for root cause
analysis.
 Ericsson Internal
OPERAT. GUIDELINES 20 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

2.3.1.4 Measured categories

The quality of a Resource Service is characterized by the following three

aspects:

- Accessibility – probability that the Resource Service can be

started when the end user starts a system service.

- Retainability – probability that the Resource Service can be kept

until the end-user stops the system service.

- Integrity – the ability of the Resource Service to deliver the data

with a certain speed and delay in a correct way so that the data is not lost or
compromised.

2.3.2 Formula naming

General information about formulas, e.g.

Equation 1. IMS Registration Success Ratio

IMS Re gSuccRatio =
cscfAcceptedRegistrations
cscfAcceptedRegistrations + cscfRejectedRegistrations

Equation name, in this case IMS Registration Success Ratio, is used as label
for the KPI presentation and therefore needs to be unique.

The formula end result, in this case IMSRegSuccRatio is not presented and
used as placeholder in the formula.

The scope of this document is changed to IP Multimedia Core Network

(IMCN) system. The formula naming prefix IMS will be kept for backwards
compatible reasons. Changing all formula names would be to costly for
external systems like Ericsson and 3PP OSS systems.

2.3.3 Service and node availability

The accessibility formulas in this document cover the accessibility of a system

service as such. If the complete accessibility with the node availability is
considered, then the system service accessibility shall be multiplied with the
availability of the node.

Example:

IMS Re gSuccRatioTotal = IMSRegSuccRatio * nodeAvalability

 Ericsson Internal
OPERAT. GUIDELINES 21 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

2.3.4 Aggregation on system level

The node measurements are delivered on a per node basis. The performance
indicators have an interest both on node level and system level. It is not
stated in the formulas whether they cover node or system level, it is an
assumption that both levels are available in a PM report package.

2.3.5 Trend analysis

The performance indicators and formulas specified in this document are

mainly intended for trend analysis. Due to the nature of the the subnetwork
manager performance manager application collection, storage and
presentation mechanisms, real time graphs are not supported.

2.3.6 Busy hour performance indicators

The busy hour performance indicators are calculated from measurements

reported per granularity period over a one hour sliding window, obtaining the
busy hour values. The busy hour calculation is not indicated in the formulas, it
is assumed to be a generic function of the subnetwork manager performance
manager application. The busy hour performance indicators are assumed to
be calculated in the Operations Support System (OSS) layer.

2.3.7 General for formulas on intensities

In this document, formulas on intensities, meaning events per time unit are
generally expressed as events per second or in some few cases, events per
hour. A reporting tool may select any time resolution, where events per
second and events per hour are the most prioritized.

2.3.8 Formula and measurement names and the formula editor

The formula editor used for this document uses presentation conventions in
formula and measurement names that introduce possible confusions.
Reserved function names, e.g. tan(), Re is presented with a specific format
also for formula and measurement names. This function presentations shall
be neglected. Example, the formula name IMSRegSuccRatio is presented as
IMS Re gSuccRatio. The intended formula name is IMSRegSuccRatio.

2.3.9 Node document versions

Node documents versions are not stated in the referenced documents. Node
documents with correct versions may be obtained from the same library from
where this document is published.
 Ericsson Internal
OPERAT. GUIDELINES 22 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

3 IMCN R-KPIs for VoLTE

The below Table 1 ‘IMCN R-KPI contribution to VoLTE KPIs’ provides a list of
IMCN nodes measurable performance indicators (R-KPI formulas) that best
represents the IMCN nodes contribution to the VoLTE service QoS
performance S-KPIs. The below R-KPIs has been selected with VoLTE
perspective, but reflects also Wi-Fi and fixed access except for the VoLTE
specifics (SR-VCC).

Base for the VoLTE KPIs is the VoLTE E2E Performance Management 4/195
83-HSC12034, ref. [10] document.

VoLTE KPI IMCN KPI IMCN KPI Name

Accessibility

Accessibility IMS Session Setup SBG

VoLTE-KPI-1 Equation IMS SBG Incoming Session Set-up

239 Success Ratio

VoLTE-KPI-2 Equation IMS SBG Outgoing Session Set-up

240 Success Ratio

Accessibility IMS Session Setup MMTel AS

VoLTE-KPI-3 Equation 84 IMS MMTEL AS Originating Session Set-

up Success Ratio

VoLTE-KPI-4 Equation 85 IMS MMTEL AS Terminating Session Set-

up Success Ratio

Accessibility IMS Session Setup SCC AS

VoLTE-KPI-5 Equation IMS SCC AS Originating Service

136 Centralization and Continuity (SCC) from
CS using CAP Registered and
Unregistered Success Ratio

Accessibility IMS Initial Registration CSCF

VoLTE-KPI-7 Equation 2 IMS CSCF Third Party Registration

Success Ratio

Accessibility IMS Initial Registration SBG

VoLTE-KPI-8 Equation IMS A-SBG Initial Registration Success

233 Ratio

Retainability

Retainability IMS Session Completion MMTel AS

 Ericsson Internal
OPERAT. GUIDELINES 23 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

VoLTE-KPI-9 Equation 95 IMS MMTel AS Orginating Session

Completion Ratio

VoLTE-KPI-10 Equation 96 IMS MMTel AS Terminating Session

Completion Ratio

Retainability IMS SRVCC Access Transfer Success Ratio (on the CS NW

IF)

VoLTE-KPI-11-1 Equation IMS SBG SRVCC Access Transfer

250 Success Ratio

VoLTE-KPI-11-2 Equation IMS SCC AS Enhanced Single Radio

138 Voice Call Continuity (SRVCC) Access
Transfer Success Ratio

VoLTE-KPI-11-3 Equation 18 IMS CSCF EATCF SRVCC Access

Transfer Success Ratio

Integrity

Integrity IMS Session Setup SBG

VoLTE-KPI-18 Equation IMS SBG Incoming Sessions Set-up Time

251 [milliseconds]

VoLTE-KPI-18 Equation IMS SBG Outgoing Sessions Set-up Time

252 [milliseconds]

Integrity IMS Initial Registration SBG

VoLTE-KPI-20 Equation IMS A-SBG Initial Registration Time

238 [milliseconds]

Integrity IMS Packet Loss SBG

VoLTE-KPI-23-1 Equation IMS SBG Media RTP Lost Packets Ratio

257

VoLTE-KPI-23-2 Equation IMS SBG Media RTP Out of Sequence

258 Packets Ratio

Emergency and Priority services related VoLTE Acessibility

VoLTE-KPI-25 Equation IMS MMTel AS Priority Call Successfully

154 Established Ratio

VoLTE-KPI-26 Equation IMS SBG Incoming Priority Session Set-up

242 Success Ratio

VoLTE-KPI-27 Equation IMS SBG Emergency Session Set-up

 Ericsson Internal
OPERAT. GUIDELINES 24 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

241 Success Ratio

VoLTE-KPI-28 Equation IMS A-SBG Emergency Initial Registration

234 Success Ratio
Table 1 IMCN R-KPI contribution to VoLTE KPIs

4 IMS CSCF
The R-KPIs specified in this section cover the CSCF product comprising
P-,I-,S-,E-CSCF.

4.1 Access Type tokens for Access Aware R-KPIs

This section specifies the common access-type tokens used in the CSCF
Access Aware R-KPIs.

Access Awareness R-KPIs are indexed on the Access Type (AT). AT is

Access Type value in the P-Access-Network-Information header, with one of
the following access-type tokens: "3GPP-GERAN","3GPP-UTRAN-FDD",
"3GPP-UTRAN-TDD", "3GPP-E-UTRAN-FDD", "3GPP-E-UTRAN-TDD",
"3GPP2-1X", "3GPP2-1X-HRPD", "3GPP2-UMB", "3GPP2-1X-Femto", "IEEE-
802.11", "IEEE-802.11a", "IEEE-802.11b", "IEEE-802.11g", "IEEE-802.11n",
"ADSL", "ADSL2", "ADSL2+", "RADSL", "SDSL", "HDSL", "HDSL2",
"G.SHDSL", "VDSL", "IDSL", or "DOCSIS", "IEEE-802.3", "IEEE-802.3a",
"IEEE-802.3e", "IEEE-802.3i", "IEEE-802.3j", "IEEE-802.3u", or "IEEE-
802.3ab", "IEEE-802.3ae", "IEEE-802.3ah", "IEEE-802.3ak", "IEEE-802.3aq",
"IEEE-802.3an", "IEEE-802.3y", "IEEE-802.3z" or "DVB-RCS2", from 3GPP
24.229 IP multimedia call control protocol based on Session Initiation Protocol
(SIP) and Session Description Protocol (SDP);Stage 3 specification.

The access-type tokens for WoWiFi is 801.11x, where ‘x’ is any character
including no character.

4.2 IMS CSCF Registration Accessibility

4.2.1 Definition

IMS CSCF Registration Accessibility is defined as the probability of being able

to successfully register, re-register and de-register into the IMS CSCF.

4.2.2 Formula

Equation 1. IMS CSCF Initial Registration Success Ratio

IMSCSCFInit Re gSuccRatio[%] = 100 *

(cscfAcceptedRegistrations +
cscfRegistrationsFailure.400 + cscfRegistrationsFailure.403)
(cscfAcceptedRegistrations + cscfRegistrationsFailure.SUM -
cscfRegistrationsFailure.401)
 Ericsson Internal
OPERAT. GUIDELINES 25 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Note that 401, Unauthorized response codes are not regarded as failures,
they are part of the authorization procedure.

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.2
Accessibility: IMS Initial Registration Success Ratio [%].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.1
Initial Registration Success Rate.

Equation 2. IMS CSCF Third Party Registration Success

Ratio

IMSCSCFThirdParty Re gSuccRatio[%] = 100 *

scscfThirdPartyRegistrationSuccess
)
(scscfThirdPartyRegistrationSuccess + scscfThirdPartyRegistrationFailure.SUM -
scscfThirdPartyRegistrationFailure.401)

Note that 401, Unauthorized response codes are not regarded as failures,
they are part of the authorization procedure.

Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS);

Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.4 Third party
registration success rate (of S-CSCF).

IMS S-CSCF Registration Accessibility per Access Type

R-KPIs per access type is used to distinguish between access types like LTE,
WiFi, Fixed accesss.

Equation 3. IMS S-CSCF Initial Registration Success Ratio

per Acesss Type

IMSSCSCFInit Re gSuccRatio[%] = 100 *

(scscfSuccessfulRegistrationPerAccess.AT +
scscfFailedRegistrationPerAccess.AT.400 +
scscfFailedRegistrationPerAccess.AT.403)
(scscfAttemptedRegistrationPerAccess.AT -
scscfFailedRegistrationPerAccess.AT.401)

Note: AT is Access Type value in the P-Access-Network-Information header

and that 401, Unauthorized response codes are not regarded as failures, they
are part of the authorization procedure.
 Ericsson Internal
OPERAT. GUIDELINES 26 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.2
Accessibility: IMS Initial Registration Success Ratio [%].
Counter Name Definition

cscfAcceptedRegistrations Number of successful registrations of

contact addresses. One contact address is
registered per registration request with one
or more associated public user identities.
Public user identities belonging to the same
implicit registration set is counted as one
registration.
Counter on CSCF node.
cscfRegistrationsFailure Number of initial registration attempts that
resulted in rejection. Each new contact
registered by a user will be counted as an
initial registration. The reasons for the
rejection include failed authentication and
authorization checks. Syntactically invalid
initial registration messages are not
counted. The counter is keyed with the SIP
response code. There is also a SUM key,
which is incremented for all response
codes.
Counter on CSCF node.
cscfCxDeregisterAnswersReceived Counts the number of received RTRs.
Counter on CSCF node.

cscfCxDeregisterAnswersSuccess Counts the number of sent RTAs with

Diameter result code
"DIAMETER_SUCCESS”.
Counter on CSCF node.
cscfAcceptedReregistrations Number of successful re-registrations of
contact addresses. One contact address is
re-registered per re-registration request with
one or more associated public user
identities. Public user identities belonging to
the same implicit registration set is counted
as one registration.
Counter on CSCF node.
cscfReregistrationsFailure Number of reregistration attempts that
resulted in rejection. The reasons for the
rejection include failed authentication and
authorization checks. Syntactically invalid
reregistration messages are not counted.
The counter is keyed with the SIP response
code. There is also a SUM key, which is
incremented for all response codes.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 27 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfThirdPartyRegistrationSuccess Number of successful third party registration

procedures in the S-CSCF.
Counter on S-CSCF node.
scscfThirdPartyRegistrationFailure Number of failed third party registration
procedures in the S-CSCF. This counter is
keyed with the SIP response code. There is
also a SUM key, which is incremented for all
response codes.
Counter on S-CSCF node.
scscfAttemptedRegistrationPerAccess This counter is the number of attempted
initial registrations (first contact or adding
new contact) per access type in S-CSCF.
The counter is keyed on the access type
value in P-Access-Network-Information
header in the REGISTER request. If the
PANI header is not received, "DEFAULT" is
used as key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
This counter is the number of successful
scscfSuccessfulRegistrationPerAcces initial registrations (first contact or adding
s new contact) per access type in S-CSCF.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the REGISTER request. If the
PANI header is not received, "DEFAULT" is
used as key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
This counter is the number of non-
scscfFailedRegistrationPerAccess successful initial registrations (first contact
or adding new contact) per access type.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the REGISTER request and error
code (3xx/4xx/5xx/6 xx) from the response. If
the PANI header is not received,
"DEFAULT" is used as key. The S-CSCF
will also always increment the counter once
with the key "SUM".
Counter on CSCF node.

Reference:CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.3 IMS CSCF Registration Retainability

4.3.1 Definition

IMS CSCF Registration Retainability is defined as the probability of being able

to successfully re-register and successfully complete (normally terminate) an
active registration in IMS CSCF.
 Ericsson Internal
OPERAT. GUIDELINES 28 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

4.3.2 Formula

Equation 4. IMS CSCF Reregistration and Deregistration

Success Ratio

IMSCSCF Re AndDeregSuccRatio[%] = 100 * (

(cscfAcceptedReregistrations +
cscfReregistrationsFailure.400 + cscfReregistrationsFailure.403 +
cscfAcceptedDeregistrations + cscfCxDeregisterAnswersSuccess)
(cscfAcceptedReregistrations +
cscfReregistrationsFailure.SUM − cscfReregistrationsFailure.401 +
cscfAcceptedDeregistrations +
cscfDeregistrationsFailure.SUM − cscfDeregistrationsFailure.401 +
cscfCxDeregisterRequestReceived)

Note that 401, Unauthorized response codes are not regarded as failures,
they are part of the authorization procedure.

The re-registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”.

Equation 5. IMS CSCF Re-registration Success Ratio

IMSCSCF Re regSuccRatio[%] = 100 *

(cscfAcceptedReregistrations +
cscfReregistrationsFailure.400 + cscfReregistrationsFailure.403)
(cscfAcceptedReregistrations + cscfReregistrationsFailure.SUM -
cscfReregistrationsFailure.401)

Note that 401, Unauthorized response codes are not regarded as failures,
they are part of the authorization procedure.

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”.

IMS S-CSCF Registration Retainability per Access Type

Equation 6. IMS S-CSCF Reregistration and Deregistration

Success Ratio per Access Type
 Ericsson Internal
OPERAT. GUIDELINES 29 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCSCF Re AndDeregSuccRatio[%] = 100 *

(scscfSuccessfulReregistrationPerAccess.AT +
scscfFailedReregistrationPerAccess.AT.400 +
scscfFailedReregistrationPerAccess.AT.403 +
scscfSuccessfulDeregistrationPerAccess.AT +
scscfFailedDeregistrationPerAccess.AT.400 +
scscfFailedDeregistrationPerAccess.AT.403)
(scscfAttemptedReregistrationPerAccess.AT −
scscfFailedReregistrationPerAccess.AT.401 +
scscfAttemptedDeregistrationPerAccess.AT −
scscfFailedDeregistrationPerAccess.AT.401)

Note: AT is Access Type value in the P-Access-Network-Information header

and that 401, Unauthorized response codes are not regarded as failures, they
are part of the authorization procedure.

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”..

References for this section: Key Performance Indicators for IMS System, ref.
[8] Section 3.2.2 Retainability: IMS Registration Completion Ratio [%],
Reference: Key Performance Indicators (KPI) for the IP Multimedia
Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.5
Reregistration Success Rate.
Counter Name Definition

cscfAcceptedDeregistrations Number of successful de-registrations of

contact addresses or public user identities.
If one contact address is de-registered then
all associated public user identities
belonging to the contact address are
removed. Public user identities belonging to
the same implicit registration set is counted
as one registration. If a public user identity
is de-registered then all associated contact
addresses belonging to the public user
identity are de-registered.
Counter on CSCF node.
cscfDeregistrationsFailure Number of deregistration attempts that
resulted in rejection. The reasons for the
rejection include failed authentication and
authorization checks. Syntactically invalid
deregistration messages are not counted.
This counter is keyed with the SIP response
code. There is also a SUM key, which is
incremented for all response codes.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 30 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfAcceptedReregistrations Number of successful re-registrations of
contact addresses. One contact address is
re-registered per re-registration request with
one or more associated public user
identities. Public user identities belonging to
the same implicit registration set is counted
as one re-registration.
Counter on CSCF node.
cscfReregistrationsFailure Number of initial registration attempts that
resulted in rejection. Each new contact
registered by a user will be counted as an
initial registration. The reasons for the
rejection include failed authentication and
authorization checks. Syntactically invalid
initial registration messages are not
counted. The counter is keyed with the SIP
response code. There is also a SUM key,
which is incremented for all response
codes.
Counter on CSCF node.
cscfCxDeregisterRequestReceived Counts the number of received RTRs.
Counter on CSCF node.
cscfCxDeregisterAnswersSuccess Counts the number of sent RTAs with
Diameter result code
"DIAMETER_SUCCESS”.
Counter on CSCF node.
scscfAttemptedReregistrationPerAcce This counter is the number of attempted
ss reregistrations per access type in S-CSCF.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the Re-REGISTER request. If the
PANI header is not received, "DEFAULT" is
used as key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
scscfSuccessfulReregistrationPerAcce This counter is the number of successful
ss reregistrations per access type in S-CSCF.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the Re-REGISTER request. If the
PANI header is not received, "DEFAULT" is
used as key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 31 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfFailedReregistrationPerAccess This counter is the number of non-
successful reregistrations per access type.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the Re-REGISTER request and
error code (3xx/4xx/5xx/6 xx) from the
response. If the PANI header is not
received, "DEFAULT" is used as key. The
S-CSCF will also always increment the
counter once with the key "SUM".
Counter on CSCF node.
scscfAttemptedDeregistrationPerAcce This counter is the number of attempted
ss user initiated deregistrations per access
type in S-CSCF. The counter is keyed on
the access type value in the P-Access-
Network-Information header in the De-
REGISTER request. If the PANI header is
not received, "DEFAULT" is used as key.
The S-CSCF will also always increment the
counter once with the key "SUM".
Counter on CSCF node.
scscfSuccessfulDeregistrationPerAcce This counter is the number of successful
ss user initiated deregistrations per access
type in S-CSCF. The counter is keyed on
the access type value in the P-Access-
Network-Information header in the De-
REGISTER request. If the PANI header is
not received, "DEFAULT" is used as key.
The S-CSCF will also always increment the
counter once with the key "SUM".
Counter on CSCF node.
scscfFailedDeregistrationPerAccess This counter is the number of non-
successful deregistrations per access type.
The counter is keyed on the access type
value in the P-Access-Network-Information
header in the De-REGISTER request and
error code (3xx/4xx/5xx/6 xx) from the
response. If the PANI header is not
received, "DEFAULT" is used as key. The
S-CSCF will also always increment the
counter once with the key "SUM".
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].
 Ericsson Internal
OPERAT. GUIDELINES 32 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

4.4 IMS CSCF Dropped Registrations Ratio

4.4.1 Definition

IMS CSCF Dropped Registrations Ratio is defined as the probability of

abnormal termination (dropped) of an active registration in CSCF. The reason
for the abnormal termination may be lost PDP context or UE IP address, that
is, causes outside of CSCF. IMS CSCF Dropped Registrations Ratio is an
alternative to IMS CSCF Registrations Completion Ratio to express IMS
Registration Retainability.

4.4.2 Formula

Equation 7. IMS CSCF Dropped Registrations Ratio

IMS Re gDroppedRatio[%] = 100 * (

(cscfDeregistrationsFailure.SUM - cscfDeregistrationsFailure.401 +
cscfCxDeregisterRequestReceived - cscfCxDeregisterAnswersSuccess)
(cscfAcceptedDeregistrations + cscfDeregistrationsFailure.SUM -
cscfDeregistrationsFailure.401 + cscfCxDeregisterRequestReceived))

Note that 401, Unauthorized response codes are not regarded as failures,
they are part of the authorization procedure.
Counter Name Definition

cscfAcceptedDeregistrations Number of successful de-registrations of

contact addresses or public user identities.
If one contact address is de-registered then
all associated public user identities
belonging to the contact address are
removed. Public user identities belonging to
the same implicit registration set is counted
as one registration. If a public user identity
is de-registered then all associated contact
addresses belonging to the public user
identity are de-registered.
Counter on CSCF node.
cscfDeregistrationsFailure Number of deregistration attempts that
resulted in rejection. The reasons for the
rejection include failed authentication and
authorization checks. Syntactically invalid
deregistration messages are not counted.
This counter is keyed with the SIP response
code. There is also a SUM key, which is
incremented for all response codes.
Counter on CSCF node.
cscfCxDeregisterRequestReceived Counts the number of received RTRs.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 33 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfCxDeregisterAnswersSuccess Counts the number of sent RTAs with
Diameter result code
"DIAMETER_SUCCESS”.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.5 IMS CSCF Session Setup Accessibility

4.5.1 Definition

IMS CSCF Session Accessibility is defined as the probability of being able to

successfully initiate a session into the IMS CSCF.

4.5.2 Formula

Session accessibility, these KPIs are also called Network Efficiency Ratio
(NER) because they characterize the network performance. It is the
percentage of calls where the called user was alerted for a new call and
where user behavior is eliminated.

Equation 8. IMS CSCF Originating Session Set-up Success

Ratio

IMSCSCFOrgSessSetupSuccRatio[%] = 100 *
(scscfOriginatingInviteSuccessfulEstablishedNoAs.sum −
scscfOriginatingInviteSuccessfulEstablishedNoAs.181 +
scscfOriginatingInviteSuccessfulEstablishedToAs.sum −
scscfOriginatingInviteSuccessfulEstablishedToAs.181 +
scscfOriginatingInviteCancelledBeforeEarlyDialog)
(scscfOriginatingInviteNoAsAttempts + cscfOriginatingInviteToAsAttempts)

Equation 9. IMS CSCF Terminating Session Set-up Success

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 34 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSCSCFTermSessSetupSuccRatio[%] = 100 *
(scscfTerminatingInviteSuccessfulEstablishedNoAs.sum −
scscfTerminatingInviteSuccessfulEstablishedNoAs.181 +
scscfTerminatingInviteSuccessfulEstablishedToAs.sum −
scscfTerminatingInviteSuccessfulEstablishedToAs.181 +
scscfTerminatingInviteCancelledBeforeEarlyDialog)
(scscfTerminatingInviteNoAsAttempts + cscfTerminatingInviteToAsAttempts)

Note1. The SuccessfulEstablished counters are keyed on the response code

(18x, 20x), the key sum represents the sum of all successful session
established responses with the exception of Redirection (181) which is
subtracted.

Note2: The IMS S-CSCF Session Setup performance indicators will not reach
100% since user factors are not covered by the formulas, such as User is not
registered, Forbidden (403), User is Not Found (404) and so on

Note that Equation 8 is reflecting the KPI referenced above where the
originating user initiates a session set-up. Equation 9 is a supporting formula
for the terminating case.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.9
Session Establishment Network Success Rate.

IMS S-CSCF Session Setup Accessibility per Access Type

Equation 10. IMS CSCF Originating Session Set-up Success

Ratio per Access Type

IMSCSCFOrgSessSetupSuccRatio[%] = 100 *
scscfOrigSuccessfulEstablishedInvitePerAccess.AT
scscfOrigAttemptedInvitePerAccess.AT

Equation 11. IMS CSCF Terminating Session Set-up Success

Ratio per Access Type

IMSCSCFTermSessSetupSuccRatio[%] = 100 *
scscfTermSuccessfulEstablishedInvitePerAccess.AT
scscfTermAttemptedInvitePerAccess.AT

Note1: AT is Access Type value in the P-Access-Network-Information header.

 Ericsson Internal
OPERAT. GUIDELINES 35 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Note2: The IMS S-CSCF Session Setup per Access Type performance
indicators will not reach 100% since user factors are not covered by the
formulas, such as User is not registered, Forbidden (403), User is Not Found
(404) and so on.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.9
Session Establishment Network Success Rate.

IMS S-CSCF Session Setup per Media Type

The R-KPIs specified in this section cover the S-CSCF Session Setup per
Media Performance Indicators.

Please note that the counters for S-CSCF Session Setup per Media
Performance Indicators are by default disabled. In order to enable them, the
CSCF configuration parameter scscfMediaTypeCountersEnabled should be
set to true.

Please also note by enabling the counters for S-CSCF Session Setup per
Media Performance Indicators the CSCF load increases approximately 1%.

Equation 12. IMS CSCF Originating Session Set-up Success

Ratio per Media Type

IMSCSCFOrgSessSetupSuccRatio[%] = 100 *
scscfOrigSuccessfulEstablishedSessionPerMedia.MT
scscfOrigAttemptedSessionPerMedia.MT

Equation 13. IMS CSCF Terminating Session Set-up Success

Ratio per Media Type

IMSCSCFTermSessSetupSuccRatio[%] = 100 *
cscfTermSuccessfulEstablishedSessionPerMedia.MT
scscfTermAttemptedSessionPerMedia.MT

Note1: MT is Media Type value present in the first SDP answer received.

Note2: The IMS S-CSCF Session Setup per Media Type performance
indicators will not reach 100% since user factors are not covered by the
formulas, such as User is not registered, Forbidden (403), User is Not Found
(404) and so on.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%].
 Ericsson Internal
OPERAT. GUIDELINES 36 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.9
Session Establishment Network Success Rate.

Equation 14. IMS CSCF Emergency Session Set-up Success

Ratio

IMSCSCFEmergencySessSuccRatio[%] = 100 *
ecscfSuccessfulEmergencySessions
(ecscfFailedEmergencySessions.sum +
ecscfSuccessfulEmergencySessions)

Session accessibility; Answer to Seizure Ratio (ASR). It is the percentage of

answered telephone calls with respect to the total call volume.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.9
Session Establishment Network Success Rate.

Equation 15. IMS CSCF Originating Session Answer to Seizure

Ratio (ASR)

IMSCSCFOrgSessAnswerToSeizureRatio[%] = 100 *
(scscfOriginatingInviteNoAsAnswered + scscfOriginatingInviteToAsAnswered)
(scscfOriginatingInviteNoAsAttempts + cscfOriginatingInviteToAsAttempts)

Equation 16. IMS CSCF Terminating Session Answer to

Seizure Ratio (ASR)

IMSCSCFTermSessAnswerToSeizureRatio[%] = 100 *
(scscfTerminatingInviteNoAsAnswered + scscfTerminatingInviteToAsAnswered)
(scscfTerminatingInviteNoAsAttempts + cscfTerminatingInviteToAsAttempts)
These equations are based on measurements in CSCF node.

Counter Name Definition

scscfOriginatingInviteNoAsAttempts Number of times initial SIP INVITE requests

received by the S-CSCF on the originating
side, no Application Server is invoked.

cscfOriginatingInviteToAsAttempts Number of times an initial SIP INVITE

request attempts received by the S-CSCF
on the originating side on Mw or (Gm
interface for a colocated CSCF), resulting in
an AS invocation on ISC interface.
 Ericsson Internal
OPERAT. GUIDELINES 37 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOriginatingInviteSuccessfulEstabl Number of times the first early dialog

ishedNoAs response (typically 180 Ringing) to initial
SIP INVITE without AS invocations is
transmitted by originating S-CSCF on Mw.
The counter is stepped on 2xx response if
no early dialog response was received.
The counter is keyed on transmitted
response code. Extra key 'sum' represents
the total.
Counter on CSCF node.
scscfOriginatingInviteSuccessfulEstabl Number of times the first early dialog
ishedToAs response (typically 180 Ringing) to initial
SIP INVITE with one or more AS
invocations is transmitted by S-CSCF on
Mw. The counter is stepped on 2xx
response if no early dialog response was
received.
The counter is keyed on transmitted
response code. Extra key 'sum' represents
the total.
Counter on CSCF node.
scscfOriginatingInviteCancelledBefore Number of cancelled session
EarlyDialog establishments on originating S-CSCF prior
to transmitting early dialog response.
Incremented when originating S-CSCF
receives a 487 Request Terminated
response that followed a CANCEL request.
This counter is only incremented if CANCEL
is received.
Counter on CSCF node.
scscfOriginatingInviteNoAsFailed Number of times non-successful responses
to initial SIP INVITE without AS invocations
transmitted by S-CSCF on Mw on the
originating side.
This counter is stepped by originating S-
CSCF when the response is transmitted on
Mw. Incremented for these types of events:
- Transmission of 3xx-6xx class SIP INVITE
response on Mw interface, except 407
Proxy authentication required;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 38 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOriginatingInviteToAsFailed Number of times non-successful responses

to initial SIP INVITE with one or more AS
invocations are transmitted by S-CSCF on
Mw on the originating side.
This counter is stepped by originating S-
CSCF when the response is transmitted on
Mw. Incremented for these types of events:
- Transmission of 3xx-6xx class SIP INVITE
response on Mw interface, except 407
Proxy authentication required;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
scscfTerminatingInviteNoAsAttempts Number of times initial SIP INVITE requests
received by the S-CSCF on the terminating,
no Application Server is invoked.
Counter on CSCF node.
cscfTerminatingInviteToAsAttempts Number of times an initial SIP INVITE
request attempts received by the S-CSCF
on the terminating side on Mw interface,
resulting in an AS invocation on ISC
interface.
Counter on CSCF node.
scscfTerminatingInviteSuccessfulEsta Number of times the first early dialog
blishedNoAs response (typically 180 Ringing) to initial
SIP INVITE without AS invocations is
transmitted by terminating S-CSCF. The
counter is stepped on 2xx response if no
early dialog response was received.
The counter is keyed on transmitted
response code. Extra key 'sum' represents
the total.
Counter on CSCF node.
scscfTerminatingInviteSuccessfulEsta Number of times the first early dialog
blishedToAs response (typically 180 Ringing) to initial
SIP INVITE with one or more AS
invocations is transmitted by terminating S-
CSCF. The counter is stepped on 2xx
response if no early dialog response was
received.
The counter is keyed on transmitted
response code. Extra key 'sum' represents
the total.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 39 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTerminatingInviteCancelledBefor Number of cancelled session

eEarlyDialog establishments on terminating S-CSCF prior
to transmitting early dialog response.
Incremented when terminating S-CSCF
receives a 487 Request Terminated
response that followed a CANCEL request.
This counter is only incremented if CANCEL
is received.
Counter on CSCF node.
scscfTerminatingInviteNoAsFailed Number of times non-successful responses
to initial SIP INVITE without AS invocations
are transmitted by S-CSCF on the
terminating side.
This counter is stepped by terminating S-
CSCF when the response is transmitted.
Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back by S-CSCF;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
scscfTerminatingInviteToAsFailed Number of times non-successful responses
to initial SIP INVITE with one or more AS
invocations are transmitted by S-CSCF on
the terminating side.
This counter is stepped by terminating S-
CSCF when the response is transmitted.
Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back by S-CSCF;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
scscfOrigAttemptedInvitePerAccess This counter is the number of attempted
INVITE session establishments per access
type in originating S-CSCF. The counter is
keyed on the stored access type value from
P-Access-Network-Info in REGISTER
request for the served user. If no access
type has been stored, "DEFAULT" is used
as the counter key. The S-CSCF will also
always increment the counter once with the
key "SUM".
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 40 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOrigSuccessfulEstablishedInvite This counter is the number of attempted

PerAccess INVITE session establishments per access
type in originating S-CSCF. The counter is
keyed on the stored access type value from
P-Access-Network-Info in REGISTER
request for the served user. If no access
type has been stored, "DEFAULT" is used
as the counter key. The S-CSCF will also
always increment the counter once with the
key "SUM".
Counter on CSCF node.
scscfOrigFailedInvitePerAccess This counter is the number of non-
successful INVITE session establishments
per access type in originating S-CSCF. The
counter is keyed on the stored access type
value from P-Access-Network-Info in
REGISTER request for the served user and
the error code (3xx/4xx/5xx/6 xx) in the
response. If no access type has been
stored, "DEFAULT" is used as the counter
key. The S-CSCF will also always increment
the counter once with the key "SUM"..
Counter on CSCF node.
scscfTermAttemptedInvitePerAccess This counter is the number of attempted
INVITE session establishments per access
type in terminating S-CSCF. The counter is
keyed on the stored access type value from
P-Access-Network-Info in REGISTER
request for the served user. If no access
type has been stored, "DEFAULT" is used
as the counter key. The S-CSCF will also
always increment the counter once with the
key "SUM".
Counter on CSCF node.
scscfTermSuccessfulEstablishedInvite This counter is the number of attempted
PerAccess INVITE session establishments per access
type in terminating S-CSCF. The counter is
keyed on the stored access type value from
P-Access-Network-Info in REGISTER
request for the served user. If no access
type has been stored, "DEFAULT" is used
as the counter key. The S-CSCF will also
always increment the counter once with the
key "SUM".
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 41 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTermFailedInvitePerAccess This counter is the number of non-

successful INVITE session establishments
per access type in terminating S-CSCF. The
counter is keyed on the stored access type
value from P-Access-Network-Info in
REGISTER request for the served user and
the error code (3xx/4xx/5xx/6 xx) in the
response. If no access type has been
stored, "DEFAULT" is used as the counter
key. The S-CSCF will also always increment
the counter once with the key "SUM"..
Counter on CSCF node.
scscfOrigAttemptedSessionPerMedia Number of attempted INVITE session
establishments per media type in originating
S-CSCF.
It is incremented once for each unique
media type present in the first SDP offer
received during the call establishment. The
counter is keyed for the following media
types: Application, Audio, Control, Data,
Image, Message, Model, Multipart, Text and
Video. The "DEFAULT" key is used for
unknown media types. S-CSCF also
increments the counter with key "SUM"
once per media type.
Counter on CSCF node.
scscfOrigSuccessfulEstablishedSessi Number of successful INVITE session
onPerMedia establishments per media type in originating
S-CSCF.
It is incremented once for each unique
media type present in the first SDP answer
received. The first SDP answer could be
received during call establishment or in the
successful answer. The counter has two
keys, the SIP response code of the SIP
response that carried the SDP answer, and
the media type that can be one of the
following: Application, Audio, Control, Data,
Image, Message, Model, Multipart, Text and
Video. The "DEFAULT" key is used for
unknown media types. S-CSCF also
increments the counter with key "SUM"
once per media type.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 42 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOrigFailedSessionPerMedia Number of unsuccessful INVITE session

establishments per media type in originating
S-CSCF.
It is incremented once for each unique
media type present in the first SDP offer
received during the call establishment. The
counter has two keys, the SIP response
code (3xx/4xx/5xx/6 xx), and the media type
that can be one of the following: Application,
Audio, Control, Data, Image, Message,
Model, Multipart, Text and Video. The
"DEFAULT" key is used for unknown media
types. S-CSCF also increments the counter
with key "SUM" once per media type.
Counter on CSCF node.
scscfTermAttemptedSessionPerMedia Number of attempted INVITE session
establishments per media type in
terminating S-CSCF.
It is incremented once for each unique
media type present in the first SDP offer
received during the call establishment. The
counter is keyed for the following media
types: Application, Audio, Control, Data,
Image, Message, Model, Multipart, Text and
Video. The "DEFAULT" key is used for
unknown media types. S-CSCF also
increments the counter with key "SUM"
once per media type.
Counter on CSCF node.
scscfTermSuccessfulEstablishedSessi Number of successful INVITE session
onPerMedia establishments per media type in
terminating S-CSCF.
It is incremented once for each unique
media type present in the first SDP answer
received. The first SDP answer could be
received during call establishment or in the
successful answer. The counter has two
keys, the SIP response code of the SIP
response that carried the SDP answer, and
the media type that can be one of the
following: Application, Audio, Control, Data,
Image, Message, Model, Multipart, Text and
Video. The "DEFAULT" key is used for
unknown media types. S-CSCF also
increments the counter with key "SUM"
once per media type.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 43 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTermFailedSessionPerMedia Number of unsuccessful INVITE session

establishments per media type in
terminating S-CSCF.
It is incremented once for each unique
media type present in the first SDP offer
received during the call establishment. The
counter has two keys, the SIP response
code (3xx/4xx/5xx/6 xx), and the media type
that can be one of the following: Application,
Audio, Control, Data, Image, Message,
Model, Multipart, Text and Video. The
"DEFAULT" key is used for unknown media
types. S-CSCF also increments the counter
with key "SUM" once per media type.
Counter on CSCF node.

ecscfFailedEmergencySessions The number of non-successful final

response to an emergency call set up.
The counter is incremented at reception of
any non-successful final response to an
emergency call setup or upon an internal
error when handling the emergency
session. It will be keyed on the final
response failure code. Undocumented key
‘sum’ for sum of sum of response failure
codes
Counter on CSCF node.

ecscfSuccessfulEmergencySessions The number of 2xx successful final

response on an emergency call set up.
The counter is incremented at reception of a
2xx successful final response on an
emergency call setup.
Counter on CSCF node.

scscfOriginatingInviteNoAsAnswered The number of answered session

establishments in originating S-CSCF, no
AS invocations.
Incremented when the first final 2xx
response to initial SIP INVITE is transmitted
by originating S-CSCF on Mw.
Counter on CSCF node.

scscfOriginatingInviteToAsAnswered The number of answered session

establishments in originating S-CSCF, with
one or more AS invocations.
Incremented when the first final 2xx
response to initial SIP INVITE is transmitted
by originating S-CSCF on Mw.
Counter on CSCF node.

scscfTerminatingInviteNoAsAnswered The number of answered session

establishments in terminating S-CSCF, no
AS invocations.
Incremented when the first final 2xx
response to initial SIP INVITE is transmitted
by terminating S-CSCF on Mw.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 44 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTerminatingInviteToAsAnswered The number of answered session

establishments in terminating S-CSCF, with
one or more AS invocations.
Incremented when the first final 2xx
response to initial SIP INVITE is transmitted
by terminating S-CSCF on Mw.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.6 IMS CSCF Session Retainability

4.6.1 Definition

IMS CSCF Session Retainability is defined as the probability of being able to

successfully complete (normally terminate) an active session in the IMS
CSCF once it has been successfully set-up.

4.6.2 Formula

Equation 17. IMS CSCF Session Completion Ratio

IMSCSCFSessCompRatio[%] = 100 * (
sipStatsByeIns
( ))
sipStatsByeIns + cscfExpiredSessions

Reference: Key Performance Indicators for IMS System, ref. [8] Section
Retainability: IMS Session Completion Ratio [%].

The formula is approximate, since sipStatsByeIns is used. The measurement

sipStatsByeIns counts the session completion trials, whereas session
successful completions are required.

CSCF ATCF SRVCC Access Transfer

Equation 18. IMS CSCF EATCF SRVCC Access Transfer

Success Ratio

IMSCSCEATFSRVCCAccTransferRatio[%] = 100 *
eatfSuccessfulEmergencySessionAccessTransfer
(eatfSuccessfulEmergencySessionAccessTransfer +
eatfFailedEmergencySessionAccessTransfer.SUM)

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.2.3
Retainability: SRVCC Access Transfer Success Ratio (IMS part) [%].
 Ericsson Internal
OPERAT. GUIDELINES 45 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfExpiredSessions Number of sessions that have been

removed due to session expiry.
Counter on CSCF node.

sipStatsByeIns The total number of BYE requests received,

including retransmissions. This counter is
keyed with the IP address of the application
it is received from.
Counter on CSCF node.
eatfSuccessfulEmergencySessionAcc The number of successful Emergency SR-
essTransfer VCC Access Transfer in EATF.
Incremented by 1 when EATF receives an
ACK of an emergency SR-VCC access
transfer request from the CS UE.
Counter on CSCF node.
eatfFailedEmergencySessionAccessT The number of failed Emergency SR-VCC
ransfer Access Transfer in EATF. This counter is
keyed on the received negative response
code (3xx-6xx) if the negative response
comes from the other nodes. This counter is
keyed on the sent negative response code if
it is generated by EATF. This counter is also
keyed on SUM. The SUM key represents
the total number of failed Emergency SR-
VCC Access Transfer in EATF.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.7 IMS CSCF Dropped Sessions Ratio

4.7.1 Definition

IMS CSCF Dropped Sessions Ratio is defined as the probability of abnormal

termination of an active session in the IMS CSCF. IMS CSCF Dropped
Sessions Ratio is an alternative to IMS CSCF Session Completion Ratio to
express IMS CSCF Session Retainability.

4.7.2 Formula

Equation 19. IMS CSCF Dropped Sessions Ratio

IMSCSCFSessDroppedRatio[%] = 100 *
cscfExpiredSessions
sipStatsByeIns + cscfExpiredSessions

Note to Equation 19 IMS CSCF Dropped Sessions Ratio; the formula is

approximate, since sipStatsByeIns is used. sipStatsByeIns counts the session
completion tries, whereas session successful completions are required.
 Ericsson Internal
OPERAT. GUIDELINES 46 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.2.1
Call Drop Rate of IMS Sessions.
Counter Name Definition

cscfExpiredSessions Number of sessions that have been

removed due to session expiry.
Counter on CSCF node.

sipStatsByeIns The total number of BYE requests received,

including retransmissions. This counter is
keyed with the IP address of the application
it is received from.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6 and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765 0209-V1,
ref. [14].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.2.1
Call Drop Rate of IMS Sessions.

4.8 IMS CSCF Session Set-up Integrity

4.8.1 Definition

The time period between when the IMS CSCF receives an SIP INVITE
corresponding to a user initiates an IMS session by e.g. pressing the session
set-up button, and when the IMS CSCF sends a SIP 180 Ringing or SIP 200
OK response corresponding to the originating user receives a callee alerted
notification, or in the case that terminating phone is configured to use
automatic answer, the originating user receives a notification that the session
has been set-up.

4.8.2 Formula

Equation 20. IMS CSCF Originating Sessions Set-up Time

[milliseconds]

IMSCSCFOrgSessSessionSetupTime[ms] =
scscfAccumulatedOriginatingSessionEstablishmentTime
(scscfOriginatingInviteSuccessfulEstablishedNoAs.sum +
scscfOriginatingInviteSuccessfulEstablishedToAs.sum)

Equation 21. IMS CSCF Terminating Sessions Set-up Time

[milliseconds]
 Ericsson Internal
OPERAT. GUIDELINES 47 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSCSCFTermSessSessionSetupTime[ms] =
scscfAccumulatedTerminatingSessionEstablishmentTime
(scscfTermiginatingInviteSuccessfulEstablishedNoAs.sum +
scscfTerminatingInviteSuccessfulEstablishedToAs.sum)

Note that Equation 20 is reflecting the R-KPI referenced above where the
originating user initiates a session set-up. Equation 21 is a supporting formula
for the terminating case.

IMS S-CSCF Session Duration per Access Type

Equation 22. IMS S-CSCF Originating Session Duration per

Access Type [Seconds]

IMSSCSCFOrgSessDuration[S] =
scscfOrigAccumulatedCallTimePerAccess.AT
scscfOrigAnsweredInvitePerAccess.AT)

Equation 23. IMS S-CSCF Terminating Sessions Duration per

Access Type [Seconds]

IMSSCSCFTermSessDuration[S] =
scscfTermAccumulatedCallTimePerAccess.AT
scscfTermAnsweredInvitePerAccess.AT
Note: AT is Access Type value in the P-Access-Network-Information header.

References for this section: Key Performance Indicators for IMS System, ref.
[8] Section 3.3.1 Integrity: IMS Session Set-up Time [s],
Reference: Key Performance Indicators (KPI) for the IP Multimedia
Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.2
Session Setup Time (Mean).
Counter Name Definition

scscfAccumulatedOriginatingSessionE The accumulated duration between

stablishmentTime receiving SIP INVITE in originating S-CSCF
and transmitting the first early dialog
response (typically 180 Ringing) or 200OK if
not early dialog response was received.
Counter on CSCF node.
scscfOriginatingInviteSuccessfulEstabl Number of times the first early dialog
ishedNoAs response (typically 180 Ringing) to initial
SIP INVITE without AS invocations is
transmitted by originating S-CSCF on Mw.
The counter is stepped on 2xx response if
no early dialog response was received.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 48 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOriginatingInviteSuccessfulEstabl Number of times the first early dialog

ishedToAs response (typically 180 Ringing) to initial
SIP INVITE with one or more AS
invocations is transmitted by S-CSCF on
Mw. The counter is stepped on 2xx
response if no early dialog response was
received.
Incremented when the first early dialog
response to SIP INVITE is transmitted by S-
CSCF or when 2xx response is transmitted
if no early dialog response was received.
When transmitting multiple responses due
to forking, it is the first response only that is
counted. The counter is keyed on
transmitted response code. Extra key 'sum'
represents the total.
Counter on CSCF node.
scscfAccumulatedTerminatingSession The accumulated duration between
EstablishmentTime receiving SIP INVITE in terminating S-
CSCF and transmitting the first early dialog
response (typically 180 Ringing) or 200OK if
not early dialog response was received.
Counter on CSCF node.
scscfTerminatingInviteSuccessfulEsta Number of times the first early dialog
blishedNoAs response (typically 180 Ringing) to initial
SIP INVITE without AS invocations is
transmitted by terminating S-CSCF. The
counter is stepped on 2xx response if no
early dialog response was received.
Incremented when the first early dialog
response to SIP INVITE is transmitted by S-
CSCF or when 2xx response is transmitted
if no early dialog response was received.
When transmitting multiple responses due
to forking, it is the first response only that is
counted. The counter is keyed on
transmitted response code. Extra key 'sum'
represents the total.
Counter on CSCF node.
scscfTerminatingInviteSuccessfulEsta Number of times the first early dialog
blishedToAs response (typically 180 Ringing) to initial
SIP INVITE with one or more AS
invocations is transmitted by terminating S-
CSCF. The counter is stepped on 2xx
response if no early dialog response was
received.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 49 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOrigAccumulatedCallTimePerAcc This counter is the accumulated INVITE

ess session time per access type in seconds in
originating S-CSCF. The duration for each
INVITE session is between receiving 200OK
(INVITE) and receiving BYE in S-CSCF.
The counter is keyed on the stored access
type value from P-Access-Network-Info in
REGISTER request for the served user. If
no access type has been stored,
"DEFAULT" is used as the counter key. If
authentication is active for BYE request
then it is the BYE with valid challenge
response that triggers this counter.
It is incremented for each INVITE session
with amount of seconds between receiving
200OK (INVITE) and receiving BYE in S-
CSCF . The counter is not incremented for
expired sessions. The counter is not
incremented for the cases where it is S-
CSCF itself that generates BYE (for
example when credit limit is reached for
online charging or when administrative state
of CSCF is locked).
Counter on CSCF node.
scscfTermAccumulatedCallTimePerAc This counter is the accumulated INVITE
cess session time per access type in seconds in
terminating S-CSCF. The duration for each
INVITE session is between receiving 200OK
(INVITE) and receiving BYE in S-CSCF.
The counter is keyed on the stored access
type value from P-Access-Network-Info in
REGISTER request for the served user. If
no access type has been stored,
"DEFAULT" is used as the counter key. If
authentication is active for BYE request
then it is the BYE with valid challenge
response that triggers this counter.
It is incremented for each INVITE session
with amount of seconds between receiving
200OK (INVITE) and receiving BYE in S-
CSCF . The counter is not incremented for
expired sessions. The counter is not
incremented for the cases where it is S-
CSCF itself that generates BYE (for
example when credit limit is reached for
online charging or when administrative state
of CSCF is locked).
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 50 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfOrigAnsweredInvitePerAccess This counter is the number of answered

session establishments per access type in
originating S-CSCF. The counter is keyed
on the stored access type value from P-
Access-Network-Info in REGISTER request
for the served user. If no access type has
been stored, "DEFAULT" is used as the
counter key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
scscfTermAnsweredInvitePerAccess This counter is the number of answered
session establishments per access type in
terminating S-CSCF. The counter is keyed
on the stored access type value from P-
Access-Network-Info in REGISTER request
for the served user. If no access type has
been stored, "DEFAULT" is used as the
counter key. The S-CSCF will also always
increment the counter once with the key
"SUM".
Counter on CSCF node.
scscfOrigAccumulatedCallTimePerMe The duration for each INVITE session is
dia between receiving 2xx (INVITE) and
receiving BYE in S-CSCF.
It is incremented once for each unique
media type present in the first SDP answer
received. The first SDP answer could be
received during call establishment or in the
successful answer. The counter is keyed for
the following media types: Application,
Audio, Control, Data, Image, Message,
Model, Multipart, Text and Video. The
"DEFAULT" key is used for unknown media
types. S-CSCF also increments the counter
with key "SUM" once per media type. If
authentication is active for BYE request
then it is the BYE with valid challenge
response that triggers this counter. The
counter is not incremented for expired
sessions. The counter is not incremented
for the cases where it is S-CSCF itself that
generates BYE (for example when credit
limit is reached for online charging or when
administrative state of CSCF is locked).
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 51 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTermAccumulatedCallTimePerM This counter is the accumulated INVITE

edia session time per access type in seconds in
terminating S-CSCF. The duration for each
INVITE session is between receiving 200OK
(INVITE) and receiving BYE in S-CSCF.
The counter is keyed on the stored access
type value from P-Access-Network-Info in
REGISTER request for the served user. If
no access type has been stored,
"DEFAULT" is used as the counter key. If
authentication is active for BYE request
then it is the BYE with valid challenge
response that triggers this counter.
It is incremented for each INVITE session
with amount of seconds between receiving
200OK (INVITE) and receiving BYE in S-
CSCF . The counter is not incremented for
expired sessions. The counter is not
incremented for the cases where it is S-
CSCF itself that generates BYE (for
example when credit limit is reached for
online charging or when administrative state
of CSCF is locked).
Counter on CSCF node.
scscfOrigAnsweredSessionPerMedia Number of successfully answered sessions
(SIP 2xx received) per media type in
originating S-CSCF.
It is incremented once for each unique
media type present in the first SDP answer
received. The first SDP answer could be
received during call establishment or in the
successful answer. The counter is keyed for
the following media types: Application,
Audio, Control, Data, Image, Message,
Model, Multipart, Text and Video. The
"DEFAULT" key is used for unknown media
types. S-CSCF also increments the counter
with key "SUM" once per media type.
Counter on CSCF node.
scscfTermAnsweredSessionPerMedia Number of successfully answered sessions
(SIP 2xx received) per media type in
terminating S-CSCF.
It is incremented once for each unique
media type present in the first SDP answer
received. The first SDP answer could be
received during call establishment or in the
successful answer. The counter is keyed for
the following media types: Application,
Audio, Control, Data, Image, Message,
Model, Multipart, Text and Video. The
"DEFAULT" key is used for unknown media
types. S-CSCF also increments the counter
with key "SUM" once per media type.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 52 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.9 IMS CSCF Charging Accessibility

4.9.1 Definition

IMS CSCF Charging Accessibility is defined as the probability to perform

charging requests for offline and online charging. Some error indication
performance indicators on charging are also listed.

4.9.2 Formula

Equation 24. IMS CSCF Rf Accounting Request Success Ratio

IMSCSCFRfAccReqSuccRatio[%] = 100 *
cscfACASuccess
cscfACR
Equation 25. IMS CSCF Rf Accounting Permanent Failures
[per second]

cscfACAPermanentFailure
IMSCSCFRfAccPermFail =
T
Equation 26. IMS CSCF Rf Accounting Protocol Errors [per
second]

cscfACAProtocolErrors
IMSCSCFRfAccProtoErr =
T
Equation 27. CSCF Rf ACR to Backup [per second]

cscfACABackup
IMSCSCFRfACRBackup =
T

Equation 28. IMS CSCF Ro Accounting Request Success

Ratio

IMSCSCFRoAccReqSuccRatio[%] = 100 *
cscfCCASuccess
cscfCCR

Counter Name Definition

Number of successful Accounting Answers
(ACAs) received from Diameter.
cscfACASuccess Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 53 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

The number of Accounting Requests sent.
cscfACR Counter on CSCF node.
Number of Accounting Answers (ACA) with
permanent errors (code 5xxx) received from
Diameter.
cscfACAPermanentFailure Counter on CSCF node.
Number of Accounting Answers (ACAs) with
protocol errors (code 3xxx) received from
Diameter.
cscfACAProtocolErrors Counter on CSCF node.
When protocol error or no Accounting
Response is received on the ACR message
the CSCF sends an ACR to the Offline
backup process.
The counter is incremented when protocol
errors:
DIAMETER_UNABLE_TO_DELIVER,
DIAMETER_TOO_BUSY and transient
failures DIAMETER_OUT_OF_SPACE and
ELECTION_LOST are received from
Diameter.
cscfACABackup Counter on CSCF node.
The number of successful Credit Control
Answers (CCAs).
cscfCCASuccess Counter on CSCF node.
The number of Credit Control Request
(CCR) messages sent.
cscfCCR Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.10 Traffic Indicators

4.10.1 Definition

Traffic indicator is the most important service independent traffic intensity

performance indictors in IMS CSCF.

4.10.2 Formula

T in formula is measured/reported time in seconds

Equation 29. IMS CSCF Registered Users

IMSCSCF Re gisteredUsers = cscfConcurrentRegistrations

The mean number of registered and unregistered users in standalone P-

CSCF or S-CSCF or co-located CSCF.
 Ericsson Internal
OPERAT. GUIDELINES 54 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 30. IMS CSCF Registered User Profiles

IMSCSCF Re gisteredUser Pr ofiles =

cscfConcurrentRegisteredUserProfiles

The mean number of registered user profiles in standalone P-CSCF or S-

CSCF or co-located CSCF.

Equation 31. IMS CSCF Unregistered User Profiles

IMSCSCFUn Re gisteredUser Pr ofiles =

scscfConcurrentUnregisteredUserProfiles

The mean number of registered user profiles for unregistered service

invocations in S-CSCF.

Equation 32. IMS CSCF Dropped Registrations [per second]

cscfExpiredRegistrations
IMSCSCFDropped Re gistrations =
T

IMSCSCFDroppedRegistrations is the total number of dropped registrations

per second.

Equation 33. IMS CSCF Failed Registrations [per second]

IMSCSCFFailed Re gistrations =
cscfRegistrationsFailure.SUM - cscfRegistrationsFailure.401 +
cscfReregistrationsFailure.SUM - cscfReregistrationsFailure.401
T
IMSCSCFFailedRegistrations is the total number of failed registrations per
second.

Equation 34. IMS CSCF Initial Registration Failures [per

second]

IMSCSCFInitial Re gFailures =
cscfRegistrationsFailure.rspCode
T
IMSCSCFInitialRegFailures is the number of initial REGISTER request that
has been rejected by the CSCF per response code. The counter is keyed with
the SIP error response code.

Equation 35. IMS CSCF Re-registration Failures [per second]

 Ericsson Internal
OPERAT. GUIDELINES 55 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSCSCF Re Re gFailures =
cscfReRegistrationsFailure.rspCode
T
IMSCSCRelRegFailures is the number of RE-REGISTER request that has
been rejected by the CSCF per response code. The counter is keyed with the
SIP error response code.

Equation 36. IMS CSCF Active Sessions

IMSCSCFActiveSessions = cscfConcurrentSessions

IMSActiveSessions is the total number of established sessions in IMS.

Equation 37. IMS CSCF EATF Active Sessions

IMSCSCFEATFActiveSessions = eatfConcurrentSessions

IMSCSCFEATFActiveSessions is the mean number of concurrent Emergency

SR-VCC sessions in CSCF EATF.

Equation 38. IMS CSCF Dropped Sessions [per second]

cscfExpiredSessions
IMSCSCFDroppedSessions =
T

IMSCSCFDroppedSession is the total number of dropped sessions per

second.

Equation 39. IMS CSCF Originating Failed Sessions [per

second]

IMSCSCFOrgFailedSessions =
(scscfOriginatingInviteNoAsFailed(key : sum)
+ scscfOriginatingInviteToAsFailed(key : sum))
T
IMSCSCFOrgFailedSession is the total number of failed originating sessions
per second.

Equation 40. IMS CSCF Terminating Failed Sessions [per

second]

IMSCSCFTermFailedSessions =
(scscfTerminatingInviteNoAsFailed(key : sum)
+ scscfTerminatingInviteToAsFailed(key : sum))
T
 Ericsson Internal
OPERAT. GUIDELINES 56 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSCSCFTermFailedSession is the total number of failed Terminating

sessions per second.

Equation 41. IMS CSCF Session Setup Attempts with Internal

Failures [per second]

IMSCSCFSessSetupIntFailures =
cscfInviteCommunicationFailure.respCode
T
IMSCSCFSessSetupIntFailues is the number of initial INVITE request that
has been rejected by the CSCF because of internally generated SIP error
responses. The counter is keyed with the concatenation of the SIP error
response code, the SIP reason phrase and hexadecimal error code,
separated by a whitespace. The counter also has a "SUM" key.

Equation 42. IMS CSCF SIP Error Responses [per second]

IMSCSCFSIPError Re sponses =
cscfSipErrorResponse.Method.respCode.HexCode
T
IMSCSCFSIPErrrorResponses is the number of SIP error responses
generated by CSCF with generated hexadecimal error code. The counter is
keyed with the SIP Method, SIP response code and hexadecimal error code
separated by a comma, for example: SIPMethod=INVITE,
SIPResponseCode=408, HexErrorCode=020311913.

Equation 43. IMS ESCF Emergency Session Setup Failures

[per second]

IMSECSCFEmergFailedSessions =
ecscfFailedEmergencySessions.rspCode
T
Equation 44. IMS CSCF EATF SRVCC Emergency Access
Transfer Failures [per second]

IMSCSCFEATFSRVCCEmergAccessTransferFail =
eatfFailedEmergencySessionAccessTransfer.rspCode(rspCode)
T
Equation 45. IMS S-CSCF P-CSCF Restoration Attempts [per
second]

IMSCSCF Re storationAttempts =
scscfPcscfRestorationAttempts.reason
T
 Ericsson Internal
OPERAT. GUIDELINES 57 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

The number of P-CSCF restoration attempts by the S-CSCF. The counter is

keyed on the reasons triggering the P-CSCF restoration, that is SIP error
response code or "Blacklisted"; and a "sum" key for the total number of P-
CSCF restoration attempts by S-CSCF.

Equation 46. IMS S-CSCF P-CSCF Restoration Failures [per

second]

IMSCSCF Re storationFailure =
scscfPcscfRestorationFailure.errCode
T
The number of failed P-CSCF restorations due to signaling with HSS. The
counter is keyed on the Diameter error code, "ReqTimeout",
"ReqConnectionProblem", "ReqProtocolError", "ReqUnspecFailure",
"ReqThrottled", or "AnsInvalidResult"; and a "sum" key for the total number of
P-CSCF restoration failures due to signaling with HSS.

Equation 47. IMS CSCF Request Timeouts [per second]

sipStatsReqTimeout(key : Server IP address)

IMSCSCF Re qTimeouts =
T

IMSCSCFReqTimeouts is the total number of request time outs without

having received a response per second. The measurement is presented per
server IP address, so it’s possible to know direction of the problem.

Equation 48. IMS CSCF Throttled HSS Requests [per second]

IMSCSCFThrottledHssRequests =
cscfThrottledHssRequests(keys : HSS Destination Host, HSS Destination Realm)
T
IMSCSCFThrottledHSSRequests is the number of times that a request to
HSS over the Cx/Dx interface was throttled due to HSS overload. This R-KPI
is keyed on the HSS Destination Host and HSS Destination Realm and SUM.

Equation 49. IMS CSCF Average Reporting OC value

IMSCSCFAvgReportingOCValue =
cscfAverageSipReportingOverloadControlValue

IMSCSCFAvgReportingOCValue is the average of the highest reported oc-

value generated for the SIP Overload Control function during a granularity
period. The SIP Overload Control function produces an array of OC values
every second. The formula calculates the average of the highest values from
the array.

Equation 50. IMS CSCF Peak Reporting OC value

 Ericsson Internal
OPERAT. GUIDELINES 58 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSCSCFPeakReportingOCValue =
cscfPeakSipReportingOverloadControlValue

IMSCSCFPeakReportingOCValue is the maximum of the highest reported oc-

value generated for the SIP Overload Control function during a granularity
period. The SIP Overload Control function produces an array of OC values
every second. The formula calculates the maximum of the highest values
from the array.

Equation 51. IMS CSCF Registerd Users Redistributed

IMSCSCFRegisteredUsersRedistributed =
scscfUserRedistributionRegistered

IMSCSCFRegisteredUsersRedistributed is the number of users that are

redistributed at registration attempts where the user has at least one contact
registered in the S-CSCF when the administrative state is Shutting Down.

Equation 52. IMS CSCF Unregisterd Users Redistributed

IMSCSCFUnRegisteredUsersRedistributed =
scscfUserRedistributionNotRegistered

IMSCSCFUnRegisteredUsersRedistributed is the number of users that are

redistributed at registration attempts where the user is not registered or in
state unregistered by the S-CSCF when the administrative state is Shutting
Down.
Counter Name Definition

cscfConcurrentRegistrations The mean number of registered public user

identities in the node during a measurement
granularity period. One or several public
user identities are registered as a result of
an invoked terminating service. Note that
several public user identities are registered
as a part of an Implicit Registration Set
(IRS).
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 59 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfConcurrentRegisteredUserProfiles The counter measures the mean number of

registered users in the CSCF during a
measurement granularity period. The
counter is applicable in the following
scenarios:
• The CSCF configured as a
standalone P-CSCF or S-CSCF.
The counter measures the mean
number of registered users in the
P-CSCF or the SCSCF.
• The CSCF configured as a
collocated CSCF. The counter
measures the mean number of
registered users in the CSCF
(users registered only in P-CSCF,
and users registered only in the S-
CSCF, and users registered in the
combined PS-CSCF).
“Registered users” are here defined as the
number of “registered implicit registration
sets” and the number of “registered public
identities not belonging to an implicit
registration set”. The numbers of registered
users are increased when a user has
successfully performed initial registration.
The number of registered users is
decreased when a user successfully
deregisters or when network initiated
deregistration is initiated for the user.
Counter on CSCF node.
scscfConcurrentUnregisteredUserProfi The counter measures the mean number of
les unregistered users in the S-CSCF during a
measurement granularity period.
“Unregistered users” are here defined as
the number of “unregistered implicit
registration sets” and the number of
“unregistered public identities not belonging
to an implicit registration set”, for both
Public User Identities and Public Service
Identities. The numbers of unregistered
users are increased when a user has been
invoked for unregistered services. The
number of unregistered users are
decreased at network initiated deregistration
or when a user successfully registers
(changes state from unregistered to
registered).
Counter on CSCF node.
cscfCxDeregisterRequestReceived Counts the number of received RTRs.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 60 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfExpiredRegistrations Number of expired registered contact

addresses. One or more associated public
user identities are possibly unregistered as
a result of the expired contact address.
Counter on CSCF node.
cscfConcurrentSessions The mean number of established INVITE
and SUBSCRIBE dialogs in the node during
a measurement granularity period.
Counter on CSCF node.
eatfConcurrentSessions The mean number of concurrent Emergency
SR-VCC sessions in EATF during a
measurement granularity period.
Counter on CSCF node.
cscfSuccessfulSessions(key:sum) Number of successful session
establishments, as a result of successful
final responses to initial SIP INVITE
received by CSCF. The counter is keyed on
the feature code in the SIP Request
message (Accept-Contact header).
If there are more feature codes in the
message, the CSCF will increment the
counter once per feature code.
If there are more feature codes in the
message, CSCF will increment the counter
once per feature code. If there is no feature
code in the message, CSCF will increment
the counter for key "DEFAULT". CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
success.
Key = sum means the sum of all successful
sessions.
Counter on CSCF node.
cscfExpiredSessions Number of sessions that have been
removed due to session expiry.
Counter on CSCF node.

scscfOriginatingInviteNoAsAttempts Number of times initial SIP INVITE requests

received by the S-CSCF on the originating
side, no Application Server is invoked.
Counter on CSCF node
cscfOriginatingInviteToAsAttempts Number of times an initial SIP INVITE
request attempts received by the S-CSCF
on the originating side on Mw or (Gm
interface for a colocated CSCF), resulting in
an AS invocation on ISC interface.
Counter on CSCF node
scscfTerminatingInviteNoAsAttempts Number of times initial SIP INVITE requests
received by the S-CSCF on the terminating,
no Application Server is invoked.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 61 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfTerminatingInviteToAsAttempts Number of times an initial SIP INVITE

request attempts received by the S-CSCF
on the terminating side on Mw interface,
resulting in an AS invocation on ISC
interface.
Counter on CSCF node.
scscfOriginatingInviteNoAsFailed Number of times non-successful responses
to initial SIP INVITE without AS invocations
transmitted by S-CSCF on Mw on the
originating side.
This counter is stepped by originating S-
CSCF when the response is transmitted on
Mw. Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back on Mw interface, except 407
Proxy authentication required;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
scscfOriginatingInviteToAsFailed Number of times non-successful responses
to initial SIP INVITE with one or more AS
invocations are transmitted by S-CSCF on
Mw on the originating side.
This counter is stepped by originating S-
CSCF when the response is transmitted on
Mw. Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back on Mw interface, except 407
Proxy authentication required;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 62 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

scscfTerminatingInviteNoAsFailed Number of times non-successful responses

to initial SIP INVITE without AS invocations
are transmitted by S-CSCF on the
terminating side.
This counter is stepped by terminating S-
CSCF when the response is transmitted.
Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back by S-CSCF;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
scscfTerminatingInviteToAsFailed Number of times non-successful responses
to initial SIP INVITE with one or more AS
invocations are transmitted by S-CSCF on
the terminating side.
This counter is stepped by terminating S-
CSCF when the response is transmitted.
Incremented for these types of events:
- A 3xx-6xx class SIP INVITE response is
sent back by S-CSCF;
- Transaction timeout at waiting for the
response occurs;
The counter is keyed on the response code
transmitted by S-CSCF. The S-CSCF will
also always increment the counter once with
the key "sum" in order to keep track of total
number of failures.
Counter on CSCF node.
cscfInviteCommunicationFailure The counter measures the number of initial
INVITE request that has been rejected by
the CSCF because of internally generated
SIP error responses. The counter is
applicable when the CSCF is configured as
a standalone node, or as a collocated node
including the E-CSCF and BCF. The
counter is keyed with the concatenation of
the SIP error response code, the SIP
reason phrase and hexadecimal error
code, separated by a whitespace. The
counter also has a "SUM" key.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 63 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfSipErrorResponse Number of SIP error responses generated

by CSCF with generated hexadecimal error
code. The counter is keyed with the SIP
Method, SIP response code and
hexadecimal error code separated by a
comma, for example: SIPMethod=INVITE,
SIPResponseCode=408,
HexErrorCode=020311913.
Counter on CSCF node.
sipStatsReqTimeout The total number a request times out
without having received a response. The
counter should be keyed on the IP address
of the server being addressed.
Counter on CSCF node.
scscfPcscfRestorationAttempts The number of P-CSCF restoration attempts
by the S-CSCF. The counter is keyed on the
reasons triggering the P-CSCF restoration,
that is SIP error response code or
"Blacklisted"; and a "sum" key for the total
number of P-CSCF restoration attempts by
S-CSCF.
This counter is incremented when the
triggering condition of P-CSCF restoration is
met. The triggering condition is a blacklisted
P-CSCF or the SIP error response code
returned by the P-CSCF matching an entry
in configuration parameter
scscfPcscfRestorationSipErrorCodes.
Counter on CSCF node.
scscfPcscfRestorationFailure The number of failed P-CSCF restorations
due to signaling with HSS. The counter is
keyed on the Diameter error code,
"ReqTimeout", "ReqConnectionProblem",
"ReqProtocolError", "ReqUnspecFailure",
"ReqThrottled", or "AnsInvalidResult"; and a
"sum" key for the total number of P-CSCF
restoration failures due to signaling with
HSS.
This counter is incremented when the SAR
request sent for initiating the P-CSCF
Restoration procedure is not successful.
Counter on CSCF node.
cscfAverageSipReportingOverloadCo This counter contains the average oc-value
ntrolValue generated for the SIP Overload Control
function during a granularity period.
The counter is updated every second with
current calculated oc-value based on the
cluster average resource utilization level
when the reporting role for SIP Overload
Control is enabled.
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 64 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

cscfPeakSipReportingOverloadControl This counter contains the maximum oc-

Value value for the SIP Overload Control function
during a granularity period.
The counter is updated every second with
current calculated oc-value based on the
cluster average resource utilization level
when the reporting role for SIP Overload
Control is enabled.
Counter on CSCF node.
scscfUserRedistributionRegistered This counter contains the number of users
that are redistributed at registration attempts
where the user is not registered or in state
unregistered by the S-CSCF when the
administrative state is Shutting Down.
The counter is incremented when a
REGISTER request is rejected with 305
(Use Proxy) or 480 (Temporary
Unavailable) responses by the S-CSCF for
a not registered user or a user in state
unregistered when the administrative state
of the S-CSCF is Shutting Down.
Counter on CSCF node.
scscfUserRedistributionNotRegistered This counter contains the number of users
that are redistributed at registration attempts
where the user is not registered or in state
unregistered by the S-CSCF when the
administrative state is Shutting Down.
The counter is incremented when a
REGISTER request is rejected with 305
(Use Proxy) or 480 (Temporary
Unavailable) responses by the S-CSCF for
a not registered user or a user in state
unregistered when the administrative state
of the S-CSCF is Shutting Down.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

4.11 IMS Active Users

4.11.1 Definition

IMS Active Users is the total number of IMS users using at least one of the
IMS services.

4.11.2 Formula

This alternative of IMS CSCF Active users is working in the CSCF native
node. It uses the Ericsson HSS as storage for time stamps, so without the
Ericsson HSS, this alternative will not work.
 Ericsson Internal
OPERAT. GUIDELINES 65 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 53. IMS CSCF Active Users

IMSCSCFActiveUsers = csc fActiveUsers (key : global )

The number of active users is counted in three measurement intervals each

month. The measurement intervals are (starting at 0:00):

• 1st to 10th,

• 11th to 20th, and

• 21st to end of the month.

In each measurement interval, a counter is incremented only for the first valid
event for each user in the measurement period, ensuring that users are not
counted multiple times during the same period.

Since the number of active users is reported in a differential form for a

reporting interval, the number of active users is only valid for a complete 10
day period. When ordering a number of active users report, the report start
date and time should be specified as 1st , 11th or 21st 00.00 and the end date
10th, 20th or end of month 23.45 respectively.

IMS CSCF Active Users for the Presence Service:

IMSCSCFActiveUsers with key equals DEFAULT may be used for the

number of users using the Presence Service. This measurement may not be
fully accurate, since it is based on Active User measurements on Subscribe,
Publish and Notify SIP methods. These SIP methods do not carry feature
codes like SIP INVITE does and therefore is it not possible to point to exactly
the presence service.

IMS CSCF Active Users for the MMTel Service:

IMSCSCFActiveUsers with key equals to urn:7:3gpp-service.ims.icsi.mmtel

may be used to measure the number of users using the MMTel Service.

The measurement is keyed with the feature tag received in SIP Request
message (Accept-Contact header). The feature tag provided in formula is the
MTAS delivery configuration, normally set to urn:7:3gpp-
service.ims.icsi.mmtel, but may be set to whatever value of the operator
choice.

Equation 54. IMS S-CSCF Active Users per Profile

IMSSCSCFActiveUsersPer Pr ofile = scscfActiveUsersPerProfile(key : profile)

The number of active users per CSCF licence profile in a configurable

measurement period. The CSCF licence model profiles are:”personal”,
“advanced”, or “professional”. The possible measurement intervals are;

• 1 day
 Ericsson Internal
OPERAT. GUIDELINES 66 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

• 1 week based on calendar year

• 10 days based on calendar month

• 1 month based on calendar month

Counter Name Definition
cscfActiveUsers represent the number
cscfActiveUsers(key: global) of active users during the
measurement period. The counter is
keyed. The key ‘global’ to this counter
sums all users to all IMS services.
The active user counters have it’s specific
behavior specified in the IMS Active Users
FS, 6/155 17-HSC 113 06, ref. [12].
Counter on CSCF node.
scscfActiveUsersPerProfile represent the
scscfActiveUsersPerProfile(key: number of users per active user license
profile) model profile during the measurement
interval in S-CSCF.
The counter is keyed on the active user
license model profile values:”personal”,
“advanced”, or “professional”.
In each measurement interval, the counter
is incremented only for the first valid event
for each IRS in the measurement period,
ensuring that users are not counted multiple
times during the same period.
This counter is incremented for the present
measurement interval when an initial SIP
INVITE with the mmtel feature tag (e.g.
VOICE) is received. The counter is
incremented whether the request is
successful or not.
The measurement interval has possible the
values:
ONE_DAY (measurement interval of 1 day),
ONE_WEEK (measurement interval of 1
week based on calendar year),
TEN_DAYS (measurement interval of 10
days based on calendar month), and
ONE_MONTH (measurement interval of 1
month based on calendar month). The
default value is ONE_MONTH.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].
 Ericsson Internal
OPERAT. GUIDELINES 67 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

5 PSTN Interworking and Transit

5.1 IMS PSTN Interworking and Transit Accessibility

5.1.1 Definition

IMS PSTN Interworking and Transit is defined as the probability of being able
to successfully initiate an IMS PSTN Interworking or Transit session into the
IMS network.

5.1.2 Formula

Equation 55. IMS CSCF PSTN Interworking Originating

Session Set-up Success Ratio

IMSCSCFPSTNInterworkOrgSessSetupSuccRatio[%] = 100 * (
cscfTelBgcfOrigInvocationSuccess
(cscfTelBgcfOrigInvocationSuccess + cscfTelBgcfOrigInvocationFailure)

IMSCSCFPSTNInterworkOrgSessionSetup is the probability of successfully

setup a session with BGCF when serving the originating side, that is in S-
CSCF. This is a originating session setup for an outgoing call to PSTN/PLMN.

Equation 56. IMS CSCF PSTN Interworking Terminating

Session Set-up Success Ratio

IMSCSCFPSTNInterworkTermSessSetupSuccRatio[%] = 100 * (
cscfTelBgcfTermInvocationSuccess
(cscfTelBgcfTermInvocationSuccess + cscfTelBgcfTermInvocationFailure))

IMSCSCFPSTNInterworkTermSessionSetup is the probability of successfully

setup a session with BGCF when serving the terminating side, that is in I-
CSCF or S-CSCF (UAC). This is a terminating session setup for an incoming
call from PSTN/PLMN.

Equation 57. IMS I-CSCF Transit Set-up Success Ratio

IMSICSCFTransitSetupSuccRatio[%] = 100 *
Coden
icscfTransitSessionAttempts - ∑ icscfTransitSessionFailures
Code1

icscfTransitSessionAttempts

IMSICSCFTransitSetupSuccRatio is the probability of success for transit

session setup (INVITE) requests received by terminating I-CSCF. The
icscfTransitSessionFailures counter is keyed on error response code, all
counters should be added to get the sum of errors.
 Ericsson Internal
OPERAT. GUIDELINES 68 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

5.2 Traffic Indicator

Equation 58. IMS CSCF PSTN Interworking Originating

Attempts [per second]

IMSCSCFPSTNInterworkOrgAttempts =
cscfTelBgcfOrigInvocationSuccess + cscfTelBgcfOrigInvocationFailure
T
Equation 59. IMS CSCF PSTN Interworking Terminating
Attempts [per second]

IMSCSCFPSTNInterworkTermAttempts =
cscfTelBgcfTermInvocationSuccess + cscfTelBgcfTermInvocationFailure
T
Equation 60. IMS I-CSCF Transit Set-up Attempts [per second]

icscfTransitSessionAttempts
IMSICSCFTransitSetupAttempts =
T

IMSICSCFTransitAttempts is the number of transit session setup attempts

(INVITE) requests received by terminating I-CSCF.

T = measured/reported time in seconds

Counter Name Definition

cscfTelBgcfOrigInvocationSuccess Counts the number of times BGCF returns a

successful response when serving the
originating side, that is in S-CSCF.
Counter on CSCF node.

cscfTelBgcfOrigInvocationFailure The counter is incremented each time an

error code is returned from BGCF when
serving the originating side, that is in S-
CSCF.
Counter on CSCF node.

cscfTelBgcfTermInvocationSuccess Counts the number of times BGCF returns a

successful response when serving the
terminating side, that is in I-CSCF or S-
CSCF (UAC).
Counter on CSCF node.

cscfTelBgcfTermInvocationFailure The counter is incremented each time an

error code is returned from BGCF, when
serving the terminating side, that is in I-
CSCF or S-CSCF (UAC).
Counter on CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 69 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

icscfTransitSessionAttempts Number of attempted session

establishments (INVITE) resulting in that
terminating I-CSCF performs a transit
attempt.
Counter on CSCF node.

icscfTransitSessionFailures Number of failed transit attempts, that is, the

counter is stepped for every transit attempt
which results in sending of a negative
response. The counter is keyed on the
response code to make it possible to
determine what types of faults that have
occurred.
Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

6 IMS MTAS
The R-KPIs specified in this section cover the MTAS product comprising
MMTel, SR-VCC and Conference Application Servers.

6.1 IMS MTAS Registration Accessibility

6.1.1 Definition

IMS MTAS Registration Accessibility is defined as the probability of being

able to successfully register, re-register and de-register into the IMS MTAS.

6.1.2 Formula

Equation 61. IMS MTAS Initial Registration Success Ratio

IMSMTASInit Re gSuccRatio[%] = 100 *

MtasSubsDataInitialRegOk
(MtasSubsDataInitialRegOk + MtasSubsDataInitialRegNOkE +
MtasSubsDataInitialRegNOkI)

This formula covers the MMTel specific initial registration success ratio,
measured at the MTAS node.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.2
Accessibility: IMS Initial Registration Success Ratio [%].

Equation 62. IMS MTAS Automatic Registration Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 70 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMTASAuto Re gSuccRatio[%] = 100 *

MtasSubsDataAutoRegOk
(MtasSubsDataAutoRegOk + MtasSubsDataAutoRegNOkE +
MtasSubsDataAutoRegNOkI)

This formula covers the MMTel specific registration on INVITE success ratio,
measured at the MTAS node.

Equation 63. IMS MTAS Re-registration Success Ratio

IMSMTAS Re Re gSuccRatio[%] = 100 *

MtasSubsDataReregOk
(MtasSubsDataReregOk + MtasSubsDataReregNOkE +
MtasSubsDataReregNOkI)

Counter Name Definition

MtasSubsDataInitialRegOk The number of initial registration procedures

that were completed successfully.
Counter on MTAS node.
The number of initial registration procedures
MtasSubsDataInitialRegNOkE that could not be completed successfully
because of external reasons.
Counter on MTAS node.
The number of initial registration procedures
MtasSubsDataInitialRegNOkI that could not be completed successfully
because of internal reasons.
Counter on MTAS node.
MtasSubsDataAutoRegOk The number of automatically performed
registrations that were completed
successfully.
Counter on MTAS node.
MtasSubsDataAutoRegNOkE The number of automatically performed
registrations that could not be completed
successfully because of external reasons.
Counter on MTAS node.
MtasSubsDataAutoRegNOkI The number of automatically performed
registrations that could not be completed
successfully because of internal reasons.
Counter on MTAS node.
The number of reregistration procedures
MtasSubsDataReregOk that were completed successfully.
Counter on MTAS node.
MtasSubsDataReregNOkE The number of reregistration procedures
that could not be completed successfully
because of external reasons.
Counter on MTAS node.
MtasSubsDataReregNOkI The number of reregistration procedures
that could not be completed successfully
because of internal reasons.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 71 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.2 IMS MTAS Registration Retainability

6.2.1 Definition

IMS MTAS Registration Retainability is defined as the probability of being

able to successfully re-register and successfully complete (normally
terminate) an active registration in the IMS MTAS.

6.2.2 Formula

Equation 64. IMS MTAS Re- and De-registration Completion

Ratio

IMSMTASDeAnd Re Re gCompRatio[%] = 100 *

(MtasSubsDataDeregOk + MtasSubsDataReregOk)
(MtasSubsDataDeregOk + MtasSubsDataDeregNOkE +
MtasSubsDataDeregNOkI +
MtasSubsDataReregOk + MtasSubsDataReregNOkE +
MtasSubsDataReregNOkI)

This formula covers the MMTel specific re- and de-registrations completion
ratio, measured at the MTAS node.
Reference: Key Performance Indicators for IMS System, ref. [8] Section,
3.2.2, Retainability - IMS Registration Completion Ratio [%].

Counter Name Definition

MtasSubsDataDeregOk The number of deregistration procedures
that were completed successfully.
Counter on MTAS node.
MtasSubsDataDeregNOkE The number of deregistration procedures
that could not be completed successfully
because of external reasons.
Counter on MTAS node.
MtasSubsDataDeregNOkI The number of deregistration procedures
that could not be completed successfully
because of internal reasons.
Counter on MTAS node.
MtasSubsDataReregOk The number of reregistration procedures
that were completed successfully.
Counter on MTAS node.
MtasSubsDataReregNOkE The number of reregistration procedures
that could not be completed successfully
because of external reasons.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 72 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSubsDataReregNOkI The number of reregistration procedures
that could not be completed successfully
because of internal reasons.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.3 IMS MMTEL AS Session Setup Accessibility

6.3.1 Definition

IMS MMTEL AS Session Accessibility is defined as the probability of being

able to successfully initiate a session into the IMS MMTEL AS.

6.3.2 Formula

Session accessibility for registered and un-registered PUI:s, these R-KPIs are
also called Network Efficiency Ratio (NER) because they characterize the
network performance. It is the percentage of calls where the called user was
alerted for a new call and where user behavior is eliminated.

Equation 65. IMS MMTEL AS Originating Session Set-up

Success Ratio

IMSMMTelASOrgSessSetupSuccRatio[%] = 100 *
respCode = 20n
(MtasMmtOrigNetworkSuccessSessionEstablish +
( ∑
respCode =18m MtasMmtOrigUnregNetworkSuccessSessionEstablish)
+

MtasMmtInitOrigSessNOkUser.sum + MtasMmtInitOrigUnregSessNOkUser.sum )
respCode = 20n
(MtasMmtOrigNetworkSuccessSessionEstablish +
( ∑ +
respCode =18m MtasMmtOrigUnregNetworkSuccessSessionEstablish)

MtasMmtInitOrigSessNOkUser.sum + MtasMmtInitOrigUnregSessNOkUser.sum +
MtasMmtInitOrigSessNOkNet.sum + MtasMmtInitOrigUnregSessNOkNet.sum +
MtasMmtInitOrigSessNOkService.sum +
MtasMmtInitOrigUnregSessNOkService.sum
MtasMmtInitOrigSessNOkSupportNode.sum +
MtasMmtInitOrigUnregSessNOkSupportNode.sum)

Equation 66. IMS MMTEL AS Terminating Session Set-up

Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 73 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASOrgSessSetupSuccRatio[%] = 100 *
respCode = 20n
(MtasMmtTermNetworkSuccessSessionEstablish +
( ∑
respCode =18m MtasMmtTermUnregNetworkSuccessSessionEstablish)
+

MtasMmtInitTermSessNOkUser.sum + MtasMmtInitTermUnregSessNOkUser.sum )
respCode = 20n
(MtasMmtTermNetworkSuccessSessionEstablish +
( ∑ +
respCode =18m MtasMmtTermUnregNetworkSuccessSessionEstablish)

MtasMmtInitTermSessNOkUser.sum + MtasMmtInitTermUnregSessNOkUser.sum +
MtasMmtInitTermSessNOkNet.sum + MtasMmtInitTermUnregSessNOkNet.sum +
MtasMmtInitTermSessNOkService.sum +
MtasMmtInitTermUnregSessNOkService.sum
MtasMmtInitTermSessNOkSupportNode.sum +
MtasMmtInitTermUnregSessNOkSupportNode.sum)

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%]. These R-KPIs are also
called Network Efficiency Ratio (NER) because they characterize the network
performance where user behavior is eliminated. The session setup is
considered as successful from network performance perspective for the
following responses caused by user behaviour:

• User cancelled in early dialog

• User is not registered, Forbidden (403)

• User is Not Found or Called User Unknown (404)

• Temporarily Unavailible (480)

• Address Incomplete (484)

• Busy Here (486)

• Request Terminated (487)

• Busy Everywhere (600)

• Decline (603)

Session accessibility for registered and un-registered PUI:s, Answer to

Seizure Ratio (ASR). It is the percentage of answered telephone calls with
respect to the total call volume.

Equation 67. IMS MMTEL AS Originating Answer to Seizure

Ratio (ASR)
 Ericsson Internal
OPERAT. GUIDELINES 74 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASOrgAnswerToSeizureRatioASR[%] = 100 *
(MtasMmtOrigAnswered + MtasMmtOrigUnregAnswered)
(MtasMmtOrigAnswered + MtasMmtOrigUnregAnswered +
MtasMmtOrigFailedAttempt + MtasMmtOrigUnregFailedAttempt)

Equation 68. IMS MMTEL AS Terminating Answer to Seizure

Ratio (ASR)

IMSMMTelASTermAnswerToSeizureRatioASR[%] = 100 *
(MtasMmtTermAnswered + MtasMmtUnregTermAnswered)
(MtasMmtTermAnswered + MtasMmtUnregTermAnswered +
MtasMmtTermFailedAttempt + MtasMmtTermUnregFailedAttempt)

The counters in ASR formulas are keyed on CSCF IP address, which means
that formulas are presented per CSCF. It is possible to make a sum for the
system for all CSCFs.

Traffic indicators/Causes for failed attempts

Equation 69. IMS MMTEL AS Failed Originating Sessions

[per second]

IMSMMTelASFailedOrgSessions =
(MtasMmtOrigFailedAttemptCause.cause +
MtasMmtOrigUnregFailedAttemptCause.cause)
T
Equation 70. IMS MMTEL AS Failed Terminating Sessions
[per second]

IMSMMTelASFailedTermSessions =
(MtasMmtTermFailedAttemptCause.cause +
MtasMmtTermUnregFailedAttemptCause.cause)
T
Equation 71. IMS MMTEL AS User Rejected Originating
Sessions [per second]

IMSMMTelASNOkUserOrigSessions =
MtasMmtInitOrigSessNOkUser.key + MtasMmtInitOrigUnregSessNOkUser.key
T

Equation 72. IMS MMTEL AS User Rejected Terminating

Sessions [per second]
 Ericsson Internal
OPERAT. GUIDELINES 75 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASNOkUserTermSessions =
MtasMmtInitTermSessNOkUser.key + MtasMmtInitTermUnregSessNOkUser.key
T

Equation 73. IMS MMTEL AS Network Rejected Originating

Sessions [per second]

IMSMMTelASNOkNetOrigSessions =
MtasMmtInitOrigSessNOkNet.key + MtasMmtInitOrigUnregSessNOkNet.key
T

Equation 74. IMS MMTEL AS Network Rejected Terminating

Sessions [per second]

IMSMMTelASNOkNetTermSessions =
MtasMmtInitTermSessNOkNet.key + MtasMmtInitTermUnregSessNOkNet.key
T

Equation 75. IMS MMTEL AS Service Logic Rejected

Originating Sessions [per second]

IMSMMTelASNOkServiceOrigSessions =
(MtasMmtInitOrigSessNOkService.key +
MtasMmtInitOrigUnregSessNOkService.key)
T
Equation 76. IMS MMTEL AS Service Logic Rejected
Terminating Sessions [per second]

IMSMMTelASNOkServiceTermSessions =
(MtasMmtInitTermSessNOkService.key +
MtasMmtInitTermUnregSessNOkService.key)
T
Equation 77. IMS MMTEL AS External Support Node
Rejected Originating Sessions [per second]

IMSMMTelASNOkSupportNodeOrigSessions =
(MtasMmtInitOrigSessNOkSupportNode.key +
MtasMmtInitOrigUnregSessNOkSupportNode.key)
T
 Ericsson Internal
OPERAT. GUIDELINES 76 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 78. IMS MMTEL AS External Support Node

Rejected Terminating Sessions [per second]

IMSMMTelASNOkSupportNodeTermSessions =
(MtasMmtInitTermSessNOkSupportNode.key +
MtasMmtInitTermUnregSessNOkSupportNode.key)
T
Note: The notation ‘.key’ is the key per cause code
“<Protocol>,<Cause>,<Text>” which gives most information for trouble
shooting purposes. If a sum of faults are needed, ‘.sum’ key should be used.

Equation 79. IMS MMTEL AS Call Released No Credit [per

second]

MtasCsiCallReleasedNoCredit
IMSMMTelASCall Re lNoCredit =
T
Equation 80. IMS MMTEL AS Rejected Parlay-X requests, per
cause code [per second]

IMSMMTelASParlayX Re j Re quests =
MtasPxRejectedRequests.cause
T
Note: These measurememts are presented separately per cause code. The
notation ‘.cause’ is the key (part of MOID) to the cause code.

Equation 81. IMS MTAS DNS Failover [per second]

MtasFuncFailover
IMSMTASDNSFailover =
T

IMSMTASDNSFailover is the number of DNS based failover attempts to other

external servers, when an initial request to the previous one failed due to
connection error, time out or server error message is received.
 Ericsson Internal
OPERAT. GUIDELINES 77 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtOrigNetworkSuccessSession The accumulated number of successful

Establish MMTel session establishments counted by
the originating MTAS. The response code
(180 or 200) or string "sum" is used as key.
One instance of the counter shall count sum
of all events causing the counter to
increment in case with key="sum".
The counter is incremented when sending
180 message on initial INVITE or when
sending 200 OK (INVITE) if no 180
message has been sent or when sending
200 OK (PRACK) in case with early media
and no preconditions or when sending 200
OK (UPDATE) on new early dialog in case
with early media and preconditions or when
sending 200 OK (PRACK) on new early
dialog in case with early media and
preconditions initially met.
Counter on MTAS node.
The accumulated number of successful
MtasMmtTermNetworkSuccessSessio MMTel session establishments counted by
nEstablish the terminating MTAS. The response code
(180 or 200) or string "sum" is used as
key.One instance of the counter shall count
sum of all events causing the counter to
increment in case with key="sum".
The counter is incremented when sending
180 message on initial INVITE or when
sending 200 OK (INVITE) if no 180
message has been sent or when sending
200 OK (PRACK) in case with early media
and no preconditions or when sending 200
OK (UPDATE) on new early dialog in case
with early media and preconditions or when
sending 200 OK (PRACK) on new early
dialog in case with early media and
preconditions initially met, by the
terminating MTAS.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 78 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtOrigUnregNetworkSuccessS The accumulated number of successful

essionEstablish MMTel session establishments counted by
the unregistered originating MTAS. The
response code (180 or 200) or string "sum"
is used as key. One instance of the counter
shall count sum of all events causing the
counter to increment in case with
key="sum".
The counter is incremented when sending
180 message on initial INVITE or when
sending 200 OK (INVITE) if no 180
message has been sent or when sending
200 OK (PRACK) in case with early media
and no preconditions or when sending 200
OK (UPDATE) on new early dialog in case
with early media and preconditions or when
sending 200 OK (PRACK) on new early
dialog in case with early media and
preconditions initially met, by the originating
unregistered MTAS.
Counter on MTAS node.

MtasMmtTermUnregNetworkSuccess The accumulated number of successful

SessionEstablish MMTel session establishments counted by
the unregistered terminating MTAS. The
response code (180 or 200) or string 'sum'
is used as key.One instance of the counter
shall count sum of all events causing the
counter to increment in case with
key="sum".
The counter is incremented when sending
180 message on initial INVITE or when
sending 200 OK (INVITE) if no 180
message has been sent or when sending
200 OK (PRACK) in case with early media
and no preconditions or when sending 200
OK (UPDATE) on new early dialog in case
with early media and preconditions or when
sending 200 OK (PRACK) on new early
dialog in case with early media and
preconditions initially met, by the
terminating unregistered MTAS.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 79 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitOrigSessNOkService The counter is incremented when

originating MMTel AS Internal service logic
evaluates to decline a call setup due to such
cases as user barring or user limitations and
sends negative response on INVITE. The
counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.

MtasMmtInitOrigUnregSessNOkServic The counter is incremented when

e originating unregistered MMTel AS Internal
service logic evaluates to decline a call
setup due to such cases as user barring or
user limitations and sends negative
response on INVITE. The counter is keyed
on the string "t;<Protocol>,<Cause>,<Text>
" or "sum", where Protocol is signaling
protocol, e.g. SIP, Q.850, Cause is the
response code, or cause code in Reason
header of a CANCEL, e.g. 480, 503 and
Text is the reason phrase in a response, or
reason text in Reason header of a
CANCEL. One instance of the counter shall
count sum of all events causing the counter
to increment in case with key="sum".
Counter on MTAS node.

MtasMmtInitTermSessNOkService The counter is incremented when

terminating MMTel AS Internal service logic
evaluates to decline a call setup due to such
cases as user barring or user limitations and
sends negative response on INVITE. The
counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 80 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitTermUnregSessNOkServi The counter is incremented when

ce terminating unregistered MMTel AS Internal
service logic evaluates to decline a call
setup due to such cases as user barring or
user limitations and sends negative
response on INVITE. The counter is keyed
on the string "t;<Protocol>,<Cause>,<Text>
" or "sum", where Protocol is signaling
protocol, e.g. SIP, Q.850, Cause is the
response code, or cause code in Reason
header of a CANCEL, e.g. 480, 503 and
Text is the reason phrase in a response, or
reason text in Reason header of a
CANCEL. One instance of the counter shall
count sum of all events causing the counter
to increment in case with key="sum".
Counter on MTAS node.

MtasMmtInitOrigSessNOkNet The counter is incremented when the call is

declined due to network problems, received
by an originating MTAS and sends negative
response on INVITE. The counter is keyed
on the string "t;<Protocol>,<Cause>,<Text>
" or "sum", where Protocol is signaling
protocol, e.g. SIP, Q.850, Cause is the
response code, or cause code in Reason
header of a CANCEL, e.g. 480, 503 and
Text is the reason phrase in a response, or
reason text in Reason header of a
CANCEL. One instance of the counter shall
count sum of all events causing the counter
to increment in case with key="sum".
Counter on MTAS node.

MtasMmtInitOrigUnregSessNOkNet The counter is incremented when the call is

declined due to network problems, received
by an originating unregistered MTAS and
sends negative response on INVITE. The
counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 81 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitTermSessNOkNet The counter is incremented when the call is

declined due to network problems, received
by a terminating MTAS and sends negative
response on INVITE. The counter is keyed
on the string "t;<Protocol>,<Cause>,<Text>
" or "sum", where Protocol is signaling
protocol, e.g. SIP, Q.850, Cause is the
response code, or cause code in Reason
header of a CANCEL, e.g. 480, 503 and
Text is the reason phrase in a response, or
reason text in Reason header of a
CANCEL. One instance of the counter shall
count sum of all events causing the counter
to increment in case with key="sum".
Counter on MTAS node.

MtasMmtInitTermUnregSessNOkNet The counter is incremented when the call is

declined due to network problems , received
by a terminating unregistered MTAS and
sends negative response on INVITE. The
counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.

MtasMmtInitOrigSessNOkUser The counter is incremented when CANCEL

before ringing with reason code other than
5xx or negative response on INVITE with
code 403, 404, 480, 484, 486, 600, 603 is
received by the originating MTAS from a
Remote User. The counter is keyed on the
string "t;<Protocol>,<Cause>,<Text> " or
"sum", where Protocol is signaling protocol,
e.g. SIP, Q.850, Cause is the response
code, or cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 82 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitOrigUnregSessNOkUser The counter is incremented when CANCEL

before ringing with reason code other than
5xx or negative response on INVITE with
code 403, 404, 480, 484, 486, 600, 603 is
received by the originating unregistered
MTAS from a Remote User. The counter is
keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.

MtasMmtInitTermSessNOkUser The counter is incremented when CANCEL

before ringing with reason code other than
5xx or negative response on INVITE with
code 403, 404, 480, 484, 486, 600, 603 is
received by the terminating MTAS from a
Remote User. The counter is keyed on the
string "t;<Protocol>,<Cause>,<Text> " or
"sum", where Protocol is signaling protocol,
e.g. SIP, Q.850, Cause is the response
code, or cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum"..
Counter on MTAS node.

MtasMmtInitTermUnregSessNOkUser The counter is incremented when CANCEL

before ringing with reason code other than
5xx or negative response on INVITE with
code 403, 404, 480, 484, 486, 600, 603 is
received by the terminating unregistered
MTAS from a Remote User. The counter is
keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 83 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitOrigSessNOkSupportNod The counter is incremented when the

e originating MMTel AS call is declined due to
error of external support node and sends
negative response on INVITE. The counter
is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.

MtasMmtInitOrigUnregSessNOkSupp The counter is incremented when the

ortNode originating unregistered MMTel AS call is
declined due to error of external support
node and sends negative response on
INVITE. The counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
The counter is incremented when the
MtasMmtInitTermSessNOkSupportNo terminating MMTel AS call is declined due
de error of external support node and sends
negative response on INVITE. The counter
is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 84 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtInitTermUnregSessNOkSupp The counter is incremented when the

ortNode terminating unregistered MMTel AS call is
declined due to error of external support
and sends negative response on INVITE.
The counter is keyed on the string
"t;<Protocol>,<Cause>,<Text> " or "sum",
where Protocol is signaling protocol, e.g.
SIP, Q.850, Cause is the response code, or
cause code in Reason header of a
CANCEL, e.g. 480, 503 and Text is the
reason phrase in a response, or reason text
in Reason header of a CANCEL. One
instance of the counter shall count sum of
all events causing the counter to increment
in case with key="sum".
Counter on MTAS node.

MtasMmtOrigAnswered The accumulated number of MMTel

INVITEs answered, counted by the
originating MTAS. The CSCF IP address is
used as key. The counter is incremented
when receiving the 200 OK message.
Counter on MTAS node.

MtasMmtOrigUnregAnswered The total number of received 2xx (INVITE),

by the originating unregistered MTAS. The
counter is keyed with CSCF IP address.
The counter is incremented when receiving
the 200 OK message.
Counter on MTAS node.

MtasMmtTermAnswered The accumulated number of MMTel

INVITEs answered by registered PUIs,
counted by the terminating MTAS. The
CSCF IP address is used as key.
The counter is incremented when receiving
the 200 OK message.
Counter on MTAS node.

MtasMmtUnregTermAnswered The accumulated number of MMTel

INVITEs answered by unregistered PUIs,
counted by the terminating MTAS. The
CSCF IP address is used as key.
The counter is incremented when receiving
the 200 OK message.
Counter on MTAS node.

MtasMmtOrigFailedAttemptCause The accumulated number of failed MMTel

INVITEs made to registered PUIs, counted
by the originating MTAS. The cause code
and reason is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx messages.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 85 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtOrigUnregFailedAttemptCau The accumulated number of failed MMTel

se INVITEs made to unregistered PUIs,
counted by the orignating MTAS. The cause
code and reason is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx messages.
Counter on MTAS node.

MtasMmtTermFailedAttemptCause The accumulated number of failed MMTel

INVITEs made to registered PUIs, counted
by the terminating MTAS. The cause code
and reason is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx messages.
Counter on MTAS node.

MtasMmtTermUnregFailedAttemptCa The accumulated number of failed MMTel

use INVITEs made to unregistered PUIs,
counted by the terminating MTAS. The
cause code and reason is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx messages.
Counter on MTAS node.

MtasCsiCallReleasedNoCredit The number of times of call is released

because of the ACH message received from
SCP which contains IE
ReleaseIfDurationExceeded.
Counter on MTAS node.

MtasPxRejectedRequests The counter is incremented when rejecting

a received Parlay X Request in MTAS. The
cause code is used as key.
Counter on MTAS node.

MtasFuncFailover The number of DNS based failover attempts

to other external servers, when the request
to the previous one failed due to connection
error, time out or server error message is
received.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.4 IMS MTAS (MMTel AS and SCC AS) Session Retainability

6.4.1 Definition

IMS MTAS (MMTel AS and SCC AS) Session Retainability is defined as the
probability of being able to successfully complete (normally terminate) an
active IMS MTAS session.
 Ericsson Internal
OPERAT. GUIDELINES 86 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.4.2 Formula

Equation 82. IMS MMTel AS Orginating Session Completion

Ratio

IMSMMTelASOrgSessCompRatio[%] = 100 *
(MtasMmtTermOrigSessOk.SIP; cause = 487 +
MtasMmtTermOrigSessOk.Q.850; cause = 16)
(MtasMmtTermOrigSessOk.SIP; cause = 487 +
MtasMmtTermOrigSessOk.Q.850; cause = 16 +
Cscf = n

∑ (MtasMmtTermOrigSessNOkI + MtasMmtTermOrigSessNOkE ) )
Cscf =1

Equation 83. IMS MMTel AS Terminating Session Completion

Ratio

IMSMMTelASTermSessCompRatio[%] = 100 *
(MtasMmtTermTermSessOk.SIP; cause = 487 +
MtasMmtTermTermSessOk.Q.850; cause = 16)
(MtasMmtTermTermSessOk.SIP; cause = 487 +
MtasMmtTermTermSessOk.Q.850; cause = 16 +
Cscf = n

∑ (MtasMmtTermTermSessNOkI + MtasMmtTermTermSessNOkE)
Cscf =1

Equation 84. IMS MMTel AS Orginating Dropped Sessions

Ratio

IMSMMTelASOrgDroppedSessRatio[%] = 100 *
Cscf = n

∑ (MtasMmtTermOrigSessNOkI + MtasMmtTermOrigSessNOkE )
Cscf =1

(MtasMmtTermOrigSessOk.SIP; cause = 487 +

MtasMmtTermOrigSessOk.Q.850; cause = 16 +
Cscf = n

∑ (MtasMmtTermOrigSessNOkI + MtasMmtTermOrigSessNOkE ) )
Cscf =1

Equation 85. IMS MMTel AS Terminating Dropped Sessions

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 87 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASOrgDroppedSessRatio[%] = 100 *
Cscf = n

∑ (MtasMmtTermTermSessNOkI + MtasMmtTermTermSessNOkE )
Cscf =1

(MtasMmtTermTermSessOk.SIP; cause = 487 +

MtasMmtTermTermSessOk.Q.850; cause = 16 +
Cscf = n

∑ (MtasMmtTermTermSessNOkI + MtasMmtTermTermSessNOkE ) )
Cscf =1

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.2.1
Call Drop Rate of IMS Sessions.

Equation 86. IMS SCC AS Originating CS Session Completion

Ratio

IMSSCCASOrgCsSessCompRatio[%] = 100 *
(MtasSccTermOrigCsSessOk.SIP; cause = 487 +
MtasSccTermOrigCsSessOk.Q.850; cause = 16)
(MtasSccTermOrigCsSessOk.SIP; cause = 487 +
MtasSccTermOrigCsSessOk.Q.850; cause = 16 +
Cause = n (MtasSccTermOrigCsSessNOk + MtasSccTermOrigCsSessNOkECause +

∑
Cause =1 MtasSccTermOrigCsSessNOkServiceCause) +
Cscf = n

∑ (MtasSccTermOrigCsSessNOkI) )
Cscf =1

Equation 87. IMS SCC AS Terminating CS Session Completion

Ratio

IMSSCCASTermCsSessCompRatio[%] = 100 *
(MtasSccTermTermCsSessOk.SIP; cause = 487 +
MtasSccTermTermCsSessOk.Q.850; cause = 16)
(MtasSccTermTermCsSessOk.SIP; cause = 487 +
MtasSccTermTermCsSessOk.Q.850; cause = 16 +
Cause = n (MtasSccTermTermCsSessNOk + MtasSccTermTermCsSessNOkECause +
∑
Cause =1 MtasSccTermTermCsSessNOkServiceCause) +
Cscf = n

∑ (MtasSccTermTermCsSessNOkI) )
Cscf =1

Equation 88. IMS SCC AS Originating PS Session Completion

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 88 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASOrgPsSessCompRatio[%] = 100 *
(MtasSccTermOrigPsSessOk.SIP; cause = 487 +
MtasSccTermOrigPsSessOk.Q.850; cause = 16)
(MtasSccTermOrigCPsSessOk.SIP; cause = 487 +
MtasSccTermOrigPsSessOk.Q.850; cause = 16 +
(MtasSccTermOrigPsSessNOk + MtasSccTermOrigPsSessNOkECause +
Cause = n

∑
Cause =1 MtasSccTermOrigPsSessNOkServiceCause) +
Cscf = n

∑ (MtasSccTermOrigPsSessNOkI) )
Cscf =1

Equation 89. IMS SCC AS Terminating PS Session Completion

Ratio

IMSSCCASTermPsSessCompRatio[%] = 100 *
(MtasSccTermTermPsSessOk.SIP; cause = 487 +
MtasSccTermTermPsSessOk.Q.850; cause = 16)
(MtasSccTermTermPsSessOk.SIP; cause = 487 +
MtasSccTermTermPsSessOk.Q.850; cause = 16 +
Cause = n (MtasSccTermTermPsSessNOk + MtasSccTermTermPsSessNOkECause +

∑
Cause =1 MtasSccTermTermPsSessNOkServiceCause) +
Cscf = n

∑ (MtasSccTermTermPsSessNOkI) )
Cscf =1

Reference: Key Performance Indicators for IMS System, ref. [8] Section
Retainability: IMS Session Completion Ratio [%].

For formulas Equation 94 to Equation 101, an SBG SMM rule must be

applied. The SMM rule in SBG P-CSCF and I-BCF shall add a reason header
in BYE requests with cause 487 response code as first reason header in
access networks (from UE) and foreign networks.

SBG SMM rule to be applied:

Ruleset "Add a new Reason with cause 487 response code first in BYE"
If
is_request and
SIP:cseq.method == "BYE"
Do
add first SIP:reason := "SIP;cause=487;text=\"Session cancelled\""
End
End
This SMM rule shall be applied for “Incoming SMM Filter” fields of all access
and foreign networks.
 Ericsson Internal
OPERAT. GUIDELINES 89 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Traffic indicators/Causes for failed session completion and dropped sessions

Equation 90. IMS MMTEL AS Failed Originating Session

completion [per second]

IMSMMTelASFailedOrigSessionComp =
MtasMmtOrigTermSessNOkECause .cause
T
IMSMMTelASFailedOrigSessionComp is the number of unsuccessful call
completion in originating MMTEL AS triggered by external nodes like
Charging server,HSS or DNS.

Equation 91. IMS MMTEL AS Failed Terminating Sessions

completion [per second]

IMSMMTelASFailedTermSessionComp =
MtasMmtTermTermSessNOk.cause
T
IMSMMTelASFailedTermSessionComp is the number of unsuccessful call
completion in terminatiing MMTEL AS triggered by external nodes like
Charging server,HSS or DNS.

Equation 92. IMS SCC AS Failed Originating CS Session

completion [per second]

IMSSCCASFailedOrigCSSessionComp =
MtasSccTermOrigCSSessNOkECause .cause
T
IMSSCCASFailedOrigCSSessionComp is the number of unsuccessful call
completion from CS domain in originating SCC AS triggered by external
nodes like Charging server,HSS or DNS.

Equation 93. IMS SCC AS Failed Terminating CS Sessions

completion [per second]

IMSSCCASFailedTermCSSessionComp =
MtasSccTermTermCSSessNOkECause .cause
T
IMSSCCASFailedTermCSSessionComp is the number of unsuccessful call
completion from CS domain in terminatiing SCC AS triggered by external
nodes like Charging server,HSS or DNS.

Equation 94. IMS SCC AS Failed Originating PS Session

completion [per second]
 Ericsson Internal
OPERAT. GUIDELINES 90 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASFailedOrigPSSessionComp =
MtasSccTermOrigPSSessNOkECause .cause
T
IMSSCCASFailedOrigPSSessionComp is the number of unsuccessful call
completion from PS domain in originating SCC AS triggered by external
nodes like Charging server,HSS or DNS.

Equation 95. IMS SCC AS Failed Terminating PS Sessions

completion [per second]

IMSSCCASFailedTermPSSessionComp =
MtasSccTermTermPSSessNOkECause .cause
T
IMSSCCASFailedTermPSSessionComp is the number of unsuccessful call
completion from PS domain in terminatiing SCC AS triggered by external
nodes like Charging server,HSS or DNS.

Counter Name Definition

MtasMmtTermOrigSessOk The number of successful call completion in

Originating MMTEL AS triggered by UE.
The counter is incremented when BYE
request with Reason header with SIP;cause
= 487 is received or with Q.850;cause=16 is
received from network.
The counter is keyed on cause in reason
header.
Counter on MTAS node.
MtasMmtTermOrigSessNOkI The accumulated number of MMTel
sessions, in the originating MTAS,
terminated prematurely by the MTAS due to
internal reasons. The counter is keyed on
the CSCF IP address.
Counter on MTAS node.
MtasMmtTermOrigSessNOkE The accumulated number of MMTel
sessions, in the originating MTAS,
terminated prematurely by the MTAS due to
external reasons. The counter is keyed on
the CSCF IP address.
Counter on MTAS node.
MtasMmtTermOrigSessNOkECause The number of unsuccessful call completion
due to external faults in Originating MMTEL
AS. The counter is keyed on cause of fault
in Reason Header.
The counter is incremented when MMTEL
AS deducts faults in the external nodes like
Charging server,HSS or DNS.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 91 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMmtTermTermSessOk The number of successful call completion in

Terminating MMTEL AS triggered by UE.
The counter is incremented when BYE
request with Reason header with SIP;cause
= 487 is received or with Q.850;cause=16 is
received from network.
The counter is keyed on cause in reason
header.
Counter on MTAS node.
MtasMmtTermTermSessNOkI The accumulated number of MMTel
sessions, in the Terminating MTAS,
terminated prematurely by the MTAS due to
internal reasons. The counter is keyed on
the CSCF IP address.
Counter on MTAS node.
MtasMmtTermTermSessNOkE The accumulated number of MMTel
sessions, in the terminating MTAS,
terminated prematurely by the MTAS due to
external reasons. The counter is keyed on
the CSCF IP address.
Counter on MTAS node.
MtasMmtTermTermSessNOkECause The number of unsuccessful call completion
due to external faults in terminating MMTEL
AS. The counter is keyed on cause of fault
in Reason Header.
The counter is incremented when MMTEL
AS deducts faults in the external nodes like
Charging server,HSS or DNS.
Counter on MTAS node.
MtasMmtTermOrigSessNOkECause The number of unsuccessful call completion
due to external faults in Originating MMTEL
AS. The counter is keyed on cause of fault
in Reason Header.
The counter is incremented when MMTEL
AS deducts faults in the external nodes like
Charging server,HSS or DNS.
Counter on MTAS node.
MtasSccTermOrigCsSessNOk The number of unsuccessful call completion
from CS domain in Originating SCC AS
triggered by network. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when BYE
request with Reason header other than
SIP;cause = 487 is received or with
Q.850;cause=16 received from network or
BYE request from network without reason
header.
Counter on SCC AS node.
 Ericsson Internal
OPERAT. GUIDELINES 92 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccTermOrigCsSessNOkI The accumulated number of SCC session

completion from CS domain due to node
internal reasons like crash, in the originating
SCC AS. The counter is keyed on the CSCF
IP address.
Counter on SCC AS node.
MtasSccTermOrigCsSessNOkECause The number of unsuccessful call completion
from CS domain due to external faults in
Originating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS deducts with the external nodes
like Charging server,HSS or DNS.
Counter on SCC AS node.
MtasSccTermOrigCsSessNOkService The number of unsuccessful call completion
Cause from CS domain due to service logic in
Originating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS triggers the termination.
Counter on SCC AS node.
MtasSccTermTermCsSessOk The number of successful call completion
from CS domain in Terminating SCC AS
triggered by UE. The counter is keyed on
cause in Reason Header.
The counter is incremented when BYE
request with Reason header with SIP;cause
= 487 is received or with Q.850;cause=16 is
received from network.
Counter on SCC AS node.
MtasSccTermTermCsSessNOk The number of unsuccessful call completion
from CS domain in Terminating SCC AS
triggered by network. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when BYE
request with Reason header other than
SIP;cause = 487 is received or with
Q.850;cause=16 received from network or
BYE request from network without reason
header.
Counter on SCC AS node.
MtasSccTermTermCsSessNOkI The accumulated number of SCC session
completion from CS domain due to node
internal reasons like crash, in the
Terminating SCC AS. The counter is keyed
on the CSCF IP address.
Counter on SCC AS node.
 Ericsson Internal
OPERAT. GUIDELINES 93 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccTermTermCsSessNOkECaus The number of unsuccessful call completion

e from CS domain due to external faults in
Terminating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS deducts with the external nodes
like Charging server,HSS or DNS.
Counter on SCC AS node.
MtasSccTermTermCsSessNOkServic The number of unsuccessful call completion
eCause from CS domain due to service logic in
Terminating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS triggers the termination.
Counter on SCC AS node.
MtasSccTermOrigPsSessOk The number of successful call completion
from PS domain in Originating SCC AS
triggered by UE. The counter is keyed on
cause in Reason Header.
The counter is incremented when BYE
request with Reason header with SIP;cause
= 487 is received or with Q.850;cause=16 is
received from network.
Counter on SCC AS node.
MtasSccTermOrigPsSessNOk The number of unsuccessful call completion
from PS domain in Originating SCC AS
triggered by network. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when BYE
request with Reason header other than
SIP;cause = 487 is received or with
Q.850;cause=16 received from network or
BYE request from network without reason
header.
Counter on SCC AS node.
MtasSccTermOrigPsSessNOkI The accumulated number of SCC session
completion from PS domain due to node
internal reasons like crash, in the originating
SCC AS. The counter is keyed on the CSCF
IP address.
Counter on SCC AS node.
MtasSccTermOrigPsSessNOkECause The number of unsuccessful call completion
from PS domain due to external faults in
Originating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS deducts with the external nodes
like Charging server,HSS or DNS.
Counter on SCC AS node.
 Ericsson Internal
OPERAT. GUIDELINES 94 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccTermOrigPsSessNOkService The number of unsuccessful call completion

Cause from PS domain due to service logic in
Originating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS triggers the termination.
Counter on SCC AS node.
MtasSccTermTermPsSessOk The number of successful call completion
from PS domain in Terminating SCC AS
triggered by UE. The counter is keyed on
cause in Reason Header.
The counter is incremented when BYE
request with Reason header with SIP;cause
= 487 is received or with Q.850;cause=16 is
received from network.
Counter on SCC AS node.
MtasSccTermTermPsSessNOk The number of unsuccessful call completion
from PS domain in Terminating SCC AS
triggered by network. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when BYE
request with Reason header other than
SIP;cause = 487 is received or with
Q.850;cause=16 received from network or
BYE request from network without reason
header.
Counter on SCC AS node.
MtasSccTermTermPsSessNOkI The accumulated number of SCC session
completion from PS domain due to node
internal reasons like crash, in the
Terminating SCC AS. The counter is keyed
on the CSCF IP address.
Counter on SCC AS node.
MtasSccTermTermPsSessNOkECaus The number of unsuccessful call completion
e from PS domain due to external faults in
Terminating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS deducts with the external nodes
like Charging server,HSS or DNS.
Counter on SCC AS node.
MtasSccTermTermPsSessNOkServic The number of unsuccessful call completion
eCause from PS domain due to service logic in
Terminating SCC AS. The counter is keyed
on cause of fault in Reason Header.
The counter is incremented when Service in
SCC AS triggers the termination.
Counter on SCC AS node.
MtasSrvccTransferOk The number of successful access transfers
using Single Radio Voice Call Continuity.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 95 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSrvccTransferNOkE The number of unsuccessful (due to node

external error) access transfers attempts
using Single Radio Voice Call Continuity.
Counter on MTAS node.
MtasSrvccTransferNOkI The number of unsuccessful (due to node
internal error) access transfers attempts
using Single Radio Voice Call Continuity.
Counter on MTAS node.
MtasSrvccEAttempt The number of attempts to initiate access
transfer using enhanced Single Radio Voice
Call Continuity (Rel. 10-12).
Counter on MTAS node.
MtasSrvccETransferNOkE The number of unsuccessful (due to node
external error) access transfers using
enhanced Single Radio Voice Call
Continuity (Rel. 10-12).
Counter on MTAS node.
MtasSrvccETransferNOkI The number of unsuccessful (due to node
internal error) access transfers using
enhanced Single Radio Voice Call
Continuity (Rel. 10-12).
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.5 IMS MMTEL AS Hold/Resume Service Accessibility

6.5.1 Definition

IMS MMTEL AS Hold/Resume Service Accessibility is defined as the

probability of being able to successfully access the Hold/Resume services.

6.5.2 Formula

Equation 96. IMS MMTEL AS Hold Service Success Ratio

IMSMMTelASHoldSuccRatio[%] = 100 *
MtasHoldInitiatedHoldOk
MtasHoldInitiatedHold
Equation 97. IMS MMTEL AS Resume Service Success Ratio

IMSMMTelASHoldSuccRatio[%] = 100 *
MtasHoldInitiatedResumeOk
MtasHoldInitiatedResume
 Ericsson Internal
OPERAT. GUIDELINES 96 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasHoldInitiatedHold The number of initiated Holds in the MTAS

for invoking UA.
Counter on MTAS node.
The number of successful initiated Holds in
MtasHoldInitiatedHoldOk the MTAS for the invoking UA.
Counter on MTAS node.

MtasHoldInitiatedResume The number of initiated Resumes in the

MTAS for invoking UA.
Counter on MTAS node.

MtasHoldInitiatedResumeOk The number of successful initiated resumes.

Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.6 IMS MMTEL AS Communication Diversion Service Accessibility

6.6.1 Definition

IMS MMTEL AS Communication Diversion Service Accessibility is defined as

the probability of being able to successfully access the Communication
Diversion service.

6.6.2 Formula

Equation 98. IMS MMTEL AS Communication Diversion

Success Ratio

IMSMMTelASCallDiversionSuccRatio[%] = 100 *
MtasCDivNumberOfCdivOk
MtasCDivNumberOfCdivOk + MtasCDivNumberOfCdivNotOk

The measurements in the formula are keyed by type of diversion, so the

formula may be expressed per type of diversion or as a sum of all types of
diversion.
Counter Name Definition

MtasCDivNumberOfCdivOk A performance measurement (PM) counter

that is incremented each time
Communication Diversion (CDiv)
successfully establishes communication
following diversion of an incoming
communication. There is one counter for the
entire node. The counter is keyed by type of
diversion: CFU, CFB, CFNR, CFNL, CDar,
CDwr, CFNRc, DNDCF.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 97 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

A performance measurement (PM) counter
MtasCDivNumberOfCdivNotOk that is incremented each time
Communication Diversion (CDiv) fails for
any reason to establish communication
following diversion of an incoming
communication. There is one counter for the
entire node. The counter is keyed by type of
diversion: CFU, CFB, CFNR, CFNL, CDar,
CDwr, CFNRc, DNDCF.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.7 IMS MMTEL AS Conference Service Accessibility

6.7.1 Definition

IMS MMTEL AS Conference Service Accessibility is defined as the probability

of being able to successfully initiate the conference services.

6.7.2 Formula

Equation 99. IMS MMTEL AS Conference Creation Success

Ratio

IMSMMTelASConfCreateSuccRatio[%] = 100 *
MtasConfCreationOk
(MtasConfCreationOk + MtasConfCreationNOkI +
MtasConfCreationNOkE)

Equation 100. IMS MMTEL AS Joined Conference Participant

Success Ratio

IMSMMTelASJoinedConfPartSuccRatio[%] = 100 *
MtasConfDialOutOk
(MtasConfDialOutOk + MtasConfDialOutNOkI +
MtasConfDialOutNOkE)

Counter Name Definition

MtasConfCreationOk The number of successfully created

conference sessions.
Counter on MTAS node.
The number of unsuccessful conference
MtasConfCreationNOkI creation attempts due to node internal
reasons.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 98 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasConfCreationNOkE The number of unsuccessful conference

creation attempts due to node external
reasons.
Counter on MTAS node.

MtasConfDialOutOk The number of successfully joined

conference participants through dial-out.
Counter on MTAS node.

MtasConfDialOutNOkI The number of failed dial-out attempts due

to node internal reasons.
Counter on MTAS node.

MtasConfDialOutNOkE The number of failed dial-out attempts due

to node external reasons, for example an
MRFP failure.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.8 IMS Conference AS Scheduled Conference Accessibility

6.8.1 Definition

IMS Conference AS Scheduled Conference Accessibility is defined as the

probability of being able to successfully initiate the scheduled conference
services.

6.8.2 Formula

Equation 101. IMS Conference AS Scheduled Conference Dial-

in Success Ratio

IMSConfASSchedConfSuccRatio[%] = 100 *
MtasConfSchedAttempt -
(MtasConfSchedDialInNOkE + MtasConfSchedDialInNOkI)
MtasConfSchedAttempt
Counter Name Definition

MtasConfSchedAttempt The number of dial-in attempts to a

scheduled conference.
Counter on MTAS node.

MtasConfSchedDialInNOkE The number of failed dial-in attempts to a

scheduled conference due to node external
reasons.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 99 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

The number of failed dial-in attempts to a
MtasConfSchedDialInNOkI scheduled conference due to node internal
reasons.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.9 IMS MTAS Conference Service Retainability

6.9.1 Definition

IMS MTAS Conference Service Retainability is defined as the probability of

being able to successfully successfully complete (normally terminate) the
active conferences.

6.9.2 Formula

Equation 102. IMS MTAS Conference Termination Success

Ratio

IMSMTASConfTer min ateSuccRatio[%] = 100 *

(MtasConfCreationOk - MtasConfTerminatedNOkI -
MtasConfTerminatedNOkE)
MtasConfCreationOk
Counter Name Definition

MtasConfCreationOk The number of successfully created

conference sessions.
Counter on MTAS node.
The number of successfully created
MtasConfTerminatedNOkI conference sessions, abnormally terminated
due to node internal reasons (faults). A
conference is normally terminated by the
Conference Creator. Abnormal termination
is performed by the Conference Focus due
to the occurrence of an unexpected node
internal event/fault that means that the
conference cannot continue.
Counter on MTAS node.

MtasConfTerminatedNOkE The number of successfully created

conference sessions, abnormally terminated
due to node external reasons (faults). A
conference is normally terminated by the
Conference Creator. Abnormal termination
is performed by the Conference Focus due
to the occurrence of an unexpected node
external event/fault that means the
conference cannot continue, for example an
MRFP failure.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 100 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.10 IMS MMTEL AS Calling Name Identification Presentation (CNIP)

Services Accessibility
6.10.1 Definition

IMS MMTEL AS Calling Name Identification Presentation (CNIP) Services

Accessibility is defined as the probability of being able to successfully invoke
the Calling Name Identification Presentation (CNIP) services. When
presentation of the caller's name is restricted is considered as a normal
condition, and thus not counted as failure.

6.10.2 Formula

Equation 103. IMS MMTEL AS Calling Name Identification

Presentation (CNIP) Success Ratio

IMSMMTelASId Pr esCnipSuccRatio[%] = 100 *

(MtasIdPresCnipAttempt - MtasIdPresCnipNOkNotFound -
Keyn

∑ MtasIdPresCnipFailed(Key))
Key1

MtasIdPresCnip

Where key is one of the following failing reasons:

• LICENSES

• OUT-OF-SERVICE

• SUBSCRIBE-FAILURE

• MALFORMED-NOTIFY-BODY

Counter Name Definition

MtasIdPresCnipAttempt The number of CNIP external queries to

retrieve the caller display name.
Counter on MTAS node.
The number of invocations of the CNIP
MtasIdPresCnip service.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 101 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

The number of times the CNIP service was
MtasIdPresCnipFailed not successfully executed. The key
describes the reason why it was not
successful. Current list of keys:
- LICENSES
- OUT-OF-SERVICE
- SUBSCRIBE-FAILURE
- MALFORMED-NOTIFY-BOD Y
This counter is not applicable when using
NameDb.
Counter on MTAS node.
The number of invocations of the CNIP
MtasIdPresCnipNOkNotFound service where no display name is found for
the caller.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.11 IMS MMTEL AS Announcement Service Accessibility

6.11.1 Definition

IMS MMTEL AS Announcement Service Accessibility is defined as the

probability of being able to successfully successfully initiate the playing of an
announcement from MTAS MRFC to an external MRFP.

6.11.2 Formula

Equation 104. IMS MMTEL AS Playing of Announcement

Success Ratio

IMSMMTelASAnnouncementSuccRatio[%] = 100 *
MtasMrfcInitiatedAnnOk(key : annCode)
(MtasMrfcInitiatedAnnOk(key : annCode) +
MtasMrfcInitiatedAnnNOkI(key : annCode) +
MtasMrfcInitiatedAnnNOkE(key : annCode))

The counters in this formula are indexed with the announcement code
(annCode). The formula result may be presented per announcement code or
added to a sum for all announcement codes.
Counter Name Definition

MtasMrfcInitiatedAnnOk The number of successfully initiated playing

of announcement. The counter is keyed on
announcement code.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 102 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

The number of unsuccessfully initiated
MtasMrfcInitiatedAnnNOkI playing of announcement due to internal
error in MTAS.The counter is keyed on
announcement code.
Counter on MTAS node.

MtasMrfcInitiatedAnnNOkE The number of unsuccessfully initiated

playing of announcement due to external
error, e.g. in MRFP. The counter is keyed
on announcement code.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.12 IMS MMTEL AS Abbreviated Dialing Service Accessibility

6.12.1 Definition

IMS MMTEL AS Abbreviated Dialing Service Accessibility is defined as the

probability of being able to successfully invoke the Abbreviated Dialing
service.

6.12.2 Formula

Equation 105. IMS MMTEL AS Abbreviated Dialing Success

Ratio

IMSMMTelASAbDiaSuccRatio[%] = 100 *
MtasAbDialOk
(MtasAbDialOk + MtasAbDialNOk)

Counter Name Definition

MtasAbDialOk Count of the total number of successful

invocation of the Abbreviated Dialing
function.
Counter on MTAS node.
Count of the total number of unsuccessful
MtasAbDialNOk invocations of the Abbreviated Dialing
function. Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].
 Ericsson Internal
OPERAT. GUIDELINES 103 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.13 IMS MMTEL AS Dial Tone Management Service Accessibility

6.13.1 Definition

IMS MMTEL AS Dial Tone Management Service Accessibility is defined as

the probability of being able to successfully send a NOTIFY for a dial tone
pattern.

6.13.2 Formula

Equation 106. IMS MMTEL AS Playing of Announcement

Success Ratio

IMSMMTelASDTMSuccRatio[%] = 100 *
MtasDtmNotifyOk
(MtasDtmNotifyOk + MtasDtmNotifyNOkI +
MtasDtmNotifyNOkE)

Counter Name Definition

MtasDtmNotifyOk MtasDtmNotifyOk contains the count of the

total number of NOTIFY messages sent for
dial tone pattern.
Counter on MTAS node.
MtasDtmNotifyNOkl contains the count of
MtasDtmNotifyNOkI the total number of unsuccessful NOTIFY
messages sent for dial tone pattern.
Counter on MTAS node.

MtasDtmNotifyNOkE MtasDtmNotifyNOkE contains the count of

the total number of successful NOTIFY
(dial-tone-pattern) messages sent, that get
no reply or a failure response. If the failure
is due to absence of a valid DTM license,
the counter is keyed by "LICENSES".
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.14 IMS MMTEL AS Communication Waiting Service Accessibility

6.14.1 Definition

IMS MMTEL AS Communication Waiting Service Accessibility is defined as

the probability of a user accepted a communication waiting notification.

Note this formula id for user behaviour; it does not reflect the network
function.
 Ericsson Internal
OPERAT. GUIDELINES 104 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.14.2 Formula

Equation 107. IMS MMTEL AS (User) Communication Waiting

Success Ratio

IMSMMTelASCWSuccRatio[%] = 100 *
MtasCwAccepted
MtasCwUsed

Counter Name Definition

MtasCwAccepted Number of waiting communications that

have been accepted by Communication
Waiting subscribers.
Counter on MTAS node.
Number of times the Communication
MtasCwUsed Waiting has been used by Communication
Waiting Subscribers.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.15 IMS MMTEL AS Advice of Charge Service Accessibility

6.15.1 Definition

IMS MMTEL AS Advice Of Charge (AOC) Service Accessibility is defined as

the probability of being able to successfully invoke the AoC Service.

6.15.2 Formula

Equation 108. IMS MMTEL AS Advice of Charge Start (AoC-S)

Success Ratio

IMSMMTelASAOCStartSuccRatio[%] = 100 *
MtasAocStartOk
(MtasAocStartOk + MtasAocStartNOkI +
MtasAocStartNOkE)

Equation 109. IMS MMTEL AS Advice of Charge During (AoC-D)

Success Ratio

IMSMMTelASAOCDuringSuccRatio[%] = 100 *
MtasAocDuringOk
(MtasAocDuringOk + MtasAocDuringNOkI +
MtasAocDuringNOkE)
 Ericsson Internal
OPERAT. GUIDELINES 105 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 110. IMS MMTEL AS Advice of Charge End (AoC-E)

Success Ratio

IMSMMTelASAOCEndSuccRatio[%] = 100 *
MtasAocEndOk
(MtasAocEndOk + MtasAocEndNOkI +
MtasAocEndNOkE)
Counter Name Definition

MtasAocStartOk The Advice of Charge-Start (AoC-S) service

type has been successfully executed at the
start of a communication.
Counter on MTAS node.
MtasAocStartNOkI Due to an internal error, MTAS failed
provide the required AoC-S tariff data at
communication setup. Counter on MTAS
node.
Counter on MTAS node.
MtasAocStartNOkE MTAS failed to provide the required AoC-S
tariff data at communication setup due to an
external error. An external error includes the
receipt of an incomplete tariff or a missing
tariff.
Counter on MTAS node.
MtasAocDuringOk The Advice of Charge-During (AoC-D)
service type indicating the cost incurred to
date has been successfully executed.
Counter on MTAS node.
MtasAocDuringNOkI The Advice of Charge-During (AoC-D)
service type indicating the cost incurred to
date, fails to complete, due to an internal
error.
Counter on MTAS node.
MtasAocDuringNOkE The Advice of Charge-During (AoC-D)
service type indicating the cost incurred to
date, fails to complete, due to an external
error.
Counter on MTAS node.
MtasAocEndOk The Advice of Charge-End (AoC-E) service
type indicating the cost of an event has
been successfully executed.
Counter on MTAS node.
MtasAocEndNOkI The Advice of Charge-End (AoC-E) service
type indicating the cost, fails to complete,
due to an internal error.
Counter on MTAS node.
MtasAocEndNOkE The Advice of Charge-End (AoC-E) service
type indicating the cost, fails to complete,
due to an external error.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 106 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.16 IMS MMTEL AS Third Party (3PTY) Call Creation Accessibility

6.16.1 Definition

IMS Multimedia Third Party (3PTY) Call Creation Accessibility is defined as

the probability of being able to successfully make a Third Party (3PTY) Call
Creation.

6.16.2 Formula

Equation 111. IMS MMTel AS Third Party (3PTY) Call Creation

Success Ratio

IMSMMTelASThirdPartyCallCreationSuccRatio[%] = 100 *
Mtas3ptyCreationOk
(Mtas3ptyCreationOk + Mtas3ptyCreationNOkE +
Mtas3ptyCreationNOkI)
Counter Name Definition

Mtas3ptyCreationOk The number of successfully created 3PTY

calls.
Mtas3ptyCreationNOkE The number of failed attempts to create
3PTY calls due to node external reasons.
Mtas3ptyCreationNOkI The number of failed attempts to create
3PTY calls due to node internal reasons.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref.
[26].

6.17 IMS MMTEL AS Third Party (3PTY) Call Creation Retainability

6.17.1 Definition

IMS Multimedia Third Party (3PTY) Call Creation Retainability is defined as

the probability of being able to successfully complete (normally terminate) a
Third Party (3PTY) Call once it was successfully established.

6.17.2 Formula

Equation 112. IMS MMTel AS Third Party (3PTY)

Communication Completion Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 107 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASThirdPartyCommCompletionSuccRatio[%] = 100 *
(Mtas3ptyCreationOk - Mtas3ptyTerminationNOkE -
Mtas3ptyTerminationNOkI)
Mtas3ptyCreationOk

Counter Name Definition

Mtas3ptyCreationOk The number of successfully created 3PTY

calls.
Mtas3ptyTerminationNOkE The number of abnormaly terminated 3PTY
calls due to node external reasons.
Mtas3ptyTerminationNOkI The number of abnormaly terminated 3PTY
calls due to node internal reasons.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.18 IMS MMTEL AS Communication Completion Service Accessibility

6.18.1 Definition

IMS MMTEL AS Communication Completion Service Accessibility is defined

as the probability of being able to successfully invoke the Communication
Completion Service. The Communication Completion services are of type
Communication Completion Busy Subscriber (CCBS) and Communication
Completion No Reply (CCNR)

6.18.2 Formula

6.18.2.1 Communication Completion Busy Subscriber (CCBS)

Equation 113. IMS MMTEL AS Communication Completion

Busy Subscriber (CCBS) Invocation Success Ratio

IMSMMTelASCCBSInvocationSuccRatio[%] = 100 *
MtasCcbsInvocationOrigOk
(MtasCcbsInvocationOrigOk + MtasCcbsInvocationOrigNOkI +
MtasCcbsInvocationOrigNOkE)

6.18.2.2 Communication Completion No Reply (CCNR)

Equation 114. IMS MMTEL AS Communication Completion No

Reply (CCNR) Invocation Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 108 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASCCNRInvocationSuccRatio[%] = 100 *
MtasCcnrInvocationOrigOk
(MtasCcnrInvocationOrigOk + MtasCcnrInvocationOrigNOkI +
MtasCcnrInvocationOrigNOkE)
Counter Name Definition

MtasCcbsInvocationOrigOk The total number of successful originating

Communication Completion Busy
Subscriber (CCBS) invocations.
Counter on MTAS node.
MtasCcbsInvocationOrigNOkI The total number of unsuccessful
Communication Completion Busy
Subscriber (CCBS) originating invocations
because of an internal error.
Counter on MTAS node.
MtasCcbsInvocationOrigNOkE The total number of unsuccessful
Communication Completion Busy
Subscriber (CCBS) originating invocations
because of an external error.
Counter on MTAS node.
MtasCcnrInvocationOrigOk The total number of successful originating
Communication Completion No Reply
(CCNR) invocations.
Counter on MTAS node.
MtasCcnrInvocationOrigNOkI The total number of unsuccessful
Communication Completion No Reply
(CCNR) originating invocations because of
an internal error.
Counter on MTAS node.
MtasCcnrInvocationOrigNOkE The total number of unsuccessful
Communication Completion No Reply
(CCNR) originating invocations because of
an external error.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.19 IMS MMTEL AS Flexible Communication Distribution Service

Accessibility
6.19.1 Definition

IMS MMTEL AS Flexible Communication Distribution (FCD) Service

Accessibility is defined as the probability of being able to successfully invoke
the Flexible Communication Distribution Service
 Ericsson Internal
OPERAT. GUIDELINES 109 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.19.2 Formula

Equation 115. IMS MMTEL AS Flexible Communication

Distribution (FCD) Success Ratio

IMSMMTelASFCDSuccRatio[%] = 100 *
MtasFcdOk
MtasFcdNumberOfAttempt

Equation 116. IMS MMTEL AS Flexible Communication

Distribution (FCD) Ongoing Sessions

IMSMMTelASFCDOngoingSessions =
MtasFcdOngoingSessions

Counter Name Definition

MtasFcdOk A performance measurement (PM) counter

that is incremented each time Flexible
Communication Distribution Divert Primary
(FCDDP) successfully establishes
connection when the primary diverted target
answers the incoming communication.
There is one counter for the entire node.
Counter on MTAS node.
MtasFcdNumberOfAttempt A performance measurement (PM) counter
that is incremented each time there is
Flexible Communication Distribution (FCD)
session attempts.
Counter on MTAS node.
MtasFcdOngoingSessions Counter for the number of ongoing Flexible
Communication Distribution (FCD) Service
Sessions.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.20 IMS MMTEL AS Short Number Dialing Accessibility

6.20.1 Definition

IMS MMTEL AS Short Number Dialing (SND) Service Accessibility is defined

as the probability of being able to successfully invoke the Short Number
Dialing Service
 Ericsson Internal
OPERAT. GUIDELINES 110 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.20.2 Formula

Equation 117. IMS MMTEL AS Originating Short Number Dialing

(SND) Success Ratio

IMSMMTelASOrgSNDSuccRatio[%] = 100 *
MtasSndOrigSuccAttempt
(MtasSndOrigSuccAttempt + MtasSndOrigFailAttempt)

Equation 118. IMS MMTEL AS Terminating Short Number

Dialing (SND) Success Ratio

IMSMMTelASTermSNDSuccRatio[%] = 100 *
MtasSndTermSuccAttempt
(MtasSndTermSuccAttempt + MtasSndTermFailAttempt)

Counter Name Definition

MtasSndOrigSuccAttempt Number of received 180 Ringing message

or received 2xx (INVITE) if no 180 Ringing
message has been received, by the
originating MTAS.
Counter on MTAS node.
MtasSndOrigFailAttempt Number of rejected SND INVITES by the
originating MTAS. Incremented when
receiving PAI and ReqURI domains don't
match on originating MTAS.
Counter on MTAS node.
MtasSndTermSuccAttempt Number of received 180 Ringing message
or received 2xx (INVITE) if no 180 Ringing
message has been received, by the
terminating MTAS.
Counter on MTAS node.
MtasSndTermFailAttempt Number of rejected SND INVITES by the
terminating MTAS. Incremented when
receiving PAI and ReqURI domains don't
match on terminating MTAS.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.21 IMS SCC AS Centralization and Continuity (SCC) Accessibility

6.21.1 Definition

IMS SCC AS Centralization and Continuity (SCC) Service Accessibility is

defined as the probability of being able to successfully invoke the Service
Centralization and Continuity (SCC) Service from CS side and PS side.
 Ericsson Internal
OPERAT. GUIDELINES 111 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.21.2 Formula

ICS Session accessibility; Answer to Seizure Ratio (ASR). It is the percentage

of answered telephone calls with respect to the total call volume.

Originating SCC

Equation 119. IMS SCC AS Originating Service from CS

Success Ratio

IMSSCCASOrigCSSuccRatio[%] = 100 *
MtasSccInitOrigSessCsOk
(MtasSccInitOrigSessCsOk + MtasSccInitOrigSessCsNOkE +
MtasSccInitOrigSessCsNOkI)

Equation 120. IMS SCC AS Originating Service from PS

Success Ratio

IMSSCCASOrigPSSuccRatio[%] = 100 *
MtasSccInitOrigSessPsOk
(MtasSccInitOrigSessPsOk + MtasSccInitOrigSessPsNOkE +
MtasSccInitOrigSessPsNOkI)

Equation 121. IMS SCC AS Originating Unregistered Service

from CS Success Ratio

IMSSCCASOrigUnregCSSuccRatio[%] = 100 *
MtasSccInitOrigUnregSessCsOk
(MtasSccInitOrigUnregSessCsOk + MtasSccInitOrigUnregSessCsNOkE +
MtasSccInitOrigUnregSessCsNOkI)

Equation 122. IMS SCC AS Originating Unregistered Service

from PS Success Ratio

IMSSCCASOrigUnregPSSuccRatio[%] = 100 *
MtasSccInitOrigUnregSessPsOk
(MtasSccInitOrigUnregSessPsOk + MtasSccInitOrigUnregSessPsNOkE +
MtasSccInitOrigUnregSessPsNOkI)

Terminating SCC

Equation 123. IMS SCC AS Terminating Service Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 112 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASTermSuccRatio[%] = 100 *
MtasSccInitTermSessOk
(MtasSccInitTermSessOk + MtasSccInitTermSessNOkE +
MtasSccInitTermSessNOkI)

Equation 124. IMS SCC AS Terminating Unregistered Service

Success Ratio

IMSSCCASTermUnregSuccRatio[%] = 100 *
MtasSccInitTermUnregSessOk
(MtasSccInitTermUnregSessOk + MtasSccInitTermUnregSessNOkE +
MtasSccInitTermUnregSessNOkI)

Session accessibility, R-KPIs for Network Efficiency Ratio (NER). They reflect
the percentage of calls where the called user was alerted for a new call. Note
that user behavior factors are included in the formulas.

Equation 125. IMS SCC AS Terminating Service to VoLTE CS

UE Success Ratio

IMSSCCASTermCSSuccRatio[%] = 100 *
MtasSccTermCsSuccAttempt
(MtasSccTermCsSuccAttempt + MtasSccTermCsFailedAttempt)

Equation 126. IMS SCC AS Terminating Service to VoLTE PS

UE Success Ratio

IMSSCCASTermPSSuccRatio[%] = 100 *
MtasSccTermPsSuccAttempt
(MtasSccTermPsSuccAttempt + MtasSccTermPsFailedAttempt)

Equation 127. IMS SCC AS Terminating Unregistered Service to

VoLTE CS UE Success Ratio

IMSSCCASTermUnregCSSuccRatio[%] = 100 *
MtasSccTermUnregCsSuccAttempt
(MtasSccTermUnregCsSuccAttempt + MtasSccTermUnregCsFailedAttempt)

Equation 128. IMS SCC AS Terminating Unregistered Service to

VoLTE PS UE Success Ratio

IMSSCCASTermUnregPSSuccRatio[%] = 100 *
MtasSccTermUnregPsSuccAttempt
(MtasSccTermUnregPsSuccAttempt + MtasSccTermUnregPsFailedAttempt)
 Ericsson Internal
OPERAT. GUIDELINES 113 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

SCC from CS including CAP signaling

Equation 129. IMS SCC AS Session Setup from CS using CAP

Registered and Unregistered Users Success Ratio

IMSSCCASCSSetupWithCAPSuccRatio[%] = 100 *
(MtasSccInitOrigSessCsOk + MtasSccInitOrigUnregSessCsOk +
MtasSccTermCsSuccAttempt + MtasSccTermUnregCsSuccAttempt)
(MtasSccInitOrigSessCsOk + MtasSccInitOrigSessCsNOkE +
MtasSccInitOrigSessCsNOkI +
MtasSccInitOrigUnregSessCsOk + MtasSccInitOrigUnregSessCsNOkE +
MtasSccInitOrigUnregSessCsNOkI +
MtasSccTermCsSuccAttempt + MtasSccTermCsFailedAttempt +
MtasSccTermUnregCsSuccAttempt + MtasSccTermUnregCsFailedAttempt) *
MtasSdsCapInitDPOk
(MtasSdsCapInitDPOk + MtasSdsCapInitDPNOkE +
MtasSdsCapInitDPNOkI)

Note: The above formula Equation 135 is a combination of the CAP and SIP
signaling for the SCC CS service (registered and unregistered) invocation. It
reflects answer to seizure (ASR) accessibility. It is the percentage of
answered telephone calls with respect to the total call volume.
Counter Name Definition

MtasSccInitOrigSessCsOk The accumulated number of SCC session

attempts from the CS access domain, in the
originating MTAS, which was either
answered, not answered, or was rejected by
a service due to operator policy. The
counter is keyed on the CSCF IP address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 114 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitOrigSessCsNOkE The accumulated number of SCC session

attempts from the CS access domain, in the
originating MTAS, which was rejected due
to node external reasons. The counter is
keyed on the CSCF IP address.
The counter is incremented by 1 in the
originating MTAS, if the INVITE-ACK
transaction did not conclude successfully
due to external reasons, for example invalid
feature tag or too many media components
in SDP or because of receiving a 4xx, 5xx,
or 6xx as the final response, or any
signaling transactions to external nodes
failed or timed out and the configuration of
the MTAS required the interaction with the
external node to be successful in order to
proceed the session. The counter will only
be stepped for one of the reasons (once,
that is) for a particular session setup.
Counter on MTAS node.
MtasSccInitOrigSessCsNOkI The accumulated number of SCC session
attempts from the CS access domain, in the
originating MTAS, which was rejected due
to node internal reasons. The counter is
keyed on the CSCF IP address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSdsCapInitDPOk This counter is the accumulated number of
CAMEL Application Part (CAP) InitialDP
requests processed successfully.
Counter on MTAS node.
MtasSdsCapInitDPNOkE This counter is the accumulated number of
CAMEL Application Part (CAP) InitialDP
requests that failed because the request
message was faulty, for example missing
mandatory parameter or parameter having
unknown value.
Counter on MTAS node.
MtasSdsCapInitDPNOkI This counter is the accumulated number of
CAMEL Application Part (CAP) InitialDP
requests that failed because of problems
internal to the SCC AS, an IMRN could not
be allocated, for example because of no
free IMRN.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 115 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitOrigSessPsOk The accumulated number of SCC session

attempts from the PS access domain, in the
originating MTAS, which was either
answered, not answered, or was rejected by
a service due to operator policy. The
counter is keyed on the CSCF IP address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
MtasSccInitOrigSessPsNOkE The accumulated number of SCC session
attempts from the PS access domain, in the
originating MTAS, which was rejected due
to node external reasons. The counter is
keyed on the CSCF IP address.
The counter is incremented by 1 in the
originating MTAS, if the INVITE-ACK
transaction did not conclude successfully
due to external reasons, for example invalid
feature tag, too many media components in
SDP or ICS UE signalling over Gm when
attached to CS is not supported or because
of receiving a 4xx, 5xx, or 6xx as the final
response, or any signaling transactions to
external nodes failed or timed out and the
configuration of the MTAS required the
interaction with the external node to be
successful in order to proceed the session.
The counter will only be stepped for one of
the reasons (once, that is) for a particular
session setup.
Counter on MTAS node.
MtasSccInitOrigSessPsNOkI The accumulated number of SCC session
attempts from the PS access domain, in the
originating MTAS, which was rejected due
to node internal reasons. The counter is
keyed on the CSCF IP address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSccInitOrigUnregSessCsOk The accumulated number of SCC session
attempts from an unregistered user in the
CS access domain, in the originating MTAS,
which was either answered, not answered,
or was rejected by a service due to operator
policy. The counter is keyed on the CSCF
IP address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 116 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitOrigUnregSessCsNOkE The accumulated number of SCC session

attempts from an unregistered user on the
CS access domain, in the originating MTAS,
which was rejected due to node external
reasons. The counter is keyed on the CSCF
IP address.
Incremented by 1 in originating MTAS if;
The INVITE-ACK transaction did not
conclude successfully e.g invalid feature tag
or too many media components in SDP or
because SCC AS rejects an INVITE
unregistered from the CS domain due to
external reasons, e.g request not supported
by SCC AS or because any signaling
transactions towards external nodes failed
or timed out and the configuration of MTAS
required the interaction with the external
node to be successful in order to proceed
the call. The counter will only be stepped for
one of the reasons (that is, once) for a
particular call setup.
Counter on MTAS node.

MtasSccInitOrigUnregSessCsNOkI The accumulated number of SCC session

attempts from an unregistered user in the
CS access domain, in the originating MTAS,
which was rejected due to node internal
reasons. The counter is keyed on the CSCF
IP address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSccInitOrigUnregSessPsOk The accumulated number of SCC session
attempts from an unregistered user on the
PS access domain, in the originating MTAS,
which was either answered, not answered,
or was rejected by a service due to operator
policy. The counter is keyed on the CSCF
IP address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 117 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitOrigUnregSessPsNOkE The accumulated number of SCC session

attempts from an unregistered user in the
PS access domain, in the originating MTAS,
which was rejected due to node external
reasons. The counter is keyed on the CSCF
IP address.
Incremented by 1 in originating MTAS if;
The INVITE-ACK transaction did not
conclude successfully e.g invalid feature
tag, too many media components in SDP or
ICS UE signalling over Gm when attached
to CS is not supported or because any
signaling transactions towards external
nodes failed or timed out and the
configuration of MTAS required the
interaction with the external node to be
successful in order to proceed the call. The
counter will only be stepped for one of the
reasons (that is, once) for a particular call
setup.
Counter on MTAS node.
MtasSccInitOrigUnregSessPsNOkI The accumulated number of SCC session
attempts from an unregistered user in the
PS access domain, in the originating MTAS,
which was rejected due to node internal
reasons. The counter is keyed on the CSCF
IP address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSccInitTermSessOk The accumulated number of SCC session
attempts, in the terminating MTAS, which
was either answered, not answered, or was
rejected by a service due to operator policy.
The counter is keyed on the CSCF IP
address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 118 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitTermSessNOkE The accumulated number of SCC session

attempts, in the terminating MTAS, which
was rejected due to node external reasons.
The counter is keyed on the CSCF IP
address.
The counter is incremented by 1 in the
terminating MTAS if; the INVITE-ACK
transaction did not conclude successfully or
any signaling transactions to external nodes
failed or timed out and the configuration of
the MTAS required the interaction with the
external node to be successful in order to
proceed the session. The counter will only
be stepped for one of the reasons (once,
that is) for a particular session.
Counter on MTAS node.
MtasSccInitTermSessNOkI The accumulated number of SCC session
attempts, in the terminating MTAS, which
was rejected due to node internal reasons.
The counter is keyed on the CSCF IP
address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSccInitTermUnregSessOk The accumulated number of SCC session
attempts, in the terminating MTAS to an
unregistered user, which was either
answered, not answered, or was rejected by
a service due to operator policy. The
counter is keyed on the CSCF IP address.
Incremented by 1 when the INVITE-ACK
transaction has concluded after the final
response or when the INVITE was rejected
by a service due to operator policy.
Counter on MTAS node.
MtasSccInitTermUnregSessNOkE The accumulated number of SCC session
attempts, in the terminating MTAS to an
unregistered user, which was rejected due
to node external reasons. The counter is
keyed on the CSCF IP address.
The counter is incremented by 1 in the
terminating MTAS if; the INVITE-ACK
transaction did not conclude successfully or
any signaling transactions to external nodes
failed or timed out and the configuration of
the MTAS required the interaction with the
external node to be successful in order to
proceed the session. The counter will only
be stepped for one of the reasons (once,
that is) for a particular session.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 119 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccInitTermUnregSessNOkI The accumulated number of SCC session

attempts, in the terminating MTAS to an
unregistered user, which was rejected due
to node internal reasons. The counter is
keyed on the CSCF IP address.
Incremented by 1 when the INVITE was
rejected due to internal reasons, for
example processor or memory shortage.
Counter on MTAS node.
MtasSccTermCsSuccAttempt The accumulated number of terminating
INVITE requests from SCC AS that were
successfully responded by a VoLTE UE on
the CS access domain.
The counter is incremented when receiving
the 180 Ringing message or when receiving
the 200 OK message if no 180 Ringing
message has been received.
Counter on MTAS node.
MtasSccTermCsFailedAttempt The accumulated number of terminating
registered INVITE requests to VoLTE UE on
CS domain that were rejected. The CSCF
IP address is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx message if
MtasSccTermCsSuccAttempt has not
previously been incremented for the
session.
Counter on MTAS node.
MtasSccTermPsSuccAttempt The accumulated number of terminating
INVITE requests from SCC AS that were
successfully responded by a VoLTE UE on
the PS access domain. The CSCF IP
address is used as key.
The counter is incremented when receiving
the 180 Ringing message or when receiving
the 200 OK message if no 180 Ringing
message has been received.
Counter on MTAS node.
MtasSccTermPsFailedAttempt This counter is the accumulated number of
terminating initial INVITE requests to VoLTE
UE on CS domain that were rejected.
The CSCF IP address is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx message if
MtasSccTermPsSuccAttempt has not
previously been incremented for the
session.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 120 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSccTermUnregCsSuccAttempt The accumulated number of terminating

unregistered INVITE requests from SCC AS
that were successfully responded by a
VoLTE UE on the CS access domain. The
CSCF IP address is used as key.
The counter is incremented when receiving
the 180 Ringing message or when receiving
the 200 OK message if no 180 Ringing
message has been received.
Counter on MTAS node.
MtasSccTermUnregCsFailedAttempt The accumulated number of terminating
unregistered INVITE requests to VoLTE UE
on CS domain that were rejected. The
CSCF IP address is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx message if
MtasSccTermUnregCsSuccAttempt has not
previously been incremented for the
session.
Counter on MTAS node.
MtasSccTermUnregPsSuccAttempt The accumulated number of terminating
unregistered INVITE requests from SCC AS
that were successfully responded by a
VoLTE UE on the PS access domain. The
CSCF IP address is used as key.
The counter is incremented when receiving
the 180 Ringing message or when receiving
the 200 OK message if no 180 Ringing
message has been received.
Counter on MTAS node.
MtasSccTermUnregPsFailedAttempt The accumulated number of terminating
unregistered INVITE requests to VoLTE UE
on PS domain that were rejected. The
CSCF IP address is used as key.
The counter is incremented when receiving
3xx/4xx/5xx/6 xx message if
MtasSccTermUnregPsSuccAttempt has not
previously been incremented for the
session.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].
 Ericsson Internal
OPERAT. GUIDELINES 121 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.22 IMS SCC AS Centralization and Continuity (SCC) - SRVCC

6.22.1 Definition

IMS SCC AS Centralization and Continuity (SCC) - SRVCC is defined as the

probability of being able to successfully maintain an ongoing session using
the Single Radio Voice Call Continuity (SRVCC) Transfer service.

6.22.2 Formula

Equation 130. IMS SCC AS SR-VCC Access Transfer Success

Ratio

IMSSCCASSRVCCAccessTransferRatio[%] = 100 *
MtasSrvccETransferOk
MtasSrvccEAttempt

IMSSCCASSRVCCAccessTransferRatio is probability of successfully

maintain an ongoing session using enhanced Single Radio Voice Call
Continuity (Rel. 10-12).

Equation 131. IMS SCC AS Single Radio Voice Call Continuity

(SRVCC) Active Session Access Transfer Success Ratio

IMSSCCASSRVCCActiveSessionAccessTransferRatio[%] = 100 *
rspCoden
(MtasSrvccActiveTransferOk + ∑ MtasSrvccActiveTransferNOkUser)
rspCode1

MtasSrvccActiveAttempt

SRVCC access transfer success rate of session in Active state. Note that that
failures caused by end users are counted as success.

Equation 132. IMS SCC AS Single Radio Voice Call Continuity

(SRVCC) Alerting Access Transfer Success Ratio

IMSSCCASSRVCCAlertingAccessTransferRatio[%] = 100 *
rspCoden
(MtasSrvccAlertingTransferOk + ∑ MtasSrvccAlertingTransferNOkUser)
rspCode1

MtasSrvccAlertingAttempt

SRVCC access transfer success rate of session in Alerting state. Note that
that failures caused by end users are counted as success.

Equation 133. IMS SCC AS Single Radio Voice Call Continuity

(SRVCC) pre-Alerting Access Transfer Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 122 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASSRVCC Pr eAlertingAccessTransferRatio[%] = 100 *

rspCoden
(MtasSrvccPreAlertingTransferOk + ∑ MtasSrvccPreAlertingTransferNOkUser)
rspCode1

MtasSrvccPreAlertingAttempt

SRVCC access transfer success rate of session in pre-Alerting state. Note

that that failures caused by end users are counted as success.

Equation 134. IMS SCC AS Single Radio Voice Call Continuity

(SRVCC) Mid Call Access Transfer Success Ratio

IMSSCCASSRVCCMidCallAccessTransferRatio[%] = 100 *
rspCoden
(MtasSrvccMidcallTransferOk + ∑ MtasSrvccMidcallTransferNOkUser)
rspCode1

MtasSrvccMidcallAttempt
SRVCC access transfer success rate of session in mid call state (held call or
or additional call). Note that that failures caused by end users are counted as
success.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.2.3
Retainability: SRVCC Access Transfer Success Ratio (IMS part) [%].

SRVCC Fault Indicators per cause code

Equation 135. IMS SCC AS Network Failed Active Session

Access Transfers, per cause code

IMSSCCASNetwFailedAccessTransferActiveSession =
MtasSrvccActiveTransferNOkNet.cause

IMSSCCASNetwFailedAccessTransferActiveSession is the number of

SRVCC access transfers of session in Active state that failed or cancelled
due to network problems.

Equation 136. IMS SCC AS User Failed Active Session Access

Transfers, per cause code

IMSSCCASUserFailedAccessTransferActiveSession =
MtasSrvccActiveTransferNOkUser.cause

IMSSCCASUserFailedAccessTransferActiveSession is the number of SRVCC

access transfers of session in Active state that failed or cancelled due to
failure by end-user.

Equation 137. IMS SCC AS Network Failed Alerting Session

Access Transfers, per cause code
 Ericsson Internal
OPERAT. GUIDELINES 123 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASNetwFailedAccessTransferAlertingSession
MtasSrvccAlertingTransferNOkNet.cause

IMSSCCASNetwFailedAccessTransferAlertingSession is the number of

SRVCC access transfers of session in Alerting state that failed or cancelled
due to network problems.

Equation 138. IMS SCC AS User Failed Alerting Session Access

Transfers, per cause code

IMSSCCASUserFailedAccessTransferAlertingSession
MtasSrvccAlertingTransferNOkUser.cause

IMSSCCASUserFailedAccessTransferAlertingSession is the number of

SRVCC access transfers of session in Alerting state that failed or cancelled
due to failure by end-user.

Equation 139. IMS SCC AS Network Failed pre-Alerting Session

Access Transfers, per cause code

IMSSCCASNetwFailedAccessTransferPreAlertingSession
MtasSrvccPreAlertingTransferNOkNet.cause

IMSSCCASNetwFailedAccessTransferPreAlertingSession is the number of

SRVCC access transfers of session in pre-Alerting state that failed or
cancelled due to network problems.

Equation 140. IMS SCC AS User Failed pre-Alerting Session

Access Transfers, per cause code

IMSSCCASUserFailedAccessTransferPreAlertingSession
MtasSrvccPreAlertingTransferNOkUser.cause

IMSSCCASUserFailedAccessTransferPreAlertingSession is the number of

SRVCC access transfers of session in pre-Alerting state that failed or
cancelled due to failure by end-user.

Equation 141. IMS SCC AS Network Failed Mid-call Access

Transfers, per cause code

IMSSCCASNetwFailedMidcallAccessTransfer
MtasSrvccMidcallTransferNOkNet.cause

IMSSCCASNetwFailedMidcallAccessTransfer is the number of SRVCC Mid-

call access transfers that failed or cancelled due to network problems.

Equation 142. IMS SCC AS User Failed pre-Alerting Session

Access Transfers, per cause code
 Ericsson Internal
OPERAT. GUIDELINES 124 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASUserFailedMidcallAccessTransfer
MtasSrvccMidcallTransferNOkUser.cause

IMSSCCASUserFailedMidcallAccessTransfer is the number of SRVCC Mid-

call access transfers that failed or cancelled due to failure by end-user.

Counter Name Definition

MtasSrvccTransferOk The number of successful access transfers

using Single Radio Voice Call Continuity.
Counter on MTAS node.
MtasSrvccTransferNOkE The number of unsuccessful (due to node
external error) access transfers attempts
using Single Radio Voice Call Continuity.
Counter on MTAS node.
MtasSrvccTransferNOkI The number of unsuccessful (due to node
internal error) access transfers attempts
using Single Radio Voice Call Continuity.
Counter on MTAS node.
MtasSrvccEAttempt The number of attempts to initiate access
transfer using enhanced Single Radio Voice
Call Continuity (Rel. 10-12).
Counter on MTAS node.
MtasSrvccETransferOk The number of successful access transfers
using enhanced Single Radio Voice Call
Continuity (Rel. 10-12).
Counter on MTAS node.
MtasSrvccActiveAttempt The number of SRVCC access transfer
attempts of session in Active state.
The counter is incremented when an
INVITE due to STN-SR is received and the
target session is in active state.
Counter on MTAS node.
MtasSrvccActiveTransferNOkNet The number of SRVCC access transfers of
session in Active state that failed or
cancelled due to network problems.
The counter is incremented after an SRVCC
access transfer of session in Active state
has been initiated and the access transfer is
cancelled by MME/SGSN or failure by UE to
transition to CS, or the target CS access leg
is released with protocol=Q.850 and
cause=31, or the remote side responds with
a 5xx on the re-INVITE for media re-
negotiation.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 125 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSrvccActiveTransferNOkUser The number of SRVCC access transfers of

session in Active state that failed or
cancelled due to failure by end-user.
The counter is incremented after an SRVCC
access transfer of session in Active state
has been initiated and the access transfer is
cancelled because the target CS access leg
is released with reason other than
protocol=Q.850 and cause=31, or the
remote side responds with 4xx or 6xx on the
re-INVITE for media re-negotiation.
Keyed on transfer failure cause.
Counter on MTAS node.
MtasSrvccActiveTransferOk The number of successful SRVCC access
transfers of session in Active state.
The counter is incremented when a 200 OK
response is sent to INVITE due to STN-SR
for the transferred session in active state,
and PS fallback did not happen.
Counter on MTAS node.
MtasSrvccAlertingAttempt The number of SRVCC access transfer
attempts of session in Alerting state.
The counter is incremented when an
INVITE due to ATU-STI is received and the
target session is in alerting state.
Counter on MTAS node.
MtasSrvccAlertingTransferNOkNet The number of SRVCC access transfers of
session in Alerting state that failed or
cancelled due to network problems.
The counter is incremented after an SRVCC
access transfer of session in Alerting state
has been initiated and the access transfer is
cancelled by MME/SGSN or failure by UE to
transition to CS, or the target CS access leg
is released with protocol=Q.850 and
cause=31, or the remote side responds with
a 5xx on the UPDATE for media re-
negotiation.
Keyed on transfer failure cause.
Counter on MTAS node.
MtasSrvccAlertingTransferNOkUser The number of SRVCC access transfers of
session in Alerting state that failed or
cancelled due to failure by end-user.
The counter is incremented after an SRVCC
access transfer of session in Alerting state
has been initiated and the access transfer is
cancelled because the target CS access leg
is released with reason other than
protocol=Q.850 and cause=31, or the
remote side responds with 4xx or 6xx on the
UPDATE for media re-negotiation.
Keyed on transfer failure cause.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 126 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSrvccAlertingTransferOk The number of successful SRVCC access

transfers of session in Alerting state.
The counter is incremented when a session
in alerting state has successfully been
transferred (200 OK to SIP INFO received
and PS fallback timer expired without PS
fallback request). Transfer of additional
early sessions due to forking is not counted.
Counter on MTAS node.
MtasSrvccPreAlertingAttempt The number of SRVCC access transfer
attempts of session in pre-Alerting state.
The counter is incremented when an
INVITE due to ATU-STI is received and the
target session is in pre-alerting state.
Counter on MTAS node.
MtasSrvccPreAlertingTransferNOkNet The number of SRVCC access transfers of
session in pre-Alerting state that failed or
cancelled due to network problems.
The counter is incremented after an SRVCC
access transfer of session in pre-Alerting
state has been initiated and the access
transfer is cancelled by MME/SGSN or
failure by UE to transition to CS, or the
target CS access leg is released with
protocol=Q.850 and cause=31, or the
remote side responds with a 5xx on the
UPDATE for media re-negotiation.
Counter on MTAS node.
MtasSrvccPreAlertingTransferNOkUse The number of SRVCC access transfers of
r session in pre-Alerting state that failed or
cancelled due to failure by end-user.
The counter is incremented after an SRVCC
access transfer of session in pre-Alerting
state has been initiated and the access
transfer is cancelled because the target CS
access leg is released with reason other
than protocol=Q.850 and cause=31, or the
remote side responds with 4xx or 6xx on the
UPDATE for media re-negotiation.
Counter on MTAS node.
MtasSrvccPreAlertingTransferOk The number of successful SRVCC access
transfers of session in pre-Alerting state.
The counter is incremented when a session
in pre-alerting state has successfully been
transferred (200 OK to SIP INFO received
and PS fallback timer expired without PS
fallback request). Transfer of additional
early sessions due to forking is not counted.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 127 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSrvccMidcallAttempt The number of SRVCC Mid-call access

transfer attempts.
The counter is incremented when an access
transfer INVITE is received, SCC AS
applies SRVCC Mid-call and transfers a
Held call or an additional call.
Counter on MTAS node.
MtasSrvccMidcallTransferOk The number of successful SRVCC Mid-call
access transfer attempts.
The counter is incremented when an
SRVCC Mid-call transfer has successfully
been completed.
Counter on MTAS node.
MtasSrvccMidcallTransferNOkUser The number of SRVCC Mid-call access
transfers that failed or cancelled due to
failure by end-user.
The counter is incremented after an SRVCC
Mid-call access transfer has been initiated
and the access transfer is cancelled
because the target CS access leg is
released with reason other than
protocol=Q.850 and cause=31, or the
remote side responds with 403,404,484,486
or 600,603 on the UPDATE for media re-
negotiation.
Keyed on transfer failure cause.
Counter on MTAS node.
MtasSrvccMidcallTransferNOkNet The number of SRVCC Mid-call access
transfers that failed or cancelled due to
network problems.
The counter is incremented after an SRVCC
Mid-call transfer has been initiated and the
access transfer is cancelled by MME/SGSN
or failure by UE to transition to CS, or the
target CS access leg is released with
protocol=Q.850 and cause=31, or the
remote side responds with a 4xx,5xx or 6xx
except the error codes that are counted as
user behavior (403,404,484,486 or 600,603)
on the UPDATE for media re-negotiation.
Keyed on transfer failure cause.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25].

6.23 IMS MMTEL AS Customized Alerting Tones Service Accessibility

6.23.1 Definition

IMS MMTEL AS Customized Alerting Tones (CAT) Service Accessibility is

defined as the probability of being able to successfully invoke the Customized
Alerting Tones Service. The formula may be evaluated per CAT server or
summed up for the MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 128 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.23.2 Formula

Equation 143. IMS MMTEL AS Customized Alerting Tones

(CAT) Service Success Ratio

IMSMMTelASCATSuccRatio[%] = 100 *
MtasCatSignalOk
(MtasCatSignalOk + MtasCatSignalNOkE + MtasCatSignalNOkI)

Counter Name Definition

MtasCatSignalOk The number of successful Customized

Alerting Tones sending requests to the
external CAT server. Key is CAT server IP
address or FQDN.
Counter on MTAS node.
MtasCatSignalNOkE The number of Customized Alerting Tones
sending requests that failed due to external
reasons.
The counter is incremented when a non-200
response is received from the CAT-S or the
request time outs. Key is CAT server IP
address or FQDN.
Counter on MTAS node.
MtasCatSignalNOkI The number of Customized Alerting Tones
sending requests that failed due to internal
reasons. Key is CAT server IP address or
FQDN.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.24 IMS MMTEL AS Session Transfer to Own Device Service

Accessibility

6.24.1 Definition

IMS MMTEL AS Session Transfer to Own Device (STOD) Service

Accessibility is defined as the probability of being able to successfully invoke
the Telephony Session Transfer to Own Device Service

6.24.2 Formula

Transfer to Own Device (STOD) Call Push Service

Equation 144. IMS MMTEL AS Session Transfer to Own Device

(STOD) Service Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 129 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASSTODSuccRatio[%] = 100 *
MtasStodOk
MtasStodAttempt

Transfer to Own Device (STOD) Call Pull Service

Equation 145. IMS MMTEL AS Session Transfer to Own Device

(STOD) Call Pull Service Success Ratio

IMSMMTelASSTODCallPullSuccRatio[%] = 100 *
(MtasStodCallPullOk + MtasStodCallPullFailure)
(MtasStodCallPullOk + MtasStodCallPullFailure +
MtasStodCallPullNOkE + MtasStodCallPullNOkI)

Note: MtasStodCallPullFailure is considered as successful case from MTAS

and network perspective, since Call pull policies or unfulfilled preconditions
are MTAS expected behavior.

Counter Name Definition

MtasStodOk The total number of successful STOD

invocations.
Counter on MTAS node.
MtasStodAttempt The total number of STOD invocations.
Counter on MTAS node.
MtasStodCallPullOk The number of successful Call Pull
attempts.
The counter is incremented by 1 when the
Call Pull invocation is successful.
Counter on MTAS node.
MtasStodCallPullFailure The number of unsuccessful Call Pull
attempts due to Call pull policies or
unfulfilled preconditions.
The counter is incremented by 1 when the
invocation of Call Pull failed due to enabled
Call pull policies or due to service
preconditions check.
Counter on MTAS node.
MtasStodCallPullNOkE The number of unsuccessful Call Pull
attempts due to system external errors.
The counter is incremented by 1 when the
invocation of the Call Pull failed due to an
error in the interworking node.
Counter on MTAS node.
MtasStodCallPullNOkI The number of unsuccessful Call Pull
attempts due to system internal errors.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 130 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.25 IMS MMTEL AS Parlay-X Service Accessibility

6.25.1 Definition

IMS MMTEL AS Parlay-X Service Accessibility is defined as the probability of

being able to successfully invoke the Parlay-X Service. The Parlay-X Service
is viewed from the MTAS side when defining incoming and outgoing. The
formulas may be expressed per Parlay-X server or summed up for all Parlay-
X servers. The Parlay-X server key is IP address or FQDN.

6.25.2 Formula

Equation 146. IMS MMTEL AS Incoming Parlay-X Request

Success Ratio

IMSMMTelASInPxSuccRatio[%] = 100 *
(MtasPxReceivedRequests − MtasPxRejectedRequests)
MtasPxReceivedRequests

Equation 147. IMS MMTEL AS Outgoing Parlay-X Request

Success Ratio

IMSMMTelASOutPxSuccRatio[%] = 100 *
(MtasPxSentRequests − MtasPxReceivedErrorResponses)
MtasPxSentRequests

Counter Name Definition

MtasPxReceivedRequests The counter is incremented when receiving

a Parlay X Request in MTAS. Key is Parlay-
X server.
Counter on MTAS node.
MtasPxRejectedRequests The counter is incremented when rejecting
a received Parlay X Request in MTAS. Key
is Parlay-X server.
Counter on MTAS node.
MtasPxSentRequests The number of times Parlay X requests are
sent to the Parlay X application. Key is
Parlay-X server.
Counter on MTAS node.
MtasPxReceivedErrorResponses The number of times Parlay X requests are
rejected with an error response by the
Parlay X application. Key is Parlay-X server.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 131 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.26 IMS MMTEL AS Polling of Calling Name Information Accessibility

6.26.1 Definition

IMS MMTEL AS Polling of Calling Name Information Accessibility is defined

as the probability of being able to successfully retrieve calling name
information from a Calling Name Server. This function supports the Calling
Name Identification Presentation (CNIP) Service.

6.26.2 Formula

Equation 148. IMS MMTEL AS Polling of Calling Name

Information Success Ratio

IMSMMTelASPollingCNameSuccRatio[%] = 100 *
MtasSipCnamePollOk
(MtasSipCnamePollOk + MtasSipCnamePollNOk)

Counter Name Definition

MtasSipCnamePollOk The accumulated number of successful

interrogations of Calling Name Server
(CNS) for calling name information.
This counter is incremented by 1 in MTAS
when a NOTIFY (Event:calling-name)
message is received from the Calling Name
Server (CNS), in response to a
SUBSCRIBE (Event:calling-name) sent by
the MTAS.
Counter on MTAS node.
MtasSipCnamePollNOk The accumulated number of failed
interrogations of Calling Name Server
(CNS) for calling name information.
The counter is incremented by 1 in MTAS
when a SUBSCRIBE (Event:calling-name)
message sent by this MTAS towards a
Calling Name Server (CNS) does not
receive a valid NOTIFY (Event:calling-
name) response. The counter is
incremented when: * MTAS received an
error message in response to SUBSCRIBE
(Event:calling-name) request. * MTAS has
timed out waiting for the NOTIFY
(Event:calling-name) against the
corresponding SUBSCRIBE (Event:calling-
name) request. * MTAS received a
malformed NOTIFY (Event:calling-name)
against the corresponding SUBSCRIBE
(Event:calling-name) request.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 132 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.27 IMS MMTEL AS Call Return (CR) Service Accessibility

6.27.1 Definition

IMS MMTEL AS Session Call Return (CR) Service Accessibility is defined as

the probability of being able to successfully invoke the Call Return Service

6.27.2 Formula

Equation 149. IMS MMTEL AS Call Return Service Success

Ratio

IMSMMTelASCRSuccRatio[%] = 100 *
MtasCrInvAnnOk
(MtasCrInvAnnOk + MtasCrInvNOkE + MtasCrInvNOkI)

Equation 150. IMS MMTEL AS Call Return Erasure Procedure

Success Ratio

IMSMMTelASCRSuccRatio[%] = 100 *
MtasCrInvEraOk
(MtasCrInvEraOk + MtasCrInvEraNOkE + MtasCrInvEraNOkI)
Counter Name Definition

MtasCrInvAnnOk This counter is the accumulated number of

successful Call Return (CR) with
announcement attempts.
Counter on MTAS node.
MtasCrInvNOkE This counter is the accumulated number of
unsuccessful Call Return (CR) with no
announcement attempts (due to node
external error).
Incremented by 1 when when an INVITE
request is NOT sent by MTAS due to a
node external error after the caller has
invoked the CR service.
Counter on MTAS node.
MtasCrInvNOkI This counter is the accumulated number of
unsuccessful Call Return (CR) with no
announcement attempts (due to node
internal error).
Incremented by 1 when when an INVITE
request is NOT sent by MTAS due to a
node internal error after the caller has
invoked the CR service.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 133 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasCrInvEraOk This counter is the accumulated number of

successful Call Return (CR) Erasure
Procedure. Incremented by 1 when MTAS
CR Erasure Procedure is invoked and last
call is deleted successfully.
Counter on MTAS node.
MtasCrInvEraNOkE This counter is the accumulated number of
failed attempts for Call Return (CR) Erasure
Procedure for external reasons.
Incremented by 1 when MTAS CR Erasure
Procedure is invoked and last call record
deletion failed for external reasons (e.g
missing CR Subscription / CR license is
missing / No saved Last call).
Counter on MTAS node.
MtasCrInvEraNOkI This counter is the accumulated number of
failed attempts for Call Return (CR) Erasure
Procedure for internal reasons. Incremented
by 1 when MTAS CR Erasure Procedure is
invoked and last call record deletion failed
for internal reasons (e.g DBN transaction
failed).
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.28 IMS MMTEL AS Generic Supplementary Service Code Invocation

Service Accessibility
6.28.1 Definition

IMS MMTEL AS Generic Supplementary Service Code (SSC) Invocation

Service Accessibility is defined as the probability of being able to successfully
invoke the Generic Supplementary Service Code Invocation Service

6.28.2 Formula

Equation 151. IMS MMTEL AS Generic Supplementary Service

Code Invocation Service Success Ratio

IMSMMTelASGenSSCInvSuccRatio[%] = 100 *
MtasGenSscInvOk
(MtasGenSscInvOk + MtasGenSscInvNOkE + MtasGenSscInvNOkI)

Counter Name Definition

MtasGenSscInvOk The number of successful invocations

for Generic SSC service.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 134 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasGenSscInvNOkE The number of invocations failed for

Generic SSC service due to error in
interworking node.
Counter on MTAS node.
MtasGenSscInvNOkI The number of invocations failed for
Generic SSC service due to internal
MTAS fault .
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.29 IMS MMTEL AS Operator Controlled Transfer (OCT) Service

Accessibility

6.29.1 Definition

IMS MMTEL AS Operator Controlled Transfer (OCT) Service Accessibility is

defined as the probability of being able to successfully answer the Operator
Controlled Transfer Service.

6.29.2 Formula

Equation 152. IMS MMTEL AS Operator Controlled Transfer

Service Answered Ratio

IMSMMTelASOTCAnsweredRatio[%] = 100 *
MtasOctTransferorAnswered(key : phone no)
MtasOctTransferAttempt(key : phone no)

Counter Name Definition

MtasOctTransferAttempt This counter is the accumulated number of

call attempt to the target of Operator
Controlled Transfer (OCT). The counter is
keyed on the phone number to the Operator
Transferor.
Incremented by 1 when when an INVITE
request is sent by MTAS to the target of
Operator Controlled Transfer (OCT).
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 135 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasOctTransferorAnswered This counter is the accumulated number of

call established to the Operator Transferor.
The counter is keyed on the phone number
to the Operator Transferor.
Incremented by 1 when operator transferor
have answered the call, 200 OK receive by
the Operator Controlled Transfer (OCT)
service.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.30 IMS MMTEL AS MtasPriorityCall Accessibility

6.30.1 Definition

IMS MMTEL AS MtasPriorityCall Accessibility is defined as the probability of

being able to successfully establish new communication sessions with
resource priority setting.

6.30.2 Formula

Equation 153. IMS MMTel AS Priority Call Successfully

Established Ratio

IMSMMTelAS Pr ioCallSuccEstRatio[%] = 100 *

MtasPriorityCallWpsEstablished( key : wps)
MtasPriorityCallWpsRequested( key : wps)

Equation 154. IMS MMTel AS GETS Priority Service

Successfully Setup Ratio

IMSMMTelASGETSSuccSetupRatio[%] = 100 *
NWTypen
MtasPriorityCallGetsServiceOk(
∑NumberType1 ( ∑
NumberTypen

NWType1 key : GetsNumberType, GetsCallTermNwType ))

MtasPriorityCallGetsServiceAttempt
 Ericsson Internal
OPERAT. GUIDELINES 136 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasPriorityCallWpsEstablished The counter accumulates number of new

communication sessions with resource
priority setting determined by SIP Resource-
priority header 'wps' namespace (RFC
4412). The counter is keyed on wps
resource value.
The counter is incremented by 1 when a
new session with wps resource-priority
setting enters 'established' state.
Counter on MTAS node.
MtasPriorityCallWpsRequested The counter accumulates number of load
regulation requests at dialog setup, using
parameter mapped from SIP Resource-
priority header 'wps' namespace (RFC
4412). The counter is keyed on wps
resource value.
The counter is incremented by 1 when an
execute permission is requested from TSP
load regulation, for processing an incoming
INVITE, which has a valid SIP Resource-
priority header with wps namespace, and is
handled by MTAS Resource Priority
Handling function.
Counter on MTAS node.
MtasPriorityCallGetsServiceAttempt The number of times GETS(Government
Emergency Telecommunication
Service)Priority service call received in
Originating MMTel AS. The counter is
incremented unconditionally on INVITE
reception with GETS number in Request
URI and with valid Resource-Priority
Header.
Counter on MTAS node.
MtasPriorityCallGetsServiceOk The number of times GETS(Government
Emergency Telecommunication Service)
Priority service call response matched from
set of configured successful response
values in Originating MMTel AS.The counter
is incremented conditionally.
This counter is keyed on GetsNumberType
and GetsCallTermNwType.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].
 Ericsson Internal
OPERAT. GUIDELINES 137 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

6.31 IMS MMTel AS Ring Back Tone Accessibility

6.31.1 Definition

IMS MMTel AS Ring Back Tone (RBT) Accessibility is defined as the

probability of being able to successfully send Ring Back Tone requests to the
MRFP.

6.31.2 Formula

Equation 155. IMS MMTel AS Ring Back Tone Request Success

Ratio

IMSMMTelASRBT Re qRatio[%] = 100 *

MtasRbtOk
(MtasRbtOk + MtasRbtNOkE + MtasRbtNOkI)

Counter Name Definition

MtasRbtOk The number of successful Ring Back Tones

sending requests to the MRFP.
Counter on MTAS node.
MtasRbtNOkE The number of Ring Back Tones sending
requests that failed due to external reasons.
Counter on MTAS node.
MtasRbtNOkI The number of Ring Back Tones sending
requests that failed due to internal reasons.
The counter is incremented when an initial
request to the eMRFP is failed due to MTAS
internal failure.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.32 IMS SCC AS CAMEL Application Part (CAP) Accessibility

6.32.1 Definition

IMS SCC AS CAMEL Application Part (CAP) Accessibility is defined as the

probability of being able to successfully process a InitialDP CAP request.

6.32.2 Formula

Equation 156. IMS SCC AS CAP Request Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 138 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASCAP Re qRatio[%] = 100 *

MtasSdsCapInitDPOk
(MtasSdsCapInitDPOk + MtasSdsCapInitDPNOkE +
MtasSdsCapInitDPNOkI)

Note: The formula covers originating and terminating CAP requests.

Counter Name Definition

MtasSdsCapInitDPOk This counter is the accumulated number of

CAMEL Application Part (CAP) InitialDP
requests processed successfully.
Counter on MTAS node.
MtasSdsCapInitDPNOkE This counter is the accumulated number of
CAMEL Application Part (CAP) InitialDP
requests that failed because the request
message was faulty, for example missing
mandatory parameter or parameter having
unknown value.
Counter on MTAS node.
MtasSdsCapInitDPNOkI This counter is the accumulated number of
CAMEL Application Part (CAP) InitialDP
requests that failed because of problems
internal to the SCC AS, an IMRN could not
be allocated, for example because of no
free IMRN.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.33 IMS MMTel AS Closed User Group (CUG) Accessibility

6.33.1 Definition

IMS MMTel AS Closed User Group Accessibility is defined as the probability

of being able to successfully invoke the CUG service.

6.33.2 Formula

Equation 157. IMS MMTel AS Closed User Group Request

Success Ratio

IMSMMTelASCug Re qRatio[%] = 100 *

MtasCugOk
(MtasCugOk + MtasCugRejected)
 Ericsson Internal
OPERAT. GUIDELINES 139 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasCugOk The number of successful calls in a Closed

User Group.
The counter is incremented when an initial
INVITE towards a Closed User Group
member is allowed by the Closed User
Group service.
Counter on MTAS node.
MtasCugRejected The number of INVITEs rejected by the
Closed User Group (CUG) service.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.34 IMS ST AS Session Setup Accessibility

6.34.1 Definition

IMS ST AS Session Setup Accessibility is defined as the probability of being

able to successfully initiate a session into the SIP Trunking AS node .

6.34.2 Formula

Equation 158. IMS ST AS Originating Session Setup Success

Ratio per PBX

IMSSTASOrgSessSetupSuccRatioPerPbx[%] = 100 *
MtasStOrigNetworkSuccessSessionEstablish.pbxId
(MtasStOrigNetworkSuccessSessionEstablish.pbxId +
MtasStOrigFailedAttempt.pbxId)

IMS ST AS Originating Session Setup Accessibility per PBX identity.

Equation 159. IMS ST AS Terminating Session Setup Success

Ratio per PBX

IMSSTASTermSessSetupSuccRatioPerPbx[%] = 100 *
MtasStTermNetworkSuccessSessionEstablish.pbxId
(MtasStTermNetworkSuccessSessionEstablish.pbxId +
MtasStTermFailedAttempt.pbxId)

IMS ST AS Terminating Session Setup Accessibility per PBX identity.

Equation 160. IMS ST AS Originating Session Setup Success

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 140 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSTASOrigSessSetupSuccRatio[%] = 100 *
pbxId = n
( ∑ MtasStOrigNetworkSuccessSessionEstablish.pbxId +
pbxId =1

MtasStOrigFailedAttemptCause.403 +
MtasStOrigFailedAttemptCause.404 +
MtasStOrigFailedAttemptCause.407 +
MtasStOrigFailedAttemptCause.484)
(MtasStOrigNetworkSuccessSessionEstablish.pbxId +
pbxId = n

∑
pbxId =1 MtasStOrigFailedAttempt.pbxId)

IMS ST AS Originating Session Setup Accessibility for the ST AS function.

Equation 161. IMS ST AS Terminating Session Setup Success

Ratio

IMSSTASTermSessSetupSuccRatio[%] = 100 *
pbxId = n
( ∑ MtasStTermNetworkSuccessSessionEstablish.pbxId +
pbxId =1

MtasStTermFailedAttemptCause.403 +
MtasStTermFailedAttemptCause.404 +
MtasStTermFailedAttemptCause.407 +
MtasStOrigFailedAttemptCause.484)
pbxId = n
(MtasStTermNetworkSuccessSessionEstablish.pbxId +
∑
pbxId =1 MtasStTermFailedAttempt.pbxId)

IMS ST AS Terminating Session Setup Accessibility for the ST AS function.

Error indicators for failed attempts per cause, that is, SIP response code

Equation 162. IMS ST AS Failed Originating Sessions, per

cause code

IMSSTASFailedOrgSessions = MtasStOrigFailedAttemptCause.cause

Equation 163. IMS ST AS Failed Terminating Sessions, per

cause code

IMSSTASFailedTermSessions = MtasStTermFailedAttemptCause.cause

Error indicators for failed attempts per PBX Identity

Equation 164. IMS ST AS Failed Originating Sessions, per PBX

IMSSTASFailedOrgSessionsPerPbx = MtasStOrigFailedAttempt.pbxId
 Ericsson Internal
OPERAT. GUIDELINES 141 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 165. IMS ST AS Failed Terminating Sessions, per PBX

IMSSTASFailedTermSessionsPerPbx = MtasStTermFailedAttempt.pbxId

Counter Name Definition

MtasStOrigNetworkSuccessSessionE The counter is incremented when sending

stablish 18x message or when sending 2xx (INVITE)
if no 18x message has been sent, related to
an initial INVITE, received by an originating
ST AS.
The counter is incremented when sending
18x message or when sending 2xx (INVITE)
if no 18x message has been sent.
This counter is keyed on Pbx Identity.
Counter on MTAS node.
MtasStOrigFailedAttempt Counters for counting the total number of
received 3xx/4xx/5xx/6xx messages in
originating ST AS.
This counter is keyed on Pbx Identity.
Counter on MTAS node.
MtasStTermNetworkSuccessSessionE The counter is incremented when sending
stablish 18x message or when sending 2xx (INVITE)
if no 18x message has been sent, related to
an initial INVITE, received by a terminating
ST AS.
The counter is incremented when sending
18x message or when sending 2xx (INVITE)
if no 18x message has been sent.
This counter is keyed on Pbx Identity.
Counter on MTAS node.
MtasStTermFailedAttempt Counters for counting the total number of
received 3xx/4xx/5xx/6xx messages in
terminating ST AS.
This counter is keyed on Pbx Identity.
Counter on MTAS node.
MtasStCurrentSessions Gauge for current number of sessions in ST
AS. Both initiated and established sessions
are included. The counter reflects the
measure controlled by the ST AS session
capacity license.
Counter on MTAS node.
MtasStCurrentOrigSessions Gauge for current number of originating
sessions in ST AS. Both initiated and
established sessions are included.
The Gauge is incremented by 1 when a
PBX originating call session is initiated and
decremented by 1 when the call session is
terminated.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 142 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasStCurrentTermSessions Gauge for current number of terminating

sessions in ST AS. Both initiated and
established sessions are included.
The Gauge is incremented by 1 when a
PBX terminating call session is initiated and
decremented by 1 when the call session is
terminated.
Counter on MTAS node.
MtasStOrigFailedAttemptCause Total number of received 3xx/4xx/5xx/6 xx
messages for PBX originating calls. The
cause code and reason is used as key.
This counter is keyed on SIP Reason code.
Counter on MTAS node.
MtasStTermFailedAttemptCause Total number of received 3xx/4xx/5xx/6 xx
messages for PBX terminating calls. The
cause code and reason is used as key.
This counter is keyed on SIP Reason code.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.35 IMS MMTel AS H.248 MRFP Request Accessibility

6.35.1 Definition

IMS MMTel AS H.248 MRFP Request Accessibility is defined as the

probability of being able to successfully issue a H.248 request to an MRFP.

6.35.2 Formula

Equation 166. IMS MMTel AS H.248 Request Success Ratio

IMSMMTelASH 248 Re qSuccRatio[%] = 100 *

MtasMrfpResponse(key : rspCode = 0000)
rspCoden
( ∑ MtasMrfpResponse(key : rspCode) +
rspCode1

MtasMrfpResponse(key : rspCode = 0000))

Note that all requests for all MRFPs needs to be added. Response code 0000
is considered as success case.

Equation 167. IMS MMTel AS H.248 Request Replay Success

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 143 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASH 248 Re q Re playSuccRatio[%] = 100 *

MrfpIdn
(MtasMrfpOkAddReplay + MtasMrfpOkModifyReplay +
∑
MrfpId1 MtasMrfpOkSubtractReplay + MtasMrfpOkAuditReplay)
MrfpIdn
(MtasMrfpOkAddReq + MtasMrfpOkModifyReq +
∑
MrfpId1 MtasMrfpOkSubtractReq + MtasMrfpOkAuditReq)

Counter Name Definition

H.248 Commands to and Replies

from MRFP
MtasMrfpOkAddReq Successfully sent AddRequest
commands to an external MRFP peer.
The counter is keyed on the MRFP peer
Id.
Counter on MTAS node.
MtasMrfpOkModifyReq The number of successfully sent
ModifyRequest commands to
an MRFP peer.
The counter is keyed on the MRFP peer
Id.
Counter on MTAS node.
MtasMrfpOkSubtractReq The number of successfully sent
SubstractRequest commands to
an MRFP peer.
The counter is keyed on the MRFP peer
Id.
Counter on MTAS node.
MtasMrfpOkAuditReq The number of successfully sent
AuditRequest commands to
an MRFP peer.
The counter is keyed on the MRFP peer
Id.
Counter on MTAS node.
MtasMrfpResponse The number of MRFP response
messages received. The counter is
keyed on the received result code,
reason phrase.
MtasMrfpOkAddReply The number of correct AddReply
commands received from an
external MRFP peer.
Counter on MTAS node.
MtasMrfpOkModifyReply Counters for successful received
ModifyReply commands from
an MRFP peer. Counter on MTAS node.
MtasMrfpOkSubtractReply The number of successfully received
SubstractReply commands from
an MRFP peer. Counter on MTAS node.
MtasMrfpOkAuditReply The number of successfully received
AuditReply commands from
an MRFP peer. Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 144 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasMrfpProtocolErrorFromPeer The number of commands sent by the

MTAS containing a protocol error.
Counter on MTAS node.
MtasMrfpResourceUnavailFromPeer The number of “resource” errors that the
peer MRFP has encountered to perform
a request. Counter on MTAS node.
MtasMrfpRetransmission The number of retransmissions
performed by the MTAS to an MRFP.
Counter on MTAS node.
H.248 Commands from and Replies
to MRFP
MtasMrfpOkNotifyReq The number of correct NotifyRequest
commands received from an
external MRFP peer. Counter on MTAS
node.
MtasMrfpOkNotifyReply The number of successfully sent
NotifyReply commands to
an MRFP peer. Counter on MTAS node.
MtasMrfpOkServiceChangeReq The number of successfully received
ServiceChange commands to
an MRFP peer. Counter on MTAS node.
MtasMrfpOkServiceChangeReply The number of successfully sent
ServiceChangeReply commands sent to
an MRFP peer. Counter on MTAS node.
MtasMrfpProtocolErrorToPeer The number of commands received by
the MTAS containing a protocol error.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.36 IMS MMTel AS Charging Request Accessibility

6.36.1 Definition

IMS MMTel AS Charging Request Accessibility is defined as the probability of

being able to successfully issue a charging requests to a charging server.

6.36.2 Formula

Equation 168. IMS MMTel AS Charging Request Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 145 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASCh arg ing Re qSuccRatio[%] = 100 *

MtasChargingAcrStartOk +
MtasChargingBackupStart − MtasChargingBackupStartFail +
MtasChargingAcrEventOk + MtasChargingCcrInitOk
MtasChargingRttiOk)
(MtasChargingAcrStartOk + MtasChargingAcrStartNOkI +
MtasChargingAcrStartNOkE + MtasChargingBackupStart +
MtasChargingAcrEventOk + MtasChargingAcrEventNOkI +
MtasChargingAcrEventNOkE +
MtasChargingCcrInitOk + MtasChargingCcrInitNOkI +
MtasChargingCcrInitNOkE +
MtasChargingRttiOk + MtasChargingRttiNOkI +
MtasChargingRttiNOkE)

Counter Name Definition

MtasChargingAcrStartOk The number of successfully initiated

accounting sessions.
Counter on MTAS node.
MtasChargingAcrStartNOkI The number of failed initiations of
charging sessions due to internal errors.
Counter on MTAS node.
Counter on MTAS node.
MtasChargingAcrStartNOkE The number of failed initiations of
charging sessions due to external
errors.
Counter on MTAS node.
MtasChargingBackupStart The number of charging start requests
sent to backup. Counter on MTAS node.
MtasChargingBackupStartFail The number of charging start requests
sent to backup that failed. Counter on
MTAS node.
Counter on MTAS node.
MtasChargingAcrEventOk The number of successfully handled
ACR (Event Record) messages.
MtasChargingAcrEventNOkI The number of failures due to internal
errors that occurred when sending ACR
(Event Record) messages.
Counter on MTAS node.
MtasChargingAcrEventNOkE The number of failures due to external
errors that occurred when sending ACR
(Event Record) messages.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 146 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasChargingCcrInitOk The number of successfully initiated

online charging sessions. The counter is
keyed on the charging destination
(destination realm or destination host).
Counter on MTAS node.
MtasChargingCcrInitNOkE The number of failed initiations of online
charging sessions due to external
errors. The counter is keyed on the
charging destination (destination realm
or destination host).
Counter on MTAS node.
MtasChargingCcrInitNOkI The number of failed initiations of online
charging sessions due to internal errors.
The counter is keyed on the charging
destination (destination realm or
destination host).
Counter on MTAS node.
MtasChargingRttiOk Real-Time Transfer of Tariff Information
(RTTI) has been signaled backward to
MTAS and successfully provided into
the Online Charging System (OCS). The
counter uses DEFAULT as key
Counter on MTAS node.
MtasChargingRttiNOkI Real-Time Transfer of Tariff Information
(RTTI) has been signaled backward to
MTAS which was unable to provide this
data into the Online Charging System
(OCS) due to an internal error. The
counter uses DEFAULT as key.
Counter on MTAS node.
MtasChargingRttiNOkE Real-Time Transfer of Tariff Information
(RTTI) has been signaled backward to
MTAS which was unable to provide this
data into the Online Charging System
(OCS) due to an external error. The
counter uses DEFAULT as key.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.37 IMS MMTel AS Sh Request Accessibility

6.37.1 Definition

IMS MMTel AS Sh Request Accessibility is defined as the probability of being

able to successfully issue a Sh request to HSS.

6.37.2 Formula

Equation 169. IMS MMTel AS Sh Pull Request Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 147 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASShPullSuccessRatio[%] = 100 *
MtasShPullOk(key : Stack, Host)
(MtasShPullOk(key : Stack, Host) + MtasShPullNOkE(key : Stack, Host) +
MtasShPullNOkI(key : Stack, Host))
This R-KPI is calculated per Diameter Stack Id and Host. The R-KPI may also
be calculated for the node by adding values for all Stack Ids and Hosts

Equation 170. IMS MMTel AS Sh Redirect Request Success

Ratio

IMSMMTelASShRedirectSuccessRatio[%] = 100 *
MtasShRedirect(key : Stack, Host)
(MtasShRedirect(key : Stack, Host) + MtasShRedirectFailed(key : Stack, Host))

This R-KPI is calculated per Diameter Stack Id and Host. The R-KPI may also
be calculated for the node by adding values for all Stack Ids and Hosts.

Equation 171. IMS MMTel AS Sh Notification Request Success

Ratio

IMSMMTelASShRedirectSuccessRatio[%] = 100 *
MtasShNotifOk(key : Stack, Host)
(MtasShNotifOk(key : Stack, Host) +
MtasShNotifNOkE(key : Stack, Host) + MtasShNotifNOkI)

This R-KPI is calculated per Diameter Stack Id and Host. The R-KPI may also
be calculated for the node by adding values for all Stack Ids and Hosts.

Counter Name Definition

MtasShPullOk The number of Sh-Pull operations that

were completed successfully. The
counter is keyed on the Stack instance
and either HSS destination host name
(taken from the Request message) or
HSS origin host name (taken from the
Answer message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 148 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasShPullNOkE The number of Sh-Pull operations that

could not be completed successfully
because of an external cause. The
counter is keyed on the Stack instance
and either HSS destination host name
(taken from the Request message) or
HSS origin host name (taken from the
Answer message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
MtasShPullNOkI The number of Sh-Pull operations that
could not be completed successfully
because of internal reasons. The
counter is keyed on the Stack instance
and either HSS destination host name
(taken from the Request message) or
HSS origin host name (taken from the
Answer message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
MtasShRedirect The number of Sh-Redirect (Dh)
operations that were completed
successfully. The counter is keyed on
the Stack instance and either HSS
destination host name (taken from the
Request message) or HSS origin host
name (taken from the Answer
message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
MtasShRedirectFailed The number of failed Sh-Redirect (Dh)
operations. The counter is keyed on the
Stack instance and either HSS
destination host name (taken from the
Request message) or HSS origin host
name (taken from the Answer
message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
MtasShNotifOk The number of Sh-Notif requests that
were processed successfully. The
counter is keyed on the Stack instance
and either HSS destination host name
(taken from the Request message) or
HSS origin host name (taken from the
Answer message). The format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 149 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasShNotifNOkE The number of Sh-Notif operations that

could not be completed successfully
because of external reasons. The
counter is keyed on the Stack instance
and either HSS destination host name
(taken from the Request message) or
HSS origin host name (taken from the
Answer message). The format
<Stack_instance>;<Destination_Host>;<
ResultCode> or
<Stack_instance>;<Origin-
Host>;<ResultCode>.
Counter on MTAS node.
MtasShNotifNOkI The number of Sh-Notif operations that
could not be completed successfully
because of internal reasons. The
counter is keyed on the Stack instance
and and either HSS destination host
name (taken from the Request
message) or HSS origin host name
(taken from the Answer message). The
format
<Stack_instance>;<Destination_Host>
or <Stack_instance>;<Origin-Host>.
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.38 IMS MMTel AS Subscribe Session Accessibility

6.38.1 Definition

IMS MMTel AS Subscribe Session Accessibility is defined as the probability of

being able to successfully setup (create) an out-of-dialog subscription
session.

6.38.2 Formula

Equation 172. IMS MMTel AS Subscribe Setup Success Ratio

IMSMMTelASSubscribeSetupRatio[%] = 100 *
MtasMmtSubsSessOk
MtasMmtSubsSessAttempt

Equation 173. IMS MMTel AS Dialog Event Notifier Subscribe

Setup Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 150 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMMTelASDENSubscribeSetupRatio[%] = 100 *
MtasDenSubsSessOk
(MtasDenSubsSessOk + MtasDenSubsSessNOkE
MtasDenSubsSessNOkI)

Note: DEN = Dialog Event Notifier service.

Counter Name Definition

MtasMmtSubsSessAttempt The accumulated number of out-of-dialog

subscription session creation attempts
within the MMTel AS.
The counter is incremented by 1 in the
originating MMTel AS when receiving an
initial out-of-dialog SUBSCRIBE.
Counter on MTAS node.
MtasMmtSubsSessOk The accumulated number of successfully
created out-of-dialog subscription sessions
within the MMTel AS.
The counter is incremented by 1 in the
originating MMTel AS when responding with
200 OK to a received initial out-of-dialog
SUBSCRIBE.
Counter on MTAS node.
MtasDenSubsSessOk The accumlated number of successfully
created 'dialog' event package subscription
sessions.
The counter is incremented by 1 by the
Dialog Event Notifier service when 200 OK
is sent to the SUBSCRIBE request of a
'dialog' event package subscription.
Counter on MTAS node.
MtasDenSubsSessNOkE The accumlated number of unsuccessfully
created 'dialog' event package subscription
sessions due to node external reasons.
The counter is incremented by 1 by the
Dialog Event Notifier service when
responding to the SUBSCRIBE request of a
'dialog' event package subscription failed
due to node external reasons.
Counter on MTAS node.
MtasDenSubsSessNOkI The accumlated number of unsuccessfully
created 'dialog' event package subscription
sessions due to node internal reasons.
The counter is incremented by 1 by the
Dialog Event Notifier service when
responding to the SUBSCRIBE request of a
'dialog' event package subscription failed
due to node internal reasons.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 151 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.39 IMS Network AS Precondition IWF Service Accessibility

6.39.1 Definition

IMS Network Application Server (NW AS) Precondition Interworking Function

(IWF) Accessibility is defined as the probability of being able to successfully
perform precondition signaling for terminating UEs.

Precondition Interworking Service supports QoS Precondition negotiation for

basic call when remote party does not support Precondition Signalling

6.39.2 Formula

Equation 174. IMS NW AS Precondition IW Setup Success Ratio

IMSNWAS Pr econdIWSetupRatio[%] = 100 *

MtasPrIwOrigSuccess
(MtasPrIwOrigAttempt + MtasPrIwOrigEarlyAttempt)

IMSNWASPrecondIWSetupRatio is the probability of being able to

successfully perform precondition signaling for terminating UEs. The formula
is network oriented in the sense that failing to reserve MRF resources or
license is not included in the formula.

Equation 175. IMS NW AS Precondition External Failure Ratio

IMSNWAS Pr econdExtFailRatio[%] = 100 *

MtasPrIwOrigNOkE
(MtasPrIwOrigAttempt + MtasPrIwOrigEarlyAttempt +
MtasPrIwOrigRenegotiationAttempt)

IMSNWASPrecondExtFailRatio is the external failure ratio for factors outside

NW AS Precondition IWF like failing to reserve MRF resources or license.

Equation 176. IMS NW AS Precondition IW to Session Setup

Ratio

IMSNWAS Pr econdIWToSessionSetupRatio[%] = 100 *

(MtasPrIwOrigAttempt + MtasPrIwOrigEarlyAttempt)
Cscf = n

∑ (MtasMmtOrigSuccAttempt + MtasMmtOrigUnregSuccAttempt)
Cscf =1

IMSNWASPrecondIWToSessionSetupRatio is the ratio of precondition

signaling to session setup in percentage.
 Ericsson Internal
OPERAT. GUIDELINES 152 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasPrIwOrigAttempt The number of successful Precondition

session attempts requests from the User.
The counter is incremented when on
receiving 18x or 200 OK for INVITE without
precondtion support or Number recived in
R-URI is configured in
MtasPrIwBnumRangeWithoutPrecond.
Counter on MTAS node.
MtasPrIwOrigEarlyAttempt The number of successful Precondition
session attempts requests from the User
configured in the
MtasPrIwBnumRangeWithoutPrecond.
The counter is incremented when receiving
INVITE from Number configured in
MtasPrIwBnumRangeWithoutPrecond.
Counter on MTAS node.
MtasPrIwOrigNOkE The count of Precondition IWF sessions are
failed due to external reasons.
The counter is incremented when failed to
reserve MRF resources or License is
absent.
Counter on MTAS node.
MtasPrIwOrigRenegotiationAttempt The number attempts to change the media
point using UPDATE from calling user while
Precondition IWF is in session.
The counter is incremented when receiving
UPDATE for media end point changes from
calling party.
Counter on MTAS node.
MtasPrIwOrigSuccess The count of Precondition IWF sessions
which are replied with 200 Ok of INVITE to
calling Party.
The counter is incremented when sending
200 OK for initial to calling party.
Counter on MTAS node.
MtasMmtOrigSuccAttempt The accumulated number of MMTel
INVITEs successfully sent, counted by the
originating MTAS. The CSCF IP address is
used as key.
The counter is incremented when receiving
the 180 Ringing message or when receiving
the 200 OK message if no 180 Ringing
message has been received.
Counter on MTAS node.
MtasMmtOrigUnregSuccAttempt The accumulated number of early cancelled
MMTel INVITEs, counted by the originating
unregistered MTAS. The counter is keyed
on the CSCF IP address and the session
cancel reason.
The counter is incremented when receiving
the CANCEL message after a 180 Ringing
received.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 153 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

6.40 Traffic Indicators

Equation 177. IMS MTAS Number of Registered IMS Users

IMSMTASRegisteredUsers = MtasSubsDataRegisteredUsers

IMSMTASRegisteredUsers is the number of registered IMS users served by

MTAS.. It is incremented when an initial REGISTER request is received and
also incremented if an initial INVITE or SUBSCRIBE to DEN service is
received. Decremented when the de-registration of the subscriber is finished.
Contains implicitly and explitly registered users. this This performance
indicator will contain implicitly and explitly registered users where
deregistration is not explicitly issued (by the user or by the network) towards
MTAS, whose registration state is cached in MTAS for some time. .

Equation 178. IMS MMTel AS Number of Active Users

IMSMMTelASActiveUsers = MtasFuncOngoingSess

IMSMMTelASActiveUsers is the current number of active users on node level.

Equation 179. IMS MMTel AS Number of Simultaneous

Sessions

IMSMMTelASSimulSess = MtasFuncOngoingMmtSessAvg

IMSMMTelASSimulSess is the average number of simultaneous MMTel AS

sessions (half calls) on node level in measurement period.

Equation 180. IMS MMTel AS Number of Mobile Service

Simultaneous Sessions

IMSMMTelASSimulMobileSess = MtasFuncOngoingMobileSessAvg

IMSMMTelASSimulMobileSess is the average number of simultaneous

mobile service sessions (half calls) on node level in measurement period.

Simultaneous Service Centralization and Continuity Sessions for Originating

and Terminating, CS and PS domains

Equation 181. IMS SCC AS Number of Originating SCC from CS

Simultaneous Sessions

IMSSCCASSimulOrgSCCCSSess = MtasSccCurrentOrigSessionCs

Equation 182. IMS SCC AS Number of Originating SCC from PS

Simultaneous Sessions
 Ericsson Internal
OPERAT. GUIDELINES 154 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSCCASSimulOrgSCCPSSess = MtasSccCurrentOrigSessionPs

Equation 183. IMS SCC AS Number of Terminating SCC from

CS Simultaneous Sessions

IMSSCCASSimultermSCCCSSess = MtasSccCurrentTermSessionCs
Equation 184. IMS SCC AS Number of Terminating SCC from
PS Simultaneous Sessions

IMSSCCASSimulTermSCCPSSess = MtasSccCurrentTermSessionPs
Equation 185. IMS SCC AS Number of Simultaneous Sessions

IMSSCCASSimulSess =
(MtasSccCurrentOrigSessionCs + MtasSccCurrentOrigSessionPs +
MtasSccCurrentTermSessionCs + MtasSccCurrentTermSessionPs)

Equation 186. IMS MMTel AS Number of Active Subscription

Sessions

IMSMMTelASActiveSubscriptionSess = MtasFuncOngoingSubsSess

IMSMMTelASSimulMobileSess is the number of currently active subscription

sessions on node level.

Equation 187. IMS ST AS Number of SIP Trunking

Simultaneous Sessions

IMSSTASSimulSess = MtasStCurrentSessions

IMSSTASSimulSess is the current number of active sessions in ST AS (SIP

Trunking AS).

Equation 188. IMS ST AS Number of SIP Trunking

Simultaneous Originating Sessions per PBX

IMSSTASSimulOrigSessionsPerPbx = MtasStCurrentOrigSessions.pbxId

IMSSTASSimulOrigSess is the current number of active originating sessions

in ST AS (SIP Trunking AS) per PBX.

Equation 189. IMS ST AS Number of SIP Trunking

Simultaneous Terminating Sessions per PBX

IMSSTASSimulTermSessionsPerPbx = MtasStCurrentTermSessions.pbxId

IMSSTASSimulTermSess is the current number of active terminating

sessions in ST AS (SIP Trunking AS) per PBX.
 Ericsson Internal
OPERAT. GUIDELINES 155 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 190. IMS MMTel AS Number of Currently Active

Conferences

IMSMMTelASConfActiveConferences = MtasConfActiveConferences
Equation 191. IMS MMTel AS Number of Conference
Participants

IMSMMTelASConfParticipants = MtasConfParticipants

Equation 192. IMS Conference AS Number of Currently Active

Scheduled Conferences

IMSConfASConfActiveSchedConferences =
MtasConfSchedActiveConferences
Equation 193. IMS Conference AS Number of Scheduled
Conference Participants

IMSConfASSchedConfParticipants = MtasConSchedfParticipants

Equation 194. IMS SCC AS IP Multimedia Routing Numbers

(IMRN) in use [%]

IMSSCCAS Im rnInUse = MtasSdsCurrentImrnUsage

The percentage of IP Multimedia Routing Numbers in use, calculated as

(Current number of IMRNs in use / Number of assigned IMRNs)*100.

MTAS Overload Control

Equation 195. IMS MTAS Overload Control Duration [Seconds]

IMSMTASOverloadControlDuration[S] =
MtasSipOcOvlDuration

IMSMTASOverloadControlDuration is the number of seconds which the node

spent in overload condition within the measured period.

Equation 196. IMS MTAS Overload Control Periods

IMSMTASOverloadControlPeriods =
MtasSipOcOvlPeriods

IMSMTASOverloadControlPeriods is the number of cases when the node

entered the overload operation mode within the measured period.

Equation 197. IMS MTAS Overload Control Values Average

 Ericsson Internal
OPERAT. GUIDELINES 156 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMTASOverloadControlValuesAvg =
MtasSipOcOvlAvg

IMSMTASOverloadControlValuesAvg is the average of the reported overload

control (oc) values within the measured period.

Equation 198. IMS MTAS Overload Control Values Peak

IMSMTASOverloadControlValuesPeak =
MtasSipOcOvlPeak

IMSMTASOverloadControlValuesPeak is the maximum of the reported

overload control (oc) values within the measured period.

IMS MMTel Active Users:

IMS MMTel Active Users may me measured using CSCF R-KPI Equation 54
IMS CSCF Active Users, ref. IMS Active Users, section 5.4.

The measurement is keyed with the feature tag received in SIP Request
message (Accept-Contact header). The feature tag provided in formula is the
MTAS delivery configuration, normally set to urn:7:3gpp-
service.ims.icsi.mmtel, but may be set to whatever value of the operator
choice.

Note that this R-KPI is dependant of the terminals using the feature tag.

For more traffic indicators, please refer to IMCN Signaling Traffic

Performance Indicators, ref. [11], section 4.12 MTAS.

Counter Name Definition

MtasSubsDataRegisteredUsers The number of registered IMS users served

by MTAS. Incremented when an initial
REGISTER request is received. Also
incremented if an initial INVITE or
SUBSCRIBE to DEN service is received on
the registered port from a not yet registered
subscriber. Decremented when the de-
registration of the subscriber is finished..
Counter on MTAS node.
MtasFuncOngoingSess The current number of active users on node
level. The counter is incremented when a
user becomes active and decremented
when a user becomes inactive..
Counter on MTAS node.

MtasFuncOngoingMmtSessAvg The average number of simultaneous Mmt

Services sessions (half calls) on node level.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 157 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasFuncOngoingMobileSessAvg The average number of simultaneous

Mobile Service sessions (half calls) on node
level. The counter is incremented when a
user becomes active and decremented
when a user becomes inactive.
Counter on MTAS node.

MtasSccCurrentOrigSessionCs Count of the current number of SCC

originating sessions from CS domain in
setup or progress.
Counter on MTAS node.
MtasSccCurrentOrigSessionPs Count of the current number of SCC
originating sessions from PS domain in
setup or progress.
Counter on MTAS node.
MtasSccCurrentTermSessionCs Count of the current number of SCC
terminating sessions from CS domain in
setup or progress.
Counter on MTAS node.
MtasSccCurrentTermSessionPs Count of the current number of SCC
terminating sessions from PS domain in
setup or progress.
Counter on MTAS node.
MtasFuncOngoingSubsSess The number of currently active subscription
sessions on node level.
Counter on MTAS node.
MtasStCurrentSessions Gauge for current number of sessions in ST
AS. Both initiated and established sessions
are included. The counter reflects the
measure controlled by the ST AS session
capacity license.
The Gauge is incremented by 1 when a
PBX originating or terminating call session
is initiated and decremented by 1 when the
call session is terminated.
Counter on MTAS node.

MtasConfActiveConferences The number of currently active conferences.

Counter on MTAS node.

MtasConfParticipants Contains the number of conference

participants involved in conferences with 4
or more participants.
Counter on MTAS node.

MtasSchedConfParticipants Contains the number of conference

participants involved in scheduled
conferences.
Counter on MTAS node.

MtasSdsCurrentImrnUsage The percentage of IP Multimedia Routing

Numbers in use, calculated as (Current
number of IMRNs in use / Number of
assigned IMRNs)*100.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 158 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSipOcOvlAvg The average of the reported oc values

within the measured period. Only those oc
values are counted which belong to an
overload condition interval of the node.
The gauge is updated when OC value is
greater than 0.
Counter on MTAS node.

MtasSipOcOvlDuration The number of seconds which the node

spent in overload condition within the
measured period.
Counter on MTAS node.

MtasSipOcOvlPeak The maximum SIP Overload Control value

sent towards upstream nodes within the
measured period.
Counter on MTAS node.

MtasSipOcOvlPeriods The number of the cases when the node

entered the overload operation mode within
the measured period.
The counter is incremented by 1 when the
node entered the overload mode (OC value
is changes from 0 to some other value).
Counter on MTAS node.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

7 Gateway Functions
7.1 IMS MGC

Performance indicators at MGC node supporting the signal interworking and

media gateway control functions.

7.1.1 MGC SIP Session Set-up Accessibility

Equation 199. IMS MGC SIP Incoming Sessions Success Ratio

IMSMGCSIPInSessSuccRatio[%] = 100 *
mgcPmSipTotIncomingSuccesfullSessions
mgcPmSipTotIncomingSessions

Equation 200. IMS MGC SIP Outgoing Sessions Success Ratio

IMSMGCSIPOutSessSuccRatio[%] = 100 *
mgcPmSipTotOutgoingSuccesfullSessions
mgcPmSipTotOutgoingSessions
 Ericsson Internal
OPERAT. GUIDELINES 159 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

7.1.2 MGC H.248 Accessibility and Retainability

Equation 201. IMS MGC H.248 Session Setup Success Ratio

IMSMGCH 248SessSetupSuccRatio[%] = 100 *

(mgcPmMgwTotCalls - (mgcPmH248TotEquipErr +
mgcPmH248TotInvAdd +
mgcPmH248TotOtherErr +
mgcPmH248TotProtErr +
mgcPmH248TotResUnav))
mgcPmMgwTotCalls

Equation 202. IMS MGC H.248 Session Completion Ratio

IMSMGCH 248SessSetupSuccRatio[%] = 100 *

mgcPmMgwTotCalls - mgcPmMgwTotAbnormallyTerminated)
mgcPmMgwTotCalls

7.1.3 MGC ISUP Route Set-up Accessibility

Equation 203. IMS MGC ISUP Incoming Sessions Success

Ratio for PSTN Route

IMSMGCISUPInSuccRatio[%] = 100 *
mgcPmRouteTotIncomingCallsAnswered
mgcPmRouteTotIncomingCalls

Equation 204. IMS MGC ISUP Outgoing Sessions Success

Ratio for PSTN Route

IMSMGCISUPOutSuccRatio[%] = 100 *
mgcPmRouteTotOutgoingCallsAnswered
mgcPmRouteTotOutgoingCalls

7.1.4 Traffic Indicators

MGC SIP Session

Equation 205. IMS MGC Number of Simultaneous SIP Sessions

IMSMGCNoSimul tan eousSIPSess = mgcPmSipTotCurrentSessions

Equation 206. IMS MGC SIP Incoming Sessions [per second]

 Ericsson Internal
OPERAT. GUIDELINES 160 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

mgcPmSipTotIncomingSessions
IMSMGCSIPInSess =
T
Equation 207. IMS MGC SIP Outgoing Sessions [per second]

mgcPmSipTotOutgoinSessions
IMSMGCSIPOutSess =
T
MGC H.248 Contexts

Equation 208. IMS MGC Number of Simultaneous H.248

Sessions

IMSMGCNoSimH 248Sess = mgcPmMgwCallsActive

Equation 209. IMS MGC H.248 Incoming Sessions [per second]

mgcPmMgwTotCalls
IMSMGCH 248 InSess =
T
MGC ISUP PSTN Route

Equation 210. IMS MGC Number of Simultaneous ISUP

Sessions for PSTN Route

IMSMGCNoSimul tan eousISUPSess = mgcPmRouteActiveCalls

Equation 211. IMS MGC ISUP Incoming Sessions for PSTN

Route [per second]

mgcPmRouteTotIncomingCalls
IMSMGCISUPInSess =
T
Equation 212. IMS MGC ISUP Outgoing Sessions for PSTN
Route [per second]

mgcPmRouteTotOutgoingCalls
IMSMGCISUPOutSess =
T
T = measured/reported time in seconds

Counter Name Definition

mgcPmSipTotCurrentSessions Number of current sessions, both incoming

and outgoing sessions. This gauge is
incremented when a session has been
successfully established and decremented
when the session has been terminated.
Counter on MGC node.
 Ericsson Internal
OPERAT. GUIDELINES 161 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

mgcPmSipTotIncomingSessions Total number of incoming SIP sessions,

including failed session setup attempts
received by the MGCF. This counter is
incremented whenever SIP INVITE
message is received for a new session, i.e.
the possible re-INVITEs received during
ongoing session do not increment this
counter.
Counter on MGC node.
mgcPmSipTotIncomingSuccesfullSess Total number of incoming successful SIP
ions sessions. A successful session
establishment is an INVITE received for a
new session for which a 200 OK is sent and
ACK is received.
Counter on MGC node.
mgcPmSipTotOutgoingSessions Total number of outgoing SIP sessions,
including failed session setups with a SIP
INVITE message sent from the MGCF.
Counter on MGC node.
mgcPmSipTotOutgoingSuccesfullSess Total number of outgoing successful SIP
ions sessions. A successful session
establishment is an INVITE for a new
session for which 200 OK is received and
ACK is sent.
Counter on MGC node.
mgcPmMgwCallsActive Number of active sessions in MGW.
Counter on MGC node.

mgcPmMgwTotCalls Total number of served sessions including

successful setups.
Counter on MGC node.
mgcPmMgwTotAbnormallyTerminated Total number of abnormally terminated
session after successful setup.
mgcPmH248TotEquipErr Total number of server and equipment error.
mgcPmH248TotInvAdd Total number of invalid address
mgcPmH248TotOtherErr Total number of other H248 errors.

mgcPmH248TotProtErr Total number of H248 syntax or protocol

error.
mgcPmH248TotResUnav Total number of resources unavailable or
unsupported.
mgcPmH248TotUnauth Total number of unauthorized attempts.
mgcPmRouteActiveCalls Number of active sessions for the
corresponding PSTN route.
Counter on MGC node.
mgcPmRouteTotIncomingCalls Number of incoming sessions, including
session attempts for the corresponding
PSTN route.
Counter on MGC node.
 Ericsson Internal
OPERAT. GUIDELINES 162 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

mgcPmRouteTotIncomingCallsAnswer Number of incoming sessions that have

ed lead to conversation state i.e. answer
received.
Counter on MGC node.
mgcPmRouteTotOutgoingCalls Number of outgoing sessions, including
session attempts for the corresponding
PSTN route.
Counter on MGC node.
mgcPmRouteTotOutgoingCallsAnswer Number of outgoing sessions that has lead
ed to conversation state.
Counter on MGC node.

Reference: MGC System Statistics, 9/154 43-CNA 113 215/1, ref. [21].

7.2 IMS SBG

Performance indicators at SBG node supporting IP-IP Network-to-Network

(NNI) gateway function for IMS Core and external core network and access
gateway function for IMS Core and fixed BroadBand (BB) access networks,

Some parts of the chapter are valid only for A-SBG and some parts for A-SBG
and N-SBG. This is indicated with equation naming.

In this chapter A-SBG is used for standard 3GPP function Access Application
Level Gateway (A-ALG) and P-CSCF and N-SBG is used for Interconnect
Border Control Function (I-BCF).

7.2.1 Registration Accessibility

Equation 213. IMS A-SBG Initial Registration Success Ratio

IMSSBGInit Re gSuccRatio[%] = 100 *

(sbgSipRegStatInitialAccCnt + sbgSipRegStatRejInitialRegCnt400 +
sbgSipRegStatRejInitialRegCnt403 + sbgSipRegStatRejInitialRegCnt404)
sbgSipRegStatInitialAttCnt

These equations cover the deployment where SGC or P-CSCF is the entry
point to the IMS network.

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized” and “404 Not
Found”.

Equation 214. IMS A-SBG Emergency Initial Registration

Success Ratio
 Ericsson Internal
OPERAT. GUIDELINES 163 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSASBGEmergInit Re gSuccRatio[%] = 100 *

sbgSipEmerRegStatInitialAccCnt
sbgSipEmerRegStatInitialAttCnt

IMSASBGEmergInitRegSuccRatio is the ratio of successful initial emergency

registrations in SGC or P-CSCF during a reporting period.

This equation covers the deployment where SGC or P-CSCF is the entry
point to the IMS network.

Reference for this section: Key Performance Indicators for IMS System, ref.
[8] Section 3.1.2 Accessibility: IMS Initial Registration Success Ratio [%].

7.2.2 IMS SBG Registration Retainability

Equation 215. IMS A-SBG Reregistration and Deregistration

Success Ratio

IMSASBG Re AndDeregSuccRatio[%] = 100 *

(sbgSipRegStatReRegAccCnt +
sbgSipRegStatRejReRegCnt400 + sbgSipRegStatRejReRegCnt403 +
sbgSipRegStatDeRegAccCnt)
(sbgSipRegStatReRegAttCnt + sbgSipRegStatDeRegAttCnt)

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.2.2
Retainability - IMS Registration Completion Ratio [%].

Equation 216. IMS A-SBG Re-registration Success Ratio

IMSASBG Re Re gSuccRatio[%] = 100 *

(sbgSipRegStatReRegAccCnt +
sbgSipRegStatRejReRegCnt400 + sbgSipRegStatRejReRegCnt403)
)
sbgSipRegStatReRegAttCnt

IMSASBGReregSuccRatio is the ratio of successful to all re-registrations in P-

CSCF during a reporting period.

The registration is considered as successful for response codes; “400 Bad

Request”, “403” (Many reasons. e.g. “Forbidden”), “403 No Roaming
Agreement from Current Network”, “403 User Not Authorized”.

Equation 217. IMS A-SBG De-registration Success Ratio

IMSASBGDe Re gSuccRatio[%] = 100 *

sbgSipRegStatDeRegAccCnt
sbgSipRegStatDeRegAttCnt
 Ericsson Internal
OPERAT. GUIDELINES 164 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSASBGDeregSuccRatio is the ratio of successful to all de-registrations in

P-CSCF during a reporting period.

Equation 218. IMS A-SBG Emergency Re-Registration Success

Ratio

IMSASBGEmerg Re gSuccRatio[%] = 100 *

sbgSipEmerRegStatReRegAccCnt
sbgSipEmerRegStatReRegAttCnt

IMSASBGEmergReregSuccRatio is the ratio of successful to all emergency

re-registrations in P-CSCF during a reporting period.

7.2.3 IMS SBG Registation Integrity

IMS A-SBG Initial Registrations time is defined as the time period between,
when a user initiates an SBG initial registration and when the originating user
receives notification that the registration attempt is initiated or completed.

Equation 219. IMS A-SBG Initial Registration Time

[milliseconds]

IMSASBGInit Re gTime[ms] =
sbgInitRegTime
sbgSipRegStatInitialAccCnt

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.3.2
Integrity – IMS Initial Registration time [s].

Note: In formula above, only timing for the second phase in registration is
recorded, from the SIP REGISTER containing the credentials received from
UE until SIP 200 OK is sent to UE.
Counter Name Definition

sbgInitRegTime This value represents the total time for initial

register requests. The time is measured
from when the request arrives at the SGC
until the 200 OK response is sent back to
the client. Time is only measured for initial
registers that gets a 2xx response, in
particular time is not measured for a 401
response or for any subsequent re-register
request. This value contains the sum of all
such initial register times. This value is in
milli seconds.
Counter on A-SBG node.
sbgSipRegStatInitialAccCnt This counter holds the number of initial
registration sessions accepted by the CSCF
for this access network.
Counter on A-SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 165 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23].

7.2.4 IMS SBG Session Accessibility

Equation 220. IMS SBG Incoming Session Set-up Success

Ratio

IMSSBGIncSessSuccRatio[%] = 100 *
sbgSipNetIncSessionEstabNetworkSuccess
sbgSipTotalIncSessSetups

IMSSBGvIncSessSuccRatio[%] = 100 *
sbgSipNetIncSessionEstabNetworkSuccess
(sbgSipTotalIncSessSetups - sbgSipChallengedIncInvSessions)

Equation 221. IMS SBG Outgoing Session Set-up Success

Ratio

IMSSBGOutSessSuccRatio[%] = 100 *
sbgSipNetOutSessionEstabNetworkSuccess
sbgSipTotalOutSessSetups

IMSSBGvOutSessSuccRatio[%] = 100 *
sbgSipNetOutSessionEstabNetworkSuccess
(sbgSipTotalOutSessSetups - sbgSipChallengedOutInvSessions)

The SBG node support Equation 236 and Equation 237 formula variants
IMSSBGIncSessSuccRatio and IMSSBGOutSessSuccRatio for deployments
where SBG is the entry point to the IMS network called access networks,
interfacing the IMS Core, called Core networks and implements the network
to network interface (NNI) to other domains, this is called foreign networks.

The SBGv node support Equation 236 and Equation 237 formula variants
according to Table 2:

Network type Direction Incoming Direction Outgoing

P-CSCF IMSSBGvIncSessSuccRatio IMSSBGOutSessSuccRatio

Access
IMSSBGvIncSessSuccRatio
P-CSCF Core IMSSBGIncSessSuccRatio
IMSSBGvIncSessSuccRatio IMSSBGvIncSessSuccRatio
I-BCF Foreign
IMSSBGvIncSessSuccRatio IMSSBGvIncSessSuccRatio
I-BCF Core
 Ericsson Internal
OPERAT. GUIDELINES 166 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Table 2 Equation 259 and Equation 260 formula variants

SBGv supports measurements for challenge responses, 401 and 407 for the
P-CSCF and I-BCF logical nodes. The challenge response measurements are
implemented for incoming and outgoing requests for the I-BCF node and
incoming requests for the P-CSCF node.

Note also that these equation Equation 236 does not cover the interface to
the CS network in the SR-VCC access transfer use case.

References:

Key Performance Indicators (KPI) for the IP Multimedia Subsystem (IMS);

Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.2 Session
Establishment Success Rate.

Key Performance Indicators for IMS System, ref. [8] Section 3.1.1
Accessibility: IMS Session Set-up Success Ratio [%].

The KPI IMS Session Set-up Success Ratio [%] lists five supported success
criteria:

1. SIP 180 RINGING message.

2. Final “SIP 200 OK (INVITE)” message – in cases when the

terminating user has automatic answering configured.

3. In cases when NRBT service is active and preconditions used -

The first time at which the SBG opens the BGF pin hole (for allowing
authorized early media) and receives a successful H.248 Modify reply.

4. In case CANCEL (or corresponding event) from client is

received before any response except 100 Trying is sent.

5. In cases when a call set-up was not successfully initiated due to

faults outside of IMS system or user behavior, that specific call set-up
attempt shall be considered as an IMS successful call set-up.
Below user behavior factor cases shall take as success session setup:

• User is not registered

• Busy Here (486)

• Forbidden (403)

• Not Found (404)

• Decline (603)

• Address Incomplete (484)

• Busy Everywhere (600)

 Ericsson Internal
OPERAT. GUIDELINES 167 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Emergency call formula:

Equation 222. IMS SBG Emergency Session Set-up Success

Ratio

IMSSBGEmergencySessSuccRatio[%] = 100 *
sbgSgcTotalEmergencyCallsSuccess
sbgSgcTotalEmergencyCallsSetups

IMSSBGvEmergencySessSuccRatio[%] = 100 *
sbgTotalEmergencyCallsSuccess
sbgTotalEmergencyCallsSetups

Note that this formula may to be calculated per network or for all networks, in
the latter case values for all networks need to be added.

Priority call formulas (Valid for SBG, but not for SBGv):

Equation 223. IMS SBG Incoming Priority Session Set-up

Success Ratio

IMSSBGInc Pr ioritySessSuccRatio[%] = 100 *

sbgSgcIncPriorityCallSuccessSetups
sbgSgcIncPriorityCallAttempts

Equation 224. IMS SBG Outgoing Priority Session Set-up

Success Ratio

IMSSBGOut Pr ioritySessSuccRatio[%] = 100 *

sbgSgcOutPriorityCallSuccessSetups
sbgSgcOutPriorityCallAttempts

Note that this formula may to be calculated per network or for all networks, in
the latter case values for all networks need to be added.

Session accessibility; Answer to Seizure Ratio (ASR). It is the percentage of

answered telephone calls with respect to the total call volume.

Equation 225. IMS SBG Incomimg Session Answer to Seizure

Ratio

sbgSipSuccessIncSessions
IMSSBGIncSessAnswerToSeizureRatio[%] = 100 *
sbgSipTotalIncSessSetups

Equation 226. IMS SBG Outgoing Session Answer to Seizure

Ratio
 Ericsson Internal
OPERAT. GUIDELINES 168 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

sbgSipSuccessOutSessions
IMSSBGSessAnswerToSeizureRatio[%] = 100 *
sbgSipTotalOutSessSetups

Equation 227. IMS SBG Incoming S8HR Session Answer to

Seizure Ratio

IMSSBGIncS 8 HRSessionAnswerToSeizureRatio[%] = 100 *

sbgSipSuccessIncS8HrSessions
sbgSipTotalIncS8HrSessSetups

Equation 228. IMS SBG Outgoing S8HR Session Answer to

Seizure Ratio

IMSSBGOutS 8 HRSessionAnswerToSeizureRatio[%] = 100 *

sbgSipSuccessOutS8HrSessions
sbgSipTotalOutS8HrSessSetups

Note for this section that this formula may to be calculated per network or for
all networks, in the latter case values for all networks need to be added.
S8HR formulas are only applicable for access networks. The S8HR statistics
is included in the common SIP statistics, e.g. sbgSipTotalIncSessSetups and
sbgSipTotalOutSessSetups and so on.

7.2.5 IMS SBG Session Retainability

IMS SBG Session Retainability is defined as the probability of being able to

successfully complete (normally terminate) an active session in the IMS SBG
once it has been successfully set-up.

Equation 229. IMS SBG Session Completion Ratio

IMSSBGSessCompRatio[%] = 100 *
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease)
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease +
sbgSipSgcInitiatedSessionRelease)

IMSSBGvSessCompRatio[%] = 100 *
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease)
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease +
sbgSipInitiatedSessionRelease)

Reference: Key Performance Indicators for IMS System, ref. [8] Section
Retainability: IMS Session Completion Ratio [%].

This equation covers the deployment where SBG is the entry point to the IMS
network or implements the network to network interface (NNI) to other
domains.
 Ericsson Internal
OPERAT. GUIDELINES 169 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 230. IMS SBG Dropped Sessions Ratio

IMSSBGDroppedSessionsRatio[%] =
sbgSipSgcInitiatedSessionRelease
100 *
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease +
sbgSipSgcInitiatedSessionRelease )

IMSSBGvDroppedSessionsRatio[%] =
sbgSipInitiatedSessionRelease
100 *
(sbgSipSessionIncNormalRelease + sbgSipSessionOutNormalRelease +
sbgSipInitiatedSessionRelease )

SBG ATCF SRVCC Access Transfer

Equation 231. IMS SBG SRVCC Access Transfer Success Ratio

IMSSBGSRVCCAccessTransferSuccRatio[%] =
(sbgSipSuccessIncSessions + sbgSipRejectedIncAlertingSessions488 +
sbgSipRejectedIncPreAlertingSessions488)
100 *
sbgSipTotalIncSessSetups

Equation 253 is applicable for the ATCF specific CS network in SBG for
incoming SRVCC requests and responses. Response code 488 in alerting
and pre-alerting call set-up phase implies lack of SRVCC support in client,
thus it is not a IMS network fault.

7.2.6 IMS SBG Session Setup Integrity

Equation 232. IMS SBG Incoming Sessions Set-up Time

[milliseconds]

IMSSBGIncSessSessionSetupTime[ms] =
sbgSipNetIncSessionSetupTime
sbgSipNetIncSessionSetupUserSuccess

Equation 233. IMS SBG Outgoing Sessions Set-up Time

[milliseconds]

IMSSBGOutSessSessionSetupTime[ms] =
sbgSipNetOutSessionSetupTime
sbgSipNetOutSessionSetupUserSuccess
 Ericsson Internal
OPERAT. GUIDELINES 170 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

The IMSSBGIncSessSetupTime and IMSSBGOutSessSetupTime formulas

provides the mean time period between when the IMS SBG receives an SIP
INVITE corresponding to a user initiates an IMS session by e.g. pressing the
session set-up button, and when the IMS SBG sends a SIP 180 Ringing or
SIP 200 OK response corresponding to the originating user receives a callee
alerted notification, or in the case that terminating phone is configured to use
automatic answer, the originating user receives a notification that the session
has been set-up, for incoming and outgoing traffic respectively.

Note that Equation 248 is reflecting the R-KPI referenced above where the
originating user initiates a session set-up. Equation 249 is a supporting
formula for the terminating case. This is valid when access networks are
observed.

These equations (Equation 248 and Equation 249) covers the deployment
where SBG is the entry point to the IMS network called access networks,
interfacing the IMS Core, called Core networks, implements the network to
network interface (NNI) to other domains, this is called foreign networks.

Note that these equations (Equation 248 and Equation 249) does not cover
the interface to the CS network in the SR-VCC access transfer use case.

Reference: Key Performance Indicators for IMS System, ref. [8] Section 3.3.1
Integrity: IMS Session Set-up Time [s].

Reference: Key Performance Indicators (KPI) for the IP Multimedia

Subsystem (IMS); Definitions, 3GPP TS 32.454 V10.0.0, ref. [6], section 5.1.2
Session Setup Time (Mean).

7.2.7 IMS SBG Subscribe Accessibility

Equation 234. IMS SBG Incoming Subscribe Session Set-up

Success Ratio

IMSSBGIncSubscribeSuccRatio[%] = 100 *
sbgSipRejectedIncSubscribeSessions
sbgSipTotalIncSipSubscribeRequests

Note that this formula may to be calculated per access network or for all
access networks, in the latter case values for all access networks need to be
added.

Equation 235. IMS SBG Outgoing Subscribe Session Set-up

Success Ratio

IMSSBGOutSubscribeSuccRatio[%] = 100 *
sbgSipRejectedOutSubscribeSessions
sbgSipTotalOutSipSubscribeRequests
 Ericsson Internal
OPERAT. GUIDELINES 171 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Note that this formula may to be calculated per access network or for all
access networks, in the latter case values for all access networks need to be
added.

7.2.8 IMS SBG Message Accessibility

Equation 236. IMS SBG Incoming MESSAGE Request Success

Ratio

IMSSBGIncMessageSuccRatio[%] = 100 *
sbgSipSuccessIncMessage
sbgSipTotalIncMessage

Note that this formula may to be calculated per access network or for all
access networks, in the latter case values for all access networks need to be
added.

Equation 237. IMS SBG Outgoing MESSAGE Request Success

Ratio

IMSSBGOutMessageSuccRatio[%] = 100 *
sbgSipSuccessOutMessage
sbgSipTotalOutMessage

Note that this formula may to be calculated per access network or for all
access networks, in the latter case values for all access networks need to be
added.

7.2.9 Media Integrity

Equation 238. IMS SBG Media RTP Lost Packets Ratio

IMSSBGMediaRTPLostPcktsRatio[%] =
sbgSgcPktsLostRatioGauge
100

IMSSBGvMediaRTPLostPcktsRatio[%] =
sbgPktsLostRatioGauge
100
Equation 239. IMS SBG Media RTP Out of Sequence Packets
Ratio

IMSSBGMediaRTPOutSeqPcktsRatio[%] =
sbgSgcPktsOutofSeqRatioGauge
100
 Ericsson Internal
OPERAT. GUIDELINES 172 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSBGvMediaRTPOutSeqPcktsRatio[%] =
sbgPktsOutofSeqRatioGauge
100
Equation 240. IMS SBG External BGCF Call Set-up Success
Ratio

IMSSBGExtBGCFCallSetupSuccessRatio[%] = 100 *
sbgExtBgfTotCallsCnts - bgExtBgfTotCallsFailedCnt
sbgExtBgfTotCallsCnts

7.2.10 Traffic Indicator

7.2.10.1 Error PIs associated with Sessions

Initial Registration Failures per cause

Equation 241. IMS SBG Initial Registration Failure 400 [per

second]

sbgSipRegStatRejInitialRegCnt400
IMSSBGInit Re gFail 400 =
T

Equation 242. IMS SBG Initial Registration Failure 403 [per

second]

sbgSipRegStatRejInitialRegCnt403
IMSSBGInit Re gFail 403 =
T

Equation 243. IMS SBG Initial Registration Failure 404 [per

second]

sbgSipRegStatRejInitialRegCnt404
IMSSBGInit Re gFail 404 =
T

Equation 244. IMS SBG Initial Registration Failure 421 [per

second]

sbgSipRegStatRejInitialRegCnt421
IMSSBGInit Re gFail 421 =
T

Equation 245. IMS SBG Initial Registration Failure 500 [per

second]

sbgSipRegStatRejInitialRegCnt500
IMSSBGInit Re gFail 500 =
T
 Ericsson Internal
OPERAT. GUIDELINES 173 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 246. IMS SBG Initial Registration Failure 503 [per

second]

sbgSipRegStatRejInitialRegCnt503
IMSSBGInit Re gFail 503 =
T

Re-registration Failures per cause

Equation 247. IMS SBG Initial Re-registration Failure 400 [per

second]

sbgSipRegStatRejReRegCnt400
IMSSBGInit Re Re gFail 400 =
T

Equation 248. IMS SBG Initial Re-registration Failure 403 [per

second]

sbgSipRegStatRejReRegCnt403
IMSSBGInit Re Re gFail 403 =
T

Equation 249. IMS SBG Initial Re-registration Failure 404 [per

second]

sbgSipRegStatRejReRegCnt404
IMSSBGInit Re Re gFail 404 =
T

Equation 250. IMS SBG Initial Re-registration Failure 421 [per

second]

sbgSipRegStatRejReRegCnt421
IMSSBGInit Re Re gFail 421 =
T

Equation 251. IMS SBG Initial Re-registration Failure 500 [per

second]

sbgSipRegStatRejReRegCnt500
IMSSBGInit Re Re gFail 500 =
T

Equation 252. IMS SBG Initial Re-registration Failure 503 [per

second]

sbgSipRegStatRejReRegCnt4503
IMSSBGInit Re Re gFail 503 =
T

Session set-up failures

Equation 253. IMS SBG Session Set-up Failure BGF Resource

Unavailability [per second]
 Ericsson Internal
OPERAT. GUIDELINES 174 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSBGSessSetupFailBGF Re sourceUnavailable =
sbgSipNetTotBgfUnsuccReselection
T
Equation 254. IMS SBG SBG Session Set-up Failure Max
Session Reached[per second]

sbgSipRejectedMaxSessions
IMSSBGSessSetupFailMaxSessions =
T

Equation 255. IMS SBG Session Set-up Failure Release Signal

Bearer[per second]

sbgSipRejSessionReleaseOfSigBearer
IMSSBGSessSetupFail Re lSigBearer =
T

Equation 256. IMS SBG Session Set-up Failures SDP Validation

Failed [per second]

sbgSipSrcSDPValidationFailed
IMSSBGSessSetupFailSDPValidationFailed =
T

sbgSipSrcValidationFailed
IMSSBGvSessSetupFailSDPValidationFailed =
T

Equation 257. IMS SBG Inc Session Set-up Failure 403 [per
second]

sbgSipRejectedIncSessions403
IMSSBGIncSessSetupFail 403 =
T
Equation 258. IMS SBG Inc Session Set-up Failure 486 [per
second]

sbgSipRejectedIncSessions486
IMSSBGIncSessSetupFail 486 =
T
Equation 259. IMS SBG Out Session Set-up Failure 403 [per
second]

sbgSipRejectedOutSessions403
IMSSBGOutSessSetupFail 403 =
T
Equation 260. IMS SBG Out Session Set-up Failure 486 [per
second]
 Ericsson Internal
OPERAT. GUIDELINES 175 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

sbgSipRejectedOutSessions486
IMSSBGOutSessSetupFail 486 =
T
Equation 261. IMS SBG Out Session Set-up Failure 603 [per
second]

sbgSipRejectedOutSessions603
IMSSBGOutSessSetupFail 603 =
T
Equation 262. IMS SBG BGF Reselections [per second]

sbgSipNetTotBgfReselection
IMSSBGBGF Re selections =
T

Note: SBG cannot perform BGF reselection in session.

Session completion/drop failures

Equation 263. IMS SBG Initiated Session Release [per second]

IMSSBGInitiatedSessionRelease =
sbgSipSgcInitiatedSessionRelease
T
IMSSBGInitiatedSessionRelease is the number of active INVITE sessions
(ACK for 200 OK to INVITE has been received) for which a release has been
initiated by the SBG by sending a BYE. Examples of cases where the counter
is stepped are:

– Session timer expiry detected by SBG

– Media stop notification from BGF received

– Bearer release notification received from Rx interface

– Mid-dialog transaction timeout

Equation 264. IMS SBG Release Session Timer Expiry[per

second]

sbgSipSgcReleasesSessionTimer
IMSSBG Re leaseSessionTimerExpiry =
T

sbgSipReleasesSessionTimer
IMSSBGv Re leaseSessionTimerExpiry =
T
 Ericsson Internal
OPERAT. GUIDELINES 176 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSBGReleaseSessionTimer and IMSSBGvReleaseSessionTimer is the

number of SGC initiated releases due to either:
- Session timer expiry or
- Maximum non-supervised session duration timer expiry.
The counter will only be stepped for the network from which the SIP session
was originally established

Equation 265. IMS SBG Dialog Release Request Timeout [per

second]

IMSSBGDialogReleasesRequestTimeout =
sbgSipSgcDialogReleasesRequestTimeout
T

IMSSBGvDia log Re leases Re questTimeouts =

sbgSipDialogReleasesRequestTimeout
T
IMSSBGDialogReleasesRequestTimeout and
IMSSBGvDialogReleasesRequestTimeout is the number of SGC initiated
releases of SIP dialogs (INVITE,SUBSCRIBE, REFER), due to either
transaction timeout or to reception of a 408 Request Timeout response code
for an outgoing mid-dialog request.

Equation 266. IMS SBG Session Release Signaling Bearer [per

second]

IMSSBGRelSessionReleaseOfSigBearer =
sbgSipRelSessionReleaseOfSigBearer
T
Equation 267. IMS SBG Session Release Media Stop [per
second]

IMSSBGRelSessionReleasesMediaStop =
sbgSipSgcReleasesMediaStop
T
Session release for media stop include RTP timeouts detected by media
node.

7.2.10.2 SRVCC failures

Equation 268. IMS SBG SRVCC Rejected CS Transfer Attempts

[per second]
 Ericsson Internal
OPERAT. GUIDELINES 177 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSBGSRVCCRejCSTransferAtt =
sbgSipOutNwRejSessions
T
Equation 269. IMS SBG SRVCC Inc Fallback Attempts [per
second]

IMSSBGSRVCCIncFallbackAtt =
sbgSipIncFallbackSessionAttempts
T
7.2.10.3 SIP Transaction timeouts

Equation 270. IMS SBG Outgoing Transaction Timeouts [per

second]

IMSSBGOutgoingTransactionTimeouts =
sbgSipOutgoingTransactionTimeouts
T
IMSSBGOutgoingTransactionTimeouts is the number of sent SIP request
which results in transaction timeout.

7.2.10.4 External BGCF traffic failures

Equation 271. IMS SBG Abnormal Termination from BGF [per

second]

sbgExtBgfTotCallsAbnTerminatedCnt
IMSSBGAbnormalBGFTer min ations =
T

IMSSBGAbnormalBGFTerminations is the total number of contexts in 'active'

state that have been abnormally released by the SBG due to an indication
(Notify or ServiceChange) from the BGF using the associated H.248 control
link.

Equation 272. IMS SBG Hanging BGF Termination Events [per

second]

sbgExtBgfHangingTerminationCnt
IMSSBGHangingBGFTer min ations =
T

IMSSBGHangingBGFTerminations is the total number of times a hanging

termination event has been received by the SBG from an Ext Bgf.

Equation 273. IMS SBG BGF Call Failed [per second]

 Ericsson Internal
OPERAT. GUIDELINES 178 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

sbgExtBgfTotCallsFailedCnt
IMSSBGBGFCallFailed =
T

IMSSBGBGCFCallFailed is the total number of BGF failed context setup

attempts (H.248 Context) per second.

Equation 274. IMS SBG BGF Invalid Address [per second]

sbgExtH248TotInvalidAddressCnt
IMSSBGBGFInvalidAddress =
T

IMSSBGBGFInvalidAddress is the total number of BGF failed context setup

attempts using invalid identifier (H.248 Context) per second.

Equation 275. IMS SBG BGF No Resource [per second]

sbgExtH248TotNoResourcesCnt
IMSSBGBGFNo Re source =
T

IMSSBGBGFNoResource is the total number of BGF failed context setup

attempts where no resource was available (H.248 Context) per second.

Equation 276. IMS SBG BGF Other Errors [per second]

sbgExtH248TotOtherErrorCnt
IMSSBGBGFOtherError =
T

IMSSBGBGFOtherError is the total number of BGF failed context setup

attempts where unspecified error occurred (H.248 Context) per second.

Equation 277. IMS SBG BGF Protocol Errors [per second]

sbgExtH248TotProtocolErrorCnt
IMSSBGBGF Pr otError =
T

IMSSBGBGFProtError is the total number of BGF failed context setup

attempts where syntax or protocol error occurred (H.248 Context) per second.

Equation 278. IMS SBG BGF Server Errors [per second]

sbgExtH248TotServerErrorCnt
IMSSBGBGFServerError =
T

IMSSBGBGFServerError is the total number of BGF failed context setup

attempts where server or equipment error occurred (H.248 Context) per
second.

T = measured/reported time in seconds

 Ericsson Internal
OPERAT. GUIDELINES 179 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipRegStatInitialAccCnt This counter holds the number of initial
registrations accepted (200 OK) by the
CSCF for the access network. Registration
query is not counted.
Counter on A-SBG node.
sbgSipRegStatInitialAttCnt This counter holds the number of initial
registration attempts received by the SGC
for this access network. Responses to
authentication challenge (401 Unauthorized,
407 Proxy Authentication Required) are not
included. Responses to authentication
challenge are not included.
Counter on A-SBG node.
sbgSipRegStatRejInitialRegCnt400 This counter holds the total number of
registrations rejected by the SGC or the
core with error code '400 Bad Request' for
this access network. It also includes
rejected refresh registrations (that is re-
registrations). Registration query is not
counted.
Counter on A-SBG node.
sbgSipRegStatRejInitialRegCnt403 This counter holds the total number of
registrations rejected by the SGC or the
core with error code '403 Forbidden' for this
access network. It also includes rejected
refresh registrations (that is re-
registrations).Registration query is not
counted.
Counter on A-SBG node.
sbgSipRegStatRejInitialRegCnt404 This counter holds the total number of initial
registrations rejected by the SGC or the
core with '404 Not Found' for this access
network.Registration query is not counted.
Counter on A-SBG node.
This counter holds the number of attempts
sbgSipRegStatReRegAttCnt re-registrations for this access network.
Counter on A-SBG node.
This counter holds the number of successful
sbgSipRegStatReRegAccCnt re-registrations for this access network.
Counter on A-SBG node.
This counter holds the total number of re-
sbgSipRegStatRejReRegCnt400 registrations rejected by the SGC or the
core with 400 Bad Request for this access
network. Registration query is not counted.
Counter on A-SBG node.
This counter holds the total number of re-
sbgSipRegStatRejReRegCnt403 registrations rejected by the SGC or the
core with 403 Forbidden for this access
network. Registration query is not counted.
Counter on A-SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 180 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipRegStatDeRegAttCnt This counter holds the number of de-
registration attempts received by the
SGC for this access network.
Registration query is not counted.
Counter on A-SBG node.
sbgSipRegStatDeRegAccCnt This counter holds the number of
successful de-registrations for this
access network. Registration query is
not counted.
Counter on A-SBG node.
This counter holds the number of initial
sbgSipEmerRegStatInitialAccCnt emergency registrations accepted by the
CSCF for this access network.
Counter on A-SBG node.
This counter holds the number of initial
sbgSipEmerRegStatInitialAttCnt emergency registration attempts received
by the SGC for this access network.
Responses to authentication challenge are
not included.
Counter on A-SBG node.
This counter holds the number of successful
sbgSipEmerRegStatReRegAccCnt emergency re-registrations for this access
network.
Counter on A-SBG node.
This counter holds the number of
sbgSipEmerRegStatReRegAttCnt emergency re-registration attempts received
by the SGC for this access network.
Responses to authentication challenge are
not included.
Counter on A-SBG node.
Number of active INVITE sessions (ACK for
sbgSipSgcInitiatedSessionRelease 200 OK to INVITE has been received) for
which a release has been initiated by the
SGC by sending a BYE. Examples of cases
where the counter is stepped are:
-Session timer expiry detected by SBG
-Media stop notification from BGF received
-Bearer release notification received from
Rx interface
-Mid-dialog transaction timeout
When SBG receives a signaling bearer
release on Rx for an active session the
sbgSipSgcInitiatedSessionRelease counter
will be stepped on both access and core
network side, but BYE is sent only to the
core network.
Counter on SBG node.
Number of INVITE sessions for which a
sbgSipInitiatedSessionRelease release has been initiated by SBG by
sending a BYE.
Counter on SBGv node.
 Ericsson Internal
OPERAT. GUIDELINES 181 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

Number of normally released calls, where
sbgSipSessionIncNormalRelease the BYE was received to this SIP network
connection.
Counter on SBG node.
Number of normally released calls, where
sbgSipSessionOutNormalRelease the BYE was sent from this SIP network
connection.
Counter on SBG node.
The number of incoming session setup
sbgSipTotalIncSessSetups attempts. This is the number of sessions
initiated by incoming INVITEs. The session
setups may have succeeded or failed.
REGISTERs, MESSAGEs, SUBSCRIBEs,
and so on, are not counted as session setup
attempts.
Counter on SBG node.
This counter holds the total number of
sbgSipRejectedIncAlertingSessions48 incoming PS to CS SRVCC access transfer
8 INVITEs that are rejected by SGC with
response code 488, due to lack of SRVCC
support during alerting phase. The counter
is applicable only for CS network.
Counter on SBG node.
This counter holds the total number of
sbgSipRejectedIncPreAlertingSession incoming initial access transfer INVITEs that
s488 are rejected by SGC with response code
488, due to lack of SRVCC support during
pre-alerting phase. The counter is
applicable only for CS network
Counter on SBG node.
sbgSipRegStatRegUserGauge This gauge holds the number of registered
users (Contacts) currently present in the
SGC for this access network. Regular
subscribers and registered subscribers
(Contacts) connected via IMS AKA are
included.
Counter on A-SBG node.
sbgSipRegStatRegIPsecUserGauge This gauge holds the number of registered
users (Contacts) currently connected via
IMS AKA in SGC for this access network.
Counter on A-SBG node.
sbgSipEmerRegStatRegUserGauge This gauge holds the number of emergency
registered users (Contacts) currently
present in the SGC for this access network.
Counter on A-SBG node.
sbgSipTotalIncSessSetups Total incoming session setup attempts since
system started. This is the number of
sessions initiated by incoming INVITEs. The
session setups may have succeeded or
failed.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 182 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipNetIncSessionEstabNetworkSu Number of incoming INVITE sessions
ccess responded to with the following success
criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured.
4. In case CANCEL (or corresponding
event) from client is received before any
response except 100 Trying is sent.
5. In cases when a call set-up was not
successfully initiated due to faults outside of
IMS system or user behavior, that specific
call set-up attempt shall be considered as
an IMS successful call set-up.
Below user behavior factor cases shall take
as success session setup:
• User is not registered
• Busy Here (486)
• Forbidden (403)
• Not Found (404)
• Decline (603) outgoing only
• Address Incomplete (484)
• Busy Everywhere (600).
Counter on SBG node.
sbgSipChallengedIncInvSessions The number of incoming INVITE sessions
challenged by the access, foreign or core
network. This counter is incremented when
the SBG forwards a 401 Unauthorized or a
407 Proxy Authentication Required
response received from the access, foreign
or core network to the initial INVITE request.
Counter on SBGv node.
sbgSipTotalOutSessSetups The number of outgoing session setup
attempts. This is the number of sessions
initiated by outgoing INVITEs. The session
setups may have succeeded or failed.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 183 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipNetOutSessionEstabNetworkS Number of outgoing INVITE sessions
uccess responded to with responded to with the
following success criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured.
4. In case CANCEL (or corresponding
event) from client is received before any
response except 100 Trying is sent.
5. In cases when a call set-up was not
successfully initiated due to faults outside of
IMS system or user behavior, that specific
call set-up attempt shall be considered as
an IMS successful call set-up.
Below user behavior factor cases shall take
as success session setup:
• User is not registered
• Busy Here (486)
• Forbidden (403)
• Not Found (404)
• Decline (603) outgoing only
• Address Incomplete (484)
• Busy Everywhere (600).
Counter on SBG node.
sbgSipChallengedOutInvSessions The number of outgoing INVITE sessions
challenged by the core network. This
counter is incremented when the SBG
receives a 401 Unauthorized or a 407 Proxy
Authentication Required response from the
core network to the initial INVITE request.
Counter on SBGv node.
sbgSgcTotalEmergencyCallsSetups Total number of emergency calls or call-
back setups. Emergency call-back setups
are counted on the core network
connection.
Counter on SBG node.
sbgTotalEmergencyCallsSetups Total number of incoming emergency call
setup attempts.
Counter on SBGv node.
sbgSgcTotalEmergencyCallsSuccess Total number of successful incoming
emergency calls or call-back setups.
Successful emergency calls are counted on
Access and Foreign networks. Successful
emergency call-back setups are counted
only on the core network connection.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 184 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgTotalEmergencyCallsSuccess Total number of successful incoming

emergency calls. Successful Emergency
calls are those for which a 200 OK response
is received for the initial incoming INVITE
request. Successful emergency calls are
counted at incoming network.
Counter on SBGv node.
sbgSgcIncPriorityCallAttempts The number of incoming priority call
attempts per network, including the priority
calls that are either successful or failed. The
attribute is a counter and is specific to a
particular network. For each network the
counter shows the number of priority call
attempts that have been originated from that
network. This counter is incremented per
network for a priority call at the reception of
an initial INVITE.
Counter on SBG node.
sbgSgcIncPriorityCallSuccessSetups The number of incoming priority calls that
were successful.The attribute is a counter
and is specific to a particular network. For
each network the counter shows the
number of successful priority calls that have
been originated from that network. This
counter is incremented for a network when
the 200 OK for an initial priority call INVITE
is forwarded to that network.
Counter on SBG node.
sbgSgcOutPriorityCallAttempts The number of outgoing priority call
attempts per network, including the priority
calls that are either successful or failed. The
attribute is a counter and is specific to a
particular network. For each network the
counter shows the number of priority call
attempts that have been terminated at that
network. This counter is incremented for a
network when an initial priority call INVITE
is forwarded to that network.
Counter on SBG node.
sbgSgcOutPriorityCallSuccessSetups The number of outgoing priority calls that
were successful. The attribute is a counter
and is specific to a particular network. For
each network the counter shows the
number of successful priority calls that have
been terminated at that network. This
counter is incremented for a network when
the 200 OK for an initial priority call INVITE
received from that network.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 185 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipSuccessIncS8HrSessions Number of successfully answered (by 200

Ok) incoming INVITE sessions from S8HR
roaming user. Successfully answered re-
INVITEs on an already established dialog
are not counted.
Counter on SBG node.
sbgSipSuccessOutS8HrSessions Number of successfully answered (by 200
Ok) outgoing INVITE sessions to S8HR
roaming user. Not applicable to CS network
since calls terminating on CS network are
not supported. Successfully answered re-
INVITEs on an already established dialog
are not counted.
Counter on SBG node.
sbgSipTotalIncS8HrSessSetups The number of incoming session setup
attempts from S8HR roaming user. This is
the number of sessions initiated by
incoming INVITEs from S8HR roaming user.
The session setups may have succeeded or
failed. REGISTERs, MESSAGEs,
SUBSCRIBEs, and so on, are not counted
as session setup attempts.
Counter on SBG node.
sbgSipTotalOutS8HrSessSetups The number of outgoing session setup
attempts from S8HR roaming user. This is
the number of sessions initiated by outgoing
INVITEs from S8HR roaming user. The
session setups may have succeeded or
failed. Not applicable to CS network since
calls terminating on CS network are not
supported. REGISTERs, MESSAGEs,
SUBSCRIBEs, and so on, are not counted
as session setup attempts.
Counter on SBG node.
sbgSipSuccessIncSessions Number of successfully answered incoming
INVITE sessions. (picking up the call). This
counter belongs to measurement family 'SIP
session statistics'.
Counter on SBG node.
sbgSipSuccessOutSessions Number of successfully answered outgoing
INVITE sessions. (picking up the call). This
counter belongs to measurement family 'SIP
session statistics'.
Counter on SBG node.
sbgSipTotalIncFailureResponses Total number of incoming SIP failure
responses, except '401 Unauthorized' and
'407 Proxy authentication required'. That is
4xx, 5xx, 6xx, except 401 and 407.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 186 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipTotalOutFailureResponses Total number of outgoing SIP failure

responses, except '401 Unauthorized' and
'407 Proxy authentication required'. That is
4xx, 5xx, 6xx, except 401 and 407. This
counter belongs to measurement family 'SIP
transaction statistics'.
Counter on SBG node.
sbgSipNetTotBgfUnsuccReselection Number of session setup attempts rejected
by the SGC due to unavailability of BGF
resources. The reason for unavailability can
be that all BGFs serving this network are in
one of the following states: 1) are out of
resources, 2) are overloaded or 3) have
H.248 links to SGC down.
Counter on SBG node.
sbgSipRejectedMaxSessions Number of incoming and outgoing INVITE
sessions rejected by SBG due to the
configured maximum number of concurrent
INVITE sessions that are allowed for the
associated Signaling Network Connection
has been reached.

sbgSipRejSessionReleaseOfSigBeare The number of calls rejected by SGC due to

r release of signaling bearer which are
triggered by the special RAR/ASR message
from PCRF to SGC. This counter counts for
both incoming and outgoing direction. When
the RAR message contains an AVP
Specific-Action with value
'INDICATION_OF_RELEASE_OF_BEARE
R', or ASR contains Abort-Cause AVP with
value 'BEARER_RELEASED', SGC will
reject the call by sending a SIP message
with rejection code 503 to core side.

sbgSipRejectedIncSessions403 Number of incoming INVITE sessions

rejected by the SGC with code 403
Forbidden. Note: This counter does also
count the rejections which are forwarded by
the SGC.

sbgSipRejectedIncSessions486 Number of incoming INVITE sessions

rejected by the SGC with code 486 Busy
Here. Note: This counter does also count
the rejections which are forwarded by the
SGC.

sbgSipRejectedOutSessions403 Number of outgoing INVITE sessions

rejected by a neighboring node or UE with
code 403 Forbidden. Not applicable to CS
network since calls terminating on CS
network are not supported.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 187 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipRejectedOutSessions486 Number of outgoing INVITE sessions

rejected by a neighboring node or UE with
code 486 Busy Here. Not applicable to CS
network since calls terminating on CS
network are not supported.
Counter on SBG node.
sbgSipRejectedIncSessions603 Number of outgoing INVITE sessions
rejected by a neighboring node or UE with
code 603 Decline. Not applicable to CS
network since calls terminating on CS
network are not supported.
Counter on SBG node.
sbgSipThrottlingRejectedCnt The number of SIP requests towards the
core network that is rejected by SGC due to
the SIP throttling function (at IMS core
overload). The counter is only used for a
core network SIP network connection.
The total number of rejected SIP requests
because of window-based throttling, fixed
rate-based throttling and loss-based
throttling on the associated signaling
network connection. A SIP request is
rejected when a 500 error response is
returned because of core network throttling.
Counter on SBG node.
sbgSipSgcReleasesSessionTimer Number of SGC initiated releases due to
either:
- Session timer expiry or
- Maximum non-supervised session duration
timer expiry
The counter will only be stepped for the
network from which the SIP session was
originally established.
Counter on SBG node.
sbgSipReleasesSessionTimer Number of SBG initiated releases due to
either
- Session timer expiry or
- Maximum non-supervised session duration
timer expiry.
The counter will only be stepped for the
network from which the SIP session was
originally established.
Counter on SBGv node.
sbgSipSgcDialogReleasesRequestTi The number of SGC initiated releases of
meout SIP dialogs (INVITE,SUBSCRIBE, REFER),
due to either transaction timeout or to
reception of a 408 Request Timeout
response code for an outgoing mid-dialog
request.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 188 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipDialogReleasesRequestTimeou The number of SBG initiated releases of

t SIP dialogs (INVITE,SUBSCRIBE, REFER),
due to either transaction timeout or to
reception of a 408 Request Timeout
response code for an outgoing mid-dialog
request.
Counter on SBGv node.
sbgSipNetTotBgfReselection Number of BGF (including MP) reselections
performed by SGC. The reason for BGF
reselection can be that part of the BGFs
serving this network do not have resources
or are overloaded. Note that the BGF
reselection is not performed for the access
to CS transferred sessions.
Counter on SBG node.
sbgSipSrcSDPValidationFailed Number of SIP requests rejected due to a
failure to validate the SDP IP addresses
against the SIP source address, when SDP
address validation is configured. The
counter is not applicable for incoming
access transfer INVITEs from CS network.
Counter on SBG node.
sbgSipSrcValidationFailed Number of SIP requests rejected by SBG
due to a failure to validate the SDP IP
addresses against the SIP source address,
when SDP address validation is configured.
Counter on SBGv node.
sbgSipRelSessionReleaseOfSigBeare The number of calls released by SGC due
r to release of signaling bearer which are
triggered by thespecial RAR/ASR message
from PCRF to SGC. This counter counts for
both incoming and outgoing direction. When
the RAR message contains an AVP
Specific-Action with value
'INDICATION_OF_RELEASE_OF_BEARE
R', or ASR contains Abort-Cause AVP with
value 'BEARER_RELEASED', SGC will
release the call by sending 'BYE' to core
side.
Counter on SBG node.
sbgSipSgcReleasesMediaStop Number of SGC initiated releases due to
media stop notifications from the MP or
external BGF. The counter will only be
stepped for the network from which the SIP
session was originally established.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 189 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipSgcInitiatedSessionRelease Number of active INVITE sessions (ACK for

200 OK to INVITE has been received) for
which a release has been initiated by the
SGC by sending a BYE. Examples of cases
where the counter is stepped are:
-Session timer expiry detected by SBG
-Media stop notification from BGF received
-Bearer release notification received from
Rx interface
-Mid-dialog transaction timeout
When SBG receives a signaling bearer
release on Rx for an active session the
sbgSipSgcInitiatedSessionRelease counter
will be stepped on both access and core
network side, but BYE is sent only to the
core network.
Counter on SBG node.

sbgSipOutNwRejSessions The number of access to CS transfer

attempts (initial INVITEs) that were rejected
either by the SGC throttling function in the
outgoing network (only if core network is
outgoing network) or by a neighboring node
or UE. The rejects due to timeout in the
outgoing network are not counted. This
counter is only used for CS network SIP
network connection.
Counter on SBG node.
sbgSipIncFallbackSessionAttempts The number of incoming fallback attempts
(Re-INVITEs and UPDATEs) to this access
network, during or after access transfer to
CS. Fallback means that an access transfer
to the CS network is interrupted and that the
associated call is redirected back to the
access network where it initially started. The
fallback attempt may have succeeded or
failed. This counter is only used for access
network SIP network connection.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 190 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipNetIncSessionSetupTime Increased with the time in milliseconds
between the received initial INVITE and the
first sent response with the following
success criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured. The mean
response time can be calculated by dividing
this counter with
sbgSipNetIncSessionSetupUserSuccess.
Counter on SBG node.
sbgSipNetIncSessionSetupUserSucce Number of incoming INVITE sessions
ss responded to with the following success
criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured.
.
Counter on SBG node.
sbgSipNetOutSessionSetupTime Increased with the time in milliseconds
between the sent initial INVITE and the first
received response with the following
success criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured. The mean
response time can be calculated by dividing
this counter with
sbgSipNetOutSessionSetupUserSuccess.
Not applicable to CS network since calls
terminating on CS network are not
supported.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 191 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipNetOutSessionSetupUserSucc Number of outgoing INVITE sessions
ess responded to with the following success
criteria:
1. The first time at which the SBG opens the
BGF pin hole (for allowing authorized early
media) and receives a successful H.248
Modify reply.
2. SIP 180 RINGING message.
3. Final “SIP 200 OK (INVITE)” message –
in cases when the terminating user has
automatic answering configured.
Counter on SBG node.
sbgSipTotalIncSipSubscribeRequests Total number of incoming SIP SUBSCRIBE
requests.
Counter on SBG node.
sbgSipRejectedIncSubscribeSessions The total number of incoming SUBSCRIBE
session setup attempts (SUBSCRIBEs) that
have been rejected by the SGC. Session
setup attempts that were rejected by
network nodes or SIP UEs at the other side
of the SGC (provided that the incoming
request was forwarded) are not counted.
Counter on SBG node.
sbgSipTotalOutSipSubscribeRequests Total number of outgoing SIP SUBSCRIBE
requests.
Counter on SBG node.
sbgSipRejectedOutSubscribeSessions The total number of outgoing SUBSCRIBE
session setup attempts (SUBSCRIBEs) that
have been rejected either by the SGC
throttling function (rejects are only counted
to the core network) or by a neighboring
node or UE. Responses with cause 401 or
407 are not counted as rejects.
Counter on SBG node.
sbgSipTotalIncMessage Number of incoming MESSAGE requests.
Counter on SBG node.
sbgSipTotalOutMessage Number of outgoing MESSAGE requests.
Counter on SBG node.
sbgSipSuccessIncMessage Number of successful incoming MESSAGE
requests.
Counter on SBG node.
sbgSipSuccessOutMessage Number of successful outgoing MESSAGE
requests.
Counter on SBG node.
sbgSipSgcDialogReleasesRequestTi The number of SGC initiated releases of
meout SIP dialogs (INVITE,SUBSCRIBE, REFER),
due to either transaction timeout or to
reception of a 408 Request Timeout
response code for an outgoing mid-dialog
request.
Counter on SBG node.
 Ericsson Internal
OPERAT. GUIDELINES 192 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgSipOutgoingTransactionTimeouts The number of sent SIP request which
results in transaction timeout. For an access
network, when the "Deregisterunreachable
UE" is set to "always", this counter will also
count the number of de-registered users
due to transaction timeout.
Counter on SBG node.
sbgExtBgfCallsActiveGauge The total number of contexts currently
established using the associated H.248
control link.
Counter on SBG node.
sbgExtBgfTotCallsCnt The total number of context setup attempts
on the associated H.248 control link.
Counter on SBG node.
sbgExtBgfTotCallsFailedCnt The total number of failed context setup
attempts on the associated H.248 control
link.
Counter on SBG node.
ipStatsIpIfRxPackets The number of received accepted media
packets. All corresponding counters on all
IP interfaces in the network contribute to the
sum presented by this counter.
Counter on SBG node.
ipStatsIpIfTxPackets The number of packets to be sent. Some of
these packets might be discarded due to
traffic management. All corresponding
counters on all IP interfaces in the network
contribute to the sum presented by this
counter.
Counter on SBG node.
sbgSgcPktsLostRatioGauge Ratio of Sgc network connections lost RTP
packets. The number is 10000*ratio. Only
applicable for RTP streams.
Counter on SBG node.
sbgPktsLostRatioGauge The ratio of the number of lost packets to
the total number of received packets on the
network connection since the last SBG
restart. It is calculated only from monitored
RTP streams. The presented value is the
ratio value multiplied by 10000.
Counter on SBGv node.
sbgSgcPktsOutofSeqRatioGauge Ratio of Sgc network connections RTP
packets out of sequence. The number is
10000*ratio. Only applicable for RTP
streams.
Counter on SBG node.
sbgPktsOutofSeqRatioGauge The ratio of the number of packets that
arrived out of sequence to the total number
of received packets on the network
connection since the last SBG restart. It is
calculated only from monitored RTP
streams. The presented value is the ratio
value multiplied by 10000.
Counter on SBGv node.
 Ericsson Internal
OPERAT. GUIDELINES 193 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgExtBgfHangingTerminationCnt The total number of timer a hanging
termination event has been received by the
SBG from an Ext Bgf.
Counter on SBG node.
sbgExtBgfTotCallsAbnTerminatedCnt The total number of contexts in 'active' state
that have been abnormally released by the
SBG due to an indication (Notify or
ServiceChange) from the BGF using the
associated H.248 control link.
Counter on SBG node.
sbgExtH248TotInvalidAddressCnt The total number of H.248 reply messages
indicating that an invalid identifier was used
in the request. This counter is incremented
if any of the following error codes are
received by the SGC: 411 - The transaction
refers to an unknown ContextID 430 -
Unknown TerminationID 435 -
TerminationID not in specified context.
Counter on SBG node.
sbgExtH248TotNoResourcesCnt The total number of H.248 reply messages
indicating that no resources were available.
This counter is incremented if any of the
following error codes are received by the
SGC: 510 - Insufficient resources 526 -
Insufficient bandwidth 412 - Out of
ContextIds 432 - Out of TerminationIds.
Counter on SBG node.
sbgExtH248TotOtherErrorCnt The total number of other errors on the
associated H.248 control link not included in
other counters.
Counter on SBG node.
sbgExtH248TotProtocolErrorCnt The total number of H.248 reply messages
indicating syntax or protocol error. This
counter is incremented if any of the
following error codes are received by the
SGC: 400 - Syntax error in message 402 -
Unauthorized 406 - Version not supported
410 - Incorrect identifier 431 - No
TerminationID matched a wildcard 440 -
Unsupported or unknown package 441 -
Missing Remote or Local descriptor 443 -
Unsupported or unknown command 444 -
Unsupported or unknown descriptor 445 -
Unsupported or unknown property 447 -
Descriptor not legal in this command 449 -
Unsupported or unknown parameter or
property value 450 - No such property in
this package 501 - Not implemented 517 -
Unsupported or invalid mode 542 -
Command allowed on this termination.
Counter on SBG node.
sbgExtH248TotServerErrorCnt The total number of H.248 reply messages
indicating server or equipment error. This
counter is incremented if any of the
following error codes are received by the
SGC: 500 - Internal software failure in the
BGF 506 - Number of transaction pendings
exceeded 530 - Temporary network failure.
 Ericsson Internal
OPERAT. GUIDELINES 194 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23] and
SBGv Managed Object Model (MOM), 155 54-LZN7650172-V1, ref. [24].

7.3 IMS MRS

Performance indicators at MRS node supporting the MRS-MGW and MRS-

MRFP logical nodes are described in User Guide for Performance
Measurements MRS, 17/1553-AXM 101 01/11-V2, ref. [27] and (vMTAS)
Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1, ref. [26]. The
document defines R-KPI:s for Accessability, Retainability, Integrity and Traffic
and Load. The performance indicators supporting the R-KPI:s are also
defined in the document.

8 Enriched Messaging (vEMe)

EMe Enriched Messaging offers Rich Communication Services (RCS) users
new and evolved messaging services such as instant messaging, group
messaging, file transfer and multi-device support.

8.1 IMS EMe SMSoIP Transport Interworking Accessibility

8.1.1 Defintion

IMS EMe SMSoIP Transport Interworking Accessibility is defined as the

probability of successfully transport SMSoIP encapsulated Short Messages
over the IMS domain.

8.1.2 Formula

Transport interworking for IMS UE SMSoIP send procedure for EMe IP-SM-
GW and SMS-IWMsc/Service Center

Equation 279. IMS vEMe Originating RP Data Resp Success

Ratio

IMSvEMeOrigRPData Re spSuccRatio[%] = 100 *

emeIwSipOrigRpAckReqSent
emeIwSipOrigRpDataReqReceived

Equation 280. IMS vEMe Terminating RP Data Resp Success

Ratio

IMSvEMeTermRPData Re spSuccRatio[%] = 100 *

emeIwSipTermRpAckReqReceived
emeIwSipTermRpDataReqSent

Equation 281. IMS vEMe MAP MO-FSM Out Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 195 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSvEMeMOFSMOutSuccRatio[%] = 100 *
emeIwMapMoFsmReturnResultReceived
emeIwMapMoFsmInvokeSent

Equation 282. IMS vEMe MAP MT-FSM Rec Success Ratio

IMSvEMeMTFSM Re cSuccRatio[%] = 100 *

emeIwMapMtFsmReturnResultSent
emeIwMapMtFsmInvokeReceived

Equation 283. IMS vEMe MAP MT-FSM Sent (Fallback to CS)

Success Ratio

IMSvEMeMTFSMSentFallbackSuccRatio[%] = 100 *
emeIwMapMtFsmReturnResultReceived
emeIwMapMtFsmInvokeSent

Counter Name Definition

emeIwSipOrigRpAckReqSent Number of SMS RP ACK sent to SMSoIP

client over SIP
Counter on vEMe node.
emeIwSipOrigRpDataReqReceived Number of SMS RP DATA received from
SMSoIP client over SIP
Counter on vEMe node.
emeIwSipTermRpAckReqReceived Number of SMS RP ACK received from
SMSoIP client over SIP.
Counter on vEMe node.
emeIwSipTermRpDataReqSent Number of SMS RP DATA sent to SMSoIP
client over SIP.
Counter on vEMe node.
emeIwMapMoFsmReturnResultReceiv Number of Return Result received from
ed SMS-C, positive Response for MAP MO-
FSM request.
Counter on vEMe node.
emeIwMapMoFsmInvokeSent The number of SIP MESSAGE containing
RP-DATA is sent.
Counter on vEMe node.
emeIwMapMtFsmReturnResultSent The number of SIP OK response for SIP
MESSAGE containing RP-ACK is sent.
Counter on vEMe node.
emeIwMapMtFsmInvokeReceived Number of MAP MO-FSM request sent to
SMS-C.
Counter on vEMe node.
 Ericsson Internal
OPERAT. GUIDELINES 196 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

emeIwMapMtFsmReturnResultReceiv Number of Return Result received from

ed MSC, positive Response for MAP MT-FSM
request.
Counter on vEMe node.
emeIwMapMtFsmInvokeSent Number of MAP MT-FSM request sent to
MSC.
Counter on vEMe node.

Reference: Reference:vEMe Interwork Performance Indicators, 1/154 43-AVA

901 31/, ref. [30].

8.1.3 Traffic Indicators

Equation 284. IMS vEMe Originating RP Data Reqs [per second]

IMSvEMeOrigRPData Re qs =
emeIwSipOrigRpDataReqReceived
T
Equation 285. IMS vEMe Terminating RP Data Sent [per
second]

IMSvEMeTermRPDataSent =
emeIwSipTermRpDataReqSent
T
Equation 286. IMS vEMe MAP MO-FSM Out [per second]

IMSvEMeMOMAPFSMOut =
emeIwMapMoFsmInvokeSent
T
Equation 287. IMS vEMe MAP MT-FSM Rec [per second]

IMSvEMeMTMAPFSM Re c =
emeIwMapMtFsmInvokeReceived
T
Equation 288. IMS vEMe MAP MT-FSM Sent (Fallback to CS)
[per second]

IMSvEMeMTMAPFSMSentFallback =
emeIwMapMtFsmInvokeSent
T
 Ericsson Internal
OPERAT. GUIDELINES 197 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

emeIwSipOrigRpDataReqReceived Number of SMS RP DATA received from

SMSoIP client over SIP
Counter on vEMe node.
emeIwSipTermRpDataReqSent Number of SMS RP DATA sent to SMSoIP
client over SIP.
Counter on vEMe node.
emeIwMapMoFsmInvokeSent The number of SIP MESSAGE containing
RP-DATA is sent.
Counter on vEMe node.
emeIwMapMtFsmInvokeReceived Number of MAP MO-FSM request sent to
SMS-C.
Counter on vEMe node.
emeIwMapMtFsmInvokeSent Number of MAP MT-FSM request sent to
MSC.
Counter on vEMe node.

Reference: Reference:vEMe Interwork Performance Indicators, 1/154 43-AVA

901 31/, ref. [30].

9 IMS SIP Signaling

SIP being the signalling protocol in IMS is the single most important protocol.
The IMS Signalling formulas are supporting quality supervision of IMS
signalling.

9.1 IMS CSCF SIP Accessibility

9.1.1 Definition

IMS CSCF SIP Accessibility is defined as the probability of being able to

successfully handle SIP requests in the IMS network. The IMS CSCF SIP
Accessibility is evaluated with the ratio between successful and failure SIP
response codes from SIP requests. These performance indicators are valid
for CSCF node. Note: the formulas will display too low accessibility values
when the HTTP Digest procedure is used. The HTTP Digest procedure
generates 401, Unauthorized and 407, Proxy authenticatied required which
are counted as errors in the ReqFail counters, which they are not.

9.1.2 Formula

Equation 289. IMS Client SIP Response Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 198 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSClientSip Re sponseSuccessRatio[%] = 100 *

sipStatsSuccessClassIns
(sipStatsSuccessClassIns + sipStatsReqFailClassIns +
sipStatsServerFailClassIns + sipStatsGlobalFailClassIns)

Equation 290. IMS Server SIP Response Success Ratio

IMSServerSip Re sponseSuccessRatio[%] = 100 *

sipStatsSuccessClassOuts
(sipStatsSuccessClassOuts + sipStatsReqFailClassOuts +
sipStatsServerFailClassOuts + sipStatsGlobalFailClassOuts)

Note: These formulas may be presented per source IP address for incoming
traffic and destination IP address for outgoing traffic. The direction
presentation is dependant on node configuration; the default configuration
contains no direction information.

SIP MESSAGE formulas:

Equation 291. IMS CSCF Orig MESSAGE Success Ratio

IMSCSCFOrigMessageSuccessRatio[%] = 100 *
scscfOriginatingMessageSuccess
(scscfOriginatingMessageSuccess +
scscfOriginatingMessageFailed)

Equation 292. IMS CSCF Term MESSAGE Success Ratio

IMSCSCFOrigMessageSuccessRatio[%] = 100 *
scscfTerminatingMessageSuccess
(scscfTerminatingMessageSuccess +
scscfTerminatingMessageFailed)

Counter Name Definition

The total number of 4xx class SIP
sipStatsReqFailClassIns(key: IP responses received. This counter is keyed
Address)
with the IP address of the application it is
received from.
Counter on the CSCF node.
The total number of 5xx class SIP
sipStatsServerFailClassIns(key: IP responses received. This counter is keyed
Address)
with the IP address of the application it is
received from.
Counter on the CSCF node.
 Ericsson Internal
OPERAT. GUIDELINES 199 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

The total number of 6xx class SIP
sipStatsGlobalFailClassIns(key: IP responses received. This counter is keyed
Address)
with the IP address of the application it is
received from.
Counter on the CSCF node.
The total number of 2xx class SIP
sipStatsSuccessClassIns(key: IP responses received. This counter is keyed
Address)
with the IP address of the application it is
received from.
Counter on the CSCF node.
The total number of 4xx class SIP
sipStatsReqFailClassOuts(key: IP responses sent (originated and relayed).
Address)
This counter is keyed with
the IP address of the application the SIP
message is sent to.
Counter on the CSCF node.
The total number of 5xx class SIP
sipStatsServerFailClassOuts(key: IP responses sent (originated and relayed).
Address) This counter is keyed with
the IP address of the application the SIP
message is sent to.
Counter on the CSCF node.
The total number of 6xx class SIP
sipStatsGlobalFailClassOuts(key: IP responses sent (originated and relayed).
Address) This counter is keyed with
the IP address of the application the SIP
message is sent to.
Counter on the CSCF node.
The total number of 2xx class SIP
sipStatsSuccessClassOuts(key: IP responses sent (originated and
Address) relayed).This counter is keyed with the IP
address of the application the SIP message
is sent to.
Counter on the CSCF node.
Number of 2xx responses to SIP MESSAGE
scscfOriginatingMessageSuccess transmitted by S-CSCF on originating side.

Number of times non-successful responses

scscfOriginatingMessageFailed to SIP MESSAGE request are transmitted
by S-CSCF on originating side.

Number of 2xx responses to SIP MESSAGE

scscfTerminatingMessageSuccess transmitted by S-CSCF on terminating side
Number of times non-successful responses
scscfTerminatingMessageFailed to SIP MESSAGE request are transmitted
by S-CSCF on terminating side.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

9.2 IMS MGC SIP Signaling Accessibility

Refer to chapter 9.1.1, MGC SIP Session Set-up Accessibility with the
following equation:

• Equation 195, IMS MGC SIP Incoming Sessions Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 200 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

• Equation 196, IMS MGC SIP Outgoing Sessions Success Ratio

9.3 IMS SBG SIP Signaling Accessibility

Equation 293. IMS SBG SIP Response Success Ratio

IMSSBGSIP Re spSuccRatio[%] = 100 *

(sbgSipTotalOutSipResponses - sbgSipTotalOutProvisionalResponses -
sbgSipTotalOutFailureResponses)
(sbgSipTotalOutSipResponses - sbgSipTotalOutProvisionalResponses)

Note: This formula covers the incoming and outgoing responses, since the
counters covers responses generated at the SBG at the remote network. This
formula covers the SBG SIP signalling accessibility through the responses
rather than the requests. The ‘number of SIP requests’ measurement display
slightly higher numbers than SIP responses, since not all requests have
responses, e.g. ACK.
Counter Name Definition
sbgSipTotalOutSipResponses Total number of outgoing responses.
Counter on SBG node.
sbgSipTotalOutFailureResponses Total number of outgoing SIP failure
responses: 4xx, 5xx, 6xx.
Counter on SBG node.
sbgSipTotalOutProvisionalResponses Total number of outgoing SIP provisional
responses: 1xx.
Counter on SBG node.

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23].

9.4 IMS JavaSIP Accessibility

Equation 294. IMS JavaSIP Register Success Ratio

IMSJavaSip Re gisterSuccessRatio[%] = 100 *

(Received2xxRegisterResponses
ReceivedRegisterRequests

Equation 295. IMS JavaSIP Message Success Ratio

IMSJavaSipMessageSuccessRatio[%] = 100 *
Received2xxMessageResponses
ReceivedMessageRequests

Equation 296. IMS JavaSIP Invite Success Ratio

 Ericsson Internal
OPERAT. GUIDELINES 201 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSJavaSipInviteSuccessRatio[%] = 100 *
Received2xxInviteResponses
ReceivedInviteRequests

Equation 297. IMS JavaSIP Bye Success Ratio

IMSJavaSipByeSuccessRatio[%] = 100 *
Received2xxByeResponses
ReceivedByeRequests

Counter Name Definition

Incremented when a 2xx for register is
Received2xxRegisterResponses received.
Counter on the vEMe or vWCG node.
Total number of register requests received,
ReceivedRegisterRequests including retransmissions.
Counter on the vEMe or vWCG node.
Incremented when a 2xx for message is
Received2xxMessageResponses received
Counter on the vEMe or vWCG node.
Total number of message requests
ReceivedMessageRequests received, including retransmissions.
Counter on the vEMe or vWCG node.
Incremented when a 2xx for invite is
Received2xxInviteResponses received
Counter on the vEMe or vWCG node.
Total number of invite requests received,
ReceivedInviteRequests including retransmissions.
Counter on the vEMe or vWCG node.
Incremented when a 2xx for bye is received
Received2xxByeResponses Counter on the vEMe or vWCG node.
Total number of bye requests received,
ReceivedByeRequests including retransmissions.
Counter on the vEMe or vWCG node.
 Ericsson Internal
OPERAT. GUIDELINES 202 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

10 IMS Overload and Load Regulation

10.1 IMS CSCF SIP Load Regulation Rejection Ratio

10.1.1 Definition

IMS CSCF SIP Load Regulation Rejection Ratio is defined as the probability
of having a Load Regulation rejections when initiating a SIP session into the
IMS CSCF node. This performance indicator is valid for CSCF node. This
performance indicator indicates Load Regulation rejections are based on
TSP/vDicos system resources like CPU, Memory and TIPC. Load Regulation
rejections are based on different priorty levels for normal, priority and
emergency calls. Most but not all of SIP request methods are part of the load
regulation. The overload rejections on UDP and TCP protocol level are not
part of this formula although measurement names indicates this. Note that
rejections caused by TSP/vDicos overload protection are not part of the
formula.

Equation 298. IMS CSCF SIP Inbound Load Regulation

Rejection Ratio

IMSSipLoad Re gInRatio[%] = 100 *

sipStatsUdpCongestions + sipStatsTcpCongestions
( )
sipSummaryInRequests

Counter Name Definition

The total number of SIP messages,
sipStatsUdpCongestions including retransmissions, discarded due to
load regulation decisions taken in the SIP
UDP transport process.
Counter on CSCF node.
The total number of SIP messages,
sipStatsTcpCongestions including retransmissions, discarded due to
load regulation decisions taken in the SIP
TCP transport process.
Counter on CSCF node.
The total number of SIP requests received.
sipSummaryInRequests Counter on CSCF node.

Reference: CSCF Performance Management Parameters, 1/1551-AVA 901

19/6, ref. [13] and (vCSCF) Managed Object Model (MOM), 155 54-LZN 765
0209-V1, ref. [14].

10.1.2 Comment

There is no performance measurement for outbound congestions.

 Ericsson Internal
OPERAT. GUIDELINES 203 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

10.2 IMS JavaSIP Overload Rejection

10.2.1 Definition

IMS JavaSIP Overload Rejection Ratio is defined as the probability of having

an overload condition when initiating a SIP session into the IMS vEMe and
vWCG nodes. This performance indicator indicates congestion based on the
system overload conditions CPU and memory.

10.2.2 Formula

Equation 299. IMS JavaSIP Overload Rejection Ratio

IMSJavaSipOverloadRatio[%] = 100 *
OverloadRejectedSipRequests
(OverloadRejectedSipRequests + ReceivedSipRequests)

Counter Name Definition

The number of SIP requests rejected due to
OverloadRejectedSipRequests overload conditions.
Counter on vEMe and vWCG nodes.
The number of SIP requests received,
ReceivedSipRequests including retransmissions.
Counter on vEMe and vWCG nodes.

Reference: JavaSIP Performance Measurements, ref. [18].

10.3 MGC Overload Rejection

10.3.1 Definition

IMS MGC Overload Rejection Ratio is defined as the probability of having an

overload condition when initiating a SIP Call in the MGW node. This
performance indicator indicates congestion based on the system overload
conditions CPU and memory.

10.3.2 Formula

Equation 300. IMS MGC SIP Call Congestion Ratio

IMSMGCSIPCallCongestionRatio[%] = 100 *
mgcPmSipTotServerCongestion
I
mgcPmSipTotIncomingSessions
 Ericsson Internal
OPERAT. GUIDELINES 204 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

mgcPmSipTotIncomingSessions Total number of incoming SIP sessions,
including failed session setup attempts
received by the MGCF. This counter is
incremented whenever SIP INVITE
message is received for a new session, i.e.
the possible re-INVITEs received during an
ongoing session do not increment this
counter.
Counter on MGC node.
mgcPmSipTotServerCongestion Total number of session establishment
request failures due to server congestion.
The counter is used only for incoming
sessions. It is incremented when a 503
response is sent.
Counter on MGC node.

Reference: MGC System Statistics, 9/154 43-CNA 113 215/1, ref. [21].

10.4 SBG Overload Rejection

10.4.1 Definition

IMS SBG Overload Rejection Ratio is defined as the probability of having an

overload condition when initiating a SIP Session in the SBG node. This
performance indicator indicates congestion based on the system overload
conditions CPU and memory.

10.4.2 Formula

Equation 301. IMS SBG SIP Overload Rejection Ratio

IMSSBGSIPOverload Re jectionRatio[%] = 100 *

sbgSipUnsuccOverloadCnt
sbgSipTotalIncSessSetups

Equation 302. IMS SBG SIP Core Overload (throttling) Rejection

Ratio

IMSSBGSIPCoreOverload Re jectionRatio[%] = 100 *

sbgSipThrottlingRejectedCnt
sbgSipTotalOutSessSetups

The number of SIP requests towards the core network that is rejected by SGC
due to the SIP throttling function (at IMS core overload). The formula is only
used for a core network SIP network connection

Equation 303. IMS SBG BGF Overload Rejection Ratio

 Ericsson Internal
OPERAT. GUIDELINES 205 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSBGBGFOverload Re jectionRatio[%] = 100 *

sbgSipNetTotBgfUnsuccReselection
sbgSipTotalIncSessSetups

Number of session setup attempts rejected by the SGC due to unavailability

of BGF resources.

Counter Name Definition

sbgSipTotalIncSessSetups Total incoming session setup attempts since

system started. This is the number of
sessions initiated by incoming INVITEs. The
session setups may have succeeded or
failed.
Counter on SBG node.
sbgSipUnsuccOverloadCnt Rejected sessions due to temporary SGC
overload.
Counter on SBG node.
sbgSipThrottlingRejectedCnt The number of SIP requests towards the
core network that is rejected by SGC due to
the SIP throttling function (at IMS core
overload). The counter is only used for a
core network SIP network connection.
Counter on SBG node.
sbgSipTotalOutSessSetups The number of outgoing session setup
attempts. This is the number of sessions
initiated by outgoing INVITEs. The session
setups may have succeeded or failed.
Counter on SBG node.
sbgSipNetTotBgfUnsuccReselection Number of session setup attempts rejected
by the SGC due to unavailability of BGF
resources. The reason for unavailability can
be that all BGFs serving this network are in
one of the following states: 1) are out of
resources, 2) are overloaded or 3) have
H.248 links to SGC down.
Counter on SBG node.

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23].

10.5 MTAS

10.5.1 MTAS MRFC Overload Rejection

10.5.2 Definition

IMS MTAS MRFC Overload Rejection Ratio is defined as the probability of

having an overload condition when sending a MRFC request. This
performance indicator indicates congestion based on the MRFC buffer
towards a particular MRFP.
 Ericsson Internal
OPERAT. GUIDELINES 206 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 304. IMS MTAS MRFC Overload Rejection Ratio

IMSMTASMRFCOverload Re jectionRatio[%] = 100 *

MtasMrfcOverloadThresholdReached
(MtasMrfcInitiatedContextOk + MtasMrfcInitiatedContextNOkI +
MtasMrfcInitiatedContextNOkE + MtasMrfcContextTerminiatedOk)

Counter Name Definition

MtasMrfcOverloadThresholdReached The number of MRFC requests rejected due

to the overload.
Counter on MTAS node.
MtasMrfcInitiatedContextOk The number of successfully initiated
contexts.
Counter on MTAS node.
MtasMrfcInitiatedContextNOkI The number of unsuccessfully initiated
contexts caused by the MTAS due to
internal reasons.
Counter on MTAS node.
MtasMrfcInitiatedContextNOkE The number of unsuccessfully initiated
contexts caused by the MTAS due to
external reasons.
Counter on MTAS node.
MtasMrfcContextTerminiatedOk The number of successfully terminated
media conversion or handling
acknowledgements from the MRFP ordered
by the MTAS.

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

10.5.3 MTAS SIP Overload Rejections

10.5.4 Definition

IMS MTAS SIP Overload Rejection Ratios are defined as the probability of
having an overload condition when receiving a SIP request. This performance
indicator indicates congestion based on overload in MTAS, either CPU or
memory utilization overload. Several overload rejections exist, origination or
terminating half calls.

Note that all measurements used are keyed on SIP method, so the formulas
given may be used per method or for a sum of all methods.

Equation 305. IMS MTAS SIP PSI Overload Rejection Ratio

 Ericsson Internal
OPERAT. GUIDELINES 207 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMTASSIPPSIOverload Re jectionRatio[%] = 100 *

MtasSipFuncPsiOverloadRej
(MtasSipFuncPsiOverloadRej + MtasFuncPsiOk)

Equation 306. IMS MTAS SIP Orig Requests Overload Rejection

Ratio

IMSMTASSIPOrg Re qOverload Re jectionRatio[%] = 100 *

(MtasSipOrigRequestOverloadRej + MtasSipOrigUnregRequestOverloadRej)
(MtasSipOrigRequestIn + MtasSipOrigUnregRequestIn)

Equation 307. IMS MTAS SIP Term Requests Overload

Rejection Ratio

IMSMTASSIPTerm Re qOverload Re jectionRatio[%] = 100 *

(MtasSipTermRequestOverloadRej + MtasSipTermUnregRequestOverloadRej)
(MtasSipTermRequestIn + MtasSipTermUnregRequestIn)

Equation 308. IMS MTAS SIP Presence Requests Overload

Rejection Ratio

IMSMTASSIP Pr esenceOverload Re jectionRatio[%] = 100 *

MtasSipPresenceRequestOverloadRej
MtasSipPresenceRequest

Equation 309. IMS SCC AS SIP Orig Requests Overload

Rejection Ratio

IMSSCCASSIPOrg Re qOverload Re jectionRatio[%] = 100 *

MtasSipSccOrigRequestOverloadRej
MtasSipSccOrigRequestIn

Equation 310. IMS SCC AS SIP Term Requests Overload

Rejection Ratio

IMSSCCASASSIPTerm Re qOverload Re jectionRatio[%] = 100 *

MtasSipSccTermRequestOverloadRej
MtasSipSccTermRequestIn

Equation 311. IMS MTAS Priority Call Overload Rejection Ratio

 Ericsson Internal
OPERAT. GUIDELINES 208 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSMTAS Pr ioCallOverload Re jectionRatio[%] = 100 *

MtasPriorityCallWpsRejected( key : wps)
MtasPriorityCallWpsRequested( key : wps)

Counter Name Definition

MtasSipFuncPsiOverloadRej The total number of received SIP request

message destined to a Public Service
Identifier (PSI) is rejected due to overload in
MTAS.
Counter on MTAS node.
MtasFuncPsiOk The number of received SIP messages
destined to a supported Public Service
Identifier (PSI).
Counter on MTAS node.
MtasSipOrigRequestOverloadRej The total number of SIP request rejected
due to overload in originating MTAS. The
counter is keyed on request method.
Counter on MTAS node.
MtasSipOrigRequestIn The total number of SIP requests received
in originating MTAS, including
retransmissions. The counter is keyed on
request method
Counter on MTAS node.
MtasSipTermRequestOverloadRej The total number of SIP request rejected
due to overload in Terminating MTAS. The
counter is keyed on request method.
Counter on MTAS node.
MtasSipTermRequestIn The total number of SIP requests received
in Terminating MTAS, including
retransmissions. The counter is keyed on
request method
Counter on MTAS node.
MtasSipTermUnregRequestOverload The total number of SIP request rejected
Rej from an unregistered Public User Identity
(PUI) due to overload in terminating MTAS.
The counter is keyed on request method.
Counter on MTAS node.
MtasSipTermUnregRequestIn The total number of SIP requests received
in terminating MTAS to an unregistered
Public User Identity (PUI). The counter is
keyed on request method.
Counter on MTAS node.
MtasSipPresenceRequestOverloadRej The total number of received SIP presence
request rejected due to overload in MTAS.
The counter is keyed on request method.
Counter on MTAS node.
MtasSipPresenceRequest The counter is incremented when receiving
SIP Presence requests in MTAS. The
counter is keyed on the SIP method.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 209 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

MtasSipSccOrigRequestOverloadRej This counter is the total number of SIP

requests rejected from an unregistered
IMPU due to overload in originating SCC
AS. The counter is keyed on request
method.
Counter on MTAS node.
MtasSipSccOrigRequestIn This counter is the total number of SIP
requests received in originating SCC AS,
including retransmissions. The counter is
keyed on request method.
Counter on MTAS node.
MtasSipSccTermRequestOverloadRej This counter is the total number of SIP
requests rejected from an unregistered
IMPU due to overload in terminating SCC
AS. The counter is keyed on request
method.
Counter on MTAS node.
MtasSipSccTermRequestIn This counter is the total number of SIP
requests received in terminating SCC AS,
including retransmissions. The counter is
keyed on request method.
Counter on MTAS node.
MtasPriorityCallWpsRejected The counter accumulates number of
rejected load regulation requests at dialog
setup, using parameter mapped from SIP
Resource-priority header 'wps' namespace
(RFC 4412). The counter is keyed on wps
resource value.
The counter is incremented by 1 when an
execute permission request for processing
an incoming INVITE, which has a valid SIP
Resource-priority header with wps
namespace, and is handled by MTAS
Resource Priority Handling function, is
denied by TSP load regulation.
Counter on MTAS node.
MtasPriorityCallWpsRequested The counter accumulates number of load
regulation requests at dialog setup, using
parameter mapped from SIP Resource-
priority header 'wps' namespace (RFC
4412). The counter is keyed on wps
resource value.
The counter is incremented by 1 when an
execute permission is requested from TSP
load regulation, for processing an incoming
INVITE, which has a valid SIP Resource-
priority header with wps namespace, and is
handled by MTAS Resource Priority
Handling function.
Counter on MTAS node.
 Ericsson Internal
OPERAT. GUIDELINES 210 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Reference: MTAS, Measurement Data, 1/1553-AVA 90109/9-7, ref. [25] and

(vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1 ref.
[26].

10.6 TSP and vDicos Diameter

TSP is common for HSS, CSCF and MTAS nodes and vDicos is common for
HSSv, CSCFv and MTASv VNFs, thus the Diameter protocol is common for
these nodes. As part of TSP/vDicos overload and priority mechanisms,
Diameter messages are discarded as a result of TSP overload.

10.6.1 Diameter Overload Message Discards

Equation 312. IMS Diameter Received Requests Overload

Discarded Ratio

IMSDia Re c Re qOverloadDiscardRatio[%] = 100 *

incomingMessageDiscardedDueToOverload
receivedRequestFromPeer

IMSvDia Re c Re qOverloadDiscardRatio[%] = 100 *

IncomingMessageDiscardedDueToOverload
ReceivedRequestFromPeer

Equation 313. IMS Diameter Sent Requests Overload Discarded

Ratio

IMSDiaSent Re qOverloadDiscardRatio[%] = 100 *

outgoingMessageDiscardedDueToCongestion
sentRequestToPeer

IMSvDiaSent Re qOverloadDiscardRatio[%] = 100 *

OutgoingMessageDiscardedDueToCongestion
SentRequestToPeer
Counter Name Definition

TSP DIAMETER

receivedRequestFromPeer Reports the number of received requests

from the peer.
The counter is increased if the request
message is successfully processed by the
provider part.
Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
 Ericsson Internal
OPERAT. GUIDELINES 211 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

TSP DIAMETER

incomingMessageDiscardedDueT Number of incoming request messages

oOverload discarded due to overload from the
peer. Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
sentRequestToPeer Reports the number of sent requests to
the peer.
The counter is increased if the answer
message is successfully processed by
the provider part.
Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
outgoingMessageDiscardedDueTo Reports the number of outgoing
Congestion messages discarded due to TCP/SCTP
congestion. Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
outgoingMessageDiscardedDueTo Reports the number of outgoing
CongestionPerLink messages discarded due to congestion
per link in TCP or SCTP. Key is stack
id, host id and connection id.
Counter on TSP and vDicos Diameter
stacks.

Reference: Diameter Measurements, 2/1553-CRA 119 0019/2, Ref. [32].

Counter Name Definition

vDicos DIAMETER

ReceivedRequestFromPeer Reports the number of received requests

from all the peers.
The counter is increased if the request
message is successfully processed by the
provider part.
Key is stack id, host id.
Counter on vDicos Diameter stack.
IncomingMessageDiscardedDueT Number of incoming request messages
oOverload discarded due to overload from the
peer. Key is stack id, host id.
Counter on vDicos Diameter stack.
SentRequestToPeer The number of requests sent to all the
peers.
The counter is increased if the answer
message is successfully processed by
the provider part.
Counter on vDicos Diameter stack.
 Ericsson Internal
OPERAT. GUIDELINES 212 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

vDicos DIAMETER

OutgoingMessageDiscardedDueT Reports the number of outgoing

oCongestion messages discarded due to TCP/SCTP
congestion. Key is stack id, host id.
Counter on vDicos Diameter stack.
OutgoingMessageDiscardedDueT The number of outgoing messages
oCongestionPerLink discarded due to congestion per link.
Key is stack id, host id and connection
id.
Counter on vDicos Diameter stack.

Reference: Diameter Measurements, 5/1553-CXP 904 0375/4 (vDicos), ref.

[33].

10.7 TSP SS7 and SS7 CAF

10.7.1 TSP SS7 Signaling MTP-L2 Link Load and MTP-L3 Congestion

TSP is common for HSS, CSCF and MTAS nodes, thus the TSP SS7 protocol
is common for these nodes. As part of TSP overload and priority
mechanisms, SS7 messages are discarded as a result of TSP overload.

Equation 314. IMS TSP Signaling Link Load Sent at MTP-L2

Level Ratio

IMSTSPSS 7 MTPL 2 LoadSentRatio[%] =

tsp.m2.link_load_sent

Equation 315. IMS TSP Signaling Link Load Received at MTP-

L2 Level Ratio

IMSTSPSS 7 MTPL 2 Load Re ceivedRatio[%] =

tsp.m2.link_load_received

Equation 316. IMS TSP Signaling Cumulative Duration of SL

Congestion (Congestion Level 1) Seconds

IMSTSPSS 7 MPPL3DurationCongestionL1[sec onds ] =

tsp.m3.congestion_level_1

Equation 317. IMS TSP Signaling Cumulative Duration of SL

Congestion (Congestion Level 2) Seconds

IMSTSPSS 7 MPPL3DurationCongestionL 2[sec onds ] =

tsp.m3.congestion_level_2
 Ericsson Internal
OPERAT. GUIDELINES 213 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 318. IMS TSP Signaling Cumulative Duration of SL

Congestion (Congestion Level 3) Seconds

IMSTSPSS 7 MPPL3DurationCongestionL3[sec onds ] =

tsp.m3.congestion_level_3
Counter Name Definition

tsp.m2.link_load_sent Signaling Link Load Sent at MTP-L2 Level.

Based on SIF_SIO octets sent on a specific
link. There is one measurement per link
identified by the HSN, SDL value pair.
Counter on TSP MTP L2 stack.
Tsp.m2.link_load_received Signaling Link Load Received at MTP-L2
Level.
Based on SIF_SIO octets sent on a specific
link. There is one measurement per link
identified by the HSN, SDL value pair.
Counter on TSP MTP L2 stack.
Tsp.m3.congestion_level_1 Cumulative Duration of SL Congestion
(Congestion level 1). There is one
measurement per link identified by the
HSN, SDL value pair.
Counter on TSP MTP L3 stack.
Tsp.m3.congestion_level_2 Cumulative Duration of SL Congestion
(Congestion level 2). There is one
measurement per link identified by the
HSN, SDL value pair.
Counter on TSP MTP L3 stack.
Tsp.m3.congestion_level_3 Cumulative Duration of SL Congestion
(Congestion level 3). There is one
measurement per link identified by the
HSN, SDL value pair.
Counter on TSP MTP L3 stack.

Reference: Reference: SS7 Signalling Measurements, 1/1553-APR 901

382/4, Ref. [34].

10.7.2 SS7 CAF Signaling M3UA Congestion

SS7 CAF is common for CSCF, MTAS (and HSS-FE. The formulas provides
SS7 Signaling Congestion performance indicators per M3UA (MTP3 User
Adaptation) association.

Equation 319. IMS SS7 CAF M3UA Received Lost Data

Messages in Congestion Ratio

IMSSS 7CAFM 3UA Re cLostDataCongestionRatio[%] =

ss7M3uaAssociationLostDatasInCongestion
ss7M3uaAssociationInDatas
 Ericsson Internal
OPERAT. GUIDELINES 214 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSS7CAFM3UARecLostData Messages CongestionRatio is the of lost

DATA messages on M3UA association due to congestion to received data.

Equation 320. IMS SS7 CAF M3UA Congestion Time [Seconds]

IMSSS 7CAFM 3UACongestionTime[S ] =

ss7M3uaAssociationCongestionTime

Equation 321. IMS SS7 CAF M3UA Received Signaling

Congestion Messages [per second]

IMSSS 7CAFM 3UA Re cSigCongestions =

ss7M3uaAssociationInScons
T
Equation 322. IMS SS7 CAF M3UA Received Congestion
Indications from SCTP [per second]

IMSSS 7CAFM 3UA Re cCongestionsIndSCTP =

ss7M3uaAssociationInCongestionInds
T

Counter Name Definition

The measurements are implemented at M3UA association level. The

measured object identifier is "Ss7=1,M3ua=1,RemoteSp=<A>,LocalSp=<B>",
where <A> and <B> are integers.
ss7M3uaAssociationLostDatasInC Number of lost DATA messages on
ongestion M3UA association due to congestion.
There is one measurement per
association identified by the Local Sp,
Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationInDatas Number of received DATA messages
on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationCongestionTi Duration in seconds M3UA association
me has spent in congestion. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationInScons Number of received Signaling
Congestion (SCON) messages on
M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
 Ericsson Internal
OPERAT. GUIDELINES 215 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

ss7M3uaAssociationInCongestionI Number of received congestion

nds indications from SCTP on M3UA
association. There is one measurement
per association identified by the Local
Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationInKBytes Amount of received data on M3UA

association in KBytes. There is one
measurement per association identified by
the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationOutKBytes Amount of sent data on M3UA association
in KBytes. There is one measurement per
association identified by the Local Sp,
Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationInDatas Number of received DATA messages
on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationOutDatas Number of sent DATA messages on

M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationInNotifies Number of received NOTIFY messages

on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationNotActiveTim Duration in seconds M3UA association

e has spent in a state other than ACTIVE.
There is one measurement per
association identified by the Local Sp,
Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationInErrors Number of received ERROR messages

on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationOutErrors Number of sent ERROR messages on
M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
 Ericsson Internal
OPERAT. GUIDELINES 216 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

ss7M3uaAssociationDiscardedDat Number of discarded DATA messages

as on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationNotActive Number of times M3UA association

became not active. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

Reference: SS7 Performance Measurements 2/155 19- ANA 901 37 (SS7

CAF), ref. [36].

11 Diameter and SS7 signaling failures

11.1 CSCF and MTAS Diameter Signaling Failure Rate

TSP is common for HSS, CSCF and MTAS nodes and vDicos is common for
HSSv, CSCFv and MTASv VNFs, thus Diameter protocol is common for these
nodes. These formulas provide Diameter message receive and send
unsuccessful ratios per peer.

Equation 323. IMS Diameter Unsuccessful Received Requests

Ratio

IMSDiaUnsuccessful Re ceivedRatio[%] = 100 *

sentUnsuccessfulAnswerToPeer.Stack id.Host id
receivedRequestFromPeer.Stack id.Host id

IMSvDiaUnsuccessful Re ceivedRatio[%] = 100 *

SentUnsuccessfulAnswerToPeer.Stack id.Host id
ReceivedRequestFromPeer.Stack id.Host id

Equation 324. IMS Diameter Unsuccessful Sent Requests Ratio

IMSDiaUnsuccessfulSentRatio[%] = 100 *
receivedUnsuccessfulAnswerFromPeer.Stack id.Host id
sentRequestToPeer.Stack id.Host id

IMSvDiaUnsuccessfulSentRatio[%] = 100 *
ReceivedUnsuccessfulAnswerFromPeer.Stack id.Host id
SentRequestToPeer.Stack id.Host id
 Ericsson Internal
OPERAT. GUIDELINES 217 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 325. IMS Diameter Malformed Received Requests

Ratio

IMSDiaMalformed Re ceivedRatio[%] = 100 *

MalformedReceivedRequests.Stack id.Host id
receivedRequestFromPeer.Stack id.Host id

Note: Same for TSP and vDicos

Equation 326. IMS Diameter Protcol Errors and Permanent

Failures Ratio

IMSDia Pr otErrAndPermFailRatio[%] = 100 *

ProtocolErrorsAndPermanent Failures.Stack id.Host id
sentRequestToPeer.Stack id.Host id

Note: not applicable for vDicos

Counter Name Definition

TSP DIAMETER

receivedRequestFromPeer Reports the number of received requests

from the peer.
The counter is increased if the request
message is successfully processed by the
provider part.
Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
sentUnsuccessfulAnswerToPeer Reports the number of answers sent to
peer indicating unsuccessful request
(answer message with result code that
is out or range [2001, 2999]).
Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
sentRequestToPeer Reports the number of sent requests to
the peer.
The counter is increased if the answer
message is successfully processed by
the provider part.
Key is stack id, host id.
Counter on TSP and vDicos Diameter
stacks.
 Ericsson Internal
OPERAT. GUIDELINES 218 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

TSP DIAMETER

receivedUnsuccessfulAnswer Reports the number of answers

FromPeer received from peer indicating
unsuccessful request (answer message
with result code that is out or range
[2001, 2999]). Key is stack id, host id.
Counter on TSP Diameter and vDicos
stacks.
MalformedReceivedRequests Reports the number of malformed
received requests per peer.
CerReceivedFromUnknownPeer Reports the total number of Capabilities
Exchange Requests (CER) received
from unknown peer nodes when
connections from unknown peers are
rejected. The statistics are per
Diameter stack instance.
ProtocolErrorsAndPermanent Reports the number of protocol errors
Failures and permanent failures returned to
peer.

Reference: Diameter Measurements, 2/1553-CRA 119 0019/2, Ref. [32]

Counter Name Definition

vDicos DIAMETER

ReceivedRequestFromPeer Reports the number of received requests

from all the peers.
The counter is increased if the request
message is successfully processed by the
provider part.
Key is stack id, host id.
Counter on vDicos Diameter stack.
SentUnsuccessfulAnswerToPeer The number of unsuccessful answers
sent to all the peers indicating
unsuccessful request (answer message
with result code that is out or range
[2001, 2999]).
Counter on vDicos Diameter stack.
SentRequestToPeer The number of requests sent to all the
peers.
The counter is increased if the answer
message is successfully processed by
the provider part.
Counter on vDicos Diameter stack.
ReceivedUnsuccessfulAns wer Reports the number of answers
FromPeer received from all peers indicating
unsuccessful request (answer message
with result code that is out or range
[2001, 2999]). Key is stack id, host id.
Counter on vDicos Diameter stacks.
 Ericsson Internal
OPERAT. GUIDELINES 219 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

vDicos DIAMETER

MalformedReceivedRequests Reports the number of malformed

received requests per peer.
Key is stack id, host id.
Counter on vDicos Diameter stacks.
CerReceivedFromUnknownPeer Reports the total number of Capabilities
Exchange Requests (CER) received
from peers absent in static
configuration. The statistics are per
Diameter stack instance.
Counter on vDicos Diameter stacks.

Reference: Diameter Measurements, 5/1553-CXP 904 0375/4 (vDicos), ref.

[33].

11.2 SBG Diameter Rx, Rf, Rq or e2 Signaling

The SBG Diameter Signaling formula provide Diameter message send

successful ratios per peer for the Rx, Rf, Rq or e2 interfaces.

Equation 327. IMS SBG Diameter Request Success Ratio

IMSSBGDiameter Re questSuccessRatio[%] = 100 *

sbgDiaPeerStatSuccessfulRequests
(sbgDiaPeerStatSuccessfulRequests + sbgDiaPeerStatPermanentFailures +
sbgDiaPeerStatProtocolErrors + sbgDiaPeerStatTransientFailures)

Equation 328. IMS SBG Diameter Permanent Failures [per

second]

IMSSBGDiameterPermanentFailures =
sbgDiaPeerStatPermanentFailures
T
Equation 329. IMS SBG Diameter Transient Failures [per
second]

IMSSBGDiameterTransientFailures =
sbgDiaPeerStatTransientFailures
T
Equation 330. IMS SBG Diameter Protocol Errors [per second]

IMSSBGDiameter Pr otocolErrors =
sbgDiaPeerStatProtocolErrors
T
 Ericsson Internal
OPERAT. GUIDELINES 220 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgDiaPeerStatSuccessfulRequests The number of successful requests to this

Diameter peer server.
Counter on SBG.
sbgDiaPeerStatPermanentFailures The number of permanent failures to this
Diameter peer server
Counter on SBG.
sbgDiaPeerStatProtocolErrors The number of protocol errors received from
this Diameter peer server.
Counter on SBG.
sbgDiaPeerStatTransientFailures The number of successful requests to this
Diameter peer server.
Counter on SBG.

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23] and
SBGv Managed Object Model (MOM), 155 54-LZN7650172-V1, ref. [24].

11.3 SBG Diameter Rx NPLI Signaling

The SBG Diameter Rx Network Provided Location Information (NPLI)

Success Ratio formula provides Rx interface accessibility per peer.

Equation 331. IMS SBG Diameter Rx NPLI Success Ratio

IMSSBGDiaRxSuccessRatio[%] = 100 *
sbgDiaRealmStatsNpliSuccesses
sbgDiaRealmStatsNpliAttempts

IMSSBGvDiaRxSuccessRatio[%] = 100 *
sbgDiaRxStatsNpliSuccesses
sbgDiaRxStatsNpliAttempts
Counter Name Definition

sbgDiaRealmStatsNpliAttempts Number of NPLI subscriptions the AF

initiates to PCRF. This counter belongs to
measurement family 'DIAREALM_statistics'.
This counter is only applicable for the Rx
interface.
Counter on SBG.
sbgDiaRealmStatsNpliSuccesses Number of successful NPLI retrievals that
the PCRF has responded to. This counter
belongs to measurement family
'DIAREALM_statistics'. This counter is only
applicable for the Rx interface.
Counter on SBG.
sbgDiaRxStatsNpliAttempts The number of NPLI subscriptions the SBG
has initiated to PCRF.
Counter on SBGv.
 Ericsson Internal
OPERAT. GUIDELINES 221 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

sbgDiaRxStatsNpliSuccesses The number of successful NPLI retrievals

that the PCRF has responded to, that is:
a) PCRF has responded with a RAR to an
NPLI subscription;
b) The response was received within the
permitted time interval so that SBG could
use the location information in the P-
Access-Network-Info header.
Counter on SBGv.

Reference: SBG MIM Description, 13/155 54-CXA 112 350, ref. [23] and
SBGv Managed Object Model (MOM), 155 54-LZN7650172-V1, ref. [24].

11.4 TSP SS7 Signaling MTP-L3 Link Unavailability

TSP is common for HSS, CSCF and MTAS, thus the SS7 protocol is common
for these nodes. These formula provides SS7 MTP-L3 Link Unavailability per
link.

Equation 332. IMS TSP Signaling Duration of Link Unavailability

MTP-L3 Level Seconds

IMSTSPSS 7 MTPL3LinkUnavailable[sec onds ] =

tsp.m3.link_unavailable
Counter Name Definition

tsp.m3.link_unavailable Duration of Link Unavailability (Due to

Link Failure).
There is one measurement per link
identified by the HSN, SDL value pair.
Counter on TSP MTP L3 stack.

Reference: SS7 Signalling Measurements, 1/1553-APR 901 382/4, Ref. [34].

11.5 SS7 CAF Signaling M3UA Link Unavailability and Errors

SS7 CAF is common for CSCF, MTAS (and HSS-FE. The formulas provides
SS7 Signaling error performance indicators per M3UA (MTP3 User Adaptation)
association.

Equation 333. IMS SS7 CAF M3UA Received Errors Ratio

IMSSS 7CAFM 3UA Re cErrorsRatio[%] = 100 *

ss7M3uaAssociationInErrors
ss7M3uaAssociationInDatas
Equation 334. IMS SS7 CAF M3UA Discarded Data Ratio
 Ericsson Internal
OPERAT. GUIDELINES 222 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSSS 7CAFM 3UADiscDataRatio[%] = 100 *

ss7M3uaAssociationDiscardedDatas
ss7M3uaAssociationInDatas
Equation 335. IMS SS7 CAF M3UA Sent Errors Ratio

IMSSS 7CAFM 3UASentErrorsRatio[%] = 100 *

ss7M3uaAssociationOutErrors
ss7M3uaAssociationOutDatas

Counter Name Definition

The measurements are implemented at M3UA association level. The

measured object identifier is "Ss7=1,M3ua=1,RemoteSp=<A>,LocalSp=<B>",
where <A> and <B> are integers.
ss7M3uaAssociationInErrors Number of received ERROR messages
on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationInDatas Number of received DATA messages
on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationDiscardedDat Number of discarded DATA messages
as on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationOutErrors Number of sent ERROR messages on
M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationOutDatas Number of sent DATA messages on
M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationInKBytes Amount of received data on M3UA

association in KBytes. There is one
measurement per association identified by
the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.
 Ericsson Internal
OPERAT. GUIDELINES 223 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

ss7M3uaAssociationOutKBytes Amount of sent data on M3UA association

in KBytes. There is one measurement per
association identified by the Local Sp,
Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationInNotifies Number of received NOTIFY messages

on M3UA association. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

ss7M3uaAssociationNotActiveTim Duration in seconds M3UA association

e has spent in a state other than ACTIVE.
There is one measurement per
association identified by the Local Sp,
Remote Sp value pair.
Counter on SS7 CAF M3UA.
ss7M3uaAssociationNotActive Number of times M3UA association
became not active. There is one
measurement per association identified
by the Local Sp, Remote Sp value pair.
Counter on SS7 CAF M3UA.

Reference: SS7 Performance Measurements 2/155 19- ANA 901 37 (SS7

CAF), ref. [36].

12 vDicos NIC , TIPC Link and BGFv Media Interface

The R-KPIs specified in this section cover NIC, Link level.

12.1 vDicos NIC Perfomance Indicators

The R-KPIs specified in this section cover vDicos NICs. These R-KPIs are
relevant for the virtualized CSCF and MTAS nodes.

Equation 336. IMS NIC Send Requests [KB per second]

IMSNICSend Re quests = VS.LEM.Tx.KBs

Equation 337. IMS NIC Receive Requests [KB per second]

IMSNIC Re c Re quests = VS.LEM.Rx.KBs

Equation 338. IMS NIC Send Collision Ratio

 Ericsson Internal
OPERAT. GUIDELINES 224 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSNICSendCollisionRatio[%] = 100 *
VS.LEM.Link.Collision
VS.LEM.Tx.Packets
Equation 339. IMS NIC Send Error Ratio

IMSNICSendErrorRatio[%] = 100 *
(VS.LEM.Tx.Errors + VS.LEM.Tx.Dropped)
VS.LEM.Tx.Packets

Normal drop rate is approximately 1 in 10,000 packets. A drop rate of around

0.1% is assumed for setting values for threshold based alarm.

Equation 340. IMS NIC Receive Error Ratio

IMSNIC Re cvErrorRatio[%] = 100 *

(VS.LEM.Rx.Errors + VS.LEM.Rx.Dropped)
VS.LEM.Rx.Packets

Normal drop rate is approximately 1 in 10,000 packets. A drop rate of around

0.1% is assumed for setting values for threshold based alarm.

Counter Name Definition

VS.LEM.Tx.Packets Used to measure the total number of

packets sent for a network interface.
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Tx.KBs Used to measure the total number of
kilobytes transmitted per second in average
for a GP
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Link.Collision Used to measure the number of counted
package collisions for a network interface.
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Rx.KBs Used to measure the total number of
kilobytes received per second in average for
a GP.
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Tx.Errors Used to measure the total number of errors
that happened while transmitting packets in
a GP.
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Rx.Errors Used to measure the total number of bad
packets received in a GP.
Counter in vDicos OsmDevice PmGroup.
 Ericsson Internal
OPERAT. GUIDELINES 225 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

VS.LEM.Tx.Dropped Used to measure the total number of

dropped packages in a GP for a certain
interface for transmit side (TX).
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Rx.Dropped Used to measure the total number of
dropped packages in a GP for a certain
interface for receive side (RX).
Counter in vDicos OsmDevice PmGroup.
VS.LEM.Rx.Packets Used to measure the total number of
packets received for a network interface.
Counter in vDicos OsmDevice PmGroup.

Reference: LEM Managed Object Model PM 19089-LZN7080730/0, ref. [35].

12.2 vDicos TIPC Link Performance Indicators

The R-KPIs specified in this section cover vDicos TIPC links. These R-KPIs
are relevant for the virtualized CSCF and MTAS nodes.

Equation 341. IMS TIPC Tunnel Latency [microseconds]

IMSTIPCTunnelLatency = VS.LPM.Dialogue.Tunnel.Latency

Equation 342. IMS TIPC Send Requests [Packets per second]

VS.LEM.Tx.Packets
IMSTIPCSend Re quests[Pkts per Sec] =
T
Equation 343. IMS TIPC Receive Requests [Packets per
second]

VS.LEM.Rx.Packets
IMSTIPC Re c Re quests[Pkts per Sec] =
T
Equation 344. IMS TIPC Send Collision Ratio

IMSTIPCSendCollisionRatio[%] = 100 *
VS.LEM.Link.Collision
VS.LEM.Tx.Packets
Equation 345. IMS TIPC Send Drop Ratio

IMSTIPCSendDropRatio[%] = 100 *
VS.LEM.Tx.Naks
VS.LEM.Tx.Packets
 Ericsson Internal
OPERAT. GUIDELINES 226 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Normal drop rate is approximately 1 in 10,000 packets. A drop rate of around

0.1% is assumed for setting values for threshold based alarm.

Equation 346. IMS TIPC Receive Drop Ratio

IMSTIPC Re cvDropRatio[%] = 100 *

VS.LEM.Rx.Naks
VS.LEM.Rx.Packets

Normal drop rate is approximately 1 in 10,000 packets. A drop rate of around

0.1% is assumed for setting values for threshold based alarm.
Counter Name Definition

VS.LPM.Dialogue.Tunnel.Latency Measures the dialogue tunnel latency (RTT

in microseconds) between vDicos VMs.
Counter in vDicos VdTunnel PmGroup.
VS.LEM.Tx.Acks Used to measure the total number of acks
for TX in a GP.
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Tx.Naks Used to measure the total number of nacks
for TX in a GP. Indicates the number of
packet retransmissions.
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Link.Collision Used to measure the total number of
congestion (collision) on link in a GP.
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Tx.Packets Used to measure the total number of
packets sent in a GP..
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Rx.Acks Used to measure the total number of acks
for RX in a GP.
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Rx.Naks Used to measure the total number of nacks
for RX in a GP. Indicates the number of
packet retransmissions.
Counter in vDicos OsmTipcLink PmGroup.
VS.LEM.Rx.Packets Used to measure the total number of
packets received in a GP.
Counter in vDicos OsmTipcLink PmGroup.

Reference: LEM Managed Object Model PM 19089-LZN7080730/0, ref. [35]

and LPM Managed Object Model PM 19089-LZN7080731/0, ref. [36].

12.3 vBGF Media IP Interface Performance Indicators

Equation 347. IMS BGFv Received Octets [per second]

IMSBGFv Re cOctets = rxOctetsPerSecond

Equation 348. IMS BGFv Peak Received Octets [per second]
 Ericsson Internal
OPERAT. GUIDELINES 227 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSBGFv Re cOctetsPeak = rxOctetsPerSecondPeak

Equation 349. IMS BGFv Sent Octets [per second]

IMSBGFvSentOctets = txOctetsPerSecond
Equation 350. IMS BGFv Peak Sent Octets [per second]

IMSBGFvSentOctetsPeak = txOctetsPerSecondPeak
Equation 351. IMS BGFv Received Packets [per second]

IMSBGFv Re cPackets = rxPacketsPerSecond

Equation 352. IMS BGFv Peak Received Packets [per second]

IMSBGFv Re cPacketsPeak = rxPacketsPerSecondPeak

Equation 353. IMS BGFv Sent Packets [per second]

IMSBGFvSentPackets = txPktsPerSecond
Equation 354. IMS BGFv Peak Sent Packets [per second]

IMSBGFvSentPacketsPeak = txOctetsPerSecondPeak
Equation 355. IMS BGFv Discarded Receiver Packets Ratio

IMSBGFvDisc Re cPktsRatio[%] = 100 *

(rxDiscPkts + rxDiscPktsExc)
rxPackets

IMSBGFvDiscRecPktsRatio is the percentage of discared received packets,

received packets have been discarded, e.g due to TTL reaching 0 or
discarded due to excessive traffic caused by bandwidth policing.

Equation 356. IMS BGFv Discarded Receiver Packets [per

second]

IMSBGFvDisc Re cPackets =
rxDiscPkts
T
IMSBGFvDiscRecPackets is the number of received packets per second that
have been discarded, e.g due to TTL reaching 0.

Equation 357. IMS BGFv Discarded Excessive Receiver Packets

[per second]
 Ericsson Internal
OPERAT. GUIDELINES 228 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

IMSBGFvDisc Re cPacketsExc =
rxDiscPktsExc
T
IMSBGFvDiscRecPacketsExc is the number of received packets per second
that have discarded due to excessive traffic caused by bandwidth policing.

Equation 358. IMS BGFv Discarded Sender Packets Ratio

IMSBGFvDiscSendPktsRatio[%] = 100 *
(txDiscPkts + txDiscPktsNoNextHop)
txPackets

IMSBGFvDiscSendPktsRatio is the percentage of discared outgoing packets

for several reasons, refer to counter descriptions.

Equation 359. IMS BGFv Discarded Sender Packets [per

second]

IMSBGFvDiscSendPackets =
txDiscPkts
T
IMSBGFvDiscSendPackets is the number of outgoing packets per second
that have been discarded for the reasons:
- Packets discarded during latching when the remote address/port is still
unknown
- Packets that cannot be transmitted because the stream mode is set to
inactive or receive-only
- RTCP packets that cannot be transmitted because RTCP is not enabled

Equation 360. IMS BGFv Discarded Sender Packets No Next

Hop [per second]

IMSBGFvDiscSendPacketsNoNextHop =
txDiscPktsNoNextHop
T
IMSBGFvDiscSendPackets is the number of outgoing packets per second
that have been discarded due to no next hop MAC address.

Counter Name Definition

rxOctetsPerSecond The current throughput of received and

accepted IP datagram packets, calculated
as octets per second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
 Ericsson Internal
OPERAT. GUIDELINES 229 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

rxOctetsPerSecondPeak The peak throughput of received and

accepted IP datagram packets, calculated
as octets per second
Counter in vBGF BgfMediaIpInterface
PmGroup.
txOctetsPerSecond The current throughput of transmitted IP
datagram packets, calculated as octets per
second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
txOctetsPerSecondPeak The peak throughput of transmitted IP
datagram packets, calculated as octets per
second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
rxDiscOctetsExc The total number of octets in received
packets that have been discarded due to
excessive traffic because of bandwidth
policing.
Counter in vBGF BgfMediaIpInterface
PmGroup.
rxPackets The total number of received and accepted
packets.
Counter in vBGF BgfMediaIpInterface
PmGroup.
rxPktsPerSecond The current throughput of received and
accepted IP datagram packets, calculated
as packets per second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
rxPktsPerSecondPeak The peak throughput of received and
accepted IP datagram packets, calculated
as packets per second.

rxDiscPkts The total number of received packets that

have been discarded, e.g due to TTL
reaching 0.
Counter in vBGF BgfMediaIpInterface
PmGroup.
rxDiscPktsExc The total number of received packets that
have been discarded due to excessive
traffic because of bandwidth policing.
Counter in vBGF BgfMediaIpInterface
PmGroup.
txPackets The total number of sent packets.
Counter in vBGF BgfMediaIpInterface
PmGroup.
 Ericsson Internal
OPERAT. GUIDELINES 230 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Counter Name Definition

txPktsPerSecond The currrent throughput of transmitted IP

datagram packets, calculated as packets
per second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
txPktsPerSecondPeak The peak throughput of transmitted IP
datagram packets, calculated as packets
per second.
Counter in vBGF BgfMediaIpInterface
PmGroup.
txDiscPkts The total number of outgoing packets that
have been discarded for other reasons:
- Packets discarded during latching when
the remote address/port is still unknown
- Packets that cannot be transmitted
because the stream mode is set to inactive
or receive-only
- RTCP packets that cannot be transmitted
because RTCP is not enabled.
Counter in vBGF BgfMediaIpInterface
PmGroup.
txDiscPktsNoNextHop The total number of outgoing packets that
have been discarded due to no next hop
MAC address.
Counter in vBGF BgfMediaIpInterface
PmGroup.

Reference: Instances in BgfPmMomInstances 476/155 54-1/AXM 101 03/1-

V1, ref. [29].

13 References
[1] IMCN System Glossary of Terms and Acronyms 0033-HSC11310
[2] O&M Performance Management 24/15517-HSC11310
[3] IMS O&M Overview 2/1550-HSC 113 10
[4] TS 32.409 V10.3.0 Performance Measurements IMS
[5] TS 32.454 V11.0.0 Key Performance Indicators (KPI) for the IP
Multimedia Subsystem (IMS)
[6] Key Performance Indicators (KPI) for the IP Multimedia Subsystem
(IMS); Definitions, 3GPP TS 32.454 V10.0.0
[7] User Service Performance, White Paper, 284 23-3106, Rev A
[8] Key Performance Indicators for IMS System 2/1050-HSC 113 06
[9] ITU-T E.800 Recommendation, Telephone Network and ISDN Quality
of Service, Network Management and Traffic Engineering - Terms and
 Ericsson Internal
OPERAT. GUIDELINES 231 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Definitions Related to Quality of Service and Network Performance

including Dependability
[10] VoLTE E2E Performance Management 4/195 83-HSC12034
[11] IMCN Signaling Traffic Performance Indicators 2/154 43-HSC 113 10
[12] IMS Active Users FS, 6/155 17-HSC 113 06
[13] CSCF Performance Management Parameters, 1/1551-AVA 901 19/6
[14] (vCSCF) Managed Object Model (MOM), 155 54-LZN 765 0209-V1
[15] JavaSIP Performance Measurements, 1/1551-APR 901 0526/3
[16] MGC System Statistics, 9/154 43-CNA 113 215/1
[17] SBG MIM Description, 13/155 54-CXA 112 350
[18] SBGv Managed Object Model (MOM), 155 54-LZN7650172-V1
[19] MTAS, Measurement Data, 1/1553-AVA 90109/9-7
[20] (vMTAS) Managed Object Model (MOM), 155 54-LZN 765 0163/9-V1
[21] User Guide for Performance Measurements MRS, 17/1553-AXM 101
01/11-V2
[22] Performance Indicators Virtual Border Gateway Function 2/1551-AXM
10 103/1-V1
[23] Instances in BgfPmMomInstances 476/155 54-1/AXM 101 03/1-V1
[24] vEMe Interwork Performance Indicators, 1/154 43-AVA 901 31/3
[25] TSP Measurements, 1/1553-CRA 119 0003/2
[26] Diameter Measurements, 2/1553-CRA 119 0019/2 (TSP)
[27] Diameter Measurements, 5/1553-CXP 904 0375/4 (vDicos)
[28] SS7 Signalling Measurements, 1/1553-APR 901 382/4 (TSP)
[29] SS7 Performance Measurements 2/155 19- ANA 901 37 (SS7 CAF)
[30] LEM Managed Object Model PM 19089-LZN7080730/0
[31] LPM Managed Object Model PM 19089-LZN7080731/0
 Ericsson Internal
OPERAT. GUIDELINES 232 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Appendix 1 Formula table

Equation 1. IMS CSCF Initial Registration Success Ratio 24
Equation 2. IMS CSCF Third Party Registration Success Ratio 25
Equation 3. IMS S-CSCF Initial Registration Success Ratio per Acesss Type 25
Equation 4. IMS CSCF Reregistration and Deregistration Success Ratio 28
Equation 5. IMS CSCF Re-registration Success Ratio 28
Equation 6. IMS S-CSCF Reregistration and Deregistration Success Ratio per Access Type
28
Equation 7. IMS CSCF Dropped Registrations Ratio 32
Equation 8. IMS CSCF Originating Session Set-up Success Ratio 33
Equation 9. IMS CSCF Terminating Session Set-up Success Ratio 33
Equation 10. IMS CSCF Originating Session Set-up Success Ratio per Access Type 34
Equation 11. IMS CSCF Terminating Session Set-up Success Ratio per Access Type 34
Equation 12. IMS CSCF Originating Session Set-up Success Ratio per Media Type 35
Equation 13. IMS CSCF Terminating Session Set-up Success Ratio per Media Type 35
Equation 14. IMS CSCF Emergency Session Set-up Success Ratio 36
Equation 15. IMS CSCF Originating Session Answer to Seizure Ratio (ASR) 36
Equation 16. IMS CSCF Terminating Session Answer to Seizure Ratio (ASR) 36
Equation 17. IMS CSCF Session Completion Ratio 44
Equation 18. IMS CSCF EATCF SRVCC Access Transfer Success Ratio 44
Equation 19. IMS CSCF Dropped Sessions Ratio 45
Equation 20. IMS CSCF Originating Sessions Set-up Time [milliseconds] 46
Equation 21. IMS CSCF Terminating Sessions Set-up Time [milliseconds] 46
Equation 22. IMS S-CSCF Originating Session Duration per Access Type [Seconds] 47
Equation 23. IMS S-CSCF Terminating Sessions Duration per Access Type [Seconds] 47
Equation 24. IMS CSCF Rf Accounting Request Success Ratio 52
Equation 25. IMS CSCF Rf Accounting Permanent Failures [per second] 52
Equation 26. IMS CSCF Rf Accounting Protocol Errors [per second] 52
Equation 27. CSCF Rf ACR to Backup [per second] 52
Equation 28. IMS CSCF Ro Accounting Request Success Ratio 52
Equation 29. IMS CSCF Registered Users 53
Equation 30. IMS CSCF Registered User Profiles 54
Equation 31. IMS CSCF Unregistered User Profiles 54
Equation 32. IMS CSCF Dropped Registrations [per second] 54
Equation 33. IMS CSCF Failed Registrations [per second] 54
Equation 34. IMS CSCF Initial Registration Failures [per second] 54
Equation 35. IMS CSCF Re-registration Failures [per second] 54
Equation 36. IMS CSCF Active Sessions 55
Equation 37. IMS CSCF EATF Active Sessions 55
Equation 38. IMS CSCF Dropped Sessions [per second] 55
Equation 39. IMS CSCF Originating Failed Sessions [per second] 55
Equation 40. IMS CSCF Terminating Failed Sessions [per second] 55
Equation 41. IMS CSCF Session Setup Attempts with Internal Failures [per second] 56
Equation 42. IMS CSCF SIP Error Responses [per second] 56
Equation 43. IMS ESCF Emergency Session Setup Failures [per second] 56
Equation 44. IMS CSCF EATF SRVCC Emergency Access Transfer Failures [per second]56
Equation 45. IMS S-CSCF P-CSCF Restoration Attempts [per second] 56
Equation 46. IMS S-CSCF P-CSCF Restoration Failures [per second] 57
Equation 47. IMS CSCF Request Timeouts [per second] 57
Equation 48. IMS CSCF Throttled HSS Requests [per second] 57
Equation 49. IMS CSCF Average Reporting OC value 57
 Ericsson Internal
OPERAT. GUIDELINES 233 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 50. IMS CSCF Peak Reporting OC value 57

Equation 51. IMS CSCF Registerd Users Redistributed 58
Equation 52. IMS CSCF Unregisterd Users Redistributed 58
Equation 53. IMS CSCF Active Users 65
Equation 54. IMS S-CSCF Active Users per Profile 65
Equation 55. IMS CSCF PSTN Interworking Originating Session Set-up Success Ratio 67
Equation 56. IMS CSCF PSTN Interworking Terminating Session Set-up Success Ratio 67
Equation 57. IMS I-CSCF Transit Set-up Success Ratio 67
Equation 58. IMS CSCF PSTN Interworking Originating Attempts [per second] 68
Equation 59. IMS CSCF PSTN Interworking Terminating Attempts [per second] 68
Equation 60. IMS I-CSCF Transit Set-up Attempts [per second] 68
Equation 61. IMS MTAS Initial Registration Success Ratio 69
Equation 62. IMS MTAS Automatic Registration Success Ratio 69
Equation 63. IMS MTAS Re-registration Success Ratio 70
Equation 64. IMS MTAS Re- and De-registration Completion Ratio 71
Equation 65. IMS MMTEL AS Originating Session Set-up Success Ratio 72
Equation 66. IMS MMTEL AS Terminating Session Set-up Success Ratio 72
Equation 67. IMS MMTEL AS Originating Answer to Seizure Ratio (ASR) 73
Equation 68. IMS MMTEL AS Terminating Answer to Seizure Ratio (ASR) 74
Equation 69. IMS MMTEL AS Failed Originating Sessions [per second] 74
Equation 70. IMS MMTEL AS Failed Terminating Sessions [per second] 74
Equation 71. IMS MMTEL AS User Rejected Originating Sessions [per second] 74
Equation 72. IMS MMTEL AS User Rejected Terminating Sessions [per second] 74
Equation 73. IMS MMTEL AS Network Rejected Originating Sessions [per second] 75
Equation 74. IMS MMTEL AS Network Rejected Terminating Sessions [per second] 75
Equation 75. IMS MMTEL AS Service Logic Rejected Originating Sessions [per second] 75
Equation 76. IMS MMTEL AS Service Logic Rejected Terminating Sessions [per second] 75
Equation 77. IMS MMTEL AS External Support Node Rejected Originating Sessions [per
second] 75
Equation 78. IMS MMTEL AS External Support Node Rejected Terminating Sessions [per
second] 76
Equation 79. IMS MMTEL AS Call Released No Credit [per second] 76
Equation 80. IMS MMTEL AS Rejected Parlay-X requests, per cause code [per second] 76
Equation 81. IMS MTAS DNS Failover [per second] 76
Equation 82. IMS MMTel AS Orginating Session Completion Ratio 86
Equation 83. IMS MMTel AS Terminating Session Completion Ratio 86
Equation 84. IMS MMTel AS Orginating Dropped Sessions Ratio 86
Equation 85. IMS MMTel AS Terminating Dropped Sessions Ratio 86
Equation 86. IMS SCC AS Originating CS Session Completion Ratio 87
Equation 87. IMS SCC AS Terminating CS Session Completion Ratio 87
Equation 88. IMS SCC AS Originating PS Session Completion Ratio 87
Equation 89. IMS SCC AS Terminating PS Session Completion Ratio 88
Equation 90. IMS MMTEL AS Failed Originating Session completion [per second] 89
Equation 91. IMS MMTEL AS Failed Terminating Sessions completion [per second] 89
Equation 92. IMS SCC AS Failed Originating CS Session completion [per second] 89
Equation 93. IMS SCC AS Failed Terminating CS Sessions completion [per second] 89
Equation 94. IMS SCC AS Failed Originating PS Session completion [per second] 89
Equation 95. IMS SCC AS Failed Terminating PS Sessions completion [per second] 90
Equation 96. IMS MMTEL AS Hold Service Success Ratio 95
Equation 97. IMS MMTEL AS Resume Service Success Ratio 95
Equation 98. IMS MMTEL AS Communication Diversion Success Ratio 96
Equation 99. IMS MMTEL AS Conference Creation Success Ratio 97
 Ericsson Internal
OPERAT. GUIDELINES 234 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 100. IMS MMTEL AS Joined Conference Participant Success Ratio 97

Equation 101. IMS Conference AS Scheduled Conference Dial-in Success Ratio 98
Equation 102. IMS MTAS Conference Termination Success Ratio 99
Equation 103. IMS MMTEL AS Calling Name Identification Presentation (CNIP) Success
Ratio 100
Equation 104. IMS MMTEL AS Playing of Announcement Success Ratio 101
Equation 105. IMS MMTEL AS Abbreviated Dialing Success Ratio 102
Equation 106. IMS MMTEL AS Playing of Announcement Success Ratio 103
Equation 107. IMS MMTEL AS (User) Communication Waiting Success Ratio 104
Equation 108. IMS MMTEL AS Advice of Charge Start (AoC-S) Success Ratio 104
Equation 109. IMS MMTEL AS Advice of Charge During (AoC-D) Success Ratio 104
Equation 110. IMS MMTEL AS Advice of Charge End (AoC-E) Success Ratio 105
Equation 111. IMS MMTel AS Third Party (3PTY) Call Creation Success Ratio 106
Equation 112. IMS MMTel AS Third Party (3PTY) Communication Completion Success Ratio
106
Equation 113. IMS MMTEL AS Communication Completion Busy Subscriber (CCBS)
Invocation Success Ratio 107
Equation 114. IMS MMTEL AS Communication Completion No Reply (CCNR) Invocation
Success Ratio 107
Equation 115. IMS MMTEL AS Flexible Communication Distribution (FCD) Success Ratio
109
Equation 116. IMS MMTEL AS Flexible Communication Distribution (FCD) Ongoing
Sessions 109
Equation 117. IMS MMTEL AS Originating Short Number Dialing (SND) Success Ratio 110
Equation 118. IMS MMTEL AS Terminating Short Number Dialing (SND) Success Ratio 110
Equation 119. IMS SCC AS Originating Service from CS Success Ratio 111
Equation 120. IMS SCC AS Originating Service from PS Success Ratio 111
Equation 121. IMS SCC AS Originating Unregistered Service from CS Success Ratio 111
Equation 122. IMS SCC AS Originating Unregistered Service from PS Success Ratio 111
Equation 123. IMS SCC AS Terminating Service Success Ratio 111
Equation 124. IMS SCC AS Terminating Unregistered Service Success Ratio 112
Equation 125. IMS SCC AS Terminating Service to VoLTE CS UE Success Ratio 112
Equation 126. IMS SCC AS Terminating Service to VoLTE PS UE Success Ratio 112
Equation 127. IMS SCC AS Terminating Unregistered Service to VoLTE CS UE Success Ratio
112
Equation 128. IMS SCC AS Terminating Unregistered Service to VoLTE PS UE Success Ratio
112
Equation 129. IMS SCC AS Session Setup from CS using CAP Registered and Unregistered
Users Success Ratio 113
Equation 130. IMS SCC AS SR-VCC Access Transfer Success Ratio 121
Equation 131. IMS SCC AS Single Radio Voice Call Continuity (SRVCC) Active Session
Access Transfer Success Ratio 121
Equation 132. IMS SCC AS Single Radio Voice Call Continuity (SRVCC) Alerting Access
Transfer Success Ratio 121
Equation 133. IMS SCC AS Single Radio Voice Call Continuity (SRVCC) pre-Alerting Access
Transfer Success Ratio 121
Equation 134. IMS SCC AS Single Radio Voice Call Continuity (SRVCC) Mid Call Access
Transfer Success Ratio 122
Equation 135. IMS SCC AS Network Failed Active Session Access Transfers, per cause code
122
Equation 136. IMS SCC AS User Failed Active Session Access Transfers, per cause code 122
 Ericsson Internal
OPERAT. GUIDELINES 235 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 137. IMS SCC AS Network Failed Alerting Session Access Transfers, per cause code
122
Equation 138. IMS SCC AS User Failed Alerting Session Access Transfers, per cause code
123
Equation 139. IMS SCC AS Network Failed pre-Alerting Session Access Transfers, per cause
code 123
Equation 140. IMS SCC AS User Failed pre-Alerting Session Access Transfers, per cause
code 123
Equation 141. IMS SCC AS Network Failed Mid-call Access Transfers, per cause code 123
Equation 142. IMS SCC AS User Failed pre-Alerting Session Access Transfers, per cause
code 123
Equation 143. IMS MMTEL AS Customized Alerting Tones (CAT) Service Success Ratio 128
Equation 144. IMS MMTEL AS Session Transfer to Own Device (STOD) Service Success
Ratio 128
Equation 145. IMS MMTEL AS Session Transfer to Own Device (STOD) Call Pull Service
Success Ratio 129
Equation 146. IMS MMTEL AS Incoming Parlay-X Request Success Ratio 130
Equation 147. IMS MMTEL AS Outgoing Parlay-X Request Success Ratio 130
Equation 148. IMS MMTEL AS Polling of Calling Name Information Success Ratio 131
Equation 149. IMS MMTEL AS Call Return Service Success Ratio 132
Equation 150. IMS MMTEL AS Call Return Erasure Procedure Success Ratio 132
Equation 151. IMS MMTEL AS Generic Supplementary Service Code Invocation Service
Success Ratio 133
Equation 152. IMS MMTEL AS Operator Controlled Transfer Service Answered Ratio 134
Equation 153. IMS MMTel AS Priority Call Successfully Established Ratio 135
Equation 154. IMS MMTel AS GETS Priority Service Successfully Setup Ratio 135
Equation 155. IMS MMTel AS Ring Back Tone Request Success Ratio 137
Equation 156. IMS SCC AS CAP Request Success Ratio 137
Equation 157. IMS MMTel AS Closed User Group Request Success Ratio 138
Equation 158. IMS ST AS Originating Session Setup Success Ratio per PBX 139
Equation 159. IMS ST AS Terminating Session Setup Success Ratio per PBX 139
Equation 160. IMS ST AS Originating Session Setup Success Ratio 139
Equation 161. IMS ST AS Terminating Session Setup Success Ratio 140
Equation 162. IMS ST AS Failed Originating Sessions, per cause code 140
Equation 163. IMS ST AS Failed Terminating Sessions, per cause code 140
Equation 164. IMS ST AS Failed Originating Sessions, per PBX 140
Equation 165. IMS ST AS Failed Terminating Sessions, per PBX 141
Equation 166. IMS MMTel AS H.248 Request Success Ratio 142
Equation 167. IMS MMTel AS H.248 Request Replay Success Ratio 142
Equation 168. IMS MMTel AS Charging Request Success Ratio 144
Equation 169. IMS MMTel AS Sh Pull Request Success Ratio 146
Equation 170. IMS MMTel AS Sh Redirect Request Success Ratio 147
Equation 171. IMS MMTel AS Sh Notification Request Success Ratio 147
Equation 172. IMS MMTel AS Subscribe Setup Success Ratio 149
Equation 173. IMS MMTel AS Dialog Event Notifier Subscribe Setup Success Ratio 149
Equation 174. IMS NW AS Precondition IW Setup Success Ratio 151
Equation 175. IMS NW AS Precondition External Failure Ratio 151
Equation 176. IMS NW AS Precondition IW to Session Setup Ratio 151
Equation 177. IMS MTAS Number of Registered IMS Users 153
Equation 178. IMS MMTel AS Number of Active Users 153
Equation 179. IMS MMTel AS Number of Simultaneous Sessions 153
Equation 180. IMS MMTel AS Number of Mobile Service Simultaneous Sessions 153
 Ericsson Internal
OPERAT. GUIDELINES 236 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 181. IMS SCC AS Number of Originating SCC from CS Simultaneous Sessions 153
Equation 182. IMS SCC AS Number of Originating SCC from PS Simultaneous Sessions 153
Equation 183. IMS SCC AS Number of Terminating SCC from CS Simultaneous Sessions 154
Equation 184. IMS SCC AS Number of Terminating SCC from PS Simultaneous Sessions 154
Equation 185. IMS SCC AS Number of Simultaneous Sessions 154
Equation 186. IMS MMTel AS Number of Active Subscription Sessions 154
Equation 187. IMS ST AS Number of SIP Trunking Simultaneous Sessions 154
Equation 188. IMS ST AS Number of SIP Trunking Simultaneous Originating Sessions per
PBX 154
Equation 189. IMS ST AS Number of SIP Trunking Simultaneous Terminating Sessions per
PBX 154
Equation 190. IMS MMTel AS Number of Currently Active Conferences 155
Equation 191. IMS MMTel AS Number of Conference Participants 155
Equation 192. IMS Conference AS Number of Currently Active Scheduled Conferences 155
Equation 193. IMS Conference AS Number of Scheduled Conference Participants 155
Equation 194. IMS SCC AS IP Multimedia Routing Numbers (IMRN) in use [%] 155
Equation 195. IMS MTAS Overload Control Duration [Seconds] 155
Equation 196. IMS MTAS Overload Control Periods 155
Equation 197. IMS MTAS Overload Control Values Average 155
Equation 198. IMS MTAS Overload Control Values Peak 156
Equation 199. IMS MGC SIP Incoming Sessions Success Ratio 158
Equation 200. IMS MGC SIP Outgoing Sessions Success Ratio 158
Equation 201. IMS MGC H.248 Session Setup Success Ratio 159
Equation 202. IMS MGC H.248 Session Completion Ratio 159
Equation 203. IMS MGC ISUP Incoming Sessions Success Ratio for PSTN Route 159
Equation 204. IMS MGC ISUP Outgoing Sessions Success Ratio for PSTN Route 159
Equation 205. IMS MGC Number of Simultaneous SIP Sessions 159
Equation 206. IMS MGC SIP Incoming Sessions [per second] 159
Equation 207. IMS MGC SIP Outgoing Sessions [per second] 160
Equation 208. IMS MGC Number of Simultaneous H.248 Sessions 160
Equation 209. IMS MGC H.248 Incoming Sessions [per second] 160
Equation 210. IMS MGC Number of Simultaneous ISUP Sessions for PSTN Route 160
Equation 211. IMS MGC ISUP Incoming Sessions for PSTN Route [per second] 160
Equation 212. IMS MGC ISUP Outgoing Sessions for PSTN Route [per second] 160
Equation 213. IMS A-SBG Initial Registration Success Ratio 162
Equation 214. IMS A-SBG Emergency Initial Registration Success Ratio 162
Equation 215. IMS A-SBG Reregistration and Deregistration Success Ratio 163
Equation 216. IMS A-SBG Re-registration Success Ratio 163
Equation 217. IMS A-SBG De-registration Success Ratio 163
Equation 218. IMS A-SBG Emergency Re-Registration Success Ratio 164
Equation 219. IMS A-SBG Initial Registration Time [milliseconds] 164
Equation 220. IMS SBG Incoming Session Set-up Success Ratio 165
Equation 221. IMS SBG Outgoing Session Set-up Success Ratio 165
Equation 222. IMS SBG Emergency Session Set-up Success Ratio 167
Equation 223. IMS SBG Incoming Priority Session Set-up Success Ratio 167
Equation 224. IMS SBG Outgoing Priority Session Set-up Success Ratio 167
Equation 225. IMS SBG Incomimg Session Answer to Seizure Ratio 167
Equation 226. IMS SBG Outgoing Session Answer to Seizure Ratio 167
Equation 227. IMS SBG Incoming S8HR Session Answer to Seizure Ratio 168
Equation 228. IMS SBG Outgoing S8HR Session Answer to Seizure Ratio 168
Equation 229. IMS SBG Session Completion Ratio 168
Equation 230. IMS SBG Dropped Sessions Ratio 169
 Ericsson Internal
OPERAT. GUIDELINES 237 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 231. IMS SBG SRVCC Access Transfer Success Ratio 169
Equation 232. IMS SBG Incoming Sessions Set-up Time [milliseconds] 169
Equation 233. IMS SBG Outgoing Sessions Set-up Time [milliseconds] 169
Equation 234. IMS SBG Incoming Subscribe Session Set-up Success Ratio 170
Equation 235. IMS SBG Outgoing Subscribe Session Set-up Success Ratio 170
Equation 236. IMS SBG Incoming MESSAGE Request Success Ratio 171
Equation 237. IMS SBG Outgoing MESSAGE Request Success Ratio 171
Equation 238. IMS SBG Media RTP Lost Packets Ratio 171
Equation 239. IMS SBG Media RTP Out of Sequence Packets Ratio 171
Equation 240. IMS SBG External BGCF Call Set-up Success Ratio 172
Equation 241. IMS SBG Initial Registration Failure 400 [per second] 172
Equation 242. IMS SBG Initial Registration Failure 403 [per second] 172
Equation 243. IMS SBG Initial Registration Failure 404 [per second] 172
Equation 244. IMS SBG Initial Registration Failure 421 [per second] 172
Equation 245. IMS SBG Initial Registration Failure 500 [per second] 172
Equation 246. IMS SBG Initial Registration Failure 503 [per second] 173
Equation 247. IMS SBG Initial Re-registration Failure 400 [per second] 173
Equation 248. IMS SBG Initial Re-registration Failure 403 [per second] 173
Equation 249. IMS SBG Initial Re-registration Failure 404 [per second] 173
Equation 250. IMS SBG Initial Re-registration Failure 421 [per second] 173
Equation 251. IMS SBG Initial Re-registration Failure 500 [per second] 173
Equation 252. IMS SBG Initial Re-registration Failure 503 [per second] 173
Equation 253. IMS SBG Session Set-up Failure BGF Resource Unavailability [per second]
173
Equation 254. IMS SBG SBG Session Set-up Failure Max Session Reached[per second] 174
Equation 255. IMS SBG Session Set-up Failure Release Signal Bearer[per second] 174
Equation 256. IMS SBG Session Set-up Failures SDP Validation Failed [per second] 174
Equation 257. IMS SBG Inc Session Set-up Failure 403 [per second] 174
Equation 258. IMS SBG Inc Session Set-up Failure 486 [per second] 174
Equation 259. IMS SBG Out Session Set-up Failure 403 [per second] 174
Equation 260. IMS SBG Out Session Set-up Failure 486 [per second] 174
Equation 261. IMS SBG Out Session Set-up Failure 603 [per second] 175
Equation 262. IMS SBG BGF Reselections [per second] 175
Equation 263. IMS SBG Initiated Session Release [per second] 175
Equation 264. IMS SBG Release Session Timer Expiry[per second] 175
Equation 265. IMS SBG Dialog Release Request Timeout [per second] 176
Equation 266. IMS SBG Session Release Signaling Bearer [per second] 176
Equation 267. IMS SBG Session Release Media Stop [per second] 176
Equation 268. IMS SBG SRVCC Rejected CS Transfer Attempts [per second] 176
Equation 269. IMS SBG SRVCC Inc Fallback Attempts [per second] 177
Equation 270. IMS SBG Outgoing Transaction Timeouts [per second] 177
Equation 271. IMS SBG Abnormal Termination from BGF [per second] 177
Equation 272. IMS SBG Hanging BGF Termination Events [per second] 177
Equation 273. IMS SBG BGF Call Failed [per second] 177
Equation 274. IMS SBG BGF Invalid Address [per second] 178
Equation 275. IMS SBG BGF No Resource [per second] 178
Equation 276. IMS SBG BGF Other Errors [per second] 178
Equation 277. IMS SBG BGF Protocol Errors [per second] 178
Equation 278. IMS SBG BGF Server Errors [per second] 178
Equation 279. IMS vEMe Originating RP Data Resp Success Ratio 194
Equation 280. IMS vEMe Terminating RP Data Resp Success Ratio 194
Equation 281. IMS vEMe MAP MO-FSM Out Success Ratio 194
 Ericsson Internal
OPERAT. GUIDELINES 238 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 282. IMS vEMe MAP MT-FSM Rec Success Ratio 195
Equation 283. IMS vEMe MAP MT-FSM Sent (Fallback to CS) Success Ratio 195
Equation 284. IMS vEMe Originating RP Data Reqs [per second] 196
Equation 285. IMS vEMe Terminating RP Data Sent [per second] 196
Equation 286. IMS vEMe MAP MO-FSM Out [per second] 196
Equation 287. IMS vEMe MAP MT-FSM Rec [per second] 196
Equation 288. IMS vEMe MAP MT-FSM Sent (Fallback to CS) [per second] 196
Equation 289. IMS Client SIP Response Success Ratio 197
Equation 290. IMS Server SIP Response Success Ratio 198
Equation 291. IMS CSCF Orig MESSAGE Success Ratio 198
Equation 292. IMS CSCF Term MESSAGE Success Ratio 198
Equation 293. IMS SBG SIP Response Success Ratio 200
Equation 294. IMS JavaSIP Register Success Ratio 200
Equation 295. IMS JavaSIP Message Success Ratio 200
Equation 296. IMS JavaSIP Invite Success Ratio 200
Equation 297. IMS JavaSIP Bye Success Ratio 201
Equation 298. IMS CSCF SIP Inbound Load Regulation Rejection Ratio 202
Equation 299. IMS JavaSIP Overload Rejection Ratio 203
Equation 300. IMS MGC SIP Call Congestion Ratio 203
Equation 301. IMS SBG SIP Overload Rejection Ratio 204
Equation 302. IMS SBG SIP Core Overload (throttling) Rejection Ratio 204
Equation 303. IMS SBG BGF Overload Rejection Ratio 204
Equation 304. IMS MTAS MRFC Overload Rejection Ratio 206
Equation 305. IMS MTAS SIP PSI Overload Rejection Ratio 206
Equation 306. IMS MTAS SIP Orig Requests Overload Rejection Ratio 207
Equation 307. IMS MTAS SIP Term Requests Overload Rejection Ratio 207
Equation 308. IMS MTAS SIP Presence Requests Overload Rejection Ratio 207
Equation 309. IMS SCC AS SIP Orig Requests Overload Rejection Ratio 207
Equation 310. IMS SCC AS SIP Term Requests Overload Rejection Ratio 207
Equation 311. IMS MTAS Priority Call Overload Rejection Ratio 207
Equation 312. IMS Diameter Received Requests Overload Discarded Ratio 210
Equation 313. IMS Diameter Sent Requests Overload Discarded Ratio 210
Equation 314. IMS TSP Signaling Link Load Sent at MTP-L2 Level Ratio 212
Equation 315. IMS TSP Signaling Link Load Received at MTP-L2 Level Ratio 212
Equation 316. IMS TSP Signaling Cumulative Duration of SL Congestion (Congestion Level
1) Seconds 212
Equation 317. IMS TSP Signaling Cumulative Duration of SL Congestion (Congestion Level
2) Seconds 212
Equation 318. IMS TSP Signaling Cumulative Duration of SL Congestion (Congestion Level
3) Seconds 213
Equation 319. IMS SS7 CAF M3UA Received Lost Data Messages in Congestion Ratio 213
Equation 320. IMS SS7 CAF M3UA Congestion Time [Seconds] 214
Equation 321. IMS SS7 CAF M3UA Received Signaling Congestion Messages [per second]
214
Equation 322. IMS SS7 CAF M3UA Received Congestion Indications from SCTP [per
second] 214
Equation 323. IMS Diameter Unsuccessful Received Requests Ratio 216
Equation 324. IMS Diameter Unsuccessful Sent Requests Ratio 216
Equation 325. IMS Diameter Malformed Received Requests Ratio 217
Equation 326. IMS Diameter Protcol Errors and Permanent Failures Ratio 217
Equation 327. IMS SBG Diameter Request Success Ratio 219
Equation 328. IMS SBG Diameter Permanent Failures [per second] 219
 Ericsson Internal
OPERAT. GUIDELINES 239 (239)
Prepared (also subject responsible if other) No.

ETXJHJE Jörgen Hjellström 1/154 43-HSC 113 10 Uen

Approved Checked Date Rev Reference

BDGSEAFB [Jerker Zetterlund] 2017-12-12 G

Equation 329. IMS SBG Diameter Transient Failures [per second] 219
Equation 330. IMS SBG Diameter Protocol Errors [per second] 219
Equation 331. IMS SBG Diameter Rx NPLI Success Ratio 220
Equation 332. IMS TSP Signaling Duration of Link Unavailability MTP-L3 Level Seconds221
Equation 333. IMS SS7 CAF M3UA Received Errors Ratio 221
Equation 334. IMS SS7 CAF M3UA Discarded Data Ratio 221
Equation 335. IMS SS7 CAF M3UA Sent Errors Ratio 222
Equation 336. IMS NIC Send Requests [KB per second] 223
Equation 337. IMS NIC Receive Requests [KB per second] 223
Equation 338. IMS NIC Send Collision Ratio 223
Equation 339. IMS NIC Send Error Ratio 224
Equation 340. IMS NIC Receive Error Ratio 224
Equation 341. IMS TIPC Tunnel Latency [microseconds] 225
Equation 342. IMS TIPC Send Requests [Packets per second] 225
Equation 343. IMS TIPC Receive Requests [Packets per second] 225
Equation 344. IMS TIPC Send Collision Ratio 225
Equation 345. IMS TIPC Send Drop Ratio 225
Equation 346. IMS TIPC Receive Drop Ratio 226
Equation 347. IMS BGFv Received Octets [per second] 226
Equation 348. IMS BGFv Peak Received Octets [per second] 226
Equation 349. IMS BGFv Sent Octets [per second] 227
Equation 350. IMS BGFv Peak Sent Octets [per second] 227
Equation 351. IMS BGFv Received Packets [per second] 227
Equation 352. IMS BGFv Peak Received Packets [per second] 227
Equation 353. IMS BGFv Sent Packets [per second] 227
Equation 354. IMS BGFv Peak Sent Packets [per second] 227
Equation 355. IMS BGFv Discarded Receiver Packets Ratio 227
Equation 356. IMS BGFv Discarded Receiver Packets [per second] 227
Equation 357. IMS BGFv Discarded Excessive Receiver Packets [per second] 227
Equation 358. IMS BGFv Discarded Sender Packets Ratio 228
Equation 359. IMS BGFv Discarded Sender Packets [per second] 228
Equation 360. IMS BGFv Discarded Sender Packets No Next Hop [per second] 228