6.2.6.2 NF profile

NF profile of NF instance maintained in an NRF includes the following information:

• NF instance ID.
• NF type.
• PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN.
• Network Slice related Identifier(s) e.g. S-NSSAI, NSI ID.
• FQDN or IP address of NF.
• NF capacity information.
• NF priority information.

NOTE 1: This parameter is used for AMF selection, if applicable, as specified in clause 6.3.5. See clause 6.1.6.2.2 of TS 29.510 [58] for its detailed use.

• NF Set ID.
• NF Service Set ID of the NF service instance.
• NF Specific Service authorization information.
• if applicable, Names of supported services.
• Endpoint Address(es) of instance(s) of each supported service.
• Identification of stored data/information.

NOTE 2: This is only applicable for a UDR profile. See applicable input parameters for Nnrf_NFManagement_NFRegister service operation in clause 5.2.7.2.2 of TS 23.502 [3]. This information applicability to other NF profiles is implementation specific.

• Other service parameter, e.g. DNN or DNN list, notification endpoint for each type of notification that the NF service is interested in receiving.
• Location information or serving scope for the NF instance.

NOTE 3: This information is operator specific. Examples of such information can be geographical location, data centre.

• TAI(s).
• NF load information.
• Routing Indicator, Home Network Public Key identifier, for UDM and AUSF.
• For UDM, AUSF and NSSAAF in the case of access to an SNPN using credentials owned by a Credentials Holder with AAA Server, identification of Credentials Holder (i.e. the realm of the Network Specific Identifier based SUPI).
• For UDM and AUSF and if UDM/AUSF is used for access to an SNPN using credentials owned by a Credentials Holder, identification of Credentials Holder (i.e. the realm if Network Specific Identifier based SUPI is used or the MCC and MNC if IMSI based SUPI is used); see clause 5.30.2.1.
• For AUSF and NSSAAF in the case of SNPN Onboarding using a DCS with AAA server, identification of DCS (i.e. the realm of the Network Specific Identifier based SUPI).
• For UDM and AUSF and if UDM/AUSF is used as DCS in the case of SNPN Onboarding, identification of DCS (i.e. the realm if Network Specific Identifier based SUPI, or the MCC and MNC if IMSI based SUPI).
• One or more GUAMI(s), in the case of AMF.
• For the UPF, see clause 5.2.7.2.2 of TS 23.502 [3].
• UDM Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of internal group identifiers, range(s) of external group identifiers for UDM.
• UDR Group ID, range(s) of SUPIs, range(s) of GPSIs, range(s) of external group identifiers for UDR.
• AUSF Group ID, range(s) of SUPIs for AUSF.
• PCF Group ID, range(s) of SUPIs for PCF.
• HSS Group ID, set(s) of IMPIs, set(s) of IMPU, set(s) of IMSIs, set(s) of PSIs, set(s) of MSISDN for HSS.
• CHF Group ID(s), range(s) of SUPIs, range(s) of GPSI(s), list of PLMN(s) for CHF, as defined in clause 6.1 of TS 32.290 [67] and TS 29.510 [58].
• For NWDAF, the following information are supported:
• Analytics ID(s) (possibly per service).
• NWDAF Serving Area information (refer to clause 6.3.13).
• Supported Analytics Delay per Analytics ID (if available).
• NF types of the NF data sources, NF Set IDs of the NF data sources, if available.
• Analytics aggregation capability (if available).
• Analytics metadata provisioning capability (if available).
• ML model Filter information parameters include S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s).
• ML Model Interoperability indicator (if available) per Analytics ID(s).
• HFL capability information per analytics ID including FL capability type (i.e. HFL server and/or HFL client), if available).
• VFL capability information per analytics ID including VFL capability type (i.e. VFL server, VFL client), if available.
• VFL client aggregation capability per analytics ID, if available.
• Time interval supporting HFL (if available).
• Time interval supporting VFL (if available).
• VFL interoperability indicator per Analytics ID (if available).
• Feature ID(s) per VFL interoperability indicator (if available).
• Accuracy checking capability for ML model accuracy monitoring or Analytics Accuracy Monitoring (if available).
• Roaming exchange capability (if available).
• LMF-based AI/ML positioning indication (indicating that the NWDAF containing MTLF supports ML model training for LMF-based AI/ML positioning).

