Content for  TS 23.502  Word version:  19.1.0

This service enables one NF to manage its NF profile in NRF (i.e. register, update, deregister). This service also allows a consumer NF or SCP to subscribe in NRF to receive notifications regarding changes in the NF profile of other NFs.

Nnrf_NFManagement_NFRegister.

Registers the consumer NF in the NRF by providing the NF profile of the consumer NF to NRF and NRF marks the consumer NF available.

NF type, NF instance ID, FQDN or IP address of NF, Names of supported NF services (if applicable) and PLMN ID e.g. if NF needs to be discovered by other PLMNs/SNPNs.

Result indication.

None.

Nnrf_NFManagement_NFUpdate.

Provides the updated NF profile of NF consumer to NRF.

NF instance ID.

If replacing the full NF profile, the full NF profile shall be provided. If updating parts of the NF profile, the NF profile elements that needs to be updated shall be provided.

Result indication.

None.

Nnrf_NFManagement_NFDeregister

Inform the unavailability of NF consumer to NRF.

NF Instance ID, Reason indication.

None.

Result indication.

None.

Nnrf_NFManagement_NFStatusSubscribe.

Consumer can subscribe to be notified of the following:

callback URI.

• PLMN ID of the target NF/NF service, in the case of the subscription to the status of NF/NF service instance(s) in home PLMN from the serving PLMN, or PLMN ID and NID in the case of SNPN (see clause 5.30.2.9.3 of TS 23.501).
• Home Network Identifier: PLMN ID in the case of PLMN, PLMN ID + NID in the case of SNPN. Optionally, some NFs may additionally include a Home Network Identifier (including the identification of the CH with AAA Server or DCS with AAA Server) in the form of a realm e.g. in the case of access to an SNPN using credentials owned by CH with AAA Server or in the case of SNPN Onboarding using a DCS with AAA Server.
• Validity Time, in case to indicate the time instant after which the subscription becomes invalid.
• For updated NF profile subscription, conditions that trigger a notification from NRF. Includes monitored attributes in the NF profile (changes trigger a notification) or unmonitored attributes in the NF profile (changes do not trigger a notification)
• The following parameters are mutually exclusive:
  • NF Type (if NF status of a specific NF type is to be monitored).
  • NF Instance ID or NF Instance ID list (if NF status of a specific NF instance or a list of NF instance is to be monitored).
  • NF Service name (if NF status for NF which exposes a given NF service is to be monitored).
  • NF Set (if NF status of a set of NF Instances belonging to a certain NF Set is to be monitored).
  • NF Service Set (if the status of a set of NF Service Instances belonging to a certain NF Service Set is to be monitored).
  • NF Group (if the NF status of NF Instances identified by a NF (UDM, AUSF, PCF, BSF, CHF, HSS or UDR) Group Identity is to be monitored).
  • SCP Domain (if the status of NF or SCP instances belonging to a certain SCP domain is to be monitored).
  • For the UPF Management defined in clause 4.17.6: UPF Provisioning Information as defined in that clause.
  • For AMF, Consumer may include list of GUAMI(s), or AMF Set or AMF Region, or TAIs.
  • For SMF, Consumer may include list of TAIs.
  • S-NSSAI(s) and the associated NSI ID(s) (if available).
  • For NWDAF, Consumer may include:
    • Analytics ID(s) (possibly per service).
    • TAI(s).
    • NF Set ID, NF Type of NF data sources.
    • Analytics aggregation capability and/or Analytics metadata provisioning capability.
    • ML Model Accuracy checking capability.
    • Analytics Accuracy checking capability.
    • Roaming exchange capability.
    • For NWDAF containing MTLF, Consumer may also include the ML model Filter information parameters S-NSSAI(s) and Area(s) of Interest for the trained ML model(s) per Analytics ID(s) and ML Model Interoperability indicator per Analytics ID(s), if available (see clause 5.2 of TS 23.288).
    • For NWDAF containing MTLF with Federated Learning (FL) capability, Consumer may include FL capability type (i.e. FL client and/or FL server, if available), Time Period of Interest, if available (see clause 5.2 of TS 23.288).
    Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501.
  • For ADRF, Consumer may include:
    • Data and analytics storage and retrieval capability.
    • ML model storage and retrieval capability.
  • For NEF, Consumer may include Event ID(s) provided by AF.
  • For DCCF, Consumer may include:
    • TAI(s).
    • NF type of the NF data sources.
    • NF Set ID of the NF data sources.
    • Support for relocation of data subscription.
    Details about DCCF discovery and selection are described in clause 6.3.19 of TS 23.501.

When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Validity Time.

None.

Nnrf_NFManagement_NFStatusNotify.

NRF notifies subscribed consumers of the following:

Notification Event type; NF instance ID; for newly registered NF, NF profile; for updated NF, NF profile or NF profile changes.

None.

None.

None.

Nnrf_NFManagement_NFStatusUnsubscribe

Consumer can unsubscribe from being notified of newly registered NF along with its NF services and other events types described in the Nnrf_NFManagement_NFStatusSubscribe service operation (see clause 5.2.7.2.5).

Subscription Correlation ID.

None.

Operation execution result indication.

None.

This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF.

Nnrf_NFDiscovery_Request

provides the IP address or FQDN of the expected NF instance(s) and if present in NF profile, the Endpoint Address(es) of NF service instance(s) to the NF service consumer or SCP.

one or more target NF service Name(s), NF type of the target NF, NF type of the NF service consumer.

• One of the following:
  • A set of NF instance profiles; or
  • an indication that "indirect communication with delegated discovery with NF selection at target domain is requested"; or
  • an indication that "indirect communication without delegated discovery with NF selection at target domain is requested" together with a set of NF instance profiles;
• a validity period for the discovery result.

The set of NF instance profiles shall contain per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es) A set of NF instances, a validity period for the discovery result, containing per NF Instance: NF type, NF instance ID, FQDN or IP address(es) of the NF instance and if applicable, a list of services instances, where each service instance has a service name, a NF service instance ID and optionally Endpoint Address(es) Endpoint Address(es) may be a list of IP addresses or an FQDN for the NF service instance.

Per NF instance, other information in the NF profile listed in clause 6.2.6 of TS 23.501 related to the NF instance, such as:

The Nnrf_Bootstrapping service lets NF Service Consumers of the NRF know about the services endpoints it supports, the NRF Instance ID and NRF Set ID if the NRF is part of an NRF set, by using a version-independent URI endpoint that does not need to be discovered by using a Discovery service

Nnrf_Bootstrapping_Get

Get the NRF service instances, their addresses and associated data.

None.

None.

NRF service instances and their endpoint addresses.

NF Set ID, NFR instance ID, Oath2 requirement for authorization, NFR status.