Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.288  Word version:   16.3.0

Top   Up   Prev   Next
1…   4…   6…   6.2…   6.3…   6.4…   6.5…   6.6…   6.7…   6.7.3…   6.7.4…   6.7.5…   6.8…   6.9…   7…

 

6.5  NF load analytics
6.5.1  General
The clause 6.5 describes how NWDAF can provide NF load analytics, in the form of statistics or predictions or both, to another NF.
The service consumer may be an NF, or the OAM.
The consumer of these analytics shall indicate in the request:
  • Analytics ID set to "NF load information";
  • The Target of Analytics Reporting: an optional SUPI;
  • Analytics Filter Information:
    • optional S-NSSAI;
    • an optional list of NF Instance IDs, NF Set IDs, or NF types;
  • Optional Reporting Threshold; the Reporting Threshold is unique for all NFs matching the above Analytics Filter and the reporting applies when the conditions are met for at least one of these NFs;
  • An Analytics target period indicates the time period over which the statistics or predictions are requested;
  • In a subscription, the Notification Correlation Id and the Notification Target Address are included.
The NWDAF shall notify the result of the analytics to the consumer as indicated in clause 6.5.3.
If a list of the NF Instance IDs (or respectively of NF Set IDs) is provided, the NWDAF shall provide the analytics for each designated NF instance (or respectively for each NF instance belonging to each designated NF Set). In such case the Target of Analytics Reporting should be ignored.
Otherwise, if a SUPI is provided, the NWDAF shall use the SUPI to determine which NF instances (AMF and SMF) are serving this specific UE, filter them according to the provided S-NSSAI and NF types using data collected from NRF or OAM, and provide analytics for these NF instances.
NOTE:
Only NF instances of type AMF and SMF can be determined using a SUPI.
Up
6.5.2  Input dataWord-p. 28
For the purpose of NF load analytics, the NWDAF may collect the information as listed in Table 6.5.2-1 for the relevant NF instance(s).
Information
Source
Description

NF load
NRF
The load of specific NF instance(s) in their NF profile as defined per TS 29.510.
NF status
NRF
The status of a specific NF instance(s) (registered, suspended, undiscoverable) as defined per TS 29.510.
NF resource usage
OAM
The usage of assigned virtual resources currently in use for specific NF instance(s) (mean usage of virtual CPU, memory, disk) as defined in TS 28.552, clause 5.7.
NF resource configuration
OAM
The life cycle changes of specific NF resources (e.g., NF operational or interrupted during virtual/physical resources reconfiguration) as defined in TS 28.533, clause 5.2.

NOTE 1:
The OAM information can be used as a complement to NRF information for some or all of the following aspects: resources utilization, NRF information correlation, and alternative source of information if NRF information on load is not available.
NOTE 2:
NWDAF can request NRF for data related to NF instances, as described in TS 29.510.
NOTE 3:
NWDAF can correlate the NF resources configuration with NF resource usage for generating the analytics output.
If target NF type is UPF, the NWDAF may collect the information as listed in Table 6.5.2-2, in addition to information listed in Table 6.5.2-1.
Information
Source
Description

Traffic usage report
UPF
Report of user plane traffic in the UPF for the accumulated usage of network resources (see TS 29.244)

NOTE 4:
How NWDAF collects information in Table 6.5.2-2 is not defined in this Release of the specification.
Up
6.5.3  Output analyticsWord-p. 29
The NWDAF services as defined in the clause 7.2 and 7.3 are used to expose the analytics. NF load statistics information are defined in Table 6.5.3-1. NF load predictions information are defined in Table 6.5.3-2.
Information
Description

List of resource status (1..max)
List of observed load information for each NF instance along with the corresponding NF id / NF Set ID (as applicable)
> NF type
Type of the NF instance
> NF instance ID
Identification of the NF instance
> NF status
The availability status of the NF on the Analytics target period, expressed as a percentage of time per status value (registered, suspended, undiscoverable)
> NF resource usage
The average usage of assigned resources (CPU, memory, disk)
> NF load
The average load of the NF instance over the Analytics target period
> NF peak load (optional)
The maximum load of the NF instance over the Analytics target period

 
Information
Description

List of resource status (1..max)
List of predicted load information for each NF instance along with the corresponding NF id / NF Set ID (as applicable)
> NF type
Type of the NF instance
> NF instance ID
Identification of the NF instance
> NF status
The availability status of the NF on the Analytics target period, expressed as a percentage of time per status value (registered, suspended, undiscoverable)
> NF resource usage
The average usage of assigned resources (CPU, memory, disk)
> NF load
The average load of the NF instance over the Analytics target period
> NF peak load (optional)
The maximum load of the NF instance over the Analytics target period
> Confidence
Confidence of this prediction

NOTE:
The variations on per-instance NF load and resource usage could be influenced by the number of running NF instances in addition to the load itself.
The predictions are provided with a Validity Period, as defined in clause 6.1.3.
The number of resource status is limited by the maximum number of objects provided as input parameter.
Up
6.5.4  ProceduresWord-p. 30
The procedure depicted in Figure 6.5.4-1 allows a consumer NF to request analytics to NWDAF for NF load of various NF instances as defined in 6.5.1.
Up
Step 1.
The NF sends a request to the NWDAF for analytics for NF load for a specific NF, using either the Nnwdaf_AnalyticsInfo or Nnwdaf_AnalyticsSubscription service. The Analytics ID is set to NF load information, the target for analytics and the analytics filter are set according to clause 6.5.1. The NF can request statistics or predictions or both and can provide a time window.
Step 2-5.
If the request is authorized, and in order to provide the requested analytics, the NWDAF may need for each NF targeted instance to subscribe to OAM services to retrieve the target NF resource usage and NF resources configuration following steps captured in clause 6.2.3.2 for data collection from OAM. Steps 2-5 may be skipped when e.g. the NWDAF already has the requested analytics.
NOTE:
The call flow only shows a subscription/notification model for the simplicity, however both request-response and subscription-notification models should be supported.
Step 6a.
The NWDAF subscribes to changes on the load and status of NF instances registered in NRF and identified by their NF id from NRF using Nnrf_NFManagement_NFStatusSubscribe service operation for each NF instance.
Step 6b.
NRF notifies NWDAF of changes on the load and status of the requested NF instances by using Nnrf_NFManagement_NFStatusNotify service operation.
Step 7.
The NWDAF derives requested analytics.
Step 8.
The NWDAF provide requested NF load analytics to the NF along with the corresponding Validity Period, using either the Nnwdaf_AnalyticsInfo_Request response or Nnwdaf_AnalyticsSubscription_Subscribe response, depending on the service used in step 1.
Step 9-11.
If at step 1 the NF has subscribed to receive continuous reporting of NF load analytics, the NWDAF may generate new analytics and, when relevant according to the Analytics target period and Reporting Threshold, provide them along with the corresponding Validity Period to the NF upon reception of notification of new NF load information from OAM.
Up

Up   Top   ToC