KPI Document: NT HLR

Version Created By Reviewed By Approved By

1 NSN Mugdha Navdeep

History

Version Date Description

1 March 28, 2013 Initial version
2 May29, 2013 Comments added for CPU and transaction overload
for SMS added
2 Aug 2, 2013 PGW/PGW-DSA Calculation Ideology incorporated
OneEIR Added/ PCC Added
Final Sep 16, 2013 Convertor KPI Added
 INDEX

1 PURPOSE AND SCOPE .................................................................................. 3

2 COMMON SUBSCRIBER DATABASE ARCHITECTURE ..................................... 3
3 KPI CLASSIFICATION .................................................................................. 4
4 NT HLR FE KPIS ........................................................................................... 4
4.1 CPU STATISTICS MEASUREMENT.................................................................................................................. 4
4.2 UPDATE LOCATION FAILURE RATE (VLR): HPLMN .................................................................................... 4
4.3 UPDATE LOCATION FAILURE RATE (VLR): VPLMN .................................................................................... 5
4.4 SEND ROUTING INFO (MTC) FAILURE RATE ................................................................................................. 6
4.5 REQUEST FOR AUTHENTICATION SET (SAI) FAILURE RATE .......................................................................... 6
4.6 REQUEST FOR SHORT MESSAGE SERVICE (SRISM) FAILURE RATE .............................................................. 7
4.7 REQUEST FOR DATABASE ERRORS ................................................................................................................ 8
4.8 REQUEST FOR TRANSACTION PROCESS OVERLOAD ERRORS ......................................................................... 9
4.9 REQUEST FOR SOAP ERRORS ....................................................................................................................... 9
4.10REQUEST FOR SS7 MEASUREMENTS .......................................................................................................... 10
4.11REQUEST FOR INCOMING TRANSACTIONS .................................................................................................. 10
5 PROVISIONING GATEWAYS KPI ................................................................ 11
5.1 AVERAGE PROCESSOR UTILIZATION ........................................................................................................... 11
5.2 PGW SUCCESS RATE .................................................................................................................................. 11
5.3 PGW-DSA (NOTIFICATION SERVER) SUCCESS RATE ................................................................................. 12
6 ONE EIR .................................................................................................... 13
6.1 OPERATIONAL PERFORMANCE .................................................................................................................... 13
6.2 DATABASE PERFORMANCE.......................................................................................................................... 13
7 PCC ........................................................................................................... 13
7.1 SS7 MEASUREMENT STATS ......................................................................................................................... 13
7.2 CPU STATISTICS MEASUREMENT................................................................................................................ 13
8 MSRC (MML TO SPML CONVERTOR) ........................................................... 14

Confidential Page 2 of 14 9/17/2013

1 Purpose and Scope

The document provides a proposal for effective KPI definitions to monitor all
relevant functionalities of the ATCA NT HLR and the PGW. Noticeably, defining KPI is
not a one-time action but rather a on-going process and the definitions might
change when more results from real networks will become available. The purpose of
this document is to highlight the set of the most important performance indicators
for the ATCA NT HLR. This set of performance indicators is sufficient for monitoring
the most important aspects of the CSDB data less architecture.

2 Common Subscriber Database Architecture

The general system architecture is depicted on Figure 2-1. The subscriber data is
stored in a rack server called DS (Directory Server). The DS data is replicated to the
other 2 DSes to form so called BE-DSA (Back End Directory Service Agent) of 3 nodes
containing the same data. As the BE-DSA has a limited capacity, there might be many
of them in the system. If so, and to make the HLR response faster, the additional R-
DSAs (Routing Directory Service Agents) are put in, which contain no subscriber data
but routing to the proper BE-DSA only. All the BE-DSAs and R-DSAs form a single
ultra fast LDAP server to provide customer applications with its data.

Confidential Page 3 of 14 9/17/2013

A node which provides service logic (3GPP TS 29.002) to the network, and maps SS7
messages into LDAP queries is called NT HLR FE (NT HLR Front End). The upside of
the network NT HLR solution is that any NT HLR FE may handle request concerning
any subscriber because it is up to R-DSA to find the BE-DSA containing the requested
data. The NT HLR FE communicates to the HSMs to generate the authentication
vectors based on the keys fetched from the LDAP server previously.

The provisioning is implemented in two steps of PGW (Provisioning Gateway) which

maps provisioning protocol (as Service Provisioning Markup Language) into LDAP,
and PGW-DSA (Provisioning DSA) which stores internal PGW data.

3 KPI Classification

