1. EAGLE IDP-Related Features User's Guide
  2. Measurements

7 Measurements

This chapter describes the measurements that can be collected and generated for IDP Relay and IDP Relay-related features, and the methods that can be used for generating reports for the measurements.

7.1 Prepaid IDP Query Relay Measurements

The EAGLE Measurements system supports the collection and retrieval of measurements related to the IDP Relay feature. The IDP Relay measurements can be collected and reported with the following collection methods:
  • OAM-based (UI) measurements collection
  • 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

15 Minute Measurements can be used with the Measurements Platform or E5-OAM Integrated Measurements.

Refer to Measurements Reference for descriptions of collection methods, 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 IDP Relay.

Two measurements reports contain IDPR measurements:
  • The SYSTOT-STP report is generated using the enttype=stp parameter.

    For IDP Relay, the SYSTOT-STP report displays only the four original registers.

  • The SYSTOT-IDPR report is generated using the enttype-idpr parameter.

    For IDP Relay, the SYSTOT-IDPR report displays the four original registers, the registers for the NPP INPRTG Service Action CONNECT, CONTINUE, RELAY, and RELEASECALL responses, and the registers for the NPP SKGTARTG Service Action.

IDPR measurements registers are defined for the IDP Relay feature IDPR service and reported as indicated in Table 7-1.

Table 7-1 IDPR Measurements Registers

Register Description In SYSTOT-STP Report In SYSTOT-IDPR Report
IDPRMSERR The total number of MSUs selected for IDPR service that could not be processed due to errors in encoding, decoding, or formatting, or to IDP A-Part Routing or IDP Service Key Routing errors X X
IDPRMSFAIL Total number of MSUs that were selected for IDPR service and fell through to GTT due to the following conditions:
  • No match on MSISDN in the RTDB lookup
  • Match on MSISDN but no association to RN or SP for the CDPNNP or CGPNNP Service Actions
  • No match for IDP A-Party Blacklist query-response criteria
  • IDP A-Party Blacklist Relay resulted in falling through to GTT for routing
  • IDP A-Party Routing or IDP Service Key Routing resulted in falling through to GTT routing (due to no match on MSISDN or insufficient data)
 X X
IDPRMSRCV Total number of MSUs received and selected for IDPR service. This register includes counts for MSUs that resulted in both successful and unsuccessful RTDB lookups. X X
IDPRMSSUCC Number of MSUs selected for IDPR service for which the RTDB lookup resulted in a match on MSISDN with association to an RN or SP. This includes pegs to IDPAPTYRTD, IDPSKRTD, IDPBKLCONN, and IDPBKLCONT registers. X X
IDPINPRTG Number of IDP MSUs that are processed by the NPP INPRTG Service Action from the IDPRCDPN service.   X
IDPINPRTG2 Number of IDP MSUs that are processed by the NPP INPRTG Service Action from the IDPRCDPN2 service.   X
IDPINPRTG3 Number of IDP MSUs that are processed by the NPP INPRTG Service Action from the IDPRCDPN3 service.   X
IDPINPRTG4 Number of IDP MSUs that are processed by the NPP INPRTG Service Action from the IDPRCDPN4 service.   X
IDPSKGTARTG Number of IDP messages processed by the SKGTARTG Service Action from the IDPRCDPN service.   X
IDPSKGTARTG2 Number of IDP messages processed by the SKGTARTG Service Action from the IDPRCDPN2 service.   X
IDPSKGTARTG3 Number of IDP messages processed by the SKGTARTG Service Action from the IDPRCDPN4 service.   X
IDPSKGTARTG4 Number of IDP messages processed by the SKGTARTG Service Action from the IDPRCDPN4 service.   X
IDPINPCONN Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONNECT message from the IDPRCDPN service.   X
IDPINPCONN2 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONNECT message from the IDPRCDPN2 service.   X
IDPINPCONN3 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONNECT message from the IDPRCDPN3 service.   X
IDPINPCONN4 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONNECT message from the IDPRCDPN4 service.   X
IDPINPCONT Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONTINUE message from the IDPRCDPN service.   X
IDPINPCONT2 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONTINUE message from the IDPRCDPN2 service.   X
IDPINPCONT3 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONTINUE message from the IDPRCDPN3 service.   X
IDPINPCONT4 Number of IDP MSUs for which the NPP INPRTG Service Action sent a CONTINUE message from the IDPRCDPN4 service.   X
IDPINPRLC Number of IDP MSUs for which the NPP INPRTG Service Action sent a RELEASECALL message from the IDPRCDPN service.   X
IDPINPRLC2 Number of IDP MSUs for which the NPP INPRTG Service Action sent a RELEASECALL message from the IDPRCDPN2 service.   X
IDPINPRLC3 Number of IDP MSUs for which the NPP INPRTG Service Action sent a RELEASECALL message from the IDPRCDPN3 service.   X
IDPINPRLC4 Number of IDP MSUs for which the NPP INPRTG Service Action sent a RELEASECALL message from the IDPRCDPN4 service.   X
IDPRCDPN Total number of IDP messages processed for the IDPRCDPN service.   X
IDPRCDPN2 Total number of IDP messages processed for the IDPRCDPN2 service.   X
IDPRCDPN3 Total number of IDP messages processed for the IDPRCDPN3 service.   X
IDPRCDPN4 Total number of IDP messages processed for the IDPRCDPN4 service.   X
The following IDPR measurements registers are defined for the IDP Relay feature IDPR service. All IDPR registers are reported in the STP System Total (SYSTOT-STP) report.

  • IDPRMSERR The total number of MSUs selected for IDPR service that could not be processed due to errors in encoding, decoding, or formatting, or to IDP A-Part Routing or IDP Service Key Routing errors .

  • IDPRMSFAIL Total number of MSUs that were selected for IDPR service and fell through to GTT due to the following conditions:
    • No match on MSISDN in the RTDB lookup
    • Match on MSISDN but no association to RN or SP for the CDPNNP or CGPNNP Service Actions
    • No match for IDP A-Party Blacklist query-response criteria
    • IDP A-Party Blacklist Relay resulted in falling through to GTT for routing
    • IDP A-Party Routing or IDP Service Key Routing resulted in falling through to GTT routing (due to no match on MSISDN or insufficient data)

  • IDPRMSRCV Total number of MSUs received and selected for IDPR service. This register includes counts for MSUs that resulted in both successful and unsuccessful RTDB lookups.

  • IDPRMSSUCC Number of MSUs selected for IDPR service for which the RTDB lookup resulted in a match on MSISDN with association to an RN or SP. This includes pegs to IDPAPTYRTD, IDPSKRTD, IDPBKLCONN, and IDPBKLCONT registers.

