SGSN Schema Statistics


SGSN Schema Statistics
 
 
The SGSN schema provides the following types of statistics:
 
 
Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. The limit depends upon the counter data type.
Gauge: A gauge statistic indicates a single value representative of a single instance. This type is often used to track particular events in time.
Important: The format string syntax is described by “Schema Format String Syntax” in the Bulk Statistics Overview chapter.
Important: Unless otherwise indicated, all statistics are counters. For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615. All counter statistics are cumulative and reset only by one of the following methods: roll-over (as described above), after a system restart, or after a clear command is performed. All statistics are considered standards-based unless otherwise noted.
The following variables are supported:
 
SGSN Service Schema Statistics
Description: Total number of subscribers, including home and visiting, attached for 3G service.
Availability: per SGSN service, per RA
Type: Gauge
Description: Total number of subscribers, including home and visiting, attached for 2G service.
Availability: per GPRS service; per RA
Type: Gauge
Type: Gauge.
Type: Gauge.
Description: This proprietary gauge indicates the total number of attached subscribers (active and standby) whose MCC (from IMSI) matches with SGSN service’s MCC, but MNC is different from the SGSN service’s MNC for 3G service.
Availability: per SGSN service, per RA
Type: Gauge
Description: This proprietary gauge indicates the total number of attached subscribers (active and standby) whose MCC (from IMSI) matches with GPRS service’s MCC, but MNC is different from the GPRS service’s MNC for 2G service.
Availability: per GPRS service; per RA
Type: Gauge
Description: This proprietary gauge indicates the total number of attached subscribers (active and standby) whose MCC/MNC (from IMSI) does not match with the PLMN of the 3G SGSN service.
Availability: per SGSN service, per RA
Type: Gauge
Description: This proprietary gauge indicates the total number of attached subscribers (active and standby) whose MCC/MNC (from IMSI) does not match with the PLMN of the 2G SGSN service.
Availability: per GPRS service; per RA
Type: Gauge
Description: This proprietary gauge indicates the total number of 3G Network Sharing Supporting User Equipment currently in the system. This statistics is specific to releases 8.1 and higher.
Triggers: Increments when a network sharing supporting UE connects with the 3G SGSN.
Availability: per SGSN service, per RA
Type: Gauge
Description: This proprietary gauge indicates the total number of 3G Network Sharing Non-supporting User Equipment currently in the system. This statistics is specific to releases 8.1 and higher.
Triggers: Increments when a network sharing non-supporting UE connects with the 3G SGSN.
Availability: per SGSN service, per RA
Type: Gauge
Description: Total number of subscribers in packet mobility management-connected (PMM-CONNECTED) state.
Availability: per SGSN service, per RA
Type: Gauge
Type: Gauge
Type: Gauge
Type: Gauge
Description: Total number of 3G visiting and home subscribers in attached state with at least one active PDP context.
Triggers: This gauge changes after successful activation of the first PDP context for a subscriber.
Availability: per SGSN service, per RA
Type: Gauge
Description: Total number of 2G visiting and home subscribers in attached state with at least one active PDP context per GPRS service.
Triggers: This gauge changes after successful activation of the first PDP context for a subscriber.
Availability: per GPRS service
Type: Gauge
Type: Gauge
Type: Counter
Type: Counter
Type: Counter
Type: Counter
Type: Counter
Type: Counter.
Type: Counter
Type: Counter.
Type: Counter.
Type: Counter.
Description: Total number of Attach Request messages accepted for 3G service.
Triggers: On sending a successful attach-accept with attach-result “GPRS-only Attached”.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Accept messages sent with attach result “Combined GPRS/IMSI Attached” in 3G service.
Triggers: On sending a successful attach-accept with attach-result “Combined attached”.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Request messages accepted for 2G service.
Triggers: On sending a successful attach-accept with attach-result “GPRS-only Attached”.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Accepts sends with attach-result “Combined GPRS/IMSI Attached” in 2G service.
Triggers: On sending a successful attach-accept with attach-result “Combined attached”.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with individual causes against attach request of type “GPRS Attach” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all Attach-Reject counters with individual causes sent against Attach Requests of type "Combined GPRS/IMSI Attach" in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with individual causes against Attach Requests of type “GPRS Attach” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all Attach-Reject counters with individual causes sent against Attach requests of type "Combined GPRS/IMSI Attach" in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "imsi unknown at hlr" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "imsi unknown at hlr" against Attach requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS Services not allowed" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS Services not allowed" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per GPRS service.
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS and non-GPRS Services not allowed" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS and non-GPRS Services not allowed" against Attach requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "msid not derived by nwt" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "msid not derived by nwt" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach requests rejected with cause "implicitly detached" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach requests rejected with cause "implicitly detached" against Attach requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "plmn not allowed" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "plmn not allowed" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause “Roaming not allowed in this Location Area” against attach requests of type “GPRS Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause “Roaming not allowed in this Location Area” against attach requests of type “GPRS Attach” in 2G service.
Triggers: When operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause “GPRS services not allowed in this PLMN” against attach requests of type “GPRS Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause “GPRS services not allowed in this PLMN” against attach requests of type “GPRS Attach” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "No suitable cell in location area" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "No suitable cell in location area" against Attach requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "Network Failure" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "Network Failure" against Attach requests of type "GPRS Attach" in 3G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "sync failure" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "sync failure" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause “Congestion” against attach request of type “GPRS Attach” in a 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of GPRS attach rejected for 2G service due to network congestion.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "gsm auth unacceptable" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "gsm auth unacceptable" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "no pdp ctx activated" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "no pdp ctx activated" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "retry from new cell" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "retry from new cell" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "sem wrong msg" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "sem wrong msg" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "invalid mand info" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "invalid mand info" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg type not exist" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg type not exist" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg type not comp prot state" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg type not comp prot state" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "ie non existent" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "ie non existent" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "conditional ie err" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "conditional ie err" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg not comp prot state" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "msg not comp prot state" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "protocol error" against Attach Requests of type "GPRS Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "protocol error" against Attach Requests of type "GPRS Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach Rejects sent with cause "unknown cause" against Attach Requests of type "GPRS Attach" in 3G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Attach Rejects sent with cause "unknown cause" against Attach Requests of type "GPRS Attach" in 2G service.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS services not allowed" against attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS services not allowed" against attach requests of type "Combined GPRS/IMSI Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS and non-GPRS services not allowed" against attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS and non-GPRS services not allowed" against attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause “Roaming not allowed in LA” against attached request of type “Combined GPRS/IMSI Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause “Roaming not allowed in LA” against attached request of type “Combined GPRS/IMSI Attach” in 2G service.
Triggers: When operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS Service Not Allowed in PLMN" against attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "GPRS Service Not Allowed in PLMN" against attach requests of type "Combined GPRS/IMSI Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause “No suitable cells in LA” against Attach requests of type “Combined GPRS/IMSI Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause “No suitable cells in LA” against Attach requests of type “Combined GPRS/IMSI Attach” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "Network Failure" against Attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "Network Failure" against Attach requests of type "Combined GPRS/IMSI Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach rejects sent with cause "Congestion" against Attach requests of type "Combined GPRS/IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach rejects sent with cause "Congestion" against Attach requests of type "Combined GPRS/IMSI Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of attach requests of type “GPRS Attach” that were dropped from processing in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach requests of type “Combined GPRS/IMSI Attach” that were dropped from processing in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of 3G-total-attach-fail + 3G-total-attach-fail-comb.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach requests of type “GPRS Attach” that were dropped from processing in 2G service.
Triggers: Another Attach, differing from this attach, was received and pre-empted existing Attach procedure.
Availability: per GPRS service, per RA
Type: Counter
Description: Total number of attach requests of type “Combined GPRS/IMSI Attach” that were dropped from processing in 2G service.
Triggers: Another Attach, differing from this attach, was received and pre-empted existing Attach procedure.
Availability: per GPRS service, per RA
Type: Counter
Description: Sum of the stats for 2G-total-attach-fail + 2G-total-attach-fail-comb. This is new in release 9.0.
Availability: per GPRS service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of attach procedures failed for 3G service due to a new attach received.
Triggers: Increments when we abort an ongoing attach due to another new attach in 3G.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Attach procedures failed for 2G service due to a new attach received.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-Accepts sent against Intra-SGSN-RAU requests with update type “ RA Updating” in 3G service.
Triggers: On sending a successful RAU-Accept with update-result “RA Updating”.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU request with update type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Triggers: On sending a successful rau-accept with update-result "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach".
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-Accepts sent against Inter-SGSN-RAU requests with update type “ RA Updating” in 3G service.
Triggers: On sending a successful RAU-Accept with update-result “RA Updating”.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inter-SGSN-RAU requests with update type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-Accepts sent against Intra-SGSN-RAU requests with update type “ RA Updated” in 2G service.
Triggers: On sending a successful RAU-Accept with update-result “RA Updated”.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inra-SGSN-RAU requests with update type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Triggers: On sending a successful RAU-accept with update-result "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach".
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-Accepts sent against Inter-SGSN-RAU requests with update type “ RA Updated” in 2G service.
Triggers: On sending a successful RAU-Accept with update-result “RA Updated”.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU request with update type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-Accepts sent against Intra-SGSN-RAU requests of type “Periodic Updating” with update type “RA updating” in 3G service.
Triggers: On sending a successful RAU-Accept with update-result “Periodic Updating”.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-Accepts sent against Intra-SGSN-RAU requests of type “Periodic Updating” with update type “RA updated” in 2G service.
Triggers: On sending a successful RAU-Accept with update-result “Periodic Updated”.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “RA Updating” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “ Periodic RA Updating” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inter-SGSN-RAU requests of type “RA Updating” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “RAU Updating” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “ Periodic RA Updating” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inter-SGSN-RAU requests of type “RAU Updating” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Intra-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Sum of all RAU-reject counters with individual causes against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per GPRS service
Type: Counter
Description: Total number of RAU rejects sent with cause “GPRS service not allowed in this PLMN” against Intra-SGSN-RAU requests of type “RA Updating” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU rejects sent with cause “GPRS service not allowed in this PLMN” against Intra-SGSN-RAU requests of type “RA Updating” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “periodic updating”, for 3G service that were rejected with reject messages sent with a cause of "No Suitable Cells In Location Area".
Triggers: Increments:
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “periodic updating”, for 2G service that were rejected where “rau-reject” messages were sent with a cause of "No Suitable Cells In Location Area".
Triggers: Increments:
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “periodic updating”, for 3G service that were rejected where “rau-reject” messages were sent with a cause of "MSC temporarily not reachable".
Triggers: Increments: when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “periodic updating”, for 2G service that were rejected where “rau-reject” messages were sent with a cause of "MSC temporarily not reachable".
Triggers: Increments: when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 3G service that were rejected where the “rau-reject” message was sent with a cause "Network Failure"
Triggers: Increments :
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 2G service that were rejected where the “rau-reject” message was sent with a cause "Network Failure"
Triggers: Increments :
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 3G service that were rejected where the “rau-reject” message was sent with a cause "MAC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 2G service that were rejected where the “rau-reject” message was sent with a cause "MAC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 3G service that were rejected where the “rau-reject” message was sent with a cause "SYNC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests, of type “period updating”, for 2G service that were rejected where the “rau-reject” message was sent with a cause "SYNC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of RAU rejects sent with cause “GPRS service not allowed in this PLMN” against Intra-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU reject messages sent with cause “GPRS service not allowed in this PLMN” against Intra-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests for 3G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "No Suitable Cells In Location Area".
Triggers: Increments:
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests for 2G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "No Suitable Cells In Location Area".
Triggers: Increments:
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests for 3G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MSC temporarily not reachable".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests for 2G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MSC temporarily not reachable".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests for 3G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MSC temporarily not reachable".
Triggers: Increments:
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests for 2G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MSC temporarily not reachable".
Triggers: Increments
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests for 3G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MAC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests for 2G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "MAC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of intra-SGSN RAU requests for 3G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "SYNC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of intra-SGSN RAU requests for 2G service, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", sent with cause "SYNC Failure".
Triggers: Increments when the operator policy is configured with this value as the reject cause for RAUs.
Availability: per GPRS service
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “MSID not derived by network” against Inter-SGSN-RAU requests of type “RA Updating” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “MSID not derived by network” against Inter-SGSN-RAU requests of type “RA Updating” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of RAU rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-SGSN-RAU requests of type “RA Updating” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-SGSN-RAU requests of type “RA Updating” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “MSID not derived by network” against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of inter-SGSN routing area update request rejects sent with cause “MSID not derived by network” against Inter-SGSN-RAU requests of type “Combined RA/LA update” or “Combined RA/LA update with IMSI Attach” in 2G service.
Availability: per GPRS service
Type: Counter
Description: Total number of RAU rejects sent with cause "GPRS service not allowed in PLMN" against Inter-SGSN-RAU requests of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach" in 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU rejects sent with cause "GPRS service not allowed in PLMN" against Inter-SGSN-RAU requests of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach" in 2G service.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of Intra-SGSN-RAU requests of type “RA Updating” that were dropped from processing in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Intra-SGSN-RAU requests of type “RA Updating” that were dropped from processing in 2G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of Intra-SGSN-RAU requests of type “Periodic Updating” that were dropped from processing in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Intra-SGSN RAU requests, of type “Periodic Updating”, that were dropped from processing in 2G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN RAU requests, of type “Combined RA/LA Update or “Combined RA/LA Update with IMSI Attach”, that were failed in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN-RAU requests of type “Combined RA/LA Update or “Combined RA/LA Update with IMSI Attach” that were failed in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN-RAU requests of type “RA Updating” that were failed in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN-RAU requests of type “RA Updating” that were failed in 2G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN-RAU requests of type “Combined RA/LA Update or “Combined RA/LA Ipdate with IMSI Attach” that were failed in 3G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per SGSN service, per RA
Type: Counter
Description: This proprietary counter indicates the total number of Inter-SGSN-RAU requests of type “Combined RA/LA Update or “Combined RA/LA Ipdate with IMSI Attach” that were failed in 2G service. “Dropped” indicates that the requests were silently discarded and no reject was sent for such requests.
Availability: per GPRS service
Type: Counter
Description:Total number of combined RAUs dropped from processing as the Iu (in which the RAU came) was released. This counter is new in release 9.0.
Triggers: Increments when the Iu releases during an ongoing RAU.
Availability:per SGSN service, per RA
Type: Counter
Description:Total number of combined RAUs dropped from processing as another RAU/Attach/Detach was received. This counter is new in release 9.0.
Triggers: Increments when another Attach/RAU/Detach is received.
Availability: per SGSN service, per RA
Type: Counter
Description:Total number of combined RAUs dropped from processing as another RAU/Attach/Detach was received. This counter is new in release 9.0.
Triggers: Increments when another Attach/RAU/Detach is received.
Availability: per GPRS service
Type: Counter
Description:Total number of combined inter-SGSN RAUs dropped from processing as the Iu (in which the RAU came) was released. This counter is new in release 9.0.
Triggers: Increments when the Iu releases during an ongoing RAU.
Availability: per SGSN service, per RA
Type: Counter
Description:Total number of combined inter-SGSN RAUs dropped from processing as another RAU/Attach/Detach was received. This counter is new in release 9.0.
Triggers: Increments when another Attach/RAU/Detach is received.
Availability: per SGSN service, per RA
Type: Counter
Description:Total number of combined inter-SGSN RAUs dropped from processing as another RAU/Attach/Detach was received. This counter is new in release 9.0.
Triggers: Increments when another Attach/RAU/Detach is received.
Availability: per GPRS service
Type: Counter
Description: Total number of Attach and RAU Requests received at 3G from 2G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when a Mobile Station (MS) performs an intra-SGSN inter-RAT Attach/RAU from 2G to 3G.
Availability: Across all SGSN services
Type: Counter
Description: Total number of Attach/RAU Rejects sent against Attach/RAU Requests received at 3G from 2G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when an Attach/RAU procedure is rejected on an intra-SGSN inter-RAT Attach/RAU Request from 2G to 3G.
Availability: Across all SGSN services
Type: Counter
Description: Total number of failed Attach/RAU Procedures initiated at 3G from 2G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when an Attach/RAU procedure is dropped without an Attach/RAU Reject on an intra-SGSN inter-RAT from 2G to 3G.
Availability: Across all SGSN services
Type: Counter
Description: Total number of RAU and Attach Requests received at 2G from 3G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when a Mobile Station (MS) performs an intra-SGSN inter-RAT Attach/RAU from 3G to 2G.
Availability: Across all GPRS services
Type: Counter
Description: Total number of Attach/RAU Rejects sent against Attach/RAU Requests received at 2G from 3G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when an Attach/RAU procedure is rejected on an intra-SGSN inter-RAT Attach/RAU Request from 3G to 2G.
Availability: Across all GPRS services
Type: Counter
Description: Total number of failed Attach/RAU Procedures initiated at 2G from 3G mobile stations (MS) attached in the same SGSN.
Triggers: Increments when an Attach/RAU procedure is dropped without an Attach/RAU Reject on an intra-SGSN inter-RAT from 3G to 2G.
Availability: Across all GPRS services
Type: Counter
Description: Total number of RAU-requests of type "RA Updating" received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon reception of a RAU-request at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-accepts with update-result - "RA updated" issued against RAU-requests from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such a RAU-accept message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-rejects issued against RAU-requests of the type "RA Updating" which were received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such a RAU-reject message by the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-requests, of type "Combined RA/LA update" or "Combined RA/LA update, with IMSI Attach" received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon reception of such a RAU-request message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-accepts, with update-result - "Combined RA/LA updated", issued against RAU-requests from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such RAU-accept message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-rejects ,issued against RAU-requests of the type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such a RAU-reject message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-request messages, of the type "GPRS Attach", received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon reception of such an attach-request message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-accepts of type "GPRS only attached" issued against attach-requests from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such an attach-accept message at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-reject messages, issued against attach-requests of type "GPRS Attach", received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such an attach-reject message from the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-request messages, of type "Combined GPRS/IMSI Attach", received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon reception of such attach-request messages at the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-accept messages, of the type "Combined GPRS/IMSI attached", issued against attach-requests from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such an attach-accept message by the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of attach-reject messages, issued against attach-requests of type "Combined GPRS/IMSI Attach", received from subscribers who attached previously to the same SGSN under 2G.
Triggers: Increments upon issue of such an attach-reject message by the 3G SGSN.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of RAU-request messages, of type "RA Updating", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon reception of such a RAU-request message at the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of RAU-accept messages, with update-result - "RA updated", issued against RAU-requests from subscribers who previously attached to the same SGSN under 3G.
Triggers: Increments upon issue of such a RAU-accept message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of RAU-reject messages, issued against RAU-requests of type "Ra Updating", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon issue of such a RAU-reject message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of RAU-request messages, of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon reception of such a RAU-request message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of RAU-accept messages, with update-result - "Combined RA/LA updated", issued against RAU-requests from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon issue of such a RAU-accept message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of RAU-reject messages, issued against RAU-requests of type "Combined RA/LA update" or "Combined RA/LA update with IMSI Attach", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon issue of such a RAU-reject message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of “attach request” messages, of type "GPRS Attach", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon reception of such an ‘”attach request” message at the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of “attach-accept” messages, of type "GPRS only attached", issued against “attach-requests” from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon issue of such an “attach-accept” message at the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of “attach-reject” messages, issued against “attach-requests” of type "GPRS Attach", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon issue of such an “attach-reject” message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of “attach-request” messages, of type "Combined GPRS/IMSI Attach", received from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon reception of such an “attach-request” message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of “attach-accept” messages, of type "Combined GPRS/IMSI attached", issued against “attach-requests” from subscribers who attached previously to the same SGSN under 3G.
Triggers: Increments upon reception of such an “attach-request” message by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of Attach rejects issued against attach-requests of type "Combined GPRS/IMSI Attach" received from subscribers who are previously attached in the same sgsn under 3g.
Triggers: Increments upon issue of such an “attach-reject” by the 2G SGSN.
Availability: across all GPRS services
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Requests received in a 3G service from a 2G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Requests received in a 2G service from a 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Requests received in a 3G service from a 2G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Requests received in a 2G service from a 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Requests received in a 3G service from a 2G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Requests received in a 2G service from a 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Requests received in a 3G service from a 2G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Requests received in a 2G service from a 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Requests from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Requests from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Requests from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Requests from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Requests from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Requests from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Requests received in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Requests from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Requests from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 2G service to a 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 3G service to a 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 2G service to a 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 3G service to a 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 2G service to a 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 3G service to a 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 3G service to a 2G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter RAT RAU Accepts sent against RAU Requests from subscribers moving from a 2G service to a 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted GPRS only Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Accepts sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of retransmitted Combined Inter Service RAU Accepts sent against RAU Requests from subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects sent against RAU Requests for subscribers moving from 2G service to a 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects sent against RAU Requests for subscribers moving from 3G service to a 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects sent against RAU Requests for subscribers moving from 2G service to a 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects sent against RAU Requests for subscribers moving from 3G service to a 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent against RAU Requests for subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent against RAU Requests for subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent in both 2G and 3G services.
Availability: per RA, per GPRS/SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent against RAU Requests for subscribers moving from one 3G service to another 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent against RAU Requests for subscribers moving from one 2G service to another 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “IMSI unknown at HLR”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “IMSI unknown at HLR”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Illegal M”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Illegal MS”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Illegal ME”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Illegal ME”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Implicitly detached”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Implicitly detached”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU rejects in 3G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU rejects in 2G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU rejects in 3G service with cause “Roaming area not allowed in the given location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU rejects in 2G service with cause “Roaming area not allowed in the given location area”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “No cells in location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “No cells in location area”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “MSC not reachable”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “MSC not reachable”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Network Failure”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Network Failure”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS Only Inter Service RAU Rejects in 3G service with cause “Network Congestion”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS Only Inter Service RAU Rejects in 2G service with cause “Network Congestion”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Semantically wrong message”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Semantically wrong message”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Invalid Mandatory Info”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Invalid Mandatory Info”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Message type does not exist”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Message type does not exist”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “Information element not existent”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “Information element not existent”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “error in conditional informational element”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “error in conditional informational element”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “message not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “message not compatible with protocol state”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “protocol error”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “protocol error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 3G service with cause “unknown error”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects in 2G service with cause “unknown error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “IMSI unknown at HLR”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “IMSI unknown at HLR”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 3G service with cause “Illegal MS”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 2G service with cause “Illegal MS”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 3G service with cause “Illegal ME”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 2G service with cause “Illegal ME”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Implicitly detached”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Implicitly detached”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Roaming area not allowed in the given location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Roaming area not allowed in the given location area”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Intter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “No cells in location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “No cells in location area”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 3G service with cause “MSC not reachable”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 2G service with cause “MSC not reachable”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Network Failure”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Network Failure”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Network Congestion”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Network Congestion”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Semantically wrong message”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Semantically wrong message”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Invalid Mandatory Info”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Invalid Mandatory Info”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Message type does not exist”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Message type does not exist”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “Information element not existent”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “Information element not existent”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “error in conditional informational element”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “error in conditional informational element”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “message not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “message not compatible with protocol state”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 3G service with cause “protocol error”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU rejects in 2G service with cause “protocol error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 3G service with cause “unknown error”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects in 2G service with cause “unknown error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “IMSI unknown at HLR”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “IMSI unknown at HLR”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Illegal MS”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Illegal MS”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Illegal ME”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Illegal ME”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only inter-service routing area update request rejects sent with cause “MSID not derived by network” against Inter-Service-RAU requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only inter-service routing area update request rejects sent with cause “MSID not derived by network” against Inter-Service-RAU requests in 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Implicitly detached”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Implicitly detached”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Roaming area not allowed in the given location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Roaming area not allowed in the given location area”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Inter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Inter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “No cells in location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “No cells in location area”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “MSC not reachable”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “MSC not reachable”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Network Failure”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Network Failure”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Network Congestion”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Network Congestion”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Semantically wrong message”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Semantically wrong message”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Invalid Mandatory Info”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Invalid Mandatory Info”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Message type does not exist”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Message type does not exist”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “Information element not existent”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “Information element not existent”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “error in conditional informational element”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “error in conditional informational element”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “message not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “message not compatible with protocol state”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “protocol error”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “protocol error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 3G service with cause “unknown error”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of GPRS only Inter RAT RAU Rejects in 2G service with cause “unknown error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “IMSI unknown at HLR”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “IMSI unknown at HLR”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Illegal MS”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Illegal MS”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU rejects in 3G service with cause “Illegal ME”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU rejects in 3G service with cause “Illegal ME”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS services not allowed in this PLMN” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Rejects sent with cause “GPRS and non-GPRS service not allowed for subscriber” against Inter-service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter Service RAU Request Rejects sent with cause “MSID not derived by network” against Inter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Implicitly detached”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Implicitly detached”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “PLMN not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Location area not allowed”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Roaming area not allowed in the given location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Roaming area not allowed in the given location area”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Inter-Service-RAU Requests in 3G service.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined RAU Rejects sent with cause “GPRS service not allowed in this PLMN” against Inter-Service-RAU Requests in 2G service.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “No cells in location area”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “No cells in location area”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU rejects in 3G service with cause “MSC not reachable”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU rejects in 2G service with cause “MSC not reachable”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Network Failure”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Network Failure”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Message Authenticate Code (MAC) Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Context Synchronization Failure”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Network Congestion”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Network Congestion”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “GSM Authentication unacceptable”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “PDP context not activated”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Subscriber retried from a new cell”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Semantically wrong message”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Semantically wrong message”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Invalid Mandatory Info”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Invalid Mandatory Info”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Message type does not exist”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Message type does not exist”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Message type not compatible with protocol state”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “Information element not existent”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “Information element not existent”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “error in conditional informational element”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “error in conditional informational element”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “message not compatible with protocol state”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “message not compatible with protocol state”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “protocol error”.
Triggers: Increments when operator policy is configured with this value as the reject cause for attaches/RAUs.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “protocol error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 3G service with cause “unknown error”.
Availability: per RA, per SGSN service
Type: Counter
Description: Total number of Combined Inter RAT RAU Rejects in 2G service with cause “unknown error”.
Availability: per RA, per GPRS service
Type: Counter
Description: Total number of MS initiated Detach Requests of type 'GPRS Detach' received for 3G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of MS initiated Detach Requests of type 'GPRS Detach' received for 2G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per GPRS service
Type: Counter
Description: Total number of MS initiated Detach Requests of type 'Imsi Detach' received for 3G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of MS initiated Detach Requests of type 'Imsi Detach' received for 2G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per GPRS service
Type: Counter
Description: Total number of MS initiated GPRS and IMSI (PS and CS) Detach Requests of type 'Combined Gprs/Imsi Detach' received for 3G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of MS initiated GPRS and IMSI (PS and CS) Detach Requests of type 'Combined Gprs/Imsi Detach' received for 2G service.
Triggers: Increments when the MS initiates a Detach Request.
Availability: per GPRS service
Type: Counter
Description: Total number of network initiated Detach Request procedures sent for 3G service.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of network initiated Detach Request procedures received for 2G service.
Availability: per GPRS service, per RA
Type: Counter
Description: Total number of 3G service MS-initiated Detach Accept messages received by the SGSN and sent by the mobile station (MS) in response to network-initiated Detach Request messages.
Triggers: Increments when a Detach Accept is received from an MS.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of 2G service MS-initiated Detach Accept messages received by the SGSN and sent by the mobile station (MS) in response to network-initiated Detach Request messages.
Triggers: Increments when a Detach Accept is received from an MS.
Availability: per GPRS service
Type: Counter
Description: Total number of Network initiated Detach Accept messages in response to requests of type 'Gprs Detach' in 3G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Network initiated IMSI (CS) Detach Accept messages in response to requests of type 'Imsi Detach' in 3G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Network initiated combined (GPRS and IMSI) Detach Accept messages in response to requests of type 'Combined Gprs/Imsi Detach' in 3G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Network initiated Detach Accept messages in response to requests of type 'Gprs Detach' in 2G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per GPRS service
Type: Counter
Description: Total number of Network initiated IMSI (CS) Detach Accept messages in response to requests of type 'Imsi Detach' in 2G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per GPRS service
Type: Counter
Description: Total number of Network initiated combined (GPRS and IMSI) Detach Accept messages in response to requests of type 'Combined Gprs/Imsi Detach' in 2G service.
Triggers: Increments when the network accepts a detach initiated by the MS.
Availability: per GPRS service
Type: Counter
Description: Total number of Service Request messages received for type "Signalling" in 3G service.
Triggers: Increments when the MS initiates a Serving Request message.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages received for type "Data" in 3G service.
Triggers: Increments when the MS initiates a Serving Request message.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Accept messages sent by the network in 3G service.
Triggers: Increments when the SGSN receives and accepts a Serving Request message in connected state.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Reject messages sent by the network in 3G service.
Triggers: A derived counter. See individual counters for trigger points.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service due to network failure.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service due to unknown IMSI in HLR.
Triggers: Increments when we initiate SAI towards HLR but we get an 'imsi not known' from HLR.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service as MSID can not derived by network from message.
Triggers: Increments when we get an unknown PTMSI service request from an MS.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service due to implicitly detach.
Triggers: Increments when we get a service request from an MS that is already detached.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service due to illegal mobile subscriber.
Triggers: Increments when authentication fails on a service request.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service as message is not compatible with protocol state.
Triggers: Increments when we get a service request for ongoing authentication or attach.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service as no PDP context is activated.
Triggers: Increments when we get a service request of type ‘data’ and we have no PDP contexts activated.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 3G service as request message is semantically wrong.
Triggers: Increments when a decode failure happens on a service request.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of 3G Service Request messages rejected for unknown causes. Any number other than zero (0) indicates a software problem. This counter is new in release 9.0.
Triggers: Increments when a 3G Service Request is rejected.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of Service Request messages rejected for 2G service as request message is semantically wrong.
Triggers: Increments when a decode failure happens on a service request.
Availability: per GPRS service, per RA
Type: Counter
Description: Total number of 3G service Paging Request messages originated by SGSN and sent to the Radio Network Controller (RNC) to contact mobile stations (MS).
Availability: per SGSN service
Type: Counter
Description: Total number of 2G service Paging Request messages originated by SGSN and sent to the Radio Network Controller (RNC) to contact mobile stations (MS).
Availability: per GPRS service
Type: Counter
Description: Total number of successful paging responses in 3G service.
Triggers: Any successful Iu passing security started after Paging is started.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of successful paging responses in 2G service.
Triggers: Any LLC uplink frame received after a <X-Refs (online)>page <$paranum[chapter number]>-<$pagenum>-Request is sent to MS.
Availability: per GPRS service
Type: Counter
Description: Total authentication and ciphering request messages for 3G service.
Triggers: Whenever authentication procedure is initiated.
Availability: per SGSN service, per RA
Type: Counter
Description: Total authentication and ciphering request messages for 2G service.
Triggers: Whenever authentication procedure is initiated.
Availability: per GPRS service
Type: Counter
Description: Total authentication and ciphering request response messages for 3G service.
Triggers: Whenever the MS sends a authentication and cipher response message.
Availability: per SGSN service, per RA
Type: Counter
Description: Total authentication and ciphering request response messages for 2G service.
Triggers: Whenever the MS sends a authentication and cipher response message.
Availability: per GPRS service
Type: Counter
Description: Total authentication and ciphering failed due to message authentication code (MAC) failure in 3G service.
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per SGSN service, per RA
Type: Counter
Description: Total authentication and ciphering failed due to message authentication code (MAC) failure for 2G service.
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per GPRS service
Type: Counter
Description: Total number of authentication and cipher procedure failures messages received with cause “SYNC failure” in 3G service.
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of authentication and cipher procedure failures messages received with cause “SYNC failure” in 2G service.
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per GPRS service
Type: Counter
Description: Total number of authentication and cipher procedure fail messages received with cause “authentication unacceptable” in 3G service.
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per SGSN service, per RA
Type: Counter
Triggers: When a authorization and cipher failure message is received with this cause.
Availability: per GPRS service
Type: Counter
Description: Total number of PTMSI-Reallocation Complete messages received at 3G.
Triggers: Increments when we receive a PTMSI Realloc Complete from MS in 3G.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PTMSI-Reallocation Complete messages received at 2G.
Triggers: Increments when we receive a PTMSI Realloc Complete from MS in 2G.
Availability: per GPRS service
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMSI” in 3G service.
Triggers: When the SGSN initiates a Identity request to know the IMSI of the subscriber. This is done when:
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMSI” in 2G service.
Triggers: When the SGSN initiates an identity request to know the IMSI of the subscriber due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per GPRS service
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMEI” for 3G service.
Triggers: When the SGSN initiates an identity request to know the IMEI of the UE due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per SGSN service
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMEI” for 2G service.
Triggers: When the SGSN initiates an identity request to know the IMEI of the subscriber due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per GPRS service
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMEI-SV” for 3G service.
Triggers: When the SGSN initiates an identity request to know the IMEI-SV of the UE due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMEI-SV” for 2G service.
Triggers: When the SGSN initiates an identity request to know the IMEI-SV of the subscriber due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per GPRS service
Type: Counter
Description: Total number of identity request messages sent with identity type as “T-IMSI” for 3G service.
Triggers: When the SGSN initiates an identity request to know the temporary IMSI of the subscriber due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity request messages sent with identity type as “IMSI” for 2G service.
Triggers: When the SGSN initiates an identity request to know the IMSI of the subscriber due to unknown local-PTMSI attach is received or GTP identity with Peer SGSN failed on a Peer SGSN PTMSI attach.
Availability: per GPRS service
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMSI” for 3G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMSI.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMSI” for 2G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMSI.
Availability: per GPRS service
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMEI” for 3G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMEI.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMEI” for 2G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMEI.
Availability: per GPRS service
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMEI-SV” for 3G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMEI-SV.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of identity response messages received with MS identity of type “IMEI-SV” for 2G service.
Triggers: When the SGSN receives an Identity response initiated to an identity request initiated of identity type IMEI-SV.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of new connection (Inter-SGSN RAU and/or Attach) requests that were rejected due to an overload situation.
Availability: per SGSN Service
Type: Counter
Description: Total number of request messages accepted for 3G context activation including primary and secondary type.
Triggers: Increments when the SGSN sends Activate Accept or Activate Secondary Accept to the MS upon successful PDP Activation.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of request messages accepted for 2G context activation including primary and/or secondary type.
Triggers: Increments when the SGSN sends Activate Accept or Activate Secondary Accept to the MS upon successful PDP Activation.
Availability: per GPRS service
Type: Counter
Description: Total number of active PDP context (primary and secondary type) for 3G service in SGSN.
Availability: per SGSN service, per RAI
Type: Gauge
Description: Total number of active PDP context (primary and secondary type) for 2G service in SGSN.
Availability: per GPRS service
Type: Gauge
Description: Total number of requests rejected to activate PDP context (primary and secondary) for 3G service.
Triggers: Increments when the SGSN sends Activate Reject or Activate Secondary Reject to the MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests rejected to activate PDP context (primary and secondary) for 2G service.
Triggers: Increments when the SGSN sends Activate Reject or Activate Secondary Reject to the MS.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS Service, RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to network failure.
Triggers: Increments when the SGSN sends Activate Reject due to SGSN operator policy restrictions and the cause code was configured as Network failure. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to network failure.
Triggers: Increments when the SGSN sends Activate Reject due to SGSN operator policy restrictions and the cause code was configured as Network failure. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per GPRS service
Type: Counter
Description: Total number of requests to activate PDP context for 3G service rejected due to APN related errors such as:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to APN related errors such as:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to PDP Address related errors such as:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to PDP Address related errors such as:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to user authentication failure on GGSN.
Triggers: Increments when the SGSN receives Create PDP Context Response with authentication failure cause.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to user authentication failure on GGSN.
Triggers: Increments when the SGSN receives Create PDP Context Response with authentication failure cause.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service due to receiving Create PDP Context Response from GGSN with a cause of:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service due to receiving Create PDP Context Response from GGSN with a cause of:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service
Type: Counter
Description: Total number of requests to activate PDP context for 3G service rejected as requested service is not supported.
Triggers: Increments when the SGSN sends Activate Reject due to SGSN operator policy restrictions and the cause code was configured as Service Not Supported. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected as requested service is not supported.
Triggers: Increments when the SGSN sends Activate Reject due to SGSN operator policy restrictions and the cause code was configured as Service Not Supported. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected as subscriber is not subscribed to requested service due to:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected as subscriber is not subscribed to requested service due to:
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to semantically incorrect IE message in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to semantically incorrect IE message in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to invalid mandatory IE in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to invalid mandatory IE in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected upon receiving Create PDP Context Response from GGSN with a cause of "Mandatory IE missing".
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected upon receiving Create PDP Context Response from GGSN with a cause of "Mandatory IE missing".
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected due to conditional IE (Information Element) error in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected due to conditional IE (Information Element) error in Activate PDP Request.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected as message type is not compatible with protocol state.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected as message type is not compatible with protocol state.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 3G service rejected upon receiving Create PDP Context Response from GGSN with a cause of "unspecified protocol error”.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate PDP context for 2G service rejected upon receiving Create PDP Context Response from GGSN with a cause of "unspecified protocol error”.
Triggers: Increments when the SGSN sends Activate Reject for the above conditions.
Availability: per GPRS service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate secondary PDP context for 3G service rejected as requested service is not supported.
Triggers: Increments when the SGSN sends Activate Secondary Reject due to SGSN operator policy restrictions and the cause code was configured as Service Not Supported. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate secondary PDP context for 2G service rejected as requested service is not supported.
Triggers: Increments when the SGSN sends Activate Secondary Reject due to SGSN operator policy restrictions and the cause code was configured as Service Not Supported. Activations can be rejected due to SGSN operator policy in which the reject cause is configurable.
Availability: per GPRS service
Type: Counter
Description: Total number of requests sent to MS to activate secondary PDP context for 3G service rejected as subscriber is not subscribed to requested service due to:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of requests sent to MS to activate secondary PDP context for 2G service rejected as subscriber is not subscribed to requested service due to:
Triggers: Increments when the SGSN sends Activate Reject for all the above conditions.
Availability: per GPRS service
Type: Counter
Description: Total number of PDP context activation (primary and secondary) failed for 3G service due to:
Triggers: Increments when the SGSN drops PDP Activate Request for all the above conditions.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of PDP context activation (primary and secondary) failed for 2G service due to:
Triggers: Increments when the SGSN drops PDP Activate Request for all the above conditions.
Availability: per GPRS service
Type: Counter
Description: New counter in release 9.0: Total number of Primary PDP Activation Requests dropped due to:
Triggers: Increments when the SGSN drops the Primary PDP Activate Request for indicated condition.
Availability: per GPRS service, per RA
Type: Counter
Description: New counter in release 9.0: Total number of Secondary PDP Activation Requests dropped due to:
Triggers: Increments when the SGSN drops the Secondary PDP Activate Request for indicated condition.
Availability: per GPRS service, per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to IU release before the completion of activation procedure.
Triggers: Increments when the SGSN drops PDP Activate Request due to IU release before the completion of activation procedure.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to SM Guard Timer Expiry.
Triggers: Increments when the SGSN drops PDP Activate Request due to SM Guard Timer Expiry.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to an ongoing PDP Activation.
Triggers: Increments when the SGSN drops PDP Activate Request due to PDP Activation in progress.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to other ongoing procedures such as:
Triggers: Increments when the SGSN drops PDP Activate Request due to other ongoing procedures.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PDP Activation Requests that fail due to tunnel deactivation.
Availability: per SGSN service, per RA
Type: Counter
Description: Total number of PDP Activation Request dropped due to Handoff request from Peer SGSN for the subscriber.
Triggers: Increments when the SGSN drops PDP Activate Request due to Handoff request from Peer SGSN for the subscriber.
Availability: per SGSN Service and per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to detach request while activation was in progress.
Triggers: Increments when the SGSN drops PDP Activate Request due to detach request while activation was in progress.
Availability: per SGSN Service and per RA
Type: Counter
Description: This proprietary counter indicates the total number of PDP Activation failures due to Phase 2 offloading in 3G service. This statistics is specific to releases 8.1 and higher.
Triggers: Increments when PDP Activation fails due to Phase 2 offloading.
Availability: per SGSN service, per RA, per RNC
Type: Counter
Description: Total number of PDP Activation Requests dropped due to invalid information in activate request such as invalid Ti flag value.
Triggers: Increments when the SGSN drops PDP Activate Request due to above condition.
Availability: per SGSN Service and per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to SM Guard Timer Expiry.
Triggers: Increments when the SGSN drops PDP Activate Request due to SM Guard Timer Expiry.
Availability: per GPRS service
Type: Counter
Description: Total number of PDP Activation Requests dropped due to an ongoing PDP Activation.
Triggers: Increments when the SGSN drops PDP Activate Request due to PDP Activation in progress.
Availability: per GPRS service
Type: Counter
Description: Total number of PDP Activation Requests dropped due to other ongoing procedures such as:
Triggers: Increments when the SGSN drops PDP Activate Request due to other ongoing procedures
Availability: per GPRS service
Type: Counter
Description: Total number of PDP Activation Requests that fail due to tunnel deactivation.
Availability: per GPRS Service and per NSEI
Type: Counter
Description: Total number of PDP Activation Requests dropped due to Handoff request from Peer SGSN for the subscriber.
Triggers: Increments when the SGSN drops PDP Activate Request due to Handoff request from Peer SGSN for the subscriber.
Availability: per GPRS service
Type: Counter
Description: Total number of PDP Activation Requests dropped due to detach request while activation was in progress.
Triggers: Increments when the SGSN drops PDP Activate Request due to detach request while activation was in progress.
Availability: per GPRS service
Type: Counter
Description: This proprietary counter indicates the total number of PDP Activation failures due to Phase 2 offloading in 2G service. This statistics is specific to releases 8.1 and higher.
Triggers: Increments when PDP Activation fails due to Phase 2 offloading.
Availability: per GPRS service, per RA
Type: Counter
Description: Total number of PDP Activation Requests dropped due to invalid information in activate request such as invalid Ti flag value
Triggers: Increments when the SGSN drops PDP Activate Request due to above condition
Availability: per GPRS service
Type: Counter
Description: Total number of MS initiated PDP context deactivation requests sent to MS accepted for 3G service.
Triggers: Increments when the SGSN sends Deactivate Accept in response to MS initiated PDP deactivation.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of MS initiated PDP context deactivation requests sent to MS accepted for 2G service.
Triggers: Increments when the SGSN sends Deactivate Accept in response to MS initiated PDP deactivation.
Availability: per GPRS service
Type: Counter
Description: Total number of SGSN initiated PDP context deactivation requests received from MS accepted for 3G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to SGSN initiated Deactivation Request sent to MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of SGSN initiated PDP context deactivation requests received from MS accepted for 2G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to SGSN initiated Deactivation Request sent to MS.
Availability: per GPRS service
Type: Counter
Description: Total number of GGSN initiated PDP context deactivation requests received from MS accepted for 3G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to GGSN initiated Deactivation Request sent to MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of GGSN initiated PDP context deactivation requests received from MS accepted for 2G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to GGSN initiated Deactivation Request sent to MS.
Availability: per GPRS service
Type: Counter
Description: Total number of HLR initiated PDP context deactivation requests received from MS accepted for 3G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to HLR initiated Deactivation Request sent to MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of HLR initiated PDP context deactivation requests received from MS accepted for 2G service.
Triggers: Increments when the SGSN receives Deactivate Accept corresponding to HLR initiated Deactivation Request sent to MS.
Availability: per GPRS service
Type: Counter
Description: Total number of RAB requests rejected due to pre-empted event.
Triggers: Increments when RNC initiated RAB release procedure sends RAB Release request with this cause.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests for relocation rejected due to expiry of timer TRELOCoverall. This specifies the maximum time for the protection of overall Relocation procedure in the source RNC.
Triggers: Increments when the source RNC initiates the Iu Release Request procedure towards the SGSN with a cause value “TRELOCoverall expiry”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests for relocation rejected due to expiry of timer TRELOCprep. This specifies the maximum time for expiry of Relocation Preparation procedure in the source RNC.
Triggers: Increments when the source RNC cancels the Relocation Preparation procedure by initiating the Relocation Cancel procedure with a cause value “TRELOCprep expiry”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Indicates the maximum time for waiting the relocation completion in the CN.
Triggers: Increments when the SGSN initiate release of Iu connections towards the source and the target RNC initiates the Iu Release procedure with a cause value “TRELOCcomplete expiry”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Indicates the maximum time in the RNC for queuing the request of RAB establishment or modification.
Triggers: Increments when the RNC sends the RAB assignment response to report unsuccessful establishment/modification of RAB with the failed RAB ID list with the cause “Tqueuing Expiry”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests for relocation triggered. The action fails due to relocation of MS to another RNC.
Triggers: Increments when the Relocation required message is sent with the cause “Relocation Triggered” to the SGSN. If the relocation becomes necessary during the RAB Assignment procedure, the RNC may interrupt the ongoing RAB Assignment procedure and initiate the Relocation Preparation procedure and send the RAB assignment response as failure cause “relocation required”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected because RAB failed to establish during relocation as it cannot be supported in the target RNC or the RAB did not exist in the source RNC.
Triggers: Increments when the target RNC sends the RELOCATION REQUEST ACKNOWLEDGE message with a value in Cause IE “Unable to Establish During Relocation”, for the RABs rejected and received in RELOCATION REQUEST from SGSN, only if the Relocation Type IE is set to “UE involved in relocation of SRNS” in the request.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to unknown target RNC in request.
Triggers: Increments when the SGSN rejects the relocation of SRNS by sending a RELOCATION PREPARATION FAILURE message to the source RNC with Cause IE set to “Unknown target RNC”, if the target RNC is unknown to SGSN.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as relocation was cancelled due to interaction with other procedures.
Triggers: Increments when SGSN issues the IU release command to RNC with the cause “Relocation Cancelled”, if the Relocation Preparation procedure is unsuccessfully terminated.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to completion of successful relocation.
Triggers: Increments when SGSN issues the IU release command to RNC with the cause “Successful Relocation”, if completion of successful relocation of SRNS happened.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the UTRAN or the UE is unable to support the requested ciphering and/or integrity protection algorithms.
Triggers: If the target RNC cannot support any of the integrity protection (ciphering respectively) alternatives provided in the Integrity Protection Information IE or Encryption Information IE, in RELOCATION REQUEST from SGSN, it returns a RELOCATION FAILURE message with the cause “Requested Ciphering and/or Integrity Protection algorithms not supported”. RNC also sends the SECURITY MODE REJECT with the same cause for the same reason when receiving the SECURITY MODE COMMAND from SGSN.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to conflict with the requested security mode configuration and the already existing security mode configuration.
Triggers: If the target RNC receives a source RNC to target RNC Transparent Container IE containing Chosen Integrity Protection (Encryption respectively) Algorithm IE without Integrity Protection (Ciphering respectively) Key IE, it returns a RELOCATION FAILURE message with the cause “Conflict with already existing Integrity protection and/or Ciphering information”. RNC also sends the SECURITY MODE REJECT with the same cause for the same reason when receiving the SECURITY MODE COMMAND from SGSN.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to failure in radio interface procedure.
Triggers: If the radio interface Security Mode Control procedure fails, a SECURITY MODE REJECT message will be sent to the SGSN with cause value “Failure in the Radio Interface Procedure” from RNC.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RAB release is initiated due to UTRAN generated reason.
Triggers: Increments when RNC initiated RAB release procedure sends RAB Release request with this cause.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RAB released due to user inactivity at UTRAN on one or more non real time RABs in order to optimize radio resource.
Triggers: Increments when the source RNC initiates the Iu Release Request procedure towards the SGSN with a cause value “User Inactivity” for a particular MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as relocation is requested for time critical reason. This cause value is reserved to represent all critical cases where the connection is likely to be dropped if relocation is not performed.
Triggers: Increments when the source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Time Critical Relocation”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB request rejected as requested traffic class unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Traffic Class not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to invalid RAB parameter value.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Invalid RAB Parameters Value”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested maximum bit rate is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Maximum Bit Rate not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested maximum bit rate for downlink is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Maximum Bit Rate for DL not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested maximum bit rate for uplink is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Maximum Bit Rate for DL not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested guaranteed bit rate is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID with the cause “Requested Guaranteed Bit Rate not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested guaranteed bit rate for downlink is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Guaranteed Bit Rate for DL not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested guaranteed bit rate for uplink is unavailable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Guaranteed Bit Rate for UL not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested transfer delay is not achievable.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Requested Transfer Delay not Achievable”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to invalid RAB parameter combination.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Invalid RAB Parameters Combination”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to occurrence of condition violation for Service Data Unit (SDU) parameters.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Condition Violation for SDU Parameters”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to occurrence of condition violation for traffic handling priority.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Condition Violation for Traffic Handling Priority”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB request rejected due to occurrence of condition violation for guaranteed bit rate.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Condition Violation for Guaranteed Bit Rate”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested user plane version is not supported.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “User Plane Versions not Supported”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to Iu UP activation failure.
Triggers: Increments when RNC sends the RAB assignment response to report unsuccessful establishment/modification of a RAB with the failed RAB ID list with the cause “Iu UP Failure”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as Relocation Resource Allocation procedure failed due to expiry of the TRELOCalloc timer.
Triggers: Increments when SGSN is unable to complete the relocation of SRNS before the TRELOCalloc expiry. The SGSN then issues a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “TRELOCalloc expiry”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB request rejected due to relocation failure in target CN/RNC or target system.
Triggers: Increments when SGSN cannot complete the relocation of SRNS due to failure in the Target CN/RNC or Target System. The SGSN then issues a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “Relocation Failure in Target CN/RNC or Target System”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to invalid RAB ID in the RNC.
Triggers: If the RAB ID of a RAB requested to be released is unknown in the RNC, RNC will report as a RAB failed to release with the cause value “Invalid RAB ID” in RAB Assignment Response to SGSN. If RAB ID of RAB requested to be transferred is unknown in RNC, the SRNS CONTEXT RESPONSE message will contain the cause with the RAB ID. The RAB ID IE for each RAB for which UTRAN is not able to transfer a data volume report due to unknown RAB ID is included in the DATA VOLUME REPORT message together with a Cause IE “Invalid RAB ID”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as no RAB is available.
Triggers: Increments when SGSN issues the IU release command to RNC with the cause “No remaining RAB”, if there is no RAB associated with the IU.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as relocation was cancelled due to interaction with other procedure.
Triggers: If source RNC triggers the RELOCATION CANCEL to SGSN with cause “Interaction with other procedure” when relocation preparation is triggered and it receives another message via the same signalling IU.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to repeated failure in integrity checking.
Triggers: Increments when RNC issues the IU release request to SGSN with the cause “Repeated Integrity Checking Failure”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the RNC is not supporting the requested location request type either because it does not support the requested event or it does not support the requested report area.
Triggers: If the RNC cannot deliver the location information as requested by the SGSN, due to non-support of the requested event, then it will send location report message indicating the UE location to be “Undetermined” with cause “Requested Request Type not supported”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to a second request on the same RAB.
Triggers: In case of a request to modify or release a RAB that contains the RAB ID of a RAB being queued, the RAB will be taken out of the queue and treated according to the second request. The first request will be responded to as RAB failed to setup or modify the cause value “Request superseded” by RNC to SGSN in RAB Assignment Response.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RAB released due to UE generated signaling connection release.
Triggers: Increments when RNC issues the IU release request to SGSN with the cause “Release due to UE generated signalling connection release”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as resource optimization for relocation occurred.
Triggers: Increments when the source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Resource Optimization Relocation”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as requested information is unavailable.
Triggers: Increments when the source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Resource Optimization Relocation”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to radio related errors/causes.
Triggers: Increments when the source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Relocation desirable for radio reasons”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as relocation is not supported in target system.
Triggers: Increments when SGSN is unable to complete the relocation of SRNS due to failure in the Target CN/RNC or Target System. The SGSN then issues a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “Relocation not supported in Target RNC or Target system”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as retries directed by system.
Triggers: Directed retry is the process of assigning a User Equipment to a radio resource that does not belong to the serving RNC, for example, in situations of congestion. It is triggered by the RAB Assignment procedure and employs relocation procedures. The RNC may indicate an impending directed retry attempt to GSM by sending a RAB ASSIGNMENT RESPONSE message with a RAB ID included in the list of RABs failed to setup and a cause value of “Directed Retry”. The RNC invokes relocation by sending a RELOCATION REQUIRED message to the active SGSN node with the cause “Directed Retry”. The source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Time Critical Relocation”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as radio connection with UE is lost.
Triggers: Increments when RNC initiated RAB release procedure sends RAB Release request with this cause.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RNC is unable to establish all RAB subflow combinations indicated within the RAB Parameters IE.
Triggers: Increments when the RNC cannot initialise the requested user plane mode for any of the user plane mode versions in the UP Mode Versions IE according to the rules for initialization of the respective user plane mode versions. The RAB Assignment Response (failure) with the cause value “RNC unable to establish all RFCs” will be received from RNC. It will be received for the same reason in RELOCATION REQUEST ACKNOWLEDGE message from RNC.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RNC is unable to provide the requested deciphering keys.
Triggers: Increments when the RNC is unable to provide the requested deciphering keys. The RNC will then send a LOCATION RELATED DATA FAILURE message including the Cause IE to the SGSN with the cause “Deciphering Keys Not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as RNC is unable to successfully deliver the requested dedicated assistance data to the UE.
Triggers: Increments when the RNC is unable to successfully deliver the requested dedicated assistance data to the UE. The RNC will then send a LOCATION RELATED DATA FAILURE message including the Cause IE to the SGSN with the cause “Dedicated Assistance data Not Available”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as relocation to the indicated target cell is not allowed for the UE.
Triggers: Increments when SGSN is unable to complete the relocation of SRNS if the Relocation is not allowed in Target Cell. The SGSN then issues a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “Relocation Target not allowed”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to an inability to support location reporting caused by overload.
Triggers: Increments when the RNC cannot deliver the location information as requested by the SGSN due to non-availability of requested information. It will then send location report message indicating the UE location to be “Undetermined” with cause “Location Reporting Congestion”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the load reduction on serving cell needs to be reduced.
Triggers: Increments when the source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Reduce Load in Serving Cell”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as radio resource is unavailable in target cell.
Triggers: Increments when SGSN is unable to complete the relocation of SRNS if the Resource is not available in Target Cell. The SGSN then issues a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “No Radio Resources Available in Target Cell”. Target RNC will send RELOCATION FAILURE message to SGSN with the cause “Radio Resources Available in Target Cell”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to failure in Iu mode in GERAN. The RAB establishment/modification/relocation failed because the GERAN BSC cannot provide an appropriate RAB due to limited capabilities within GERAN.
Triggers: Increments when the RAB establishment/modification/relocation fails because the GERAN BSC cannot provide an appropriate RAB due to limited capabilities within GERAN. The RNC will then send RAB assignment response with the cause “GERAN Iu-mode failure”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as access is restricted in the cell due to shared network.
Triggers: Increments when the source RNC initiates the Iu Release Request procedure towards the SGSN with a cause value “Access Restricted Due to Shared Networks”. The source RNC initiates relocation preparation procedure by sending a RELOCATION REQUIRED message with the cause “Access Restricted Due to Shared Networks”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the incoming relocation request is not accepted by the target RNC because of the Provision of UE Specific Behavior Information to Network Entities (PUESBINE) feature.
Triggers: Increments when the target RNC cannot support the relocation due to PUESBINE feature. It sends a RELOCATION FAILURE message with the cause “Incoming Relocation Not Supported Due To PUESBINE Feature” To SGSN.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the traffic load in the target cell is higher than that in the source cell.
Triggers: Increments when SGSN is unable to complete the relocation of SRNS if the Resource is not available in Target Cell. The SGSN will then issue a RELOCATION PREPARATION FAILURE message to the source RNC with the cause “Traffic Load In The Target Cell Higher Than In The Source Cell”. Target RNC sends RELOCATION FAILURE message to SGSN with the cause “Traffic Load In The Target Cell Higher Than In The Source Cell” to SGSN when load at the target cell is higher than that in the source cell.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for Multimedia Broadcast/Multicast Service (MBMS) feature as multicast service is not supported by user equipment.
Triggers: Increments when SGSN is unable to process the UPLINK INFORMATION EXCHANGE REQUEST for reason that MS does not have the multicat service. The SGSN then sends the UPLINK INFORMATION EXCHANGE FAILURE message to the RNC about the reason for unsuccessful operation with a cause value “MBMS - No Multicast Service For This UE”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for MBMS feature because the user equipment identification is unknown to the CN.
Triggers: Increments when SGSN is unable to process the UPLINK INFORMATION EXCHANGE REQUEST for reason that UE is unknown to SGSN. The SGSN then sends the UPLINK INFORMATION EXCHANGE FAILURE message to the RNC about the reason for unsuccessful operation with a cause value “MBMS - Unknown UE ID”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for MBMS feature as the session starts without any necessary data bearer.
Triggers: Increments when the RNC decides to wait to establish the MBMS RAB. It then sends the MBMS SESSION START RESPONSE message with the cause value “Successful MBMS Session Start - No Data Bearer Necessary” to SGSN for MBMS SESSION START REQUEST.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for MBMS feature as request superseded due to NAS Node Selection Function (NNSF).
Triggers: Increments when NNSF is active and the RNC is received from several CN nodes for a certain MBMS Bearer Service. The MBMS SESSION START message is also sent by the SGSN, and the RNC informs the SGSN with MBMS SESSION START FAILURE message and cause value “MBMS - Superseded Due To NNSF”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for MBMS feature as user equipment is already linked to the given Multicast service.
Triggers: Increments when the RNC sends the MBMS UE LINKING RESPONSE message for unsuccessful linking(s) with cause value “MBMS - UE Linking Already Done”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected for MBMS feature as user equipment delinking failed because the UE had not been linked to the given Multicast service.
Triggers: Increments when the RNC sends the MBMS UE LINKING RESPONSE message for unsuccessful de-linking(s) with cause value “MBMS - UE De-Linking Failure - No Existing UE Linking”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected as the indicated Temporary Mobile Group Identifier (TMGI) is unknown.
Triggers: Increments when the MBMS REGISTRATION FAILURE message sent from SGSN informs the RNC about the reason for unsuccessful MBMS registration operation with cause value “TMGI Unknown”.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of RAB requests rejected due to unspecified failure at MS.
Availability: per SGSN service, per RAI
Type: Counter
Description: Total number of Send Authentication Request messages transmitted to HLR.
Triggers: Counter increments when a MAP Send Authentication Request is initiated from SGSN.
Availability: per SGSN service
Type: Counter
Description: Total number of User Error / Provider Error received in response to SAI request.
Triggers: Counter increments when User Error / Provider Error is received from HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of timeouts that occurred while waiting for response from HLR.
Triggers: Counter increments when there is no response from the HLR for map-auth-fail-rep-req-tx message initiated from SGSN.
Availability: per SGSN service
Type: Counter
Description: Total number of MAP Check IMEI requests initiated towards EIR.
Triggers: Counter increments when MAP CHECK IMEI Request is sent.
Availability: per SGSN service
Type: Counter
Description: Total number of successful responses for MAP Check IMEI requests.
Triggers: Counter increments when MAP CHECK IMEI Request is sent.
Availability: per SGSN service
Type: Counter
Description: Total number of failure responses for MAP Check IMEI requests received from EIR.
Triggers: Counter increments when MAP Return Error / Provider Error is received in response.
Availability: per SGSN service
Type: Counter
Description: Total number of timeouts that occurred while waiting for response from HLR.
Triggers: Counter increments when there is no response from HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of UGL (GPRS Update Location) request initiated towards HLR.
Triggers: Counter increments when UGL request is sent to HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of successful response messages sent in response to UGL request.
Triggers: Counter increments when successful response is received from the HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Failure response (User Error/Provider Error) messages received in response to UGL request.
Triggers: Counter increments when MAP Return Error / Provider Error is received to UGL request.
Availability: per SGSN service
Type: Counter
Description: Total number of timeouts that occurred while waiting for response from HLR.
Triggers: Counter increments if there is no response from HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Cancel Location Request received from HLR.
Triggers: Counter increments when MAP Cancel Location Request is received.
Availability: per SGSN service
Type: Counter
Description: Total number of successful Cancel Location Response messages sent to HLR.
Triggers: Counter increments when successful response is sent to HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Error response messages sent to HLR.
Triggers: Counter increments when MAP Return Error is sent to HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Delete Subscription Data Request received from HLR.
Triggers: Counter increments when MAP Delete Subscription Data (DSD) message is received.
Availability: per SGSN service
Type: Counter
Description: Total number of successful responses for Delete Subscription Data request sent to HLR.
Triggers: Counter increments when MAP Delete Subscription Data (DSD) message is received.
Availability: per SGSN service
Type: Counter
Description: Total number of Error responses sent for Delete Subscription Data (DSD) request received.
Triggers: Counter increments when failure response is sent to HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Authentication Failure Report Request messages transmitted by MAP.
Triggers: Counter increments when a message is initiated to inform HLR that certain vectors had problem in authenticating with the MS.
Availability: per SGSN service
Type: Counter
Description: Total number of Authentication Failure Report Request messages received by MAP.
Triggers: Counter increments when successful response is received in response to map-auth-fail-rep-req-tx.
Availability: per SGSN service
Type: Counter
Description: Total number of User Error and Provider Error received for the Authentication Failure Report Request sent to HLR.
Triggers: Counter increments when MAP Return Error/Provider Error is received in response to map-auth-fail-rep-req-tx message. There will be no effect on the call due to this.
Availability: per SGSN service
Type: Counter
Description: Total number of timeouts that occurred while waiting for response from HLR.
Triggers: Counter increments when MAP Return Error / Provider Error is received in response to map-auth-fail-rep-req-tx. There will be no effect on the call due to this.
Availability: per SGSN service
Type: Counter
Description: Total number of MAP Purge Request messages initiated towards HLR.
Triggers: Counter increments when MAP Purge Request is transmitted.
Availability: per SGSN service
Type: Counter
Description: Total number of successful MAP Purge Request messages sent to HLR.
Triggers: Counter increments when successful response is received from HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of Failure response received from HLR.
Triggers: Counter increments when MAP Return Error / Provider Error is received in response.
Availability: per SGSN service
Type: Counter
Description: Total number of timeouts that occurred while waiting for response from HLR.
Triggers: Counter increments when there is no response from HLR.
Availability: per SGSN service
Type: Counter
Description: Total number of active transaction capabilities application part (TCAP) Dialogs in the system.
Triggers: Counter increments when a new TCAP Dialog is created.
Availability: per SGSN service
Type: Gauge
Type: Gauge
Type: Gauge.
Type: Gauge.
Description: New gauge in release 9.0: Total number of mobile terminated SMS in the queue.
Triggers: If there is already an MT-SMS transaction in progress, then the gauge increments when any new messages are received and queued.
Availability: per MAP service
Type: Gauge
Type: Gauge.
Description: New counter in release 9.0: Total number of RP ERROR messages sent with the cause Protocol Error in the message header.
Triggers: Counter increments when receiving an RP ERROR, with cause Protocol Error, from the MS/SMSC.
Availability: per MAP service
Type: Counter
Description: Counter new in release 9.0: Total number RP SMMA messages received.
Triggers: Counter increments when the SGSN receives an RP SMMA message from the MS/UE.
Availability: per MAP service
Type: Counter
Important: See Bulk Statistics Overview for statistics that are common to all schema.
 
 

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883