The DL HLR evolution system architecture consists of two main products: ATCA NT
HLR as a Front End, One-NDS for DX HLR and PGW as provisioning gateways. The
KPI’s are broadly classified for three network components:

 NT HLR FE KPI
 One NDS KPI
 PGW/PGW-DSA KPI
 OneEIR KPI
 PCC
 MSRC (MML to SPML Convertor)

Note: The OneNDS KPI are already captured as part of CSDB Phase-1 and is already
incorporated in MS portal.

4 NT HLR FE KPIs

4.1 CPU Statistics Measurement

HLR FE CPU Load: (Counter ID: cpuAverageLoad)

TIAMS CPU Load: (Counter ID: cpuLoad)

4.2 Update Location Failure Rate (VLR): HPLMN

Indicates how often a location update from a VLR of the HPLMN was unsuccessfully
handled.

(UN_UPL_VLRHPMN_SUBBEH+UN_UPL_VLRHPMN_IRRVLR+UN_UPL_VLRHPMN_IRRSYS+UNS_LOC_UPD_OVL)
---------------------------------------------------------------------------------------------------------------------------------------
RCVD_UPL_VLRHPLMN + UNS_LOC_UPD_OVL

Triggers:

UN_UPL_VLRHPMN_SUBBEH: Indicates the number of losses due to improper

behavior of a national location update of subscribers

Confidential Page 4 of 14 9/17/2013

Counter 261.4.1.1

UN_UPL_VLRHPMN_IRRVLR: Indicates the number of losses due to improper