Measurements for the IDP A-Party Routing feature are described in .IDP A-Party Routing and IDP Service Key Routing Measurements Figure 7-1 illustrates the impact of the IDP A-Party Routing feature measurements pegging on the IDPR registers.

Figure 7-1 IDP A-Party Routing Impact on IDP Relay Measurements

img/idpr_aparty_routing_meas_impact.jpg

Table 7-2 IDP A-Party Routing and IDP Relay Pegs

IDP A-Party Routing and Service Key Routing Pegs IDP Relay Pegs

IDPAPTYRTD = S1

IDPAPTYSKR = S2

IDPAPTYGTT = F1 + F2

IDPRMSERR = E0 + E1 +E2

IDPRMSFAIL = F0+ F1+ F2

IDPRMSSUCC = S0 + S1 + S2

IDPRMSRCV = IDPRMSERR + IDPRMSFAIL + IDPRMSSUCC

Note: GTT success (S3) and GTT failure (E3) measurements registers are pegged separately.

Measurements for the IDP Service Key Routing feature are described in IDP A-Party Routing and IDP Service Key Routing Measurements. Figure 7-2 illustrates the impact of the IDP Service Key Routing feature measurements pegging on the IDPR registers.

Figure 7-2 IDP Service Key Routing Impact on IDP Relay Measurements

img/idpr_sk_routing_meas_impact.jpg

Table 7-3 IDP Service Key Routing and IDP Relay Pegs

IDP Service Key Routing Pegs IDP Relay Pegs

IDPSKRTC = S2

IDPSKGTT = F2

IDPRMSERR = E0 + E2

IDPRMSFAIL = F0 + F2

IDPRMSSUCC = S0 + S2

IDPRMSRCV = IDPRMSERR +IDPRMSFAIL + IDPRMSSUCC

Note: GTT success (S3) and GTT failure (E3) measurement registers are pegged separately.

Measurements for the IDP A-Party Blacklist feature are described in IDP A-Party Blacklist Measurements. Figure 7-3 illustrates the impact of the IDP-A-Party Blacklist feature measurements pegging on the IDPR registers.

Figure 7-3 IDP A-Party Blacklist (Query and Relay) Impact on IDP Relay Measurements

img/idpr_blacklist_meas_impact.jpg

Table 7-4 IDP A-Party Blacklist and IDP Relay Pegs

IDP A-Party Blacklist Pegs IDP Relay Pegs

IDPBKLCONN = S1

IDPBKLCONT = S2

IDPRMSERR = E0 + E2

IDPRMSFAIL = F0

IDPRMSSUCC = S0 + S1 + S2

IDPRMSRCV = IDPRMSERR + IDPRMSFAIL + IDPRMSSUCC

Note: GTT success (S3) and GTT failure (E3) measurements registers are pegged separately.

7.2 IDP A-Party Blacklist Measurements

Refer to Measurements Reference for descriptions of measurements and measurements reports for IDP A-Party Blacklist and IDP Relay.

See Prepaid IDP Query Relay Measurements for information about supported collection methods for IDP Relay-related measurements, and for a description of the relationship between IDP Relay and IDP A-Party Blacklist measurements.

The following measurement registers are defined for the IDP A-Party Blacklist feature. All registers for this feature are reported in the STP System Total (SYSTOT-STP) report.

  • IDPBKLCONN Total number of IDP messages received that matched the blacklist criteria and a CONNECT response was generated.

  • IDPBKLCONT Total number of IDP messages received that did not match the blacklist criteria and a CONTINUE response was generated.

