Professional Documents
Culture Documents
HSS Counter Description
HSS Counter Description
HSS 17 - HP
Release 17
CMS-8200 HSS Counter
Description
A25001-A0006-A2875-02-76P1
Issue 02
CMS-8200 HSS Counter Description
The information in this document applies solely to the hardware/software product (“Product”) specified
herein, and only as specified herein. Reference to “Nokia” later in this document shall mean the respective
company within Nokia Group of Companies with whom you have entered into the Agreement (as defined
below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used except for the
purposes defined in the agreement between You and Nokia (“Agreement”) under which this document is
distributed. No part of this document may be used, copied, reproduced, modified or transmitted in any form
or means without the prior written permission of Nokia. If You have not entered into an Agreement
applicable to the Product, or if that Agreement has expired or has been terminated, You may not use this
document in any manner and You are obliged to return it to Nokia and destroy or delete any copies thereof.
The document has been prepared to be used by professional and properly trained personnel, and You
assume full responsibility when using it. Nokia welcomes your comments as part of the process of
continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or statements
concerning the suitability, capacity, fitness for purpose or performance of the Product are given solely on
an “as is” and “as available” basis in this document, and Nokia reserves the right to change any such
information and statements without notice. Nokia has made all reasonable efforts to ensure that the
content of this document is adequate and free of material errors and omissions, and Nokia will correct
errors that You identify in this document. Nokia's total liability for any errors in the document is strictly
limited to the correction of such error(s). Nokia does not warrant that the use of the software in the Product
will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL
OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS
DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS
FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed
to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in this document
may be trademarks of their respective owners.
f Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this
product and only after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and
Environmental Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We
would like to encourage you as our customers and users to join us in working towards a cleaner, safer
environment. Please recycle product packaging and follow the recommendations for power use and proper
disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we
offer, please contact us at Nokia for any additional information.
Table of Contents
This document has 218 pages
4.3 ASH.............................................................................................. 99
4.4 CTR............................................................................................ 100
4.5 ARQ........................................................................................... 108
4.6 ATI.............................................................................................. 111
4.7 LCR............................................................................................ 114
4.8 LUP.............................................................................................116
4.9 MTC........................................................................................... 121
4.10 ORREQ...................................................................................... 122
4.11 OVERLOADHANDLING.............................................................124
4.12 RDR........................................................................................... 125
4.13 RUR........................................................................................... 126
4.14 SAI............................................................................................. 128
4.15 SMS........................................................................................... 128
4.16 TRIGGERFRAMEWORK........................................................... 132
4.17 UMSTP.......................................................................................134
4.18 UTIMACO-HSM......................................................................... 216
Index.......................................................................................... 218
List of Figures
Figure 1 New KPI Editor window...................................................................... 13
Figure 2 Integrated calculator........................................................................... 15
Figure 3 Call Flow for the KPI Successful Location Update Rate Towards HLR
(SLURH)............................................................................................. 18
Figure 4 Call Flow for the KPI Successfully Cancelled Location Rate Triggered
by HLR (SCLRTH).............................................................................. 19
List of Tables
Table 1 Issue 2.................................................................................................. 7
Table 2 Notational conventions....................................................................... 10
Table 3 Columns in the KPI tab.......................................................................13
Table 4 Columns in the Logical counters tab.................................................. 14
Table 5 Performance measurement interval................................................... 21
Table 6 CX.......................................................................................................22
Table 7 DIA......................................................................................................23
Table 8 DIAMETERDISP.................................................................................60
Table 9 DNSPH............................................................................................... 81
Table 10 IMSLB.................................................................................................81
Table 11 LCC.................................................................................................... 83
Table 12 RTTA...................................................................................................83
Table 13 RTTA...................................................................................................87
Table 14 S6A.....................................................................................................90
Table 15 SH.......................................................................................................93
Table 16 SWX................................................................................................... 94
Table 17 ACTPADAPTER................................................................................. 96
Table 18 ANZ.................................................................................................... 98
Table 19 ASH.................................................................................................... 99
Table 20 ctr......................................................................................................100
Table 21 ARQ..................................................................................................108
Table 22 ATI.....................................................................................................111
Table 23 LCR...................................................................................................114
Table 24 LUP................................................................................................... 116
Table 25 MTC..................................................................................................121
Table 26 ORREQ............................................................................................ 122
Table 27 OVERLOADHANDLING................................................................... 124
Table 28 RDR..................................................................................................125
Table 29 RUR..................................................................................................126
Table 30 SAI....................................................................................................128
Table 31 SMS..................................................................................................128
Table 32 TRIGGERFRAMEWORK................................................................. 132
Table 33 UMSTP............................................................................................. 134
Table 34 UTIMACO-HSM................................................................................216
1 About this document
This document provides information on performance counters of CMS-8200 HSS. It
provides details for monitoring the performance data of the elements in the network that
can provide the operator with important information about the system.
1.1 Intended audience
This document addresses the administrators/operators who want to observe and analyze
the system behavior. Understanding system behavior helps administrators/operators to
optimize the system behavior and increase the end-user perceived service quality.
1.2 Change history
1.2.1 Issue 2
The following modifications were made in this document for this issue.
Table 1 Issue 2
Section Change
UMSTP • AdminPNAIn5001
• AdminPNAIn5012
• AdminPNAIn5107
• CXPPRDueToCXPPACntr
• CxLIAOut5003B
• CxLIAOut5003
• CxLIAOut4002
• CxLIAOut2003
• CxLIAOut5001
• CxMAAOut5003
• CxMAAOut5002
• CxMAAOut4002
• CxMAAOut5005
• CxMAAOut5001
• CxMAAOut5006
• CxPNAIN5012
• CxPNAIN5107
• CxPNAIn5001
• CxPPAIn5001
• CxPPAIn5008
• CxPPAIn5009
• CxPPAIn5012
• CxPPAInNoSuccess
• CxPPATimeout
• CxPPAsuccess
• CxRTAIn5001
• CxRTAIn5012
• CxRTAInNoSuccess
• CxRTATimeout
• CxRTAsuccess
• CxResOCOVLendedSent
• CxRespNoOCOVLSent
• CxRespOCOVLSent
• CxSAAOut4002
• CxSAAOut5001
• CxSAAOut5002
• CxSAAOut5003
• CxSAAOut5005
• CxSAAOut5007
• CxSAAOut5009
• CxSAAOut5011
• CxUAAEmerReg
• CxUAAOtherErrEmerReg
• CxUAAOut4002
• CxUAAOut5001
• CxUAAOut5001EmerReg
• CxUAAOut5002
• CxUAAOut5002EmerReg
• CxUAAOut5003
• CxUAAOut5003B
• CxUAAOut5004
• CxUAAOut5005
• CxUAAOut5012EmerReg
• HdCLRIn
• HdCLROut
• HdPNRIn
• HdPUROut
• HdSNROut
• HdUDROut
• InvalidNSRDataRef
• MapEsrvccDtrOrreq
• MapVccRegularOrreq
• S6AuthInfoReqCntr
• S6IDRByShPURCtr
• S6PNAIn5001
• S6PNAIn5012
• S6PNAIn5107
• S6ReqOCSupFeatRcvd
• S6RespNoOCOVLSent
• S6RespOCOVLSent
• S6aIDAIn5001ByAdmin
• S6aIDAIn5001BySWx
• S6aIDAIn5001BySh
• S6aIDAIn5012ByAdmin
• S6aIDAIn5012BySWx
• S6aIDAIn5012BySh
• S6aULRHPLMNRequest
• S6aULRVPLMNRequest
• S6dULRHPLMNRequest
• S6dULRVPLMNRequest
• S6mReqOCSupFeatRcvd
• S6mResOCOVLendedSent
• S6mRespNoOCOVLSent
• S6mRespOCOVLSent
• S6mSIRIn
• S6mnSIAOutOther
• S6mnSIRIn
• S6nSIRIn
• SLhRIAOut4201
• SLhRIAOut5001
• ShPNAIn5012
• ShPNAIn5107
• ShPNAInDataErr
• ShPNAS6Success
• ShPNAShfailure
• ShPNAShsuccess
• ShPNASubsAdminfailure
• ShPNASubsAdminsuccess
• ShPNRMultSI
• ShPUAOut5011
• ShPURMultSI
• ShReqOCSupFeatRcvd
• ShResOCOVLendedSent
• ShRespNoOCOVLSent
• ShRespOCOVLSent
• ShSNAOut4100
• ShSNAOut5011
• ShUDAOut5004
• ShUDAOut5011
• WxEAPAKAAuthReqCntr
• WxEAPSIMAuthReqCntr
• WxMAAOut4002
• WxMAAOut5001
• WxMAAOut5004
• WxMAAOut5041
• WxMAAOut5043
• WxMAASuccess
• ZhMAAOut5401
1.2.2 Issue 1
1.3 Notational conventions
g
Notes that provide additional information or helpful suggestions that
apply to the subject text
1.4 Related documents
1.5 Contact us
For assistance regarding the use and maintenance of Nokia products, contact the
Customer Interaction Team (CIT).
2 Key performance indicators
Monitoring the performance data and the load of the elements in the network can
provide the operator with important information about the system. It helps the network
operator to detect and eliminate bottlenecks and vulnerable points. Thus, it helps to
maintain and improve the performance of the system and protects it from overload.
Reporter is a tool or a set of functions with the NetAct which allows the user to supervise
or monitor performance of the entire system and trigger alarm events if threshold values
are exceeded. It displays the counter in text, graph and offers the possibility to export the
counter values in CSV and Excel file for more post processing. The Reporter has the
functionality that allows the user to receive performance data from all network elements
within the NetAct environment. These data are collected for each cluster/host.
KPI definition is used to define indicators to monitor the performance of the system. The
KPI counters are defined by combining counters through a definition that contains the
counter name, the expression how to calculate the counters (total sum, average sum,
max, min) and the list of network elements for which the KPI counter is to be calculated.
g Note: Performance indicators are counters that register performance data in the
different Network Elements (NEs). Each time the event occurs and each time you start
to measure an event, the counter is incremented. The Performance Indicators (PI) are
in charge of registering performance data and this data is the base for the calculation of
a KPI.
2.1 Administering key performance indicators
The basic performance indicator (PI) defined by NetAct do not always meet all
requirements. Therefore, you can use the KPI editor to define key performance
indicators (KPI) . KPIs are calculated by using algorithms based on basic performance
counters and allow you to customize the performance views and define performance
counters distributed over NEs. A customized KPI can be used as any basic PI. To create
KPIs, in the NetAct Reporter window, select Report Editor tab and then Click ► New
Link. A KPI can consist of the counters of one network element and/or of different
network elements. The KPI expression contains arithmetic operators, such as add (+),
subtract (-), multiply (*), divide (/), numbers (0-9), decimal points (.) and basic functions,
such as minimum (MIN), maximum (MAX), average (AVG), and sum (SUM). In addition
to creating KPI you can also display and modify existing KPIs.
2.2 How to create a KPI
The table shows the data corresponding to the folder selected in the browser tree,
KPIs, and Logical counters depending on the table tab. The main purpose is to allow
reusing this data in the KPI to be created.
The following table describes the available columns in the KPI tab:
Table 3 Columns in the KPI tab
Name Type Description
The following table describes the available columns in the Logical counters tab:
Table 4 Columns in the Logical counters tab
Name Type Description
To create a new KPI, define the type of access in the Access Control drop-down list.
There are following options:
– Private - Only the current user is able to access the defined KPI.
– Public Read - Any user can access the defined KPI.
– Public Modify - Any user can access the defined KPI and also modify the
settings.
For more information about the browsing functionalities, see the online help.
To enter the Formula field data, use the integrated calculator as input.
Click on the Advanced Calculator collapsed panel, extra operations are displayed
with the available functions of the formula.
2.3 Examples of KPIs
The following Key Performance Indicators (KPI) are some examples that can help the
user to monitor the data in the elements of the IMS network giving an idea of the service
quality. To make these measurements there are defined base counters that monitor at
the NE CFX-5000 (P-CSCF, I-CSCF and S-CSCF) and CMS-8200 HSS. The NetAct is
the central point, where all the KPIs are visible to the customer. The NetAct fetches all
input counters from the different network elements and integrates those in the KPI
equation. KPIs are then visualized in the NetAct GUI. All currently available KPIs are NE-
related KPIs. NE-related KPIs monitor the behavior of the subscribers. These KPIs apply
for P-CSCF and S-CSCF.The KPIs can be created at NetAct using the counters available
there. For more information on how to create a KPI see the How to create a KPI section.
2.3.1 Global CPU Load Level Cluster 01
Description Presents the current value of the CPU load level on the CMS-8200 HSS
cluster element 1.
Detailed description
This gauge Load Level Cluster 01 for the HSS provides the current HSS load level at the
HSS cluster element number 1.
The HSS Load Level assumes one of eleven possible load levels in order to characterize
the current degree of HSS load. Depending on both the number of messages in queues
and the current CPU load, a process-specific load level is calculated. An HSS Load
Level above 0 is determined only if the queues reach certain (high) levels of fill and the
CPU load is above 91% at the same time. The HSS Load Level comprises the number
range between the values 0 to 10.
Load level values:
0 no overload
The HSS Load Level is calculated every 250 milliseconds. For the calculation of the HSS
Load Level a process specific load level in conjunction with a weighted algorithm is used.
This one takes into account the total number of messages in all queues and the number
of messages in the input queue of the process under consideration. The result is
normalized to the range of 0 to 10.
In order to avoid fast switch up and switch down of the HSS Load Level that might
potentially cause oscillations, the possible stepping between load levels during
subsequent measurement intervals is limited. For instance, switching from HSS Load
Level 0 to 10 (the same applies also for the opposite direction) requires several
intermediate measurement intervals.
2.3.2 Global CPU Load Level Cluster 02
Description Presents the current value of the CPU load level on CMS-8200 HSS cluster
element 2.
Detailed description
This gauge Load Level Node 2 for the HSS provides the current HSS load level at the
HSS cluster element number 2.
The HSS Load Level assumes one of eleven possible load levels in order to characterize
the current degree of HSS load. Depending on both the number of messages in the
process-specific input queues and the current (common) CPU load, a process-specific
load level is calculated.
A HSS Load Level above 0 is determined only if the queues reach certain (high) fill levels
and the CPU load is above 91% at the same time. The HSS Load Level comprises the
number range between the values 0 to 10.
Load level values:
0 no overload
The HSS Load Level is calculated every 250 milliseconds. For the calculation of the HSS
Load Level a process specific load level in conjunction with a weighted algorithm is used.
This one takes into account the total number of messages in all queues and the number
of messages in the input queue of the process under consideration. The result is
normalized to the range of 0 to 10.
In order to avoid fast switch up and switch down of the HSS Load Level that might
potentially cause oscillations, the possible stepping between load levels during
subsequent measurement intervals is limited. For instance, switching from HSS Load
Level 0 to 10 (the same applies also for the opposite direction) requires several
intermediate measurement intervals.
2.3.3 OS based KPIs System Resources
User
Description Presents the percentage rate of the utilization of the CPU load for cluster
element 1/2 for user tasks.
System
Description Presents the percentage rate of the utilization of the CPU load for cluster
element 1/2 for system tasks.
Idle
Description Presents the percentage rate of the disuse of the CPU load for cluster
element 1/2.
Detailed description
• User = User cpu time (or) % CPU time spent in user space
• System = System cpu time (or) % CPU time spent in kernel space
• Idle = Idle cpu time (or) % CPU time spent idle
The most important gauges are directly used as KPIs and comprise three values
representing the usage rate of CPU load for user tasks, system tasks, and the idle rate in
percent.
2.3.4 Successful Location Update Rate Towards HLR (SLURH)
Description Successful Location Update Rate towards HLR (SLURH) measures the ratio
between the number of successful location updates to the HLR and the total
number of location update requests sent to the HLR.
Figure 3 Call Flow for the KPI Successful Location Update Rate Towards HLR
(SLURH)
MCF-CSCF MCF-HSS HLR
VCCsubscribedUE
RegisteredinIMSdomain Sh-SNR
MAPULR
MAPISD
MAPEntryR-ISD
MAPULA
Sh-SNR
Detailed Description
The counter LupUlSuccResFromHlr represents the number of successful location update
responses received from HLR. This counter is incremented at HSS after receiving a
successful location update response from HLR.
The counter LupUlReqSentToHlr represents number of successful location update
request sent to HLR. This counter is incremented at HSS after successfully sending
location update request to HLR.
2.3.5 Successfully Cancelled Location Rate Triggered by HLR
(SCLRTH)
Figure 4 Call Flow for the KPI Successfully Cancelled Location Rate Triggered by
HLR (SCLRTH)
MCF-CSCF MCF-HSS HLR VLR
VCCsubscribed.
UERoamedinto
MAP-ULR CSDomain.
MAP-ISD
MAP-R-ISD
MAP-ULA
MAP-CLR
MAP-CLA
Detailed Description
The counter LupClReqRecdFromHlr represents the number of cancel location requests
received from HLR successfully. This counter is incremented at HSS after receiving a
cancel location request successfully from HLR.
The counter LupClSuccResToHlr represents the number of cancel location responses
sent to HLR successfully. This counter is incremented at HSS after sending cancel
location response successfully to HLR.
2.3.6 Cx UAR success rate
Description Success rate CxUAR is the ratio between successfully sent CxUAA and the
total number of received CxUAR
2.3.7 Cx MAR success rate
Description Success rate CxMAR is the ratio between successfully sent CxMAA and the
total number of received CxMAR
2.3.8 Cx SAR success rate
Description Success rate CxSAR is the ratio between successfully sent CxSAA and the
total number of received CxSAR
2.3.9 Cx LIR success rate
Description Success rate CxLIR is the ratio between successfully sent CxLIA and the
total number of received CxLIR
2.3.10 Sh UDR success rate
Description Success rate Sh UDR is the ratio between successfully sent Sh UDA and the
total number of received Sh UDR
2.3.11 Sh PUR success rate
Description Success rate Sh PUR is the ratio between successfully sent Sh PUA and the
total number of received Sh PUR
2.3.12 Sh SNR success rate
Description Success rate Sh SNR is the ratio between successfully sent Sh SNA and the
total number of received Sh SNR
3 Common counter data
The chapter lists the different counters available.
The following counters are applicable for both S6a and S6d:
• S6aAIAsuccess
• S6aDSR
• S6aCLR
• S6aIDR
• S6aULAsuccess
g Note:
The following measurement interval details is applicable to all the counters in Common
counter data and HSS counter data.
3.1 CX
Table 6 CX
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
Table 6 CX (Cont.)
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
responde
d with
RESULT_
CODE_DI
AMETER
_UNABLE
_TO_DEL
IVER as
the error
message
3.2 DIA
Table 7 DIA
Measure
ment
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
aligned
on the 4-
byte
boundar
y.
Since of
Sys In Connecti
Load ons
which
were
rejected
due to
the
system
overload.
BUSY
response
is sent
out
queue
being full
or
Unable
to send
message
to roles.
worker
queue is
full
ropped
ShSNRD
ropped
worker
queue is
full
due to
an
overload
situation
Server
Assignm
ent
Request
message
s which
were
blocked
due to
an
overload
situation
due to
an
overload
situation
_BUSY Cx
to CX Server
SAR Assignm
ent
Request
message
s which
were
blocked
due to
an
overload
situation
an
overload
situation
to
1.000.00
0 bytes
on the number
eth0 of
interface megabyt
es
received
on the
MAC
level on
the
physical
Ethernet
port
eth0.
One MB
is equal
to
1.000.00
0 bytes
megabyt
es
received
on the
MAC
level on
the
physical
Ethernet
port
eth2.
One MB
is equal
to
1.000.00
0 bytes
received
on the
MAC
level on
the
physical
Ethernet
port
eth4.
One MB
is equal
to
1.000.00
0 bytes
MAC
level on
the
physical
Ethernet
port
eth6.
One MB
is equal
to
1.000.00
0 bytes
incremen
t the
counter
sender
queue
full. This
counter
is not
applicabl
e for
DRA
to role
process.
This
counter
is not
applicabl
e for
DRA
sender
queue
full. This
counter
is not
applicabl
e for
DRA
sender
queue
full. This
counter
is not
applicabl
e for
DRA
send fail
to role
process
and
queue
full. This
counter
is not
applicabl
e for
DRA
on was
down for
all the
establish
ed
diameter
initiator
connecti
ons.
ER_TOO
_BUSY
(3004)
because
of
overload
at HSS.
This
counter
is not
applicabl
e for
DRA.
3.3 DIAMETERDISP
Table 8 DIAMETERDISP
Measure
ment type
Counter Name PO/CP Descrip Type XML export Supp Networ
O Label tion counter name orted k
as manage
expor ment
ted system
count
er
unknow
n
diameter
messag
es
(unknow
n
operatio
n type,
respons
e
messag
e which
cannot
be
correlate
to a
request
messag
e,
unknow
n
comman
ds).
Handler
s
because
it was
not
possible
to send
out the
messag
e.
could
not be
process
es within
time
Sh-
interface
in UDA
(result
code
5102 in
Experim
ental-
Result-
Code
AVP)
received
at the
Sh-
interface
in UDA
2001 in
Result-
Code
AVP)
received
at the
Sh-
interface
in PUA
Sh-
interface
in PUA
(result
code
5103 in
Experim
ental-
Result-
Code
AVP)
received
at the
Sh-
interface
in PUA
Code
AVP)
received
at the
Sh-
interface
in PUA
Sh-
interface
in SNA
(result
code
5106 in
Experim
ental-
Result-
Code
AVP)
received
at the
Sh-
interface
in SNA
the Sh-
interface
in PNA
messag
es
(result
code
5100 in
Experim
ental-
Result-
Code
AVP)
sent at
the Sh-
interface
in PNA
where
the
mandato
ry AVP
is
missing.
c Peer DID01
Discove for
ry Dynamic
Peer
Discover
y.
Diamete
r
connecti
on
graceful
shutdow
n
procedur
e.
3.4 DNSPH
Table 9 DNSPH
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
3.5 IMSLB
Table 10 IMSLB
Counter PO/CP O Descripti Type XML Supporte Network Measure
Name Label on export d as managem ment type
counter exported ent
name counter system
Connecte
d to Active
LB
3.6 LCC
Table 11 LCC
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as managem
counter exported ent
name counter system
3.7 RADIUSDISP
Table 12 RTTA
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as managem
counter exported ent
name counter system
n
successful
” event
registratio
n failed”
event
“Internal
Statistics”
event
3.8 RTTA
Table 13 RTTA
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as managem
counter exported ent
name counter system
registratio
n
successful
” event
based on
“SIP re-
registratio
n failed”
event
received
unknown
messages
.
3.9 S6A
Table 14 S6A
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
_UNABLE
_TO_DEL
IVER as
the error
message
3.10 SH
Table 15 SH
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
3.11 SWX
Table 16 SWX
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
4 HSS counter data
The chapter lists the different counters available.
4.1 ACTPADAPTER
Table 17 ACTPADAPTER
Counter Name PO/CP Descriptio Type XML Suppor Networ Measur
O Label n export ted as k ement
counter exporte manage type
name d ment
counter system
a
resynchron
ization
procedure.
4.2 ANZ
Table 18 ANZ
Counter Name PO/CPO Descript Type XML Support Network Measur
Label ion export ed as manage ement
counter exporte ment type
name d system
counter
4.3 ASH
Table 19 ASH
Counter PO/CP O Descripti Type XML Supporte Network Measure
Name Label on export d as managem ment type
counter exported ent
name counter system
4.4 CTR
Table 20 ctr
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
peer on
diameter
interface.
R_SUCC
ESS per
peer on
diameter
interface.
DIAMETE
R_SUCC
ESS per
peer on
diameter
interface.
result-
code
DIAMETE
R_SUCC
ESS per
peer on
diameter
interface.
g No
te:
Sa
me
can
be
foll
ow
ed
for
the
bel
ow
cou
nte
rs
Sh
Pe
erS
NR
Su
cce
ss
Sh
Pe
erP
NR
Su
cce
ss
Sh
Pe
erP
UR
Su
cce
s
peer on
diameter
interface.
4.5 ARQ
Table 21 ARQ
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
Request
responses
received
from
1xHLR.
IS41 MAP
ASReport
Request
sent to
1xHLR.
MAP
ASReport
Request
responses
sent to TP
(Transacti
on
Processin
g process
of HSS).
4.6 ATI
Table 22 ATI
Counter Name PO/CPO Descript Type XML Support Network Measur
Label ion export ed as manage ement
counter exporte ment type
name d system
counter
tion
requests
for which
there
was no
respons
e from
HLR
within
specified
time
frame.
was
unable
to send
to TP.
4.7 LCR
Table 23 LCR
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
received continue
from IS41
1xHLR MAP
Location
Request
respons
es
received
from
1xHLR.
Request
respons
es sent
to HSS-
TP.
4.8 LUP
Table 24 LUP
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
were
sent to
HLR.
requests
that
were
sent to
HSS-TP.
4.9 MTC
Table 25 MTC
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
utingInfo
Respons
es sent
to HSS-
TP.
4.10 ORREQ
Table 26 ORREQ
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
to
1xHLR
or SCP.
4.11 OVERLOADHANDLING
Table 27 OVERLOADHANDLING
Counter Name PO/CPO Descript Type XML Support Network Measur
Label ion export ed as manage ement
counter exporte ment type
name d system
counter
level of
an
Applicati
on VM
4.12 RDR
Table 28 RDR
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
Requests
sent to
HSS-TP.
4.13 RUR
Table 29 RUR
Measur
ement
Counter Name PO/CPO Descript Type XML Support Network type
Label ion export ed as manage
counter exporte ment
name d system
counter
es sent success
to IS41
1xHLR MAP
Routing
Request
respons
es sent
to
1xHLR.
4.14 SAI
Table 30 SAI
Counter Name PO/CPO Descript Type XML Support Network Measur
Label ion export ed as manage ement
counter exporte ment type
name d system
counter
4.15 SMS
Table 31 SMS
Counter Name PO/CPO Descript Type XML Support Network Measur
Label ion export ed as manage ement
counter exporte ment type
name d system
counter
Short
Messag
es sent
to SMS
Center.
from
SMS
Center.
4.16 TRIGGERFRAMEWORK
Table 32 TRIGGERFRAMEWORK
Counter Name PO/CP Descripti Type XML Support Network Measur
O Label on export ed as manageme ement
counter exporte nt system type
name d
counter
only
subscribe
r).
4.17 UMSTP
Table 33 UMSTP
Counte PO/CPO Label Description Ty XML Su Ne Me
r Name pe export pp tw as
counte ort or ur
r name ed k em
as ma ent
exp na typ
ort ge e
ed me
cou nt
nte sy
r ste
m
ShUDR Number of UDR This counter indicates the number Co ShUDR Yes Ne U
PDNG Requests received of received UDR requests on the unt PDNG tAc MS
WreqRe for PDN-GW info Sh interface retrieving project er WreqR t TP
cvd retrieval. specific PDN-GW information. ecvd
S6aIDA Received S6a IDA Count of S6a IDAs for which P- Co S6aIDA Yes Ne U
FailPCS failure for 3GPP P- CSCF Restoration failed. unt FailPC tAc MS
CFRest CSCF Restoration. er SCFRe t TP
or stor
S6dIDA Received S6d IDA Count of S6d IDAs for which P- Co S6dIDA Yes Ne U
FailPCS failure for 3GPP P- CSCF Restoration failed. unt FailPC tAc MS
CFRest CSCF Restoration. er SCFRe t TP
or stor
CxPPR CxPPR Triggered Counts the total number of sent Co CxPPR Yes Ne U
BySubs by Subscriber Cx push profile request messages unt BySubs tAc MS
AdminC Admin that are triggered by Subscriber er Admin t TP
ntr Administration. Cntr
CxRTR Triggered by Cx- Counts the total number of sent Co CxRTR Yes Ne U
ByCxM MA Cx registration termination request unt ByCxM tAc MS
ACntr messages that are triggered by er ACntr t TP
the Cx multimedia authentication
handling.
ShPNR Triggered by other Counts the total number of sent Co ShPNR Yes Ne U
ByShCn Sh Messages Sh push notification request unt ByShC tAc MS
tr messages that are triggered by Sh er ntr t TP
message handling.
CxLIAsu Successful Cx LIA Counts the number of Cx LIA with Co CxLIAs Yes Ne U
ccess sent DIAMETER_SUCCESS. unt uccess tAc MS
er t TP
CxUser Cx UAA with Counts the total no. of Cx-UAA Co CxUser Yes Ne U
AuthErr DIAMETER_UNAB messages that were not unt AuthErr tAc MS
Cntr LE_TO_COMPLY processed successfully due to er Cntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
CxServ Cx SAA with Counts the total no. of Cx-SAA Co CxServ Yes Ne U
erAssig DIAMETER_UNAB messages that were not unt erAssig tAc MS
nErrCntr LE_TO_COMPLY processed successfully due to er nErrCnt t TP
some internal errors(Unknown DB r
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
CxLocIn Cx LIA with Counts the total no. of Cx-LIA Co CxLocI Yes Ne U
foErrCnt DIAMETER_UNAB messages that were not unt nfoErrC tAc MS
r LE_TO_COMPLY processed successfully due to er ntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
CxMulti Cx MAA with Counts the total no. of Cx-MAA Co CxMulti Yes Ne U
mAuthE DIAMETER_UNAB messages that were not unt mAuth tAc MS
rrCntr LE_TO_COMPLY processed successfully due to er ErrCntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
RadAcc Rad Acc Req Start Counts the total number of Co RadAc Yes Ne U
ountReq msgs not processes RADIUS accounting request unt countR tAc MS
StartErr successfully START messages, which could er eqStart t TP
not be processed successfully. Err
RadAcc Rad Acc Req Stop Counts the total number of Co RadAc Yes Ne U
ountReq msgs not processes RADIUS accounting request unt countR tAc MS
StopErr successfully STOP messages, which could not er eqStop t TP
be processed successfully. Err
ShUser Sh UDA with Counts the total no. of Sh-UDA Co ShUser Yes Ne U
DataErr DIAMETER_UNAB messages that were not unt DataErr tAc MS
Cntr LE_TO_COMPLY processed successfully due to er Cntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
ShProfU Sh PUA with Counts the total no. of Sh-PUA Co ShProf Yes Ne U
pdateEr DIAMETER_UNAB messages that were not unt Update tAc MS
rCntr LE_TO_COMPLY processed successfully due to er ErrCntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
ShSubs Sh SNA with Counts the total no. of Sh-SNA Co ShSub Yes Ne U
cNotifEr DIAMETER_UNAB messages that were not unt scNotif tAc MS
rCntr LE_TO_COMPLY processed successfully due to er ErrCntr t TP
some internal errors(Unknown DB
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
CxPPR Cx Push Profile Counts the total number of errors Co CxPPR Yes Ne U
NotPoss Requests not which occurred during processing unt NotPos tAc MS
ibleCntr processed of CxPPR, due to no Diameter er sibleCn t TP
successfully connection available to the S- tr
CSCF or message send failed to
DIAMETER process
CxPPA Cx Push Profile Counts the total number of errors Co CxPPA Yes Ne U
ErrCntr Answers not while processing of a Cx push unt ErrCntr tAc MS
processed profile answer message. The er t TP
successfully possible errors are INVALID
RESPONSE RECEIVED and
Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
InvalidN Invalid NSR data Counts the number of invalid Co Invalid Yes Ne U
SRData reference references to NSR data identified unt NSRDa tAc MS
Ref when reading an individual er taRef t TP
subscriber profile
TpIntErr Message sent failed Counts the total number of internal Co TpIntEr Yes Ne U
Cntr due to internal error (HSS-TP) errors, when further unt rCntr tAc MS
processing of messages is er t TP
stopped.
MapAti Any Time Counts the total number of sent Co MapAti Yes Ne U
ReqCntr Interrogation MAP (Mobile Application Part) unt ReqCnt tAc MS
Requests AnyTimeInterrogation request er r t TP
messages.
MapSri Send Routing Info Counts the total number of sent Co MapSri Yes Ne U
ReqCntr Requests MAP (Mobile Application Part) unt ReqCnt tAc MS
SendRoutingInfo request er r t TP
messages.
MapUpd Update Location Counts the total number of sent Co MapUp Yes Ne U
ateLocR Requests MAP (Mobile Application Part) unt dateLo tAc MS
eqCntr UpdateLocation request er cReqC t TP
messages. ntr
MapClR Outgoing Cancel Counts the total number of sent Co MapCl Yes Ne U
eqToSg Location Requests MAP (Mobile Application Part) unt ReqTo tAc MS
snCntr CancelLocation request er SgsnC t TP
messages. ntr
MapCan MAP Cancel Loc Counts the total number of sent Co MapCa Yes Ne U
cLocErr Req not processes error MAP (Mobile Application unt ncLocE tAc MS
Cntr successfully Part) CancelLocation response er rrCntr t TP
messages.
MapMtF MAP MT Forward Counts the total number of sent Co MapMt Yes Ne U
orwardS SM not processes error MAP (Mobile Application unt Forwar tAc MS
MErrCnt successfully Part) MT Forward SM response er dSMErr t TP
r messages. Cntr
MapAti MAP Any Time Intr Counts the number of MAP Co MapAti Yes Ne U
NotPoss not possible to (Mobile Application Part) unt NotPos tAc MS
ibleCntr Send AnyTimeInterrogation request er sibleCn t TP
messages which could not be sent tr
out from HSS.
MapSai MAP Send Auth Counts the number of MAP Co MapSai Yes Ne U
NotPoss Info not possible to (Mobile Application Part) unt NotPos tAc MS
ibleCntr Send SendAuthenticationInfo request er sibleCn t TP
messages which could not be sent tr
out from HSS.
MapSri MAP Send Routing Counts the number of MAP Co MapSri Yes Ne U
NotPoss Info not possible to (Mobile Application Part) unt NotPos tAc MS
ibleCntr Send SendRoutingInfo request er sibleCn t TP
messages which could not be sent tr
out from HSS.
MapUL MAP Update Loc Counts the number of MAP Co MapUL Yes Ne U
NotPoss Req not possible to (Mobile Application Part) unt NotPos tAc MS
ibleCntr Send UpdateLocation request er sibleCn t TP
messages which could not be sent tr
out from HSS.
MapClR MAP Cancel Loc Counts the number of MAP Co MapCl Yes Ne U
eqNotP Req not Possible to (Mobile Application Part) Cancel unt ReqNot tAc MS
osCntr send Location request messages which er PosCnt t TP
could not be sent out from HSS. r
MapAti Unsuccessful MAP Counts the total number of errors Co MapAti Yes Ne U
RespErr ATI Res received while waiting for or processing of a unt RespEr tAc MS
MAP (Mobile Application Part) er r t TP
AnyTimeInterrogation response
messages (timeout on receiving
MAP AnyTimeInterrogation
response, invalid response
received and so on).
MapSai Unsuccessful MAP Counts the total number of errors Co MapSai Yes Ne U
RespErr SAI Res received while waiting for or processing of a unt RespEr tAc MS
MAP (Mobile Application Part) er r t TP
SendAuthenticationInfo response
messages (timeout on receiving
MAP SendAuthenticationInfo
response, invalid response
received and so on).
MapSri Unsuccessful MAP Counts the total number of errors Co MapSri Yes Ne U
RespErr SRI Res received while waiting for or processing of a unt RespEr tAc MS
MAP (Mobile Application Part) er r t TP
SendRoutingInfo response
messages (timeout on receiving
MAP SendRoutingInfo response,
invalid response received and so
on).
MapUpd Unsuccessful MAP Counts the total number of errors Co MapUp Yes Ne U
ateLocR UL Res received while waiting for or processing of a unt dateLo tAc MS
espErr MAP (Mobile Application Part) er cResp t TP
UpdateLocation response Err
messages (timeout on receiving
MAP UpdateLocation response,
invalid response received and so
on).
MapMo Unsuccessful MAP Counts the total number of errors Co MapMo Yes Ne U
Forward MO Forward SM while waiting for or processing of a unt Forwar tAc MS
SMRes Res received MAP (Mobile Application Part) MO er dSMRe t TP
pErr Forward SM response messages spErr
(timeout on receiving MAP MO
Forward SM response, invalid
response received and so on).
MapLup Unsuccessful MAP Counts the total number of errors Co MapLu Yes Ne U
ClResp Cancel Location while waiting for or processing of a unt pClRes tAc MS
Err Res received MAP (Mobile Application Part) er pErr t TP
Cancel Location response
messages (timeout on receiving
MAP Cancel location response,
invalid response received and so
on).
S6IDRB S6aand S6d Insert Counts the total number of sent Co S6IDR Yes Ne U
ySubsA Subscriber Data S6a and S6d Insert Subscriber unt BySubs tAc MS
dminCnt Requests Data request messages. er Admin t TP
r Cntr
S6aIDR Sent S6a and S6d Count of S6a and S6d IDR Co S6aID Yes Ne U
BySWx IDR due to SAR message triggered by SWx SAR unt RByS tAc MS
SarCtr sent out er WxSar t TP
Ctr
S6aIDR Sent S6a and S6d Count of S6a and S6d IDR Co S6aID Yes Ne U
ByShU IDR due to UDR message triggered by Sh UDR unt RBySh tAc MS
DRCtr sent out er UDRCt t TP
r
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
Success success due to with result code SUCCESS when unt Succes tAc MS
BySh UDR IDR was triggered by Sh UDR er sBySh t TP
because AS retrieved Location
Information or TADS information.
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
FailByS failure due to UDR with result code other than unt FailByS tAc MS
h SUCCESS when IDR was er h t TP
triggered by Sh UDR because AS
retrieved Location Information or
TADS information.
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
Success success due to with result code SUCCESS when unt Succes tAc MS
BySWx SAR IDR was triggered by SWx SAR. er sBySW t TP
x
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
FailByS failure due to SAR with result code other than unt FailByS tAc MS
Wx SUCCESS when IDR was er Wx t TP
triggered by SWx SAR.
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
Success success due to with result code SUCCESS when unt Succes tAc MS
ByAdmi Admin IDR was triggered by subscriber er sByAd t TP
n administration. min
S6aIDA Received IDA Count of S6a / S6d IDA responses Co S6aIDA Yes Ne U
FailByA failure due to Admin with result code other than unt FailByA tAc MS
dmin SUCCESS when IDR was er dmin t TP
triggered by subscriber
administration.
S6DSR S6a and S6d Counts the total number of sent Co S6DSR Yes Ne U
BySubs Delete Subscriber S6a and S6d Delete Subscriber unt BySubs tAc MS
AdminC Data Requests Data request messages. er Admin t TP
ntr Cntr
S6CLR S6a and S6d Counts the total number of sent Co S6CLR Yes Ne U
ByS6UL Cancel Location S6a and S6d Cancel Location unt ByS6U tAc MS
RCntr Requests by request messages due to S6ULR. er LRCntr t TP
S6ULR
S6CLR S6a and S6d Counts the total number of sent Co S6CLR Yes Ne U
BySubs Cancel Location S6a and S6d Cancel Location unt BySubs tAc MS
AdminC Requests by SA request messages due to er Admin t TP
ntr Subscriber Admin Changes. Cntr
S6RSR S6a and S6d Reset Counts the total number of sent Co S6RSR Yes Ne U
BySubs Requests S6a and S6d Reset request unt BySubs tAc MS
AdminC messages. er Admin t TP
ntr Cntr
S6aULA Successful S6a and Counts the number of S6a and Co S6aUL Yes Ne U
Success S6d ULA sent S6d ULA with unt ASucce tAc MS
DIAMETER_SUCCESS. er ss t TP
S6aNO Successful S6a and Counts the number of S6a and Co S6aNO Yes Ne U
ASucce S6d NOA sent S6d NOA with unt ASucce tAc MS
ss DIAMETER_SUCCESS. er ss t TP
S6aAIA Successful S6a and Counts the number of S6a and Co S6aAIA Yes Ne U
Success S6d AIA sent S6d AIA with unt Succes tAc MS
DIAMETER_SUCCESS. er s t TP
S6aPU Successful S6a Counts the number of S6a PUA Co S6aPU Yes Ne U
ASucce PUA sent with DIAMETER_SUCCESS for unt ASucce tAc MS
ss S6a PUR messsages that were er ss t TP
received from MME where the
current user is registered
S6dPU Successful S6d Counts the number of S6d PUA Co S6dPU Yes Ne U
ASucce PUA sent with DIAMETER_SUCCESS for unt ASucce tAc MS
ss S6d PUR messsages that were er ss t TP
received from SGSN where the
current user is registered
S6dULA Successful S6d Counts the number of S6d ULA Co S6dUL Yes Ne U
Success ULA sent with DIAMETER_SUCCESS. unt ASucce tAc MS
er ss t TP
S6aS6d Successful PUA Counts the number of PUA with Co S6aS6 Yes Ne U
PUASuc Sent DIAMETER_SUCCESS for PUR unt dPUAS tAc MS
cess messages that were received from er uccess t TP
a combined MME/SGSN where
the current user is registered.
S6Upda S6a and S6d ULA Counts the total no. of S6a and Co S6Upd Yes Ne U
teLocRe with S6d-ULA messages that were not unt ateLoc tAc MS
qErrCntr DIAMETER_UNAB processed successfully due to er ReqErr t TP
LE_TO_COMPLY some internal errors(Unknown DB Cntr
ERR, CTX create failed,.) for
which standard RESULTCODE is
not defined in Diameter standard.
So, 5012 will be sent in response
S6Purg S6a and S6d PUA Counts the total no. of S6a and Co S6Purg Yes Ne U
eUEReq with S6d-PUA messages that were not unt eUERe tAc MS
ErrCntr DIAMETER_UNAB processed successfully due to er qErrCnt t TP
LE_TO_COMPLY some internal errors(Unknown DB r
ERR CTX create failed,..) for
which standard RESULTCODE is
not defined in Diameter standard.
So, 5012 will be sent in response
S6Notif S6a and S6d NOA Counts the total no. of S6a and Co S6Notif Yes Ne U
ReqErr with S6d-NOA messages that were not unt ReqErr tAc MS
Cntr DIAMETER_UNAB processed successfully due to er Cntr t TP
LE_TO_COMPLY some internal errors(Unknown DB
ERR, CTX create failed,..) for
which standard RESULTCODE is
not defined in Diameter standard.
So, 5012 will be sent in response
S6AuthI S6A AIA with Counts the total no. of S6a-AIA Co S6Auth UM Ne U
nfoReq DIAMETER_UNAB messages that were not unt InfoRe ST tAc MS
ErrCntr LE_TO_COMPLY processed successfully due to er qErrCnt P t TP
some internal errors(Unknown DB r
S6dUpd S6D ULA with Counts the total no. of S6d-ULA Co S6dUp Yes Ne U
LocReq DIAMETER_UNAB messages that were not unt dLocRe tAc MS
ErrCntr LE_TO_COMPLY processed successfully due to er qErrCnt t TP
some internal errors(Unknown DB r
err, CTX create failed,..) for which
standard RESULTCODE is not
defined in Diameter standard. So,
5012 will be sent in response
S6CLR S6a/S6d Cancel Counts the total number of errors Co S6CLR Yes Ne U
NotPoss Loc req messages which occurred during processing unt NotPos tAc MS
ibleCntr not processed of S6a and S6d CLR, due to no er sibleCn t TP
successfully Diameter connection available to tr
the MME/SGSN or message send
failed to DIAMETER process
S6CLA S6a or S6d Cancel Counts the total number of errors Co S6CLA Yes Ne U
ErrCntr Loc Answers not while processing a S6a and S6d unt ErrCntr tAc MS
processes Cancel Location answer message. er t TP
successfully The possible errors are INVALID
RESPONSE RECEIVED and
Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
S6IDRN S6a/S6d Insert Counts the total number of errors Co S6IDR Yes Ne U
otPossi Subs Data req which occurred during processing unt NotPos tAc MS
bleCntr messages not of S6a and S6dIDR, due to no er sibleCn t TP
processed Diameter connection available to tr
successfully the MME or message send failed
to DIAMETER process
S6IDAE S6a Insert Subs Counts the total number of errors Co S6IDA Yes Ne U
rrCntr Data Ans while processing of an Insert unt ErrCntr tAc MS
messages not Subscriber Data answer message. er t TP
processed The possible errors are INVALID
successfully RESPONSE RECEIVED and
Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
S6aIDA Number of failed P- Count of IDAs for which P-CSCF Co S6aIDA Yes Ne U
FailByC CSCF Recovery Recovery failed. unt FailBy tAc MS
x S6a IDA er Cx t TP
S6DSR S6a/S6d Delete Counts the total number of errors Co S6DSR Yes Ne U
NotPoss Subs Data Req which occurred during processing unt NotPos tAc MS
ibleCntr messages not S6a and S6d DSR, due to no er sibleCn t TP
processed Diameter connection available to tr
successfully the MME or message send failed
to DIAMETER process
S6DSA S6a/S6d Delete Counts the total number of errors Co S6DSA Yes Ne U
ErrCntr Subs Data Ans while processing of a S6a and unt ErrCntr tAc MS
messages not S6d Delete Subscriber Data er t TP
processed answer message. The possible
successfully errors are INVALID RESPONSE
RECEIVED and Internal errors (for
example, internal-context
unavailability, error in answer
message packer formation and so
on).
S6RSR S6a/S6d Reset Req Counts the total number of errors Co S6RSR Yes Ne U
NotPoss messages not which occurred during processing unt NotPos tAc MS
ibleCntr processed of S6a and S6d RSR, due to no er sibleCn t TP
successfully Diameter connection available to tr
the MME or message send failed
to DIAMETER process
S6RSA S6a/S6d Reset Ans Counts the total number of errors Co S6RSA Yes Ne U
ErrCntr messages not while processing of a S6a and unt ErrCntr tAc MS
processed S6d reset answer messages. The er t TP
successfully possible errors are INVALID
RESPONSE RECEIVED and
Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
SWxRT SWx Registration Counts the total number of sent Co SWxRT Yes Ne U
RByHd Termination SWx Registration Termination unt RByHd tAc MS
CLR Requests triggered request messages, triggered by er CLR t TP
by HdCLR HdCLR from HLR.
SWxMA Successful SWx Counts the number of SWx MAA Co SWxM Yes Ne U
ASucce MAA sent with DIAMETER_SUCCESS. unt AASuc tAc MS
ss er cess t TP
SWxSA Successful SWx Counts the number of SWx SAA Co SWxSA Yes Ne U
ASucce SAA sent with DIAMETER_SUCCESS. unt ASucce tAc MS
ss er ss t TP
SWxMul SWx MAA with Counts the total no. of SWx-MAA Co SWxM Yes Ne U
timAuth DIAMETER_UNAB messages that were not unt ultimAu tAc MS
ErrCntr LE_TO_COMPLY processed successfully due to er thErrCn t TP
some internal errors(Unknown DB tr
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
SWxSer SWx SAA with Counts the total no. of SWx-SAA Co SWxSe Yes Ne U
verAsgn DIAMETER_UNAB messages that were not unt rverAsg tAc MS
ErrCntr LE_TO_COMPLY processed successfully due to er nErrCnt t TP
some internal errors(Unknown DB r
error, context creation failed,..) for
which standard RESULT CODE is
not defined in Diameter standard.
So, 5012 will be sent in response
SWxRT Swx Reg Term Req Counts the total number of errors Co SWxRT Yes Ne U
RNotPo messages not which occurred during processing unt RNotP tAc MS
ssibleC processed of SWxRTR, due to no Diameter er ossible t TP
ntr successfully connection available to the AAA or Cntr
message send failed to
DIAMETER process
SWxRT Swx Reg Term Ans Counts the total number of errors Co SWxRT Yes Ne U
AErrCnt messages not while processing of a SWx unt AErrCn tAc MS
r processed Registration Termination answer er tr t TP
successfully message. The possible errors are
INVALID RESPONSE RECEIVED
and Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
SWxPP Swx Push Profile Counts the total number of errors Co SWxPP Yes Ne U
RNotPo Req messages not which occurred during processing unt RNotP tAc MS
ssibleC processed of SWxPPR, due to no Diameter er ossible t TP
ntr successfully connection available to the AAA or Cntr
message send failed to
DIAMETER process
SWxPP Swx Push Profile Counts the total number of errors Co SWxPP Yes Ne U
AErrCnt Ans messages not while processing of a SWx push unt AErrCn tAc MS
r processed profile answer message. The er tr t TP
successfully possible errors are INVALID
RESPONSE RECEIVED and
Internal errors (for example,
internal-context unavailability,
error in answer message packer
formation and so on).
ZhMulti ZhMultimedia Counts the total number of Co ZhMulti Yes Ne U
mAuthR Authentication received Zh multimedia unt mAuth tAc MS
eqCntr Requests authentication request messages er ReqCnt t TP
(indication of the authentication of r
subscribers).
LdapRe Successful LDAP Counts the total number of LDAP Co LdapR Yes Ne U
adSucc Read Responses Read Responses which are unt eadSuc tAc MS
Cntr successful. The list of result codes er cCntr t TP
which are considered as success
are as per the configuration data.
LdapWri Successful LDAP Counts the total number of LDAP Co LdapW Yes Ne U
teSuccC Write Responses Write Responses which are unt riteSuc tAc MS
ntr successful. The list of result codes er cCntr t TP
which are considered as success
are as per the configuration data.
LdapRe Erroneous LDAP Counts the total number of LDAP Co LdapR Yes Ne U
adError Read Responses Read Responses which are unt eadErr tAc MS
Cntr erroneous. The list of result codes er orCntr t TP
which are considered as
erroneous are as per the
configuration data.
LdapWri Erroneous LDAP Counts the total number of LDAP Co LdapW Yes Ne U
teErrorC Write Responses Write Responses which are unt riteErro tAc MS
ntr erroneous. The list of result codes er rCntr t TP
which are considered as
erroneous are as per the
configuration data.
LdapRe Other LDAP Read Counts the total number of LDAP Co LdapR Yes Ne U
adOther Responses Read Responses whose result unt eadOth tAc MS
Cntr codes are not in configured list of er erCntr t TP
success OR error result codes.
LdapWri Other LDAP Write Counts the total number of LDAP Co LdapW Yes Ne U
teOther Responses Write Responses whose result unt riteOth tAc MS
Cntr codes are not inconfigured list of er erCntr t TP
success OR error result codes.
HdCLRI Received Hd CLR Counts the total number of Hd- r HdCLR Yes Ne U
nSIMCa for Seamless CLRs recevied by HSS from HLR InSIMC tAc MS
Co TP
rdChOvr Changeover due to Seamless changeover. ardCh t
unt
Ovr
e
HdCLR Sent Hd CLR with Counts the total number of Co HdCLR Yes Ne U
OutSgs SGSN Update outgoing Hd CLR requests with unt OutSgs tAc MS
nUpdate Extended Cancellation Type er nUpdat t TP
e
HdCLR Sent Hd CLR with Counts the total number of Co HdCLR Yes Ne U
OutMm MME triggered outgoing Hd CLR requests with unt OutMm tAc MS
eAttach initial attach Extended Cancellation Type MME er eAttach t TP
triggered initial attach, even if it
was not able to send because of
connectivity issues
HdCLR Sent Hd CLR with Counts the total number of send Co HdCLR Yes Ne U
OutCard Update Loc Hd CLR with Extended unt OutCar tAc MS
Change triggered card Cancellation Type value Update er dChan t TP
change Loc triggered card change, even if ge
it was not able to send because of
connectivity issues
HdCLR Hd CLR sent due to Counts the total number of Hd- Co HdCLR Yes Ne U
OutSIM Simcard CLRs triggered towards HLR due unt OutSIM tAc MS
CardCh Changeover to Simcard Chnageover. er CardCh t TP
Ovr Ovr
HdCLA Sent Hd CLA with Counts the total number of Co HdCLA Yes Ne U
OutSuc result DIAMETER outgoing Hd CLA responses with unt OutSuc tAc MS
cess SUCCESS result DIAMETER SUCCESS er cess t TP
HdUDAi Received Hd UDA Counts the total number of Hd- Co HdUDA Yes Ne U
nSucce with result UDA received at HSS with result unt inSucc tAc MS
ss DIAMETER code DIAMETER_SUCCESS er ess t TP
SUCCESS
HdPUAi Sent Hd PUA with Counts the total number of Hd- Co HdPUA Yes Ne U
nSucce result DIAMETER PUA received at HSS with result unt inSucc tAc MS
ss SUCCESS code DIAMETER_SUCCESS er ess t TP
HdSNAi Received Hd SNA Counts the total number of Hd- Co HdSNA Yes Ne U
nSucce with result SNA received at HSS with result unt inSucc tAc MS
ss DIAMETER code DIAMETER_SUCCESS er ess t TP
SUCCESS
HdPNA Sent Hd PNA with Counts the total number of Hd- Co HdPNA Yes Ne U
OutSuc result DIAMETER PNA sent out by HSS with result unt OutSuc tAc MS
cess SUCCESS code DIAMETER_SUCCESS er cess t TP
HdCLA Sent Hd CLA with Counts the total number of Co HdCLA Yes Ne U
Out501 result DIAMETER outgoing Hd CLA responses with unt Out501 tAc MS
2 UNABLE TO result DIAMETER UNABLE TO er 2 t TP
COMPLY COMPLY
HdPNA Received Hd PNA Counts the total number of Hd- Co HdPNA Yes Ne U
Out501 with result PNA sent out by HSS with result unt Out501 tAc MS
2 DIAMETER code er 2 t TP
UNABLE TO DIAMETER_UNABLE_TO_COMP
COMPLY LY
HdUDAi Sent Hd UDA with Counts the total number of Hd- Co HdUDA Yes Ne U
n5012 result DIAMETER UDA received at HSS with result unt in5012 tAc MS
UNABLE TO code er t TP
COMPLY DIAMETER_UNABLE_TO_COMP
LY
HdPUAi Received Hd PUA Counts the total number of Hd- Co HdPUA Yes Ne U
n5012 with result PUA received at HSS with result unt in5012 tAc MS
DIAMETER code er t TP
UNABLE TO DIAMETER_UNABLE_TO_COMP
COMPLY LY
HdSNAi Sent Hd SNA with Counts the total number of Hd- Co HdSNA Yes Ne U
n5012 result DIAMETER SNA received at HSS with result unt in5012 tAc MS
UNABLE TO code er t TP
COMPLY DIAMETER_UNABLE_TO_COMP
LY
HdUDA Hd UDR timeouts no response received for send Hd- Co HdUDA Yes Ne U
Timeout UDR within maximum time (no- unt Timeou tAc MS
answer timer expired) er t t TP
HdPUA Hd PUR timeouts no response received for send Hd- Co HdPUA Yes Ne U
Timeout PUR within maximum time (no- unt Timeou tAc MS
answer timer expired) er t t TP
HdSNA Hd SNR timeouts no response received for send Hd- Co HdSNA Yes Ne U
Timeout SNR within maximum time (no- unt Timeou tAc MS
answer timer expired) er t t TP
HdCLA Received Hd CLA Counts the total number of sent Co HdCLA Yes Ne U
Out500 with result Hd-CLA with result unt Out500 tAc MS
5 DIAMETER_MISSI DIAMETER_MISSING_AVP er 5 t TP
NG_AVP
HdPNA Received Hd PNA Counts the total number of sent Co HdPNA Yes Ne U
Out500 with result Hd-PUA with result unt Out500 tAc MS
5 DIAMETER_MISSI DIAMETER_MISSING_AVP er 5 t TP
NG_AVP
HdCLAi received Hd-CLA Counts the total number of Hd- Co HdCLAi Yes Ne U
n5004 with result CLA received with result code unt n5004 tAc MS
DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er t TP
D_AVP_VALUE E
(5004)
HdUDAi received Hd-UDA Counts the total number of Hd- Co HdUDA Yes Ne U
n5004 with result UDA received with result code unt in5004 tAc MS
DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er t TP
D_AVP_VALUE E
(5004)
HdPUAi received Hd-PUA Counts the total number of Hd- Co HdPUA Yes Ne U
n5004 with result PUA received with result code unt in5004 tAc MS
DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er t TP
D_AVP_VALUE E
(5004)
HdSNAi received Hd-SNA Counts the total number of Hd- Co HdSNA Yes Ne U
n5004 with result SNA received with result code unt in5004 tAc MS
DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er t TP
D_AVP_VALUE E
(5004)
HdCLA send Hd-CLA with Counts the total number of Hd- Co HdCLA Yes Ne U
Out500 result CLA sent with result code unt Out500 tAc MS
4 DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er 4 t TP
D_AVP_VALUE E
(5004)
HdPNA send Hd-PNA with Counts the total number of Hd- Co HdPNA Yes Ne U
Out500 result PNA sent with result code unt Out500 tAc MS
4 DIAMETER_INVALI DIAMETER_INVALID_AVP_VALU er 4 t TP
D_AVP_VALUE E
(5004)
HdUDAi received Hd-UDA received result code is not equal Co HdUDA Yes Ne U
nOther with other result to DIAMETER_SUCCESS (2001), unt inOther tAc MS
codes DIAMETER_INVALID_AVP_VALU er t TP
E (5004),
DIAMETER_UNABLE_TO_COMP
LY (5012),
DIAMETER_RESOURCES_EXCE
EDED (5006)
HdPUAi received Hd-PUA received result code is not equal Co HdPUA Yes Ne U
nOther with other result to DIAMETER_SUCCESS (2001), unt inOther tAc MS
codes DIAMETER_INVALID_AVP_VALU er t TP
E (5004),
DIAMETER_UNABLE_TO_COMP
LY (5012),
DIAMETER_RESOURCES_EXCE
EDED (5006)
HdSNAi received Hd-SNA received result code is not equal Co HdSNA Yes Ne U
nOther with other result to DIAMETER_SUCCESS (2001), unt inOther tAc MS
codes DIAMETER_INVALID_AVP_VALU er t TP
E (5004),
DIAMETER_UNABLE_TO_COMP
LY (5012),
DIAMETER_RESOURCES_EXCE
EDED (5006)
HdCLA Sent Hd CLA with Counts the total number of Hd Co HdCLA Yes Ne U
OutOthe other result CLA with result code other than unt OutOth tAc MS
r DIAMETER SUCCESS , er er t TP
DIAMETER AVP
UNSUPPORTED,
DIAMETER UNABLE TO
COMPLY,
DIAMETER MISSING AVP
HdPNA send Hd-PNA with Hd-PNA send with other result Co HdPNA Yes Ne U
OutOthe other result than DIAMETER_SUCCESS unt OutOth tAc MS
r (2001), er er t TP
DIAMETER_AVP_UNSUPPORTE
D (5001),
DIAMETER_INVALID_AVP_VALU
E (5004),
DIAMETER_UNABLE_TO_COMP
LY (5012),
DIAMETER_MISSING_AVP
(5005)
HdCLR Hd CLR could not Counts the total number of errors Co HdCLR Yes Ne U
NotPoss be sent which occurred when trying to unt NotPos tAc MS
ibleCntr send the outgoing Hd request e.g. er sibleCn t TP
due to no Diameter connection tr
available to the HLR or message
send failed to DIAMETER process
HdUDR Hd-UDR could not Counts the total number of errors Co HdUDR Yes Ne U
NotPoss be send which occurred when trying to unt NotPos tAc MS
ibleCntr send the outgoing Hd request e.g. er sibleCn t TP
due to no Diameter connection tr
available to the HLR or message
send failed to DIAMETER process
HdPUR Hd-PUR could not Counts the total number of errors Co HdPUR Yes Ne U
NotPoss be send which occurred when trying to unt NotPos tAc MS
ibleCntr send the outgoing Hd request e.g. er sibleCn t TP
due to no Diameter connection tr
available to the HLR or message
send failed to DIAMETER process
HdSNR Hd-SNR could not Counts the total number of errors Co HdSNR Yes Ne U
NotPoss be send which occurred when trying to unt NotPos tAc MS
ibleCntr send the outgoing Hd request e.g. er sibleCn t TP
due to no Diameter connection tr
available to the HLR or message
send failed to DIAMETER process
ShPNR Sh-PNR triggered Counts the total number of sent Co ShPNR Yes Ne U
ByS6 by S6a/S6d Sh PNR triggered by S6a and S6d unt ByS6 tAc MS
requests request er t TP
ShPNR Sh-PNR triggered Counts the total number of sent Co ShPNR Yes Ne U
ByHd by HD requests Sh PNR triggered by Hd request unt ByHd tAc MS
(Gr, UE Reachability) er t TP
ShPNA Sh-PNR timeout no response received for send Sh- Co ShPNA Yes Ne U
Timeout PNR within maximum time (no unt Timeou tAc MS
answer timer expired) er t t TP
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
sOCOV INF having OC- S6m INF having OC-Sup-Feat and unt sOCOV tAc MS
Lended Sup-Feat and OC- OC-OLR AVP(OL situation er Lended t TP
Sent OLR AVP(OlEnded) ended). That is the amount of Sent
diameter answers sent indicating
that an OL situation has
ended(OC-Reduction-Percentage
or OC-Valid-Duration set to zero)
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
spNoO INF having OC- S6m interface containing the OC- unt spNoO tAc MS
COVLS Sup-Feat AVP,but Supported-Features AVP, but no er COVLS t TP
ent no OC-OLR AVP OC-OLR AVP. That is the amount ent
of diameter answers sent under
the diameter overload signalling
feature without indicating any
overload situation
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
spOCO INF having OC- S6m interface containing the OC- unt spOCO tAc MS
VLSent Sup-Feat AVP,but Supported-Features AVP, but no er VLSent t TP
no OC-OLR AVP OC-OLR AVP. That is the amount
of diameter answers sent under
the diameter overload signalling
feature without indicating any
overload situation
S6mSIR Received S6m-SIR Counts the total number of S6m- Co S6mSI Yes Ne U
In SIR received at HSS which are unt RIn tAc MS
not blocked or dropped away er t TP
because of overload.
S6nSIRI Received S6n-SIR Counts the total number of S6n- Co S6nSIR Yes Ne U
n SIR received at HSS which are unt In tAc MS
not blocked or dropped away er t TP
because of overload.
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
OutRC5 result code SIA sent with result code unt AOutR tAc MS
012 DIAMETER_UNAB DIAMETER_UNABLE_TO_COMP er C5012 t TP
LE_TO_COMPLY LY (5012).
(5012)
S6nSIA S6n-SIA sent with Counts the total number of S6n- Co S6nSIA Yes Ne U
OutRC5 result code SIA sent with result code unt OutRC tAc MS
012 DIAMETER_UNAB DIAMETER_UNABLE_TO_COMP er 5012 t TP
LE_TO_COMPLY LY (5012).
(5012)
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
OutRC4 result code SIA sent with result code unt AOutR tAc MS
002 DIAMETER_OUT_ DIAMETER_OUT_OF_SPACE er C4002 t TP
OF_SPACE (4002) (4002).
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
Out500 experimental result SIA sent with experimental result unt AOut50 tAc MS
1 code 5001 code er 01 t TP
DIAMETER_ERROR_USER_UNK
NOWN (5001).
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
Out551 experimental result SIA sent with experimental result unt AOut55 tAc MS
0 code 5510 code er 10 t TP
DIAMETER_ERROR_UNAUTHO
RIZED_REQUESTING_ENTITY
(5510).
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
Out5511 experimental result SIA sent with experimental result unt AOut55 tAc MS
code 5511 code er 11 t TP
DIAMETER_ERROR_UNAUTHO
RIZED_SERVICE (5511).
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
OutOthe other result SIA sent with other result than unt AOutOt tAc MS
r those which have own counters er her t TP
(for example
DIAMETER_INVALID_AVP_VALU
E, etc.).
S6mSIA S6m-SIA sent with Counts the total number of S6m- Co S6mSI Yes Ne U
Success result code SIA sent with result code unt ASucce tAc MS
DIAMETER_SUCC DIAMETER_SUCCESS (2001). er ss t TP
ESS (2001)
AVPsMi AVP missing for Counts the number of instances Co AVPsM Yes Ne U
ssingCx staleness check in when staleness check failed due unt issingC tAc MS
Cx interface. to missing of mandatory AVPs er x t TP
Originating-TimeStamp or Max-
Wait-Time in Cx interface.
AVPsMi AVP missing for Counts the number of instances Co AVPsM Yes Ne U
ssingS staleness check in when staleness check failed due unt issingS tAc MS
Wx SWx interface. to missing of mandatory AVPs er Wx t TP
Originating-TimeStamp or Max-
Wait-Time in SWx interface.
AVPsMi AVP missing for Counts the number of instances Co AVPsM Yes Ne U
ssingS6 staleness check in when staleness check failed due unt issingS tAc MS
S6 interface. to missing of mandatory AVPs er 6 t TP
Originating-TimeStamp or Max-
Wait-Time in S6 interface.
NoRelia TSP indicates that Counts the number of instances Co NoReli Yes Ne U
bleLocal local time is not when TSP indicates that local time unt ableLo tAc MS
Time reliable. is not reliable. er calTime t TP
SLhRIA send SLh-RIA with Sends SLh-RIA with experimental Co SLhRIA Yes Ne U
Out500 DIAMETER_ERRO result code unt Out500 tAc MS
1 R_USER_UNKNO DIAMETER_ERROR_USER_UNK er 1 t TP
WN (5001) NOWN (5001)
SLhRIA send SLh-RIA with Sends SLh-RIA with other result Co SLhRIA Yes Ne U
OutOthe other result than those which have own unt OutOth tAc MS
r counters er er t TP
SLhRIA send SLh-RIA with Sends SLh-RIA with result code Co SLhRIA Yes Ne U
OutRC4 result code DIAMETER_OUT_OF_SPACE unt OutRC tAc MS
002 DIAMETER_OUT_ 4002 er 4002 t TP
OF_SPACE 4002
SLhRIA send SLh-RIA with Sends SLh-RIA with experimental Co SLhRIA Yes Ne U
OutRC5 DIAMETER_CONT result code unt OutRC tAc MS
007 RADICTING_AVPS DIAMETER_CONTRADICTING_A er 5007 t TP
(5007) VPS (5007)
SLhRIA send SLh-RIA with Counts the total number of SLh- Co SLhRIA Yes Ne U
OutRC5 result code RIA sent out by HSS with result unt OutRC tAc MS
012 DIAMETER_UNAB code er 5012 t TP
LE_TO_COMPLY DIAMETER_UNABLE_TO_COMP
(5012) LY (5012)
SLhRIA send SLh-RIA with Sends SLh-RIA with result code Co SLhRIA Yes Ne U
Success result code DIAMETER_SUCCESS (2001) unt Succes tAc MS
DIAMETER_SUCC er s t TP
ESS (2001)
SWxRe Sent resp on SWx Number of sent responses on the Co SWxRe Yes Ne U
sOCOV INF having OC- SWx INF having OC-Sup-Feat unt sOCOV tAc MS
Lended Sup-Feat and OC- and OC-OLR AVP(OL situation er Lended t TP
Sent OLR AVP(OlEnded) ended). That is the amount of Sent
diameter answers sent indicating
that an OL situation has ended
(OC-Reduction-Percentage or
OC-Valid-Duration set to zero)
SWxRe Sent resp on SWx Number of sent responses on the Co SWxRe Yes Ne U
spNoO INF having OC- SWx interface containing the OC- unt spNoO tAc MS
COVLS Sup-Feat AVP,but Supported-Features AVP, but no er COVLS t TP
ent no OC-OLR AVP OC-OLR AVP. That is the amount ent
of diameter answers sent under
the diameter overload signalling
feature without indicating any
overload situation
SWxRe Sent resp on SWx Number of sent responses on the Co SWxRe Yes Ne U
spOCO INF having OC- SWx interface containing the OC- unt spOCO tAc MS
VLSent Sup-Feat and OC- Supported-Features and OC-OLR er VLSent t TP
OLR AVP(OlState) AVP (overload situation). That is
the amount of diameter answers
sent under the diameter overload
signalling feature indicating an
overload situation
CxLIRpr Cx-LIR with prio 2 Cx-LIR with prio 2 received Co CxLIRp Yes Ne U
io2Rece received Number of Cx-LIR messages unt rio2Rec tAc MS
ived received with respective Session- er eived t TP
Priority 2
CxRTR Triggered by Cx- Counts the total number of sent Co CxRTR Yes Ne U
ByCxSA SAR Cx registration termination request unt ByCxS tAc MS
Cntr messages that are triggered by er ACntr t TP
the Cx server assignment request
handling.
CxLIRpr Cx-LIR with prio 0 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io0Succ successful respective Session-Priority 0 unt rio0Suc tAc MS
ess answered successfully. er cess t TP
CxLIRpr Cx-LIR with prio 1 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io1Succ successful respective Session-Priority 1 unt rio1Suc tAc MS
ess answered successfully. er cess t TP
CxLIRpr Cx-LIR with prio 2 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io2Succ successful respective Session-Priority 2 unt rio2Suc tAc MS
ess answered successfully. er cess t TP
CxLIRpr Cx-LIR with prio 3 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io3Succ successful respective Session-Priority 3 unt rio3Suc tAc MS
ess answered successfully. er cess t TP
CxLIRpr Cx-LIR with prio 4 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io4Succ successful respective Session-Priority 4 unt rio4Suc tAc MS
ess answered successfully. er cess t TP
CxLIRpr Cx-LIR with prio 0 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io0Drop dropped respective Session-Priority 0 unt rio0Dro tAc MS
ped dropped due to overload er pped t TP
CxLIRpr Cx-LIR with prio 1 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io1Drop dropped respective Session-Priority 1 unt rio1Dro tAc MS
ped dropped due to overload er pped t TP
CxLIRpr Cx-LIR with prio 2 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io2Drop dropped respective Session-Priority 2 unt rio2Dro tAc MS
ped dropped due to overload er pped t TP
CxLIRpr Cx-LIR with prio 3 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io3Drop dropped respective Session-Priority 3 unt rio3Dro tAc MS
ped dropped due to overload er pped t TP
CxLIRpr Cx-LIR with prio 4 Number of Cx-LIR messages with Co CxLIRp Yes Ne U
io4Drop dropped respective Session-Priority 4 unt rio4Dro tAc MS
ped dropped due to overload er pped t TP
CxPPAI Cx PPA with out Counts the total no. of Cx PPA Co CxPPAI Yes Ne U
nNoSuc DIAMETER_SUCC received with out unt nNoSu tAc MS
cess ESS DIAMETER_SUCCESS and for er ccess t TP
errors which does not have
specific counter.
CxPPAT Cx PPA timeout Counts the total no. of Cx PPR for Co CxPPA Yes Ne U
imeout which there is no response unt Timeou tAc MS
received by HSS within the er t t TP
configured no-answer time.
CxPPAs Successful Cx PPA Counts the total no. of successful Co CxPPA Yes Ne U
uccess received Cx PPA received with unt succes tAc MS
DIAMETER_SUCCESS. er s t TP
CxRTAI Cx RTA with out Counts the total no. of Cx RTA Co CxRTAI Yes Ne U
nNoSuc DIAMETER_SUCC received with out unt nNoSu tAc MS
cess ESS DIAMETER_SUCCESS and for er ccess t TP
errors which does not have
specific counter.
CxRTAT Cx RTA timeout Counts the total no. of Cx RTR for Co CxRTA Yes Ne U
imeout which there is no response unt Timeou tAc MS
received by HSS within the er t t TP
configured no-answer time.
CxRTAs Successful Cx RTA Counts the total no. of successful Co CxRTA Yes Ne U
uccess received Cx RTA received with unt succes tAc MS
DIAMETER_SUCCESS. er s t TP
InvalidN Invalid NSR data Counts the number of invalid Co Invalid Yes Ne U
SRData reference references to NSR data identified unt NSRDa tAc MS
Ref when reading an individual er taRef t TP
subscriber profile
MapVcc Number of VCC Counts the number of VCC related Co MapVc Yes Ne U
Regular related Regular origination requests that have not unt cRegul tAc MS
Orreq Origination been recognized as requests for er arOrreq t TP
Requests received eSRVCC Domain Transfer, i.e.
origination requests for which an
IMRN had to be allocated.
S6AuthI s6a Auth Info Counts the total number of Co S6Auth Yes Ne U
nfoReq Requests received s6a and s6d unt InfoRe tAc MS
Cntr Authentication Information request er qCntr t TP
messages.
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5001B DIAMETER_ERRO unsuccessful S6a IDA received unt In5001 tAc MS
yAdmin R_USER_UNKNO with er ByAdmi t TP
WN for IDR by DIAMETER_ERROR_USER_UNK n
Admin NOWN for IDR triggers due to
subscriber data administration.
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5001B DIAMETER_ERRO unsuccessful S6a IDA received unt In5001 tAc MS
ySWx R_USER_UNKNO with er BySWx t TP
WN for IDR by SWx DIAMETER_ERROR_USER_UNK
NOWN for IDR triggers due to
SWx.
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5001B DIAMETER_ERRO unsuccessful S6a IDA received unt In5001 tAc MS
ySh R_USER_UNKNO with er BySh t TP
WN for IDR by Sh DIAMETER_ERROR_USER_UNK
NOWN for IDR triggers due to Sh.
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5012B DIAMETER_UNAB unsuccessful S6a IDA received unt In5012 tAc MS
yAdmin LE_TO_COMPLY with er ByAdmi t TP
for IDR by admin DIAMETER_UNABLE_TO_COMP n
LY for IDR triggers due to
subscriber data administration
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5012B DIAMETER_UNAB unsuccessful S6a IDA received unt In5012 tAc MS
ySWx LE_TO_COMPLY with er BySWx t TP
for IDR by SWx DIAMETER_UNABLE_TO_COMP
LY for IDR triggers due to SWx.
S6aIDAI S6a IDA with Counts the total no. of Co S6aIDA Yes Ne U
n5012B DIAMETER_UNAB unsuccessful S6a IDA received unt In5012 tAc MS
ySh LE_TO_COMPLY with er BySh t TP
for IDR by Sh DIAMETER_UNABLE_TO_COMP
LY for IDR triggers due to Sh.
S6aULR S6a-ULR received Counts the total no. of received Co S6aUL Yes Ne U
HPLMN from HPLMN MME S6a-ULR from HPLMN MME.Will unt RHPL tAc MS
Request not be pegged when the ULR er MNReq t TP
comes from a Combi MME/SGSN uest
S6aULR S6a-ULR received Counts the total no. of received Co S6aUL Yes Ne U
VPLMN from VPLMN MME S6a-ULR from VPLMN MME.Will unt RVPLM tAc MS
Request not be pegged when the ULR er NRequ t TP
comes from a Combi MME/SGSN est
S6dULR S6d-ULR received Counts the total no. of received Co S6dUL Yes Ne U
HPLMN from HPLMN SGSN S6d-ULR from HPLMN SGSN unt RHPL tAc MS
Request er MNReq t TP
uest
S6dULR S6d-ULR received Counts the total no. of received Co S6dUL Yes Ne U
VPLMN from VPLMN SGSN S6d-ULR from VPLMN SGSN unt RVPLM tAc MS
Request er NRequ t TP
est
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
sOCOV INF having OC- S6m INF having OC-Sup-Feat and unt sOCOV tAc MS
Lended Sup-Feat and OC- OC-OLR AVP(OL situation er Lended t TP
Sent OLR AVP(OlEnded) ended). That is the amount of Sent
diameter answers sent indicating
that an OL situation has
ended(OC-Reduction-Percentage
or OC-Valid-Duration set to zero)
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
spNoO INF having OC- S6m interface containing the OC- unt spNoO tAc MS
COVLS Sup-Feat AVP,but Supported-Features AVP, but no er COVLS t TP
ent no OC-OLR AVP OC-OLR AVP. That is the amount ent
of diameter answers sent under
the diameter overload signalling
feature without indicating any
overload situation
S6mRe Sent resp on S6m Number of sent responses on the Co S6mRe Yes Ne U
spOCO INF having OC- S6m interface containing the OC- unt spOCO tAc MS
VLSent Sup-Feat and OC- Supported-Features and OC-OLR er VLSent t TP
OLR AVP(OlState) AVP (overload situation). That is
the amount of diameter answers
sent under the diameter overload
signalling feature indicating an
overload situation
S6mSIR Received S6m-SIR Counts the total number of S6m- Co S6mSI Yes Ne U
In SIR received at HSS which are unt RIn tAc MS
not blocked or dropped away er t TP
because of overload.
S6nSIRI Received S6n-SIR Counts the total number of S6n- Co S6nSIR Yes Ne U
n SIR received at HSS which are unt In tAc MS
not blocked or dropped away er t TP
because of overload.
SLhRIA send SLh-RIA with send SLh-RIA with experimental Co SLhRIA Yes Ne U
Out420 DIAMETER_ERRO result code unt Out420 tAc MS
1 R_ABSENT_USER DIAMETER_ERROR_ABSENT_U er 1 t TP
(4201) SER (4201)
SLhRIA send SLh-RIA with send SLh-RIA with experimental Co SLhRIA Yes Ne U
Out500 DIAMETER_ERRO result code unt Out500 tAc MS
1 R_USER_UNKNO DIAMETER_ERROR_USER_UNK er 1 t TP
WN (5001) NOWN (5001)
ShPNA Successful Sh PNA Counts the total no. of successful Co ShPNA Yes Ne U
S6Succ received for S6a/d Sh PNA received with unt S6Succ tAc MS
ess triggered PNR DIAMETER_SUCCESS for PNR er ess t TP
triggers due to S6a/d.
ShPNA Sh PNA with out Counts the total no. of Co ShPNA Yes Ne U
Shfailur DIAMETER_SUCC unsuccessful Sh PNA received unt Shfailur tAc MS
e ESS for PNR by Sh with out DIAMETER_SUCCESS er e t TP
for PNR triggers due to Sh.
ShPNA Successful Sh PNA Counts the total no. of successful Co ShPNA Yes Ne U
Shsucc received for Sh Sh PNA received with unt Shsucc tAc MS
ess triggered PNR DIAMETER_SUCCESS for PNR er ess t TP
triggers due to Sh.
ShPNA Sh PNA with out Counts the total no. of Co ShPNA Yes Ne U
SubsAd DIAMETER_SUCC unsuccessful Sh PNA received unt SubsA tAc MS
minfailur ESS for PNR due to with out DIAMETER_SUCCESS er dminfail t TP
e admin for PNR triggers due to subscriber ure
data administration.
ShPNA Successful Sh PNA Counts the total no. of successful Co ShPNA Yes Ne U
SubsAd received for admin Sh PNA received with unt SubsA tAc MS
minsucc triggered PNR DIAMETER_SUCCESS for PNR er dminsu t TP
ess triggers due to subscriber ccess
administration.
WxEAP Wx MAR for EAP Counts the total no. of received Co WxEAP Yes Ne U
AKAAut AKA authentication Wx multimedia authentication unt AKAAu tAc MS
hReqCn data request messages requesting er thReqC t TP
tr EAP AKA authentication data. ntr
WxEAP Wx MAR for EAP Counts the total no. of received Co WxEAP Yes Ne U
SIMAut SIM authentication Wx multimedia authentication unt SIMAut tAc MS
hReqCn data request messages requesting er hReqC t TP
tr EAP SIM authentication data. ntr
4.18 UTIMACO-HSM
Table 34 UTIMACO-HSM
Counter Name PO/CPO Descripti Type XML Supporte Network
Label on export d as manage
counter exported ment
name counter system
Index
K
key performance indicators 12
R
Reporter 12