6.3.13 NWDAF discovery and selection

23.5013GPPRelease 18System architecture for the 5G System (5GS)TS

Multiple instances of NWDAF may be deployed in a network.

The NF consumers shall utilize the NRF to discover NWDAF instance(s) unless NWDAF information is available by other means, e.g. locally configured on NF consumers. NF consumers may make an additional query to UDM, when supported, as detailed below. The NWDAF selection function in NF consumers selects an NWDAF instance based on the available NWDAF instances.

The NRF may return one or more candidate NWDAF instance(s) and each candidate NWDAF instance (based on its registered profile) supports the Analytics ID with a time that is less than or equal to the Supported Analytics Delay.

The following factors may be considered by the NF consumer for NWDAF selection:

– S-NSSAI.

– Analytics ID(s).

– Supported service(s), possibly with their associated Analytics IDs.

– NWDAF Serving Area information, i.e. list of TAIs for which the NWDAF can provide analytics, trained ML models and/or data.

NOTE 1: If all services provided by one NWDAF do not support the same Analytics ID, the NWDAF registers the Analytics IDs of the services at the service level.

NOTE 2: Analytics ID(s) at service level take precedence over Analytics ID(s) at NF level.

NOTE 3: For discovery of NWDAF supporting Nnwdaf_AnalyticsSubscription or Nnwdaf_AnalyticsInfo services, the Analytics IDs at the NWDAF NF profile are used.

– (only when DCCF is hosted by NWDAF):

– NF type of the data source.

– NF Set ID of the data source.

NOTE 4: Can be used when the NWDAF determines that it needs to discover another NWDAF which is responsible for co-ordinating the collection of required data. The NWDAF does a new discovery for a target NWDAF via NRF using NF Set ID of the data source.

NOTE 5: For discovery of NWDAF supporting Nnwdaf_DataManagement service, at least the NWDAF Serving Area information from the NWDAF profile are used.

NOTE 6: The presence of NF type of data source or NF set ID of the data source denotes that the NWDAF can collect data from such NF Sets or NF Types.

– Supported Analytics Delay of the requested Analytics ID(s) (see clause 6.2.6.2).

In the case of multiple instances of NWDAFs deployment, following factors may also be considered:

– NWDAF Capabilities:

– Analytics aggregation capability.

– Analytics metadata provisioning capability.

Applicable when NF consumer cannot determine a suitable NWDAF instance based on NRF discovery response, and when NWDAF registration in UDM is supported, as defined in clause 5.2 of TS 23.288 [86]: NF consumers may query UDM (Nudm_UECM_Get service operation) for determining the ID of the NWDAF serving the UE. The following factors may be considered by NF consumers to select an NWDAF instance already serving a UE for an Analytics ID:

– SUPI.

– Analytics ID(s).

When selecting an NWDAF for ML model provisioning, the following additional factors may be considered by the NWDAF:

– The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2, TS 23.288 [86]) for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator,, if available.

Editor’s note: It is FFS if the Interoperability indicator is per Analytics ID.

When selecting an NWDAF that supports Federated Learning, the following additional factors may be considered by the NWDAF:

– Time Period of Interest.

– when selecting FL client:

– FL capability type as FL client.

– Data available by the FL client.

– when selecting FL server:

– FL capability type as FL server.

– The ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest (see clause 5.2 of TS 23.288 [86]) for the trained ML model(s) per Analytics ID(s), if available.

Editor’s note: Clarification for "Time Period of Interest" and "Data available by the FL client" is FFS.

Editor’s note: Whether the FL capability type is per analytics ID is FFS.