NOTE 4: The NWDAF's Serving Area information is common to all its supported Analytics IDs.

NOTE 5: The Analytics IDs supported by the NWDAF may be associated with a Supported Analytics Delay i.e. the Analytics report can be generated with a time (including data collection delay and inference delay) in less than or equal to the Supported Analytics Delay.

NOTE 6: The determination of Supported Analytics Delay and how the NWDAF avoid updating its Supported Analytics Delay in NRF frequently is NWDAF implementation specific.

• For trusted AF as VFL server or VFL client, the following information is supported:
• Analytics ID(s).
• VFL capability information per analytics ID including VFL capability type (i.e. VFL client and/or VFL server).
• VFL interoperability indicator per Analytics ID, if AF acts as VFL client.
• Optionally, the time interval supporting VFL.
• Optionally supported feature ID(s) per VFL interoperability indicator.
• For NEFs serving untrusted AFs:
• Event ID(s) supported by AFs.
• For VFL, Analytics ID(s) supported by AFs.
• VFL capability information per analytics ID including VFL capability type (i.e. VFL client and/or VFL server), supported by AFs.
• VFL interoperability indicator per Analytics ID, if AF acts as VFL client.
• For VFL, optionally the time interval supporting VFL.
• For VFL, optionally feature ID(s) per VFL interoperability indicator supported by AFs.
• Event Exposure service supported event ID(s) by UPF.
• Application Identifier(s) supported by AFs, in the case of NEF.
• Range(s) of External Identifiers, or range(s) of External Group Identifiers, or the domain names served by the NEF, in the case of NEF.

NOTE 7: This is applicable when NEF exposes AF information for analytics purpose as detailed in TS 23.288 [86].

NOTE 8: It is expected service authorization information is usually provided by OA&M system and it can also be included in the NF profile in the case that e.g. an NF instance has an exceptional service authorization information.

NOTE 9: The NRF may store a mapping between UDM Group ID and SUPI(s), UDR Group ID and SUPI(s), AUSF Group ID and SUPI(s) and PCF Group ID and SUPI(s), to enable discovery of UDM, UDR, AUSF and PCF using SUPI, SUPI ranges as specified in clause 6.3 or interact with UDR to resolve the UDM Group ID/UDR Group ID/AUSF Group ID/PCF Group ID based on UE identity, e.g. SUPI (see clause 6.3.1 for details).

• IP domain list as described in clause 6.1.6.2.21 of TS 29.510 [58], Range(s) of (UE) IPv4 addresses or Range(s) of (UE) IPv6 prefixes, Range(s) of SUPIs or Range(s) of GPSIs or a BSF Group ID, in the case of BSF.
• SCP Domain the NF belongs to.
• DCCF Serving Area information, NF types of the data sources, NF Set IDs of the data sources, if available, in the case of DCCF.
• Supported DNAI list, in the case of SMF.
• Supported Local Offloading Management and the corresponding service area, in the case of SMF.
• For SNPN, capability to support SNPN Onboarding in the case of AMF and capability to support User Plane Remote Provisioning in the case of SMF.
• IP address range, DNAI for UPF.
• Supported operator configurable UPF capabilities (as described in clause 5.8.2.21) in the case of UPF.
• Supported DNS security protocols, in the case of EASDF.
• Additional V2X related NF profile parameters are defined in TS 23.287 [121].
• Additional ProSe related NF profile parameters are defined in TS 23.304 [128].
• Additional MBS related NF profile parameters are defined in TS 23.247 [129].
• Additional UAS related NF profile parameters are defined in TS 23.256 [136].
• Additional Ranging based services and Sidelink Positioning related NF profile parameters are defined in TS 23.586 [180].
• For additional information in PCF profile, see clause 5.2.7.2.2 of TS 23.502 [3].