The following existing IDP Relay registers are affected by the IDP A-Party Blacklist feature:
  • IDPRMSFAIL Total number of MSUs that were selected for IDPR service and that fell through to GTT due to the following conditions:
    • No match on MSISDN in the RTDB
    • Match on MSISDN but no association to RN or SP for CDPNNP or CGPNNP
    • No match for IDP A-Party Blacklist query-response criteria
    • IDP Blacklist relay resulted in falling through to GTT for routing
  • IDPRMSERR Total number of MSUs selected for IDPR service that could not be processed due to error in encoding, decoding, or formatting.
  • IDPRMSSUCC Number of MSUs selected for IDPR service for which the requested IDPR feature set functions were executed successfully. This includes pegs to the IDPBKLCONN and IDPBKLCONT registers.

The measurements are available in 30-minute intervals, and in 15-minute intervals when 15-Minute Measurements collection is enabled.

7.3 IDP A-Party Routing and IDP Service Key Routing Measurements

Refer to Measurements Reference for descriptions of measurements and measurements reports for IDP A-Party Routing, IDP Service Key Routing, and IDP Relay

Refer to Prepaid IDP Query Relay Measurements for information about supported collection methods for IDP Relay-related measurements, and for a description of the relationship between IDP Relay, IDP A-Party Routing, and IDP Service Key Routing measurements.

The following measurement registers are defined for the IDP A-Party Routing and IDP Service Key Routing features. The registers are updated through the IDPR service processing. All registers for these features are reported in the STP System Total (SYSTOT-STP) report.

  • IDPSKGTT Total number of IDP/IDPSSM messages that were selected for Service Key Routing (without having first gone to A-Party Routing), but fell through to GTT.

  • IDPSKRTD Total number of IDP/IDPSSM messages that were selected for Service Key Routing (without having first gone to A-Party Routing), and were successfully routed based on SK/BCSM PPSOPTS data.

  • IDPAPTYRTD Total number of IDP/IDPSSM messages that were selected for A-Party Routing service, and were successfully routed based on A-Party PPSOPTS routing data (routing data associated with the RTDB Prepaid Type assigned to the A-Party digits).

  • IDPAPTYSKR Total number of IDP/IDPSSM messages that were selected for A-Party Routing service, but fell through to Service Key (SK) Routing, and were successfully routed based on SK/BCSM PPSOPTS data (routing data associated with the RTDB Prepaid Type assigned to the SK/BCSM entry).

  • IDPSKGTT Total number of IDP/IDPSSM messages that were selected for Service Key Routing (without having first gone to A-Party Routing), but fell through to GTT.

  • IDPAPTYGTT Total number of IDP/IDPSSM messages that were selected for A-Party Routing service, but fell through to GTT (with or without having attempted Service Key Routing first).

The following existing registers are affected by the IDP A-Party Routing and IDP Service Key Routing features:
  • IDPRMSFAIL Total number of MSUs selected for IDPR service that fell through to GTT due to the following conditions:
    • No match on MSISDN in the RTDB
    • Match on MSISDN but no association to RN or SP for CDPNNP or CGPNNP
    • IDP A-Party or SK Routing resulted in falling through to GTT routing (due to no match on MSISDN or insufficient data)
  • IDPRMSERR Total number of MSUs selected for IDPR service that could not be processed due to an error in encoding, decoding, formatting, or IDP A-Party Routing or IDP SK Routing.
  • IDPRMSSUCC Number of MSUs selected for IDPR service for which the requested IDPR feature set functions were executed successfully. This includes pegs to the IDPAPTYRTD and IDPSKRTD registers.

The measurements are available in 30-minute intervals, and in 15-minute intervals when 15-Minute Measurements collection is enabled.

7.4 IDP Screening for Prepaid Feature Measurements

The EAGLE Measurements system supports the collection and retrieval of measurements related to the IDP Screening for Prepaid feature. The IDP Screening for Prepaid measurements can be collected and reported with the following collection methods:
  • OAM-based measurements collection
  • 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

15 Minute Measurements can be used with the Measurements Platform or E5-OAM Integrated Measurements.

Refer to Measurements Reference for descriptions of collection methods, 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 IDP Screening for Prepaid.

The following measurement registers are defined for the IDP Screening for Prepaid feature. All registers for this feature are reported in the STP System Total (SYSTOT-STP) report.

  • MSIDPNOMCH The total number of IDP messages that did not fully meet the criteria of the IDP Screening for Prepaid feature. These messages are relayed to their destination by GTT.

  • MSIDPMATCH The total number of IDP messages that fully met the criteria of the IDP Screening for Prepaid feature. Instead of sending the IDP message onward, a Continue message is sent to the originating MSC. The criteria involve matching the following TCAP fields with EAGLE Common Screening Lists:

    • The CalledPartyBCDNunber and Calling Party Number digits are provisioned in the In-Network Subscriber List (INSL).
    • The TeleService and Service Key values are in the SKTS List.