9 MFAF Services

23.2883GPPArchitecture enhancements for 5G System (5GS) to support network data analytics servicesRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

9.1 General

Table 9.1-1 shows the MFAF services and MFAF service operations.

Table 9.1-1: NF services provided by MFAF

Service Name	Service Operations	Operation Semantics	Example Consumer(s)
Nmfaf_3daDataManagement	Configure	Request / Response	DCCF, NWDAF
	Deconfigure	Request / Response	DCCF, NWDAF
Nmfaf_3caDataManagement	Notify	Subscribe / Notify	NWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF
	Fetch	Request / Response	NWDAF, PCF, NSSF, AMF, SMF, NEF, AF, ADRF

9.2 Nmfaf_3daDataManagement service

9.2.1 General

Service Description: The consumer (e.g. DCCF) uses this service to instruct the MFAF to map data or analytics received by the MFAF to out-bound notification endpoints. Configuration of the MFAF by the consumer may include formatting and processing instructions for each notification endpoint as described in clause 5A.4. The sending of historical data or run-time data may be configured/deconfigured using this service.

When the MFAF is configured by the consumer NF, the MFAF provides a Transaction Reference Id. The Consumer NF may use the Transaction Reference Id in subsequent transactions to modify or remove (deconfigure) the sending of data to consumers.

9.2.2 Nmfaf_3daDataManagement_Configure service operation

Service operation name: Nmfaf_3daDataManagement_Configure

Description: The consumer configures or reconfigures the MFAF to map data or analytics received by the MFAF to out-bound notification endpoints and to format and process the out-bound data or analytics.

Inputs, Required: Data Consumer or Analytics Consumer Information.

"Data Consumer or Analytics Consumer Information" contains for each notification endpoint, the consumer provided Notification Target Address (+ Analytics Consumer Notification Correlation ID) or other endpoint addresses if provisioned on the DCCF to be used by the MFAF when sending notifications.

Inputs, Optional: Formatting Instructions, Processing Instructions, MFAF Notification Information, Transaction Reference Id, ADRF ID.

"MFAF Notification Information" is used to identify Event Notifications received from a Data Source and comprises the MFAF Notification Target Address (+ MFAF Notification Correlation ID). If a Data Source is already supplying the data to the MFAF, the MFAF Notification Information previously provided by the MFAF and used by the DCCF to obtain data from a Data Source is provided as an Input. If a new subscription to a Data Source is needed, the MFAF Notification Information is not specified as an Input and the MFAF provides Notification Information as an output. The MFAF Notification Information may subsequently be used by the DCCF when subscribing to a Data Source. "ADRF ID" is used to identify the ADRF when DCCF requests that the Messaging Framework to store historical data and analytics in the ADRF via Nadrf_DataManagement_StorageRequest. When a Notification Correlation ID is provided, MFAF shall use the Nmfaf_3caDataManagement_Notify service with the notification correlation ID to send the data or analytics to the ADRF.

Outputs Required: Operation execution result indication.

Outputs, Optional: MFAF Notification Information, Transaction Reference Id.

9.2.3 Nmfaf_3daDataManagement_Deconfigure service operation

Service operation name: Nmfaf_3daDataManagement_Deconfigure

Description: Description: The consumer configures the MFAF to stop mapping data or analytics received by the MFAF to one or more out-bound notification endpoints.

Inputs, Required: Data Consumer or Analytics Consumer Information, Transaction Reference Id.

Inputs, Optional: None.

Outputs, Required: Operation execution result indication.

Outputs, Optional: None.

9.3 Nmfaf_3caDataManagement service

9.3.1 General

Service Description: This service is used to supply data or analytics from the MFAF to notification endpoints. Notifications may contain data or analytics, or an indication of availability of data or analytics.

9.3.2 Nmfaf_3caDataManagement_Notify service operation

Service operation name: Nmfaf_3caDataManagement_Notify

Description: Provides data or analytics or notification of availability of data or analytics to notification endpoints.

Inputs, Required: Notification Correlation Information.

Inputs, Optional: Requested Data with timestamp or Analytics with timestamp, Fetch Instructions.

NOTE 1: If the MFAF has received the notifications from another source (e.g. NWDAF) without a timestamp, then the MFAF adds itself a timestamp based on the time it received the notification.

Fetch Instructions indicate whether the data or analytics are to be fetched by the Consumer. If the data or analytics are to be fetched, the fetch instructions include an address from which the data may be fetched, one or more Fetch Correlation IDs and a deadline to fetch the data (Fetch Deadline).

NOTE 2: Data or Analytics provided in notifications can be processed and formatted according to the Processing and Formatting Instructions provided by the Consumer.

Outputs, Required: None.

Outputs, Optional: None.

9.3.3 Nmfaf_3caDataManagement_Fetch service operation

Service operation name: Nmfaf_3caDataManagement_Fetch

Description: Consumer retrieves from the MFAF, data or analytics (which is regarded as a kind of data) as indicated by Nmfaf_3caDataManagement_Notify Fetch Instructions.

Inputs, Required: Set of Fetch Correlation ID(s).

Inputs, Optional: None.

Outputs, Required: Operation execution result indication.

Outputs, Optional: Requested Data or Analytics.

NOTE: Data or Analytics provided in notifications can be processed and formatted according to the Processing and Formatting Instructions provided by the Consumer.