| Oracle® Communications Measurements Reference Release 46.6 E93320 Revision 1 |
|
 Previous |
 Next |
The hourly Number Portability measurements specify the entity type NP (enttype=np) which generates two separate reports per period. These reports for basic OAM measurements are generated as CSV files in the FTA. The command example will generate the following hourly reports:
Hourly System Wide Measurements
Hourly Measurements Per SSP
NP_SSP and NP_SYS reports consider system-wide SCCP cards regardless of the database type (i.e., RTDB/EPAP or RIDB/ELAP) in the system.
If any of the above cards are ISOLATED/OOS during a measurement interval, the respective report is marked I. The report is marked K only when all the cards under consideration are IS_NR throughout the measurement interval.
Command Examples
rept-meas:type=mtch:enttype=np:period=specific:day=xxx rept-ftp-meas:type=mtch:enttype=np[:period=specific:day=xxx] Measurement Events
System Wide Measurements
indicates system registers that may be pegged. Register counts for features not turned on will always be zero.
Table 3-154 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) System-Wide Registers
| Event Name | Description | Unit |
|---|---|---|
| APSMRQERR |
Number of SMSREQ messages resulting in error. |
peg count |
| APSMRQREP |
Number of SMSREQ messages resulting in SMSREQ_ACK or SMSREQ_NACK. |
peg count |
| APSMSRCV |
Number of SMS Request messages received. |
peg count |
| APSMSREL |
Number of SMS Request messages relayed. |
peg count |
| GPNOCL |
Number of non-call related messages relayed by G-Port. |
Peg Count |
| GPNOCLGT |
Number of non-call related messages that fell through to GTT. |
Peg Count |
| GPSRERR |
Number of call related messages that cause an error response message(SRI-Send Routing Information NEGATIVE ACK) because of G-Port service failure. This does not include peg counts to register GPSRERRPP. |
Peg Count |
| GPSRREPPP |
Number of call related (SRI-Send Routing Information) messages that received G-Port service specifically for feature: G-Port SRI query for Prepaid. This does not include peg counts to register GPSRREP. |
Peg Count |
| GPSRGTT |
Number of call related (SRI-Send Routing Information) messages that fell through to GTT. This does not include peg counts to register GPSRGTTPP. |
Peg Count |
| GPSRGTTPP |
Number of call related (SRI-Send Routing Information) messages that fell through to GTT specifically for feature: G-Port SRI query for Prepaid. This does not include peg counts to register GPSRGTT. |
Peg Count |
| GPSRRCV |
Number of call related (SRI-Send Routing Information) messages received. This does not include peg counts to register GPSRRCVPP. |
Peg Count |
| GPSRRCVPP |
Number of call related (SRI-Send Routing Information) messages received specifically for feature: G-Port SRI query for Prepaid. This does not include peg counts to register GPSRRCV. |
Peg Count |
| GPSRREP |
Number of call related (SRI-Send Routing Information) messages that received G-Port service. This does not include peg counts to register GPSRREPPP. |
Peg Count |
| GPSRERRPP |
Number of call related messages that cause an error response message (SRI-Send Routing Information NEGATIVE ACK) specifically for feature: G-Port SRI query for Prepaid. This does not include peg counts to register GPSRERR. |
Peg Count |
| GPSRSMERR |
Number of SRI_SM messages resulting in error. |
peg count |
| GPSRSMRCV |
Number of SRI_SM messages received. |
peg count |
| GPSRSMREP |
Number of SRI_SM messages resulting in SRI_SM_ACK or SRI_SM_NACK. |
peg count |
| INPQDSC |
Number of invalid queries that are discarded as no reply can be generated. |
peg count |
| INPQRCV |
Number of total queries received by INPQS. |
peg count |
| INPQSCRD |
Number of queries received by INPQS that meet the condition for circular route detection. |
peg count |
| INPQTCPE |
Number of error replies with TCAP error code. |
peg count |
| INPSREP |
Number of successful replies to INP non-queried queries. These replies will be either INP Connect, INP Continue, or INP ReleaseCall (every time an INAP RELEASECALL response is generated due to circular route dection by INPQS). |
peg count |
| IS41LRERR |
Number of IS-41 location request - error response messages sent. |
peg count |
| IS41LRMRCV |
Number of IS-41 location request messages received |
peg count |
| IS41LRRTRN |
Number of IS-41 location request - return result messages sent |
peg count |
MNPCRD |
Number of times Circular Route is Detected |
peg count |
| SMSMOGERR |
Number of MO_SMS messages received that result in an error |
peg count |
| SMSMOGRCV |
Number of MO_SMS messages received that result in a modification of the outgoing MO_SMS |
peg count |
| SMSMOIERR |
Number of SMDPP messages received that result in an error |
peg count |
| SMSMOIRCV |
Number of SMDPP messages received that result in a modification of the outgoing SMDPP. |
peg count |
| STATUS |
Indication of Data Validity:
|
status |
TIFFPFXRLS |
Total number of MSUs processed by TIF and blacklisted by the FPFXRLS Service Action |
peg count |
TIFNFNDRLS |
Total number of MSUs processed by TIF and blacklisted by the BLNFNDRLS Service Action |
peg count |
TIFNOCGRLS |
Total number of MSUs processed by TIF and blacklisted by the NOCGPNRLS Service Action |
peg count |
TIFRLS |
Total number of MSUs processed by TIF and blacklisted by the BLRLS Service Action |
peg count |
TIFSSCRRLS |
Number of MSUs processed by TIF and found to be blacklisted by SELSCR Service Action |
peg count |
TIFSSCRRLY |
Number of MSUs processed by TIF and relayed by SELSCR Service Action |
peg count |
| TINPERR |
Number of IAM messages received that required TIFTINP processing but resulted in execution of an error case. |
peg count |
| TINPMGEN |
Number of IAM messages received that required TIFTINP processing and resulted in the modification of the IAM message or the generation of a REL message. |
peg count |
| TINPMRCV |
Number of IAM messages received that require TIFTINP processing. |
peg count |
The following equations apply:
INPQRCV = INPQDSC + INPQTCPE + INPSREP
GPSRRCV = GPSRGTT + GPSRREP + GPSRERR
GPSRRCVPP = GPSRGTTPP + GPSRREPPP + GPSRERRPP
GPSRSMRCV = GPSRSMRLY + GPSRSMREP + GPSRSMERR
Per SSP Measurements
These measurements are available on a per SSP PC basis where SSP PC is the CGPA PC, if it exists, or it is the MTP OPC.
Table 3-155 Daily Maintenance (MTCD) and Hourly Maintenance (MTCH) SSP Registers
| Event Name | Description | Unit |
|---|---|---|
| APLRACK |
Number of call related LOCREQ messages acknowledged. |
peg count |
| APLRRLY |
Number of call related LOCREQ messages relayed. |
peg count |
| APNOCL |
Number of non-call non-LOCREQ related messages relayed. |
peg count |
| APNOCLGT |
Number of non-call non-LOCREQ related messages that fell through to GTT. |
peg count |
| APSMRQERR |
Number of SMSREQ messages resulting in error. |
peg count |
| APSMRQREP |
Number of SMSREQ messages resulting in SMSREQ_ACK or SMSREQ_NACK |
peg count |
| APSMSRCV |
Number of SMSREQ messages received |
peg count |
| GPNOCL |
Number of non-call related messages relayed by G-Port. |
peg count |
| GPNOCLGT |
Number of non-call related messages that fell through to GTT. |
peg count |
| GPSRACK |
Number of call related (SRI-Send Routing Information ACK) responses. This does not include peg counts to register GPSRACKPP. |
peg count |
| GPSRACKPP |
Number of call related (SRI-Send Routing Information ACK) responses specifically for feature 61544: G-Port SRI query for Prepaid. This does not include peg counts to register GPSRACK. |
peg count |
| GPSRNACK | Number of call related SRI Negative ACK responses in case of successful G-Port service. | peg count |
| GPSRRLY |
Number of call related (SRI-Send Routing Information) messages relayed. |
peg count |
| GPSRSMERR |
Number of SRI_SM messages resulting in error. |
peg count |
| GPSRSMRCV |
Number of SRI_SM messages received. |
peg count |
| GPSRSMREP |
Number of SRI_SM messages resulting in SRI_SM_ACK or SRI_SM_NACK |
peg count |
| INPMRCRD |
Number of messages sent to MR service that fall through to GTT due to circular route detection. |
peg count |
| INPMRGTT |
Number of messages sent to MR service that fall through to GTT. This includes the number of messages sent to MR service that fall through to GTT due to circular route detection. |
peg count |
| INPMRTR |
Number of messages sent to MR service that receive MR translation. |
peg count |
| INPQSCONN |
Number of non-erroredQS messages with QS Connect responses, per originating SSP. |
peg count |
| INPQSCONT |
Number of non-errored QS messages with QS Continue responses, per originating SSP. |
peg count |
| INPQSCRD |
Number of messages sent to INP QS that meet the condition for circular route detection. |
peg count |
| INPQSREL |
Number of messages sent to INP QS that result in successful generation of INAP RELEASECALL response due to circular route detection by INPQS. |
peg count |
| MNPCRD | Number of times Circular Route is Detected. | peg count |
| PC Type | TYPE of the point code. Valid values are ANSI, ITUI, ITUN, and ITUN24. | text |
| SMSMOGERR |
Number of MO_SMS messages received that result in an error |
peg count |
| SMSMOGRCV |
Number of MO_SMS messages received that result in a modification of the outgoing MO_SMS |
peg count |
| SMSMOIERR |
Number of SMDPP messages received that result in an error |
peg count |
| SMSMOIRCV |
Number of SMDPP messages received that result in a modification of the outgoing SMDPP |
peg count |
| STATUS |
Indication of Data Validity:
|
status |
| TIFRANGEBL |
Total number of MSUs processed by TIF and blacklisted by the FPFXRLS or NOCGPNRLS Service Action |
peg count |
TIFSBSCRBL |
Total number of MSUs processed by TIF and found to be blacklisted by BLRLS or BLNFNDRLS Service Actions |
peg count |
TIFSELSCR |
Number of IAM messages processed by TIF which resulted in either an ISUP message generation or the MSU being relayed by SELSCR Service Action |
peg count |
| TINPERR |
Number of IAM messages received that required TIFTINP processing but resulted in execution of an error case. |
peg count |
| TINPMGEN |
Number of IAM messages received that required TIFTINP processing and resulted in the modification of the IAM message or the generation of a REL message. |
peg count |
| TINPMRCV |
Number of IAM messages received that require TIFTINP processing. |
peg count |
The following equation applies to NP registers:
GPSRREP = ∑GPSRACK + ∑GPSRRLY+ ∑GPSRNACK
UI Reports
Hourly System Wide Measurements
UI Example Output File Name:M60_NP.csv
UI Example Output File Format:
"e1061001 10-08-23 00:02:22 EST EAGLE5 42.0.0-63.33.0 " "TYPE OF REPORT: HOURLY MAINTENANCE MEASUREMENTS ON NP SYSTEM" "REPORT PERIOD: LAST" "REPORT INTERVAL: 10-08-22, 23:00:00 THROUGH 23:59:59 " "Measurement data represents an incomplete interval." "INPQRCV","INPQDSC","INPQTCPE","INPSREP","GPSRRCV","GPSRGTT","GPSRREP","GPSRERR","GPNOCL", "GPNOCLGT","IS41LRERR","IS41LRMRCV","IS41LRRTRN","GPSRRCVPP","GPSRGTTPP","GPSRREPPP", "GPSRERRPP","APSMSRCV","APSMSREL","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR", "SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR", "INPQSCRD","MNPCRD", 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
Hourly Measurements Per SSP
UI Example output File Name:M60_SSP.CSV
UI Example Output File Format:
"e1061001 10-08-23 00:02:22 EST EAGLE5 42.0.0-63.33.0 " "TYPE OF REPORT: HOURLY MAINTENANCE MEASUREMENTS ON NP SSP" "REPORT PERIOD: LAST" "REPORT INTERVAL: 10-08-22, 23:00:00 THROUGH 23:59:59 " "Measurement data represents an incomplete interval." "NUMBER OF ENTIDS: 3" "SSP","INPQSCONN","INPQSCONT","INPMRTR","INPMRGTT","GPSRACK","GPSRRLY","GPNOCL","GPNOCLGT", "GPSRACKPP","APLRACK","APLRRLY","APNOCL","APNOCLGT","TINPMRCV","TINPMGEN","TINPERR", "SMSMOIRCV","SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV", "APSMRQREP","APSMRQERR","APSMSRCV","INPQSCRD","INPQSREL","INPMRCRD","MNPCRD","GPSRNACK", " 001-001-001",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, " 101-001-001",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, " 201-001-001",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
FTP Reports
Hourly System Wide Measurements
FTP Example Output File Name:mtch-np_20080125_2400.csv
FTP Example Output File Format:
"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS" "e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:50","EST ","HOURLY MAINTENANCE MEASUREMENTS ON NP SYSTEM","LAST","2010-08-19","23:00:00","24:00:00",1 "STATUS","INPQRCV","INPQDSC","INPQTCPE","INPSREP","GPSRRCV","GPSRGTT","GPSRREP","GPSRERR", "GPNOCL","GPNOCLGT","IS41LRERR","IS41LRMRCV","IS41LRRTRN","GPSRRCVPP","GPSRGTTPP", "GPSRREPPP","GPSRERRPP","APSMSRCV","APSMSREL","TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV", "SMSMOIERR","SMSMOGRCV","SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP", "APSMRQERR","INPQSCRD","MNPCRD" "K",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
Assuming each data line will be: 4 char status + 33 * (6 char data) + 2 = 204 chars
Typical file size is:
Table 3-156 Typical File Size: mtch-np.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
250 |
+ |
378 |
+ |
204 |
= |
832 bytes |
Hourly Measurements Per SSP
FTP Example Output File Name: mtch-ssp_20080125_2400.csv
FTP Example Output File Format:
"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE","IVALSTART","IVALEND","NUMENTIDS" "e1061001","EAGLE5 42.0.0-63.33.0","2010-08-20","00:00:51","EST ","HOURLY MAINTENANCE MEASUREMENTS ON NP SSP","LAST","2010-08-19","23:00:00","24:00:00",3 "STATUS","SSP","PC_TYPE","INPQSCONN","INPQSCONT","INPMRTR","INPMRGTT","GPSRACK","GPSRRLY", "GPNOCL","GPNOCLGT","GPSRACKPP","APLRACK","APLRRLY","APNOCL","APNOCLGT", "TINPMRCV","TINPMGEN","TINPERR","SMSMOIRCV","SMSMOIERR","SMSMOGRCV", "SMSMOGERR","GPSRSMREP","GPSRSMERR","GPSRSMRCV","APSMRQREP","APSMRQERR", "APSMSRCV","INPQSCRD","INPQSREL","INPMRCRD","MNPCRD","GPSRNACK" "K"," 001-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, "K"," 101-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, "K"," 201-001-001","ANSI",0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
Assuming each data line will be: 4 char status + 14 char SSP + 10 char PC type + 31 * (6 char data) + 2 = 216 chars
Typical file size is:
Table 3-157 Typical File Size: mtch-ssp.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
250 |
+ |
356 |
+ |
(216 * #Point Codes ) |
= |
606 + (216 * #Point Codes) bytes |
For a report of 200 SSPs, typical file size is:
Table 3-158 Typical File Size: mtch-ssp.csv
| System header | + | Report header | + | Report data | = | File Size |
|---|---|---|---|---|---|---|
250 |
+ |
356 |
+ |
(216 * 200 ) |
= |
43806 bytes |
