Section: 5.2.7.2.5 Nnrf_NFManagement_NFStatusSubscribe service operation
Content: Service Operation name: Nnrf_NFManagement_NFStatusSubscribe. Description: Consumer can subscribe to be notified of the following: - Newly registered NF along with its NF services. - Updated NF profile. - Deregistered NF. Inputs, Required: callback URI. Inputs, Optional: - 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[ System architecture for the 5G System (5GS) ]  [2]). - 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[ Architecture enhancements for 5G System (5GS) to support network data analytics services ]  [50]). - For NWDAF containing MTLF with Federated Learning (FL) capability, Consumer may include FL capability type (i.e. FL client, FL server, if available), Time Period of Interest, if available (see clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ]  [50]). Details about NWDAF discovery and selection are described in clause 6.3.13 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. - 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 NWDAF discovery and selection are described in clause 6.3.19 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. Outputs, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Validity Time. Outputs, Optional: None. NOTE: Alternatively, other means such as OA&M can also be used to subscribe for NF status.