LCS Schema Statistics

The Location Services (LCS) schema provides operational statistics that can be used for monitoring and troubleshooting the following products: MME.

This schema provides the following types of statistics:
  • Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached.
    • All counter statistics are cumulative and reset only by one of the following methods: roll-over when the limit is reached, after a system restart, or after a clear command is performed.
    • The limit depends upon the data type.
  • Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
  • Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.
The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:
  • Int32/Int64: An integer, either 32-bit or 64-bit:
    • 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.
  • Float: A numeric value that includes decimal points; for example, 1.345.
  • String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.

IMPORTANT:

Unless otherwise indicated, all statistics are counters and all statistics are standards-based.

Key Variables: Every schema has some variables which are typically referred to as “key variables”. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be “%vpnname%” plus “%servname%’, as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.


Table 1. Bulk Statistic Variables in LCS Schema
Variables Description Data Type

vpnname

Description:The name of the context configured on the system that is currently facilitating the LCS service.

This is a key variable.

Type: Information

String

vpnid

Description:The identification number of the context configured on the system that is currently facilitating the LCS service.

This is an internal reference number.

This is a key variable.

Type: Information

Int32

servname

Description:The name of the LCS service for which these statistics are being displayed.

This is a key variable.

Type: Information

String

servid

Description:The identification number of the LCS service for which these statistics are being displayed.

This is an internal reference number.

This is a key variable.

Type: Information

Int32

msg-psl-req

Description:The total number of Provide Subscriber Location Request messages received.

Availability: Per LCS Service

Type: Counter

Int32

msg-psl-req-drop

Description:The total number of Provide Subscriber Location Request messages dropped.

Availability: Per LCS Service

Type: Counter

Int32

msg-psl-ans

Description:The total number of Provide Subscriber Location Answer messages sent.

Availability: Per LCS Service

Type: Counter

Int32

msg-psl-ans-drop

Description:The total number of Provide Subscriber Location Answer messages dropped.

Availability: Per LCS Service

Type: Counter

Int32

msg-lr-req

Description:The total number of Network Induced Location Request (NI-LR) request messages initiated by the MME.

Trigger: This counter increments when the MME initiates an NI-LR.

Availability: Per LCS Service

Type: Counter

Int32

msg-lr-req-drop

Description:The total number of Location Request messages that were dropped (could not be sent) as a result of the peer being down.

Trigger: This counter increments when the Location Request could not be sent, and was therefore dropped.

Availability: Per LCS Service

Type: Counter

Int32

msg-lr-ans

Description:The total number of Location Request acknowledge messages received.

Trigger: This counter increments when an acknowledge message is received for a Location Request request.

Availability: Per LCS Service

Type: Counter

Int32

msg-lr-ans-drop

Description:The total number of Location Request acknowledge messages dropped. This can occur when the user name in the acknowledge message does not match that sent in the request.

Trigger: This counter increments when the Location Request could not be sent, and was therefore dropped.

Availability: Per LCS Service

Type: Counter

Int32

msg-lr-ans-timeout

Description:The total number of Location Request acknowledge messages expected but not received before the timer expired.

Trigger: This counter increments when the Location Request answer was not received.

Availability: Per LCS Service

Type: Counter

Int32

msgerror-user-unknown

Description:The total number of times the PLR was received for an unknown user (Error code: 5001).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-unauth-req-net

Description:The total number of times the requesting GMLC’s network was not authorized to request UE location information (Error code: 5490).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-unreach-user

Description:The total number of times a PLR was received for a user which could not be reached (Error code: 4221)

Availability: Per LCS Service

Type: Counter

Int32

msgerror-susp-user

Description:The total number of times the PLR was received for a user who is suspended in the MME (Error code: 4222).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-det-user

Description:The total number of times where the PLR was received for a detached user (Error code: 4223).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-pos-denied

Description:The total number of times the positioning procedure was denied (Error code: 4224).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-pos-failed

Description:The total number of times the positioning procedure failed (Error code: 4225).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-unreach-lcs-client

Description:The total number of times the GLMC indicated that the LCS Client was not known or could not be reached (Error code: 4226).

Availability: Per LCS Service

Type: Counter

Int32

msgerror-other-errors

Description:The total number of PLA messages received with other error result codes.

Availability: Per LCS Service

Type: Counter

Int32