1. EAGLE INP/AINPQ User's Guide
  2. INP/AINPQ Measurements

5 INP/AINPQ Measurements

This chapter describes the measurements that can be collected and generated for the INP and AINPQ features.

5.1 INP/AINPQ Measurements

The EAGLE Measurements system supports the collection and retrieval of measurements for he INP and AINPQ features. The INP/AINPQ measurements can be collected and reported with the following collection methods:
  • OAM-based (UI) measurements collection - INP and INP CRP measurements are available using the File Transfer Area (FTA) and not directly to EAGLE UI terminals.
  • The Measurements Platform feature enabled and the Measurements Platform collection option on
  • The E5-OAM Integrated Measurements feature enabled and on and the E5-OAM Integrated Measurements collection option on

Refer to Measurements Reference for detailed descriptions of measurements and measurements reports.

Refer to Commands User''s Guide for descriptions of the commands used to enable and turn on features, turn on measurements collection options, and schedule and generate measurements reports.

Refer to the procedures in Database Administration - System Management User''s Guide to configure the Measurements Platform feature or E5-OAM Integrated Measurements feature for use with the INP and AINPQ features.

Per System and Per SSP INP/AINPQ measurements are available in the Daily (MTCD) and Hourly (MTCH) reports for Entity Type NP.

Table 5-1 describes the Per System measurement peg counts of INP/AINPQ MSUs (Message Signalling Units) that are supported for the INP and AINPQ features. The pegs include counts used for the INP Circular Route Prevention (INP CRP), the INP Query Service (INPQS), and the INP Message Relay service (INPMR).

Table 5-1 Pegs for Per System INP/AINPQ Measurements

Event Name Description Type Unit

INPQRCV

Number of total queries received by INPQS; he total count of the number of the NPREQ and IDP queries received if either the INP feature, the AINPQ feature, or both, are turned on.

The following equation applies:

INPQRCV = INPQDSC + INPQTCPE + INPSREP

System

Peg count

INPQDSC

Number of invalid queries that are discarded as no reply can be generated

System

Peg count

INPQTCPE

Number of error replies with TCAP error code

System

Peg count
INPQSCRD Total number of circular routes detected by INPQS. System Peg count

INPSREP

Number of successful replies to INP/AINPQ queries. These replies will be:

  • Either INP Connect or INP Continue for the INP feature

  • Either Return Result with Digits or Return Result without Digits for the AINPQ feature.

  • Incremented every time a successful INAP RELEASECALL response is generated due to circular route detection by INPQS

    The following equation applies:

    INPSREP = INPQSCONN + INPQSCONT

System

Peg count

Table 5-2 describes the Per SSP measurement peg counts of INP/AINPQ MSUs that are supported for the INP and AINPQ features. The pegs include counts used for the INP Circular Route Prevention (INP CRP), the INP Query Service (INPQS), and the INP Message Relay service (INPMR).

Table 5-2 Pegs for Per SSP INP/AINPQ Measurements

Event Name Description Type Unit

INPQSCONN

Number of non-errored QS messages with QS

Point Code

Peg count

INPQSCONT

Number of non-errored QS messages with QS Continue or Return Result without Digits responses

Point Code

Peg count

INPMRTR

Number of messages sent to INPMR that receive MR translation

Point Code

Peg count

INPMRGTT

Number of messages sent to INPMR that fall through to GTT, including those that are due to circular route detection by INPMR

Point Code

Peg count
INPMRCRD Number of messages sent to INPMR that meet the condition for circular route detection by INPMR. Point Code Peg count
INPQSREL Total number of INAP RELEASECALL responses successfully generated due to circular route detection by INPQS Point Code Peg Count
INPQSCRD Total number of circular route detected by INPQS Point Code Peg count

The measurement events described in Table 5-3 are included on the STP Daily Maintenance (MTCD) and the STP Day-to-Hour (MTCDTH) measurement reports; the events include peg counts for INP/AINPQ MSUs. These reports are similar to those used for GTT. The existing GTT/SCCP measurements are used for both GTT and INP/AINPQ and appear in the same reports.

This implementation does not discriminate between the MSSCCPFL, GTTUN0NS, GTTUN1NT, or GTTPERFD pegs for INP/AINPQ or GTT applications. For example, a search failure could result from a problem in either the INP/AINPQ or GTT database.

Table 5-3 MTCD and MTCDTH Measurements

MSSCCPFL

MSUs discarded due to SCCP routing failure

Also includes INP/AINPQ MSUs that got a match from either the INP/AINPQ or GTT database, but cannot be routed because of PC (Point Code) or SS (Subsystem) congestion, PC or SS unavailable, SS unequipped, or an unqualified error.

GTTUN0NS

GTT unable to perform; no such type

Also includes INP/AINPQ Message Relay MSUs that did fall through to GTT but did not match on GTT selectors

GTTUN1NT

GTT unable to perform: no translation on this address

Also includes INP/AINPQ Message Relay MSUs that fell through to GTT, obtained a GTT selector match but still did not match on the GTA.

GTTPERFD

Number of GTT performed

Also includes INP/AINPQ MSUs that got a match in either the INP/AINPQ or GTT database.