|Event Reporting Information Parameter
|Event reporting mode
|Mode of reporting - e.g. reporting up to a maximum number of reports, periodic reporting along with periodicity, variable reporting periodicity, reporting up to a maximum duration, reporting when threshold is reached.
(see NOTE 7)
|Maximum number of reports
|Maximum number of reports after which the event subscription ceases to exist.
|(see NOTE 1)
|Maximum duration of reporting
|Maximum duration after which the event subscription ceases to exist.
|(see NOTE 1)
|Immediate reporting flag
|The Event provider NF notifies the current status of the subscribed event, if available, immediately to the consumer NF.
|Variable reporting periodicity information (0..N)
|List of variable measurement information.
|(see NOTE 7)
|> Reporting periodicity
|(see NOTE 7)
|The corresponding condition related to Reporting periodicity e.g. load of NF service producer.
|(see NOTE 7)
|Percentage of sampling (1%..100%) among impacted UEs.
(see NOTE 2)
|Criteria for partitioning UEs before applying sampling ratio.
(see NOTE 2)
|Group Reporting Guard Time
|Parameter for group-based monitoring configuration to indicate the time for which the Monitoring Event Reporting(s) related with the UEs in a group can be aggregated before sending them to the consumer NF.
|Deactivate notification flag
|Indicates to the Event provider NF that the notification of the available events shall be muted until the Event consumer NF provides the retrieval notification flag to retrieve the events stored.
|Optional (see NOTE 8)
|Retrieval notification flag
|Indicates to the Event provider NF to send the notification to the Event consumer NF with the stored events and mutes again the notification of future events.
|Optional (see NOTE 8)
|Muting Exception Instructions
|Indicates to an Event provider NF instructions for the subscription and stored events when an exception (e.g. full buffer) occurs at the Event provider.
(see NOTE 6 and NOTE 8)
|Granularity of dynamics
|The maximum amount of dynamics in the event which allows to skip an event notification.
(see NOTE 3)
|Event provider NF reports only when the events differs from the previously notified event.
(see NOTE 4)
|Threshold values indicate conditions on the level to be reached for the reporting.
(see NOTE 5)
The requester shall include 2) Maximum number of reports or 3) Maximum duration of reporting, or both, depending on 1) Event reporting mode.NOTE 2:
Parameter only applicable to certain event IDs reporting metrics (e.g. Number of UEs present in a geographical area) used and used e.g. by the NWDAF for data collection.NOTE 3:
The Granularity of dynamics includes 1) the range of scalar value, 2) the list of events identification, or 3) the previous notification. The range of scalar value is only applicable to the event depicted as number (e.g. the number of UE), the others is applicable to the event depicted as identification (e.g. UE location, UE identification).NOTE 4:
The differences in event includes the events have been newly appeared, disappeared and changed from the previous notification.NOTE 5:
This parameter is included only if the Event reporting mode indicates reporting when threshold is reached.NOTE 6:
This parameter is included only if the "Deactivate notification flag" is set.NOTE 7:
If the requester includes "variable reporting periodicity", then reporting periodicity changes depending on e.g. load of NF service producer; otherwise the reporting periodicity is fixed.NOTE 8:
The support of this parameter is only required for services where NWDAF and/or DCCF are among the example consumers. It is expected that this parameter is used only if the Event Consumer NF is NWDAF or DCCF.
|Types of Partitioning Criteria
|Type Allocation Code
|Subscriber PLMN ID
|Geographical area, i.e. list(s) of TAI(s)
|Which NF detects the event
|Loss of Connectivity
|Network detects that the UE is no longer reachable for either signalling or user plane communication (see NOTE 4). The AF may provide a Maximum Detection Time, which indicates the maximum period of time without any communication with the UE after which the AF is to be informed that the UE is considered to be unreachable (see NOTE 7). If Unavailability Period Duration has been provided by the UE, the AMF uses the remaining value of it to determine the foreseen Loss of Connectivity time as described in clause 188.8.131.52 of TS 23.501.
Detected when the UE transitions to CM-CONNECTED state or when the UE will become reachable for paging, e.g. Periodic Registration Update timer. It indicates when the UE becomes reachable for sending downlink data to the UE.
The AF may provide the following parameters:
This event is detected based on the Event Reporting Information Parameters that were received in the Monitoring Request (one-time reporting, maximum number of reports, maximum duration of reporting, periodicity, etc. as specified in clause 4.15.1).
It reports either the Current Location or the Last Known Location of a UE.
When AMF is the detecting NF:
One-time and Continuous Location Reporting are supported. For Continuous Location Reporting the serving node(s) sends a notification every time it becomes aware of a location change, with the granularity depending on the accepted accuracy of location (see NOTE 1). For One-time Reporting with immediate reporting flag set, AMF reports the Last Known Location immediately.When AMF is the detecting NF:
If the immediate reporting flag is not set, the AMF reports the UE Current Location (In case the AMF does not have the UE current location in the granularity as requested by the location report, the AMF retrieves the information via NG-RAN Location reporting procedure as defined in clause 4.10).When GMLC is the detecting NF:
Immediate and Deferred Location Reporting is supported. For Deferred Location Reporting the event types UE availability, Area, Periodic Location and Motion are supported.
|Change of SUPI-PEI association
|This event is detected when the association between PEI and subscription (SUPI) changes (USIM change).
|This event is detected based on the UE's current roaming status (the serving PLMN and/or whether the UE is in its HPLMN) and notification is sent when that status changes. (see NOTE 2). If the UE is registered via both 3GPP and N3GPP Access Type, then both instances of Roaming status are included.
|This event is detected when RAN or NAS level failure is detected based on connection release and it identifies RAN/NAS release code.
|Availability after Downlink Data Notification failure
|This event is detected when the UE becomes reachable again after downlink data delivery failure. When requesting Availability after Downlink Data Notification failure monitoring, the AF may in addition request Idle Status Indication to be included in the UE reachability event reporting.
|PDU Session Status
|This event is detected when PDU session is established or released. (see NOTE 6)
|Number of UEs present in a geographical area
|This event is detected based on the Event Reporting Information Parameters that were received in the Monitoring Request (Level of aggregation, Sampling ratio, see clause 4.15.1). It indicates the number of UEs that are in the geographical area described by the AF. The AF may ask for the UEs that the system knows by its normal operation to be within the area (Last Known Location) or the AF may request the system to also actively look for the UEs within the area (Current Location).
|CN Type change
|The event is detected when the UE moves between EPC and 5GC. It indicates the current CN type for a UE or a group of UEs when detecting that the UE switches between being served by a MME and an AMF or when accepting the event subscription. (see NOTE 3)
|Downlink data delivery status
It indicates the downlink data delivery status in the core network. Events are reported at the first occurrence of packets being buffered, transmitted or discarded, including:
|UE reachability for SMS delivery
|For SMS over NAS, this event is detected when an SMSF is registered for a UE and the UE is reachable as determined by the AMF and the UDM. For SMS over IP, the event is detected when the UE is reachable as determined by the AMF and the UDM regardless of an SMSF being registered. This enables the UE to receive an SMS. See clauses 184.108.40.206 and 220.127.116.11 (see NOTE 8).
|UE memory available for SMS
|This event is detected when the UDM receives UE memory available for SMS indication from the SMSF as part of Alert procedure as specified in clause 5.1.8 of TS 23.540
|Number of registered UEs and/or established PDU Sessions
|It indicates the current number of registered UEs or established PDU Sessions for a network slice that is subject to NSAC. For One-time Reporting with Immediate Reporting Flag set, NSACF reports the number of registered UEs or established PDU Sessions immediately.
|Area Of Interest
|It indicates change of the UE presence in the Area Of Interest.
|Group Member List Change
|It indicates the changes on the members of the group. This event apply to a group of UEs (identified by an External Group ID), such as 5G VN group (see NOTE 9) or other groups.
|Session inactivity time
|This event is detected by the SMF when the PDU Session has no data transfer for a period specified by the Inactivity Timer. via the User plane status information event, see clause 18.104.22.168.1.
|This event measures the traffic volume (UL and DL) aggregated for the PDU Session (NOTE 10).
|UL/DL data rate
|This event measures the data rate (UL and DL) aggregated for the PDU Session (NOTE 10).
|Detection of application start or stop (See NOTE 11), as described in clause 22.214.171.124 of TS 23.503.
Location granularity for event request, or event report, or both could be at cell level (Cell ID) or TA level. The granularity can also be expressed by other formats such as geodetic uncertainty shapes (e.g. polygons, circles, etc.) or civic addresses (e.g. streets, districts, etc.) which can be mapped by NEF to AMF specific granularity levels.NOTE 2:
Roaming status means whether the UE is in HPLMN or VPLMN based on the most recently received registration state in the UDM.NOTE 3:
CN type of CN Type change event is defined in clause 126.96.36.199 of TS 23.501.NOTE 4:
In the case of UDM service operation information flow, the UDM should set the subscribed periodic registration timer to a smaller value than the value of Maximum Detection Time, since the value of the mobile reachable timer is larger than the value of the periodic registration timer.NOTE 5:
Maximum Latency, Maximum Response Time and Suggested number of downlink packets are defined in clause 188.8.131.52a.NOTE 6:
The NEF makes a mapping between the 5GS internal event "PDU Session Status" and the T8 API event "PDN Connectivity Status".NOTE 7:
The preferred method for provisioning Network Configuration Parameters is External Parameter Provisioning specified in clause 184.108.40.206a. Provisioning event specific parameters as part of Monitoring Request is expected to be used only by the AF that does not support Parameter Provisioning procedure specified in clause 220.127.116.11a.NOTE 8:
The NEF maps between the T8 API event "UE reachability" with reachability type SMS and the 5GS internal event "UE reachability for SMS delivery" for SMS over NAS. The event "UE reachability for SMS delivery" for SMS over IP is used by HSS as described in clause 18.104.22.168 of TS 23.632.NOTE 9:
5G VN group management is defined in the clause 5.29.2 of TS 23.501.NOTE 10:
NEF subscribes to the UPF event applicable for a PDU session via SMF and the result is exposed to NEF by UPF directly. The corresponding procedure for NEF to trigger the UPF event can be found in clause 22.214.171.124.3.NOTE 11:
This event uses bulk subscription/notification, which may impact the PCF/SMF/UPF performance.