Information | Source | Description |
---|---|---|
UE ID | Identifies a single UE. | |
Signalling feature data | NF procedures containing signalling exchange information related to a particular UE or session from the Connection, Registration, Mobility and Session Managements procedures (NOTE 1). | |
> Request type and number from UE/RAN (0..max) | AMF | Request type of N1 or N2 interface (such as received Initial Registration Request, Mobility and Periodic Registration Request, Service Request, etc.) and the number of requests corresponding to the request type. |
>> Time duration from receiving request from UE/RAN to response to UE/RAN | AMF | Time duration between the request from UE/RAN and response to UE/RAN. |
>> Number of successful responses of UE/RAN | AMF | Number of successful responses associated to their initial requests, such as Registration Response, etc. |
>> Number of failed responses of UE/RAN | AMF | Number of failed responses associated to their initial requests, such as Registration Reject, Service Reject, etc. |
>> Reason of failed responses of UE/RAN | AMF | Reasons of failed responses associated to their initial requests, e.g. reject, no-response, etc. |
>> A posterior Request type of UE/RAN (0..max) | AMF | A posterior Request types triggered from UE/RAN, for NF Service request, or request to UE/RAN (NOTE 3). |
> Request type and number from NF (0..max) | NF | Request type (i.e. identification of NF service instance) received from NF, e.g. Namf_ |
>> Time duration from sending a request to receiving NF to response from the NF | NF | Time duration between the request from an NF and response to the NF. |
>> Number of successful responses from NF | NF | Number of successful responses associated to their initial requests (NOTE 2). |
>> Number of failed responses from NF | NF | Number of failed responses associated to their initial requests (NOTE 2). |
>> Reason of failed responses from NF | NF | Reasons of failed responses over the egress interface associated to their initial requests, e.g. reject, no-response, etc. |
>> Number of redundant signalling of NF | NF | Number of received redundant signalling. The redundant signalling means the signalling which is transmitted multiple times (NOTE 2) (NOTE 3). |
>> A posterior Request type of NF (0..max) | NF | A posterior Request types triggered from NF, for NF Service request (NOTE 3) (NOTE 4). |
> Public Warning information | AMF | Public Warning information as defined in the TS 23.041, such as WRITE-REPLACE WARNING REQUEST, etc. |
> Frequent Mobility Registration Update | AMF | The number of Mobility Registration Updates N within a period M may be an indication for abnormal ping-pong behaviour, where N and M are operator's configurable parameters. |
> Number of receiving Session Report from UPFs | SMF | Number of receive Session Report from UPF triggered by DL packet in case of PDU Session is in 5GCM-idle state. |
UE Context in NF | ||
> State transition information | AMF, SMF |
UE related state transition information such as transition type, frequency of CM state changes, etc.
State transition identifier:
|
> timer information | AMF, SMF | Timer information which has been set for the UE, such as timer type, duration. |
NOTE 1:
NWDAF can optionally provide transaction dispersion analytic information for MM and SM transactions.
NOTE 2:
This data is provided per time interval that is indicated by the NWDAF.
NOTE 3:
As a centric routing/proxy entity, SCP might be involved with some signalling that may not be visible to the NF sending the SCP's ingress traffic, such a signalling could be associated with actions such as selection & discovery, retransmissions, re-directions, re-selection, throttling, etc.
NOTE 4:
A posterior request is a request sent from NF1 to NF2 (or from NF2 to NF1) that was triggered by a previous request received by NF1. For example, in clause 4.3.2.2 of TS 23.502, the request sent by AMF in step 3 and the request sent by SMF in step 11 are both posterior requests of the request received by the AMF in step 1. These posterior requests can be collected by NF1 (the AMF in this example).
|
Information | Source | Description |
---|---|---|
NF instance ID | NF instance ID. | |
> NF profile | NRF | NF Profile information such as allowed NF information for the NF and NF Service(s), NF capacity, NF load, NF priority, NF service instance capacity, NF service instance load, NF service instance priority. |
> F load information | NRF | Load information indicates the current load of the NF and NF Service(s) (NOTE 1). |
NF heart-beat related information | NF, OAM | NF heart-beat related information such as responding time, Number of retransmissions, heart-beat intervals. |
> Unexpected operational status indicator | NF, OAM | The parameter indicates unexpected operational status occurs. It is an indication of deviation from the normal operations, based on thresholds or rules configured by operator at the NF or OAM (e.g. for energy consumptions, loads, etc.). |
NOTE 1:
If this information is not available in the NRF, it can be obtained from the OAM.
|
Information | Source | Description |
---|---|---|
NF instance ID | NF instance ID. | |
> Usage information of UE IP address resources | SMF | Usage information of UE IP address resources (dynamic and static, V4, V6, etc.) for CP or UP allocation, such as number, usage, number of UE IPs, which prohibit allocation during certain time interval, etc. This parameter is valid for SMF only. |
> Load information of connected UPFs | SMF | Load information of connected UPFs such as using PFCP Load Control Information. This parameter is valid for SMF only. |
Information | Source | Description |
---|---|---|
Application ID | AF | Identifies the application providing this information. |
User activation time information (1…max) | AF | Information of activation time for the users (e.g. IoT users) per application. |
> Number of UEs | AF | The total number of UEs. |
> Active Time | AF | The time stamp of the users per application switch to active, or the start and end time of the users activity per application. |
> Inactive Time | AF | The time stamp of the users per application switch to inactive, or the start and end time of the users inactivity per application, if applicable. |
> UE type ID | AF | Identifies a group of UEs, e.g. external group ID, or a list of UE IDs. |
Information | Source | Description |
---|---|---|
NRF ID | NRF instance ID. | |
Number of NF service registration requests | OAM | Number of registration request received at the NRF. |
> Number of successful NF service registrations | OAM | Number of successful registrations. |
> Number of failed NF service registrations due to encoding error of NF profile | OAM | Number of failed registrations. |
> Number of failed NF service registrations due to NRF internal error | OAM | Number of failed registrations. |
Number of NF service update requests | OAM | Number of update request received at the NRF. |
> Number of successful NF service updates | OAM | Number of successful updates. |
> Number of failed NF service updates due to encoding error of NF profile | OAM | Number of failed updates. |
> Number of failed NF service updates due to NRF internal error | OAM | Number of failed updates. |
Number of NF discovery requests | OAM | Number of discovery request received at the NRF. |
> Number of successful NF discoveries | OAM | Number of successful discovery attempts. |
> Number of failed NF service discoveries due to unauthorized NF Service consumer | OAM | Number of failed discovery attempts. |
> Number of failed NF discoveries due to input errors | OAM | Number of failed discovery attempts. |
> Number of failed NF discoveries due to NRF internal error | OAM | Number of failed discovery attempts. |
Information | Source | Description |
---|---|---|
affectedObject | MDAF | Indication of 5GC NFs where congestion issues occurred or potentially may occur. |
cPCongestionIssueID | MDAF | This field holds the ID of the control plane congestion issue which is reported. |
Information | Source | Description |
---|---|---|
failurePredictionObject | MDAF | Indication of NFs where the failure related issues occurred or potentially occur. |
potentialFailureType | MDAF | This field holds the ID of the control plane congestion issue which is reported. |
eventTime | MDAF | This field holds the time of potential failure predicted. |
issueID | MDAF | This filed holds the ID of this failure prediction which is reported. |
perceivedSeverity | MDAF | This field holds the value to indicate relative level of urgency for operator attention. |
Information | Source | Description |
---|---|---|
NF instance ID | NF instance ID of the service producer or consumer. | |
> Number of requests to a NF Service instance | SCP | Number of requests received for a NF service instance, such as Nudm-sdm, Namf-loc, etc. |
> Number of successful responses of different NF Service of the NF instance | SCP | Number of successful responses from NF service instances, such as Nudm-sdm, Namf-loc, etc. |
> Number of total failure responses of different NF Service of the NF instance | SCP | Number of total failure responses of different NF Service, such as Nudm-sdm, Namf-loc, etc. |
> Number of failed responses of different NF Service of the NF instance | SCP | Number of failed responses of different NF Service, such as Nudm-sdm, Namf-loc, etc. |
> Reason of failed responses of different NF Service of the NF instance | SCP | Reasons of failed responses of different NF Service, e.g. reject, no-response, etc. |
> Number of failure responses SCP generated to the NF instances | SCP | Number of total failure responses generaterd by SCP. |
> Reason of failure responses SCP generated to the NF instance | SCP | Reasons of failed responses of SCP, e.g. target nf not reachable, no-response, etc. |
> Number of SCP reselect NF instance that is originally to that NF instance | SCP | Number of SCP reselect NF instance, it happens when e.g. SCP find the original NF instance not reachable. |
> Reason of SCP reselection of NF instance | SCP | Reason of SCP reselect NF instance as defined in clause 6.3.1.0 of TS 23.501. |
> Status of the connection to the NF instance | SCP | The connection status (i.e. ACTIVE or INACTIVE) between SCP and NF instance. |
> Average time duration from sending request to the NF instance to receiving response from the NF instance | SCP | Average time duration between SCP sending the request to the NF instance and SCP receiving the response from the NF instance. |
Information | Description |
---|---|
Report (1..max) | List of observed signalling storm statistics. |
> Target NF ID/SCP ID | A list of impacted NFs/SCPs of signalling storm detected by NWDAF. |
> Cause ID of the signalling storm | The potential cause of abnormal level of signalling (i.e. massive signalling from UE or NF abnormal signalling). |
> Source UE/NF | a UE or a group of UEs or several groups of UEs identified by internal Group ID or SUPI or SUPI range, or a list of NFs which cause the signalling storm. |
> OPTIONAL Time slot entry (1..max) | List of time slots during the Analytics target period. |
>> Time slot start | Time slot start within the Analytics target period. |
>> Duration | Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size. |
>> Received Signalling Analytics | Information of signalling received by the target NF(s). |
>>> Total number of received signalling | Indicates the statistics on the number of signalling messages received by the target NF(s) in the time slot. |
>>> Growth rate of received signalling | Difference between the number of signalling messages received by the NF in the time slot and the number of signalling messages received by the target NF(s) in the previous time slot. |
>>> Signalling analytics of UE | Indicates the statistics on the number of signalling messages received from UEs within the time slot (NOTE 1). |
> OPTIONAL Timer List | The list of timer information per source UE(s) (NOTE 1). |
>> Type of timer | The type of timer which has been set. |
>> Timer duration | The timer duration that has be selected for the source UE(s). |
NOTE 1:
Only available when Cause ID of signalling storm is massive signalling from UEs, and there exists Source UE(s).
|
Information | Description |
---|---|
Report (1..max) | List of predicted signalling storm analytics. |
> Target NF ID/SCP ID | A list of impacted NFs/SCPs signalling storm predicted by NWDAF. |
> Cause ID of the signalling storm | The potential cause of abnormal level of signalling (i.e. massive signalling from UE or NF abnormal signalling). |
> Source UE/NF | a UE or a group of UEs or several groups of UEs identified by internal Group ID or SUPI or SUPI range, or a list of NFs which cause the signalling storm. |
> OPTIONAL Time slot entry (1..max) | List of time slots during the Analytics target period. |
>> Time slot start | Time slot start within the Analytics target period. |
>> Duration | Duration of the time slot. If a Temporal granularity size was provided in the request or subscription, the Duration is greater than or equal to the Temporal granularity size. |
>> Reference point | The information of the reference point impacted. (e.g. N1, N2) |
>> Service operation(s) | The information of the service operation(s) impacted. (e.g. Namf_ |
>> Received Signalling Analytics | Information of signalling received by the target NF(s). |
>>> Received number of signalling | Received number of signalling of the specific signalling type. |
>>> Growth rate of received signalling | Difference between the number of signalling messages received by the NF in the time slot and the number of signalling messages received by the target NF(s) in the previous time slot. |
>>> Signalling analytics of UE | Indicates the statistics on the number of signalling messages received from UEs within the time slot (NOTE 1). |
> OPTIONAL Timer List | The list of timer information per Source UE(s) (NOTE 1). |
>> Type of timer | The type of timer. |
>> Timer duration | The timer duration that commonly is selected for the Source UE(s). |
> Priority | Priority (relative to other NFs of the same type) of candidate NFs as defined in the TS 29.510. |
> Capacity | Candidate NF capacity information, expressed as a weight relative to other NF instances of the same type as defined in the TS 29.510. |
> Confidence | Confidence of this prediction. |
NOTE 1:
Only available when Cause ID of signalling storm is massive signalling from UEs, and there exists Source UE(s).
|
Cause of the signalling storm | Example actions of NFs |
---|---|
massive signalling from UE | AMF sets MM NAS related timer (e.g. back-off, T3512) for a selected set of UEs. |
massive signalling from UE | SMF sets SM NAS related timer (e.g. back-off) for a selected set of Sessions. |
massive signalling from UE | AMF/SMF sets suggested N1/N2 interface related ingress/egress threshold, or AMF triggers RAN to initiate overload control for a selected set of UEs in specific slice or priority as defined in clause 8.7.7 of TS 38.413 to start overload control. The AMF may assign a specific slice to the UEs under signalling storm conditions and initiate overload control for the slice under signalling storm conditions. |
NF abnormal signalling | NRF configures the local policy (e.g. to prevent the source NF with abnormal signalling from being discovered or discovering others, to update the NF profile(s)(e.g. Priority, Capacity) of NF(s) based on the signalling storm statistics and/or predictions and send the updated NF profiles(s) to NF service consumer(s) of the NF(s)(e.g. subscriber of the NF profile as defined in clause 4.17.7 of TS 23.502)). |
NF abnormal signalling | Source NF configures to (re)select other NFs instead of NF with abnormal signalling and may unsubscribes the NF with abnormal signalling. |
NF abnormal signalling | Source NF configures to deprioritize the NFs/Services with abnormal signalling from being selected. |
NF abnormal signalling | Source NF triggers UE Reregistration and/or Session Reestablishments to avoid NF with abnormal signalling. |
NF abnormal signalling | SCP blocks or throttles messages originating from an NF/service with abnormal signalling. |
NF abnormal signalling | SCP redirects requests towards an NF service producer with abnormal signalling towards another service producer. |
NF abnormal signalling | SCP notifies communication peers of an NF that the NF may suffer signalling storm. |