behavior of national location update of subscribers (for example, due to the
following MAP errors: data missing, unexpected data value, unknown subscriber
Counter 261.4.1.2

UN_UPL_VLRHPMN_IRRSYS: Indicates the number of losses due to system behavior

during a national location update (or any other cause for a negative response to the
visitor location register (VLR)).
Counter 261.4.1.3

RCVD_UPL_VLRHPLMN: Indicates the number of received location update requests

from the home PLMN’s (HPLMN) visitor location register (VLR).
Counter 261.4.1.5

UNS_LOC_UPD_OVL: Indicates the number of rejected location update (LUP)

messages due to overload.
Counter 260.5.14

4.3 Update Location Failure Rate (VLR): VPLMN

Indicates how often a location update from a VLR of the VPLMN was unsuccessfully
handled.

UN_UPL_VLRVPMN_SUBBEH+UN_UPL_VLRVPMN_IRRVLR+UN_UPL_VLRVPMN_IRRSYS+UNS_LOC_UPD_OVL
-----------------------------------------------------------------------------------------------------------------------------------------------------
RCVD_UPL_VLRVPMN + UNS_LOC_UPD_OVL

Triggers:

UN_UPL_VLRVPMN_SUBBEH: Indicates the number of losses due to improper

behavior of a national location update of subscribers
Counter 261.4.2.1

UN_UPL_VLRVPMN_IRRVLR: Indicates the number of losses due to improper

behavior of national location update of subscribers (for example, due to the
following MAP errors: data missing, unexpected data value, unknown subscriber
Counter 261.4.2.2

UN_UPL_VLRVPMN_IRRSYS: Indicates the number of losses due to system behavior

during a national location update (or any other cause for a negative response to the
visitor location register (VLR)
Counter 261.4.2.3

Confidential Page 5 of 14 9/17/2013

RCVD_UPL_VLRVPMN: Indicates the number of received location update requests
from the visited PLMN’s (VPLMN) visitor location register (VLR)
Counter 261.4.2.5

UNS_LOC_UPD_OVL: Indicates the number of rejected location update (LUP)

messages due to overload.
Counter 260.5.14

4.4 Send Routing Info (MTC) Failure Rate

Indicates the performance for a mobile terminating call

UNS_SNDRTINF_ERROR+UNS_SNDRTINF_GMSCBEH+UNS_SNDRTINF_MS_BEH+UNS_MTC_OVL
------------------------------------------------------------------------------------------------------
RCVD_ROUTINFO_GMSC + UNS_MTC_OVL

Triggers:

RCVD_ROUTINFO_GMSC: Indicates the number of SendRoutingInfo requests

received from a gateway MSC
Counter 261.6.1

UNS_SNDRTINF_ERROR: Indicates the number of TC-END U-ERROR messages

including the proper MAP errors HLR sends to a gateway MSC (GMSC) in response to
a SendRoutingInfo request.
Counter 261.6.3

UNS_SNDRTINF_GMSCBEH: Indicates the number of TC-END TC-UERROR messages

including the proper MAP errors HLR sends to a gateway MSC (GMSC) in response to
a SendRoutingInfo request.
Counter 261.6.4

UNS_SNDRTINF_MS_BEH: Indicates how often a SendRoutingInfo request is received

and no VLR address is stored in HLR.
Counter 261.6.7

UNS_MTC_OVL: Indicates the number of rejected Mobile Terminating Call (MTC)

messages due to overload.
Counter 260.5.13

4.5 Request for Authentication Set (SAI) Failure Rate

Indicates how often requests for authentication data are unsuccessfully handled.

UNS_SND_PARAM_AR+UNS_SAI_V2_NO_VEC+UNS_SEND_AUTH_INFO_V2+UNS_SAI_V3_NO_VEC+UNS_SEND
_AUTH_INFO_V3
------------------------------------------------------------------------------------------------------------------------------------------
RECVD_SEND_PARAM_AR+RCD_SEND_AUTH_INFO_V2+RCD_SND_AUTH_INF_V3

Confidential Page 6 of 14 9/17/2013

 Triggers:

RECVD_SEND_PARAM_AR: Indicates the number of received SendParameters V1

requests for authentication vectors.
Counter 260.6.1

UNS_SND_PARAM_AR: Indicates the number of unsuccessful SendParameters V1

requests for authentication vectors
Counter 260.6.6

RCD_SEND_AUTH_INFO_V2: Indicates the number of received SAI V2 requests.

Counter 260.6.7

UNS_SAI_V2_NO_VEC: Indicates the number of unsuccessful SAI V2 requests due to

unavailability of authentication vectors.
Counter 260.6.8

UNS_SEND_AUTH_INFO_V2: Indicates the number of unsuccessful SAI V2 requests

due to any other reason, for example, dialog breakdown.
Counter 260.6.9

RCD_SND_AUTH_INF_V3: Indicates the number of received SAI V3 requests.

Counter 260.6.10

UNS_SAI_V3_NO_VEC: Indicates the number of unsuccessful SAI V3 requests due to

unavailability of authentication vectors.
Counter 260.6.11

UNS_SEND_AUTH_INFO_V3: Indicates the number of unsuccessful SAI V3 requests

due to any other reason, for example, dialog breakdown.
Counter 260.6.13

4.6 Request for Short Message Service (SRISM) Failure Rate

Indicates how SRISM of SMSC are unsuccessfully handled.

UNS_GMSC_BEHAVIOR+UNS_SUB_BEHAVIOR+UNS_SECONDARY_CAUSES+UNS_SMS_OVL+UNS_ADMBLCKD_CALLBAR
---------------------------------------------------------------------------------------------------------------------------------------
RECVD_SND_SRIFSM + UNS_SMS_OVL

Triggers:

UNS_GMSC_BEHAVIOR: Indicates the number of TCU-ERRORs HLR sends to the

gateway MSC (GMSC) due to a subscription error in response to its request.
Counter 261.5.8

Confidential Page 7 of 14 9/17/2013

UNS_SUB_BEHAVIOR: Indicates the number of TCU-ERRORs HLR sends to the
gateway MSC (GMSC) in reply to a SendRoutingInfoForSM request.
Counter 261.5.9

UNS_SECONDARY_CAUSES: Indicates the number of TCU-ERRORs due to secondary

causes HLR sends to the gateway MSC (GMSC) in response to its request. Indicates
how often a routing info request for an SM is handled unsuccessfully due to
secondary causes.
Trigger: Each time TC-UERROR is sent to GMSC in response to SRISM in case of data
base and configuration data access failures (Internal error).
Counter 261.5.10

RECVD_SND_SRIFSM: Indicates the number of received SendRoutingInfo ForSM

requests.
Counter 261.5.1

UNS_SMS_OVL: Indicates the number of rejected Short Message Services (SMS)

messages due to overload.
Counter 260.5.17

UNS_ADMBLCKD_CALLBAR: Indicates the number of TCU-ERRORs HLR sends to the

gateway MSC (GMSC) due to call barring in response to its request.
Counter 260.5.6

4.7 Request for Database Errors

Performance counters for database access are used to monitor the LDAP access to
the directory servers of the subscriber repository. To read and update subscriber
data, the NT HLR FE uses LDAP.

LDAP Read Error: DB_READ_STATS_ERROR + DB_READ_OTHER_ERROR

LDAP Write Error: DB_WRITE_STATS_ERROR + DB_WRITE_OTHER_ERROR

Triggers:

DB_READ_STATS_ERROR: Indicates the number of erroneous read responses that

are considered for error threshold statistics.
Counter 262.14.11

DB_READ_OTHER_ERROR Indicates the number of erroneous read responses, other

than those considered for calculation of statistics.
Counter 262.14.12

DB_WRITE_STATS_ERROR: Indicates the number of erroneous write responses that

are considered for error threshold statistics
Counter 262.14.13

Confidential Page 8 of 14 9/17/2013

DB_WRITE_OTHER_ERROR: Indicates the number of erroneous write responses,
other than those considered for calculation of statistics.
Counter 262.14.14

4.8 Request for Transaction Process Overload Errors

Indicates performance counters that monitor transaction processing overload (HOL)

of HLR FEs.
UNS_ALL_OVL
UNS_MTC_OVL
UNS_LOC_UPD_OVL
UNS_SMS_OVL
Triggers:

UNS_ALL_OVL: Indicates the total number of rejected messages due to overload.

Counter 260.5.12

UNS_MTC_OVL: Indicates the number of rejected Mobile Terminating Call (MTC)

messages due to overload.
Counter 260.5.13

UNS_LOC_UPD_OVL: Indicates the number of rejected location update (LUP)

messages due to overload.
Counter 260.5.14
UNS_SMS_OVL: Indicates the number of rejected Short Message Services (SMS)
messages due to overload.
Counter 260.5.17

4.9 Request for SOAP Errors

Performance counters for the trigger framework are used to monitor trigger
messages between the HLR and the subscriber repository. The application trigger
interface between the subscriber repository and the NT HLR FEs is implemented
using the Simple Object Access Protocol (SOAP). The triggers are always sent by the
subscriber repository and received by the NT HLR application client. Having
performed necessary actions or data checks, the client sends a response back to the
subscriber repository.
UNS_SOAP_TRIG_REQ
---------------------------------
RECVD_SOAP_TRIG_REQ

Triggers:

RECVD_SOAP_TRIG_REQ: Indicates the total number of Simple Object Access

Protocol (SOAP) requests received at NT HLR.
Counter 262.15.1

Confidential Page 9 of 14 9/17/2013

UNS_SOAP_TRIG_REQ: Indicates the total number of Simple Object Access Protocol
(SOAP) requests rejected with SOAP fault messages.
Counter 262.15.2

4.10 Request for SS7 Measurements

The following performance counters are used to monitor the SS7 configuration through
SIGTRAN stack.

M3UA_MSU_SENT: Indicates the total number of MSUs sent via all M3UA links.
Counter 270.28

M3UA_MSU_RECEIVED: Indicates the total number of MSUs received by all M3UA

links.
Counter 270.29

NUM_M3UA_LINKS: Indicates the number of M3UA links configured in the system.

Counter 270.30
M3UA_LINK_CONGESTED: Indicates the total number of seconds the M3UA links
were congested.
Counter 270.35

M3UA_MSU_DISCARDED: Total number of MSUs discarded due to congestion of

M3UA links.
Counter 270.36
M3UA_BYTES_SENT: Indicates the total number of bytes transmitted via all M3UA
links.
Counter 270.37

M3UA_BYTES_RECEIVED: Indicates the total number of bytes received by all M3UA

links.
Counter 270.38

M3LNK_BYTES_SENT,M3LNK_BYTES_RCVD, M3LNK_MSU_SENT, M3LNK_MSU_RCVD

M3LNK_MSU_DSCRD counters can be referred to get values on per M3UA link basis.

4.11 Request for Incoming transactions

The following performance counters are used to monitor the total incoming TCAP
transactions (valid for MAP)

Total TC– BEGIN messages received

Need to capture the following as well

 Transaction per active subscriber
 Transaction per VLR-T

Confidential Page 10 of 14 9/17/2013

5 Provisioning Gateways KPI

The Provisioning Gateway (PGW) is used to manage subscriber data. It provides a

logical view on the stored data and offers an interface towards the customer care
system over SPML/DSML or batch files of bulk provisioning. The PGW uses the
Provisioning DSA (Notification Servers) to store internal data including a record of
which PGW node process a given current request. The latter information would be
necessary to cancel or display request status

5.1 Average Processor Utilization

The average processor utilization (i.e. the amount of time during the last statistics
interval that the processor has not been idle, expressed as a percentage).

Note: To be taken from OneNDS performance report

5.2 PGW Success Rate

Total requests received by PGW:

SOAP_SPML_REQ_RECVD+BULK_SPML_ORDERS_RECVD-INVALID_SPML_SYNTAX-
INVALID_REQUEST_TYPE

Triggers:

SOAP_SPML_REQ_RECVD: Indicates the number of authenticated and validated

SPML requests received over the SOAP interface.
Counter: 3000.31

BULK_SPML_ORDERS_RECVD: Indicates the number of SPML bulk orders received

over the bulk file interface
Counter: 3150.2

INVALID_SPML_SYNTAX: Indicates the number of syntactically invalid SPML requests.

Counter: 3150.19

INVALID_REQUEST_TYPE: Indicates the number of requests whose type could not be

resolved
Counter: 3150.18

Total failures on PGW:

SPML_REQ_FAIL+LDAP_CONNECTION_FAIL+REQUEST_TIMEOUT+RESPONSE_TIMEOUT

Confidential Page 11 of 14 9/17/2013

Triggers:

SPML_REQ_FAIL: Indicates the number of authentic and valid SPML requests that are
not updated successfully into the One-NDS Directory.
Counter: 3150.41

LDAP_CONNECTION_FAIL: Indicates the number of failures in bind/rebind attempts

Counter: 3000.20

REQUEST_TIMEOUT: Indicates the number of requests failed because of processing

time-outs.
Counter: 3150.25

RESPONSE_TIMEOUT: Indicates the number of response time-outs sent to the client.

Counter: 3150.27

Note: To be taken from OneNDS performance report

Total Request on PGW – Total Failures on PGW

PGW Success Rate= ------------------------------------------------------------------
Total Request on PGW

5.3 PGW-DSA (Notification Server) Success Rate

The PGW DSA (PGD) stores the configuration data of the PGW and performs the
function of notification. The Notification Manager (NTF) is a central component for
distributing all notifications from One-NDS components, that is, the NTF is
responsible for the distribution of SOAP trigger messages from the One-NDS
Directory to both PGW and application servers

Total Notification Received:

NotificationRequestReceived: Indicates No. of Notification requests received

Counter: 5001.0

Total Notification Undelivered:

NotificationRequestUndeliverable: Indicates No. of undeliverable Notification

requests.
Counter: 5001.2

Total Notification Request– Total Notification Undelivered

PGW-DSA Success Rate= ---------------------------------------------------------------------------------
Total Notification Request

Confidential Page 12 of 14 9/17/2013

 6 One EIR

The One-EIR system integrates the One-EIR Application Frontends and the One-NDS.
The One-EIR is integrated into the Nokia Siemens Network's NetAct OAM
environment for element management and consists of EIR-FE CPU blade.

6.1 Operational Performance

Following counters are used to monitor the operational performance of OneEIR:

Sl.
Counter Remarks
No
1 chImReq Number of CheckIMEI messages received
2 white Number of CheckIMEI message responses sent with equipment status of white.
3 grey Number of CheckIMEI message responses sent with equipment status of grey
4 black Number of CheckIMEI message responses sent with equipment status of black
5 unknown Number of MAP Error messages sent with reason ‘Unknown Equipment‘
6 chImRes Number of SS7 Check IMEI responses sent
7 chImErr Number of MAP Errors (Total)
8 sysfail The MAP Message responded back with System Failures
9 datamiss Number of times data is missing in messages sent
10 unexpdat Number of times invalid data is sent in messages
EIRFE Success
(chImRes/chImReq)*100
Rate

6.2 Database Performance

1. DB memory in Use: The amount of database memory in use (bytes)

2. DB memory in Total: The total size of database memory (bytes)
3. DB memory in Use freed: The amount of in use memory that has been freed and is
available for re-use (bytes))
4. DB memory utilization: The database memory utilization expressed as a percentage.

7 PCC

7.1 SS7 Measurement stats

The SS7 measurement statistics will consist of MTP, SCCP and Sigtran related
measurement reports.

7.2 CPU Statistics Measurement

PCC CPU Load: (Counter ID: cpuAverageLoad)

Confidential Page 13 of 14 9/17/2013

8 MSRC (MML to SPML Convertor)

Avg TPS
D:\userdata\
Peak TPS Load Report apriyada\My Docum
Avg Processor Load
Peak Processor Load
Convertor
MML Request Received on MSRC D:\userdata\
KPI Count apriyada\My Docum
MML Request Success on MSRC
Report
Success Rate on MSRC
Count of PGW Errors
D:\userdata\
Count of MSRC Errors Error Report apriyada\My Docum
Error Code Conversion Success

Confidential Page 14 of 14 9/17/2013