The Event Monitoring functionality allows monitoring of specific events in the 3GPP system and makes the event information available through either Service Capability Exposure Function (SCEF) or Home Subscriber Server (HSS). Allows the identification of the 3GPP network elements that are suitable for configuring specific events, detecting events, and reporting events to the authorized users.

The following example explains a specific use case for a individual subscriber.

A subscriber can track the following events:

• Location Reporting

• UE reachability

• Availability after DDN failure

• PDN Connectivity Status

• Loss of connectivity

• Communication failure

• Number of UEs available in a geographical location

• or Idle Status Indication for Availability after DDN failure for a specific subscriber (UE) from MME or HSS

  Once the tracking is initiated SCEF queries the MME service and reports the list of events failed or affected for that specific subscriber (UE).

In this release, MME supports monitoring events on s6a and t6a interfaces for monitoring the following events:

• Number of UEs present in a geographical location - This is triggered from SCEF to MME in Configuration information request message. MME responds with a configuration information Answer messages with the reports, status and supported AVPs. The following table describes the supported feature AVPs.

• Location Reporting - Montoring Events sends report when the MME detects that the UE changed location with the granularity as requested by the monitoring event configuration. If there is Minimum Reporting Interval, while the timer is running, the MME suppresses sending consecutive Location Reporting notification. On timer expiry MME sends location information that was contained in the latest suppressed Location Reporting notification and restarts the timer.

  Location Reporting is supported for Current Location or the Last Known Location of a UE. The Location Reporting type allows:

  • One Time Reporting: If request is for "Last known" of a UE the supported Accuracy in the network is at either cell level (CGI/ECGI), eNodeB, TA/RA level.

  • Periodic Reporting: Request is for current location type.

  • Continuous Location Reporting: Unless a Minimum Reporting Interval was provided, the serving node(s) sends a notification every time it becomes aware of a location change.

• UE Reachability – Monitoring Events reports when UE transitions to ECM-CONNECTED mode (for a UE using Power Saving Mode or extended idle mode DRX) or when the UE reaches for paging (for a UE using extended idle mode DRX).

• Availability after DDN failure – MME triggers this event when the UE contacts the network. For example, to perform a TAU, or to executes a service request after DDN Failure.

  The SCEF sends Monitoring request without adding Max Number of Reports, since the "Availability after DDN Failure" is an ongoing event that needs explicit deletion to cancel further reports. The information is provided to the serving node (MME) at registration. The serving node notes this and sets a Notify-on-available-after-DDN-failure flag after a DDN failure. If the flag is set when the UE next contacts the network, the serving node notifies the SCEF that the UE is reachable, and clears the flag.

  Note	Not every DDN failure triggers this event. This event is triggered only when the UE is in PSM or eDRX mode.

• PDN Connectivity Status – The following AVPs are supported.

• Loss of Connectivity– Event is triggered when UE's radio connectivity is lost. HSS configures events HSS through ULA/ISDR messages. Event reporting happens through RIR with event specific parameters. The following AVPs are supported. .

• Communication failure – Event is triggered when the MME becomes aware of a RAN or NAS failure event. Event configuration by HSS through ULA/ISDR messages.

  Important

  Handover and Roaming functions are not supported.

• Idle Status Indication for Availability after DDN failure and UE reachability – MME supports Idle Status Indication when the UE transitions into idle mode. The MME includes the time at which the UE transitioned into idle mode, the active time, and the periodic TAU/RAU time granted to the UE by the MME in the notification towards the SCEF, the eDRX cycle length, and the suggested number of downlink packets if a value is provided to the S-GW.

• External-identifier on MME for monitoring events

  – The External-identifier feature is applicable for the ULR/ULA, DSR/DSA and IDR/IDA command pairs over S6a (and S6d), when the MME (or combined MME/SGSN) supports the External-identifer.

  • If the MME/SGSN includes the External-Identifier or the MSISDN if present in the subscription data received from the HSS, the UE contains the identity of the UE, which is a grouped AVP that contains MSISDN or the External-identifier.

    Note

    If the MME or combined MME/SGSN does not support External-identifier: The HSS shall not send the External-Identifier subscription data to the MME or combined MME/SGSN within ULA. The HSS shall not send Monitoring Event configuration for UEs that are part of a group and have no MSISDN as part of its subscription data to the MME/SGSN. The HSS shall not indicate External-Identifier-Withdrawal in the DSR-Flags AVP of the DSR.

• Gtpv2 handover scenarios

• For adding TAC field in the Monitoring reporting information requests (RIR) from MME

This section describes how to configure monitoring events for a call control profile.

Important

When you configure MME service for users, monitoring-events is disabled by default.