5.5 Data Collection

29.5523GPP5G SystemNetwork Data Analytics signalling flowsRelease 17Stage 3TS

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

5.5.1 Procedure for Data Collection from NFs

5.5.1.1 Data Collection from NFs

The procedure in Figure 5.5.1-1 is used by NWDAF to subscribe/unsubscribe at NFs in order to be notified for data collection on related event(s), using Event Exposure Services as listed in Table 6.2.2.1-1 defined in TS 23.288 [2] clause 6.2.2.

Figure 5.5.1.1-1: Event Exposure Subscribe/Unsubscribe for NFs

1a. If data is to be collected for a user, i.e. for a SUPI or GPSI, the user consent has not been checked by the data consumer, and local policy and regulations require to check user consent, the NWDAF invokes Nudm_SDM_Get service operation by sending an HTTP GET request targeting the resource "AccessAndMobilitySubscriptionData" to the UDM to request the data type "User consent" as described in clause 5.2.2.2 of 3GPP TS 29.503 [22]. Otherwise the procedure begins with step 3.

2a. The UDM responds to the Nudm_SDM_Get service operation. If the request is accepted, the response includes the requested data with "200 OK". In subsequent steps, the NWDAF excludes the SUPI or GPSI from requests to collect data for users for whom the user consent is not granted.

1b. For the users for which the user consent is granted, the NWDAF subscribes to notifications of changes of the user consent by invoking the Nudm_SDM_Subscribe service operation by sending an HTTP POST request targeting the resource "SdmSubscriptions" to the UDM as described in clause 5.2.2.3 of 3GPP TS 29.503 [22].

2b. The UDM responds to the Nudm_SDM_Subscribe service operation. If the request is accepted, the UDM responds with "201 Created".

3. In order to subscribe to notifications (or to modify subscriptions to notifications) of data events from the data source NF (e.g. UDM, AMF, SMF, NEF, AF), the NWDAF invokes the Nnf_EventExposure_Subscribe service operation by sending an HTTP POST (or PUT, for modification) request targeting the resource representing event exposure subscriptions of that NF, e.g. as described in clause 5.5.2.2 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.2 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.3 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.2 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.2 of 3GPP TS 29.517 [12] for the AF.

4. The NF responds to the Nnf_EventExposure_Subscribe service operation. Upon receipt of the HTTP POST request, if the subscription is accepted to be created, the NF responds to the NWDAF with "201 Created", and the URI of the created subscription is included in the Location header field.

5. If the NF observes the subscribed event(s), the NF invokes Nnf_EventExposure_Notify service operation to report the event(s) by sending an HTTP POST request, e.g. as described in clause 5.5.2.4 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.4 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.2 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.4 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.4 of 3GPP TS 29.517 [12] for the AF.

6. The NWDAF sends an HTTP "204 No Content" response to the NF.

7. In order to unsubscribe to the notifications of data events from the NWDAF, the NWDAF invokes Nnf_ EventExposure_Unsubscribe service operation by sending an HTTP DELETE request targeting the resource that represents the previously created individual event exposure subscription, e.g. as described in clause 5.5.2.3 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.3 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.4 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.3 of 3GPP TS 29.591 [11] for the NEF, clause 4.2.3 of 3GPP TS 29.517 [12] for the AF. The request includes the event subscriptionId of the existing subscription that is to be deleted.

8. The NF responds to the Nnf_EventExposure_Unsubscribe service operation. If the subscription deletion is accepted, the NF responds with "204 No Content".

5.5.2 Data collection profile registration

This procedure depicted in Figure 5.5.2-1 is used by NWDAF or ADRF to register/update a data collection profile to the DCCF during/after the procedure of data collection.

Figure 5.5.2-1: Procedure for the NWDAF or ADRF to register data profile to DCCF

1. An ADRF or NWDAF instance is collecting or has collected data directly, e.g. from collocated NF.

2. In order to register a data collection profile, the ADRF or NWDAF invokes the Ndccf_ContextManagement_Register service operation by sending an HTTP POST request targeting the resource "DCCF Data Collection Profiles" as described in clause 4.3.2.2 of 3GPP TS 29.574 [15].

3. The DCCF responds to the Ndccf_ContextManagement_Register service operation. Upon receipt of the HTTP POST request, if the data profile is accepted to be created, the DCCF responds to the ADRF or NWDAF with "201 Created", and the URI of the created profile is included in the Location header field.

4. In order to update a data collection profile, the Data Consumer invokes the Ndccf_ContextManagement_Update service operation by sending an HTTP PUT request targeting the resource "Individual DCCF Data Collection Profile" as described in clause 4.3.2.3 of 3GPP TS 29.574 [15].

5. The DCCF responds to the Ndccf_ContextManagement_Update service operation. Upon receipt of the HTTP PUT request, if the data profile is accepted to be updated, the DCCF responds to the ADRF or NWDAF with "200 OK" with a response body containing a representation of the updated data profile or "204 No Content".

6. To obtain historical data and if the data consumer is configured to collect data via the DCCF using the Ndccf_DataManagement_Subscribe service operation, the data consumer uses the procedures described in clause 5.5.3.

7. The ADRF or NWDAF requests to delete a registered data collection profile at the DCCF invoking the Ndccf_ContextManagement_Deregister service operation by sending a HTTP DELETE request targeting the "Individual DCCF Data Collection Profile" resource of the DCCF as described in clause 4.3.2.4 of 3GPP TS 29.574 [15].

8. The DCCF responds to the Ndccf_ContextManagement_Deregister service operation with HTTP "204 No Content" status code, if the data collection profile is successfully removed.

5.5.3 Procedure for Data Collection using DCCF

5.5.3.1 Data Collection via DCCF

The procedure depicted in Figure 5.5.3.1-1 is used by a data consumer (e.g. NWDAF) to obtain data and be notified of events via the DCCF using the Ndccf_DataManagement_Subscribe service operation. Whether the data consumer directly contacts the Data Source or goes via the DCCF is based on configuration of the data consumer.

Figure 5.5.3.1-1: Data Collection via DCCF

1. In order to subscribe to notification(s) of events exposure via the DCCF based on local configuration, the Data Consumer invokes the Ndccf_DataManagement_Subscribe service operation by sending an HTTP POST request targeting the resource "DCCF Data Subscriptions" as described in clause 4.2.2.2.4 of 3GPP TS 29.574 [15].

2a. If data is to be collected for a user, i.e. for a SUPI or GPSI, the user consent has not been checked by the data consumer, and local policy and regulations require to check user consent, the DCCF invokes the Nudm_SDM_Get service operation by sending an HTTP GET request targeting the resource "AccessAndMobilitySubscriptionData" at the UDM to request the data type "User consent" as described in clause 5.2.2.2 of 3GPP TS 29.503 [22]. Otherwise the procedure continues with step 4.

3a. The UDM responds to the Nudm_SDM_Get service operation. If the request is accepted, the response includes the requested data with "200 OK". In subsequent steps, the NWDAF excludes the SUPI or GPSI from requests to collect data for users for whom the user consent is not granted.

2b. For the users for which the user consent is granted, the DCCF subscribes to notifications of changes of the user consent by invoking the Nudm_SDM_Subscribe service operation by sending an HTTP POST request targeting the resource "SdmSubscriptions" at the UDM as described in clause 5.2.2.3 of 3GPP TS 29.503 [22].

3b. The UDM responds to the Nudm_SDM_Subscribe service operation. If the request is accepted, the UDM responds with "201 Created" status code.

4. The DCCF determines the NF type(s) and/or OAM to retrieve the data based on the Service Operation requested in step 1. If the NF instance or NF Set ID is not provided by the data consumer. The DCCF determines the NF instances that can provide data as described in TS 23.288 [2] clause 5A.2 and clause 6.2.2.2. If the consumer requested storage of data in an ADRF but the ADRF ID is not provided by the data consumer, or the collected data is to be stored in an ADRF according to configuration on the DCCF, the DCCF selects an ADRF to store the collected data.

The DCCF keeps track of the data actively being collected from the Data Sources it is coordinating. The NWDAF or ADRF may register the data collection profile (including the data collection related Service Operation, Analytics/Data Specification, NWDAF ID or ADRF ID) with the DCCF. The DCCF may then determine whether certain historical data may be available in the NWDAF or ADRF based on the data collection profile and the request time window.

If the historical data handling is not applicable or not supported, the DCCF shall proceed with step 5a and skip step 5b, step 6b, step 7b, step 5c, step 6c, and step 7c.

If the historical data is available in an ADRF, the DCCF shall proceed with step 5a and step 5b, and skip step 5c, step 6c, and step 7c.

If the historical data is available in an NWDAF, the DCCF shall proceed with step 5a and step 5c, and skip step 5b, step 6b, and step 7b.

5a. The DCCF shall determine whether the data requested in step 1 are already being collected.

If the data requested are already being collected by a data consumer, the DCCF adds the data consumer to the list of data consumers that are subscribed for these data.

If the DCCF determines that no subscriptions need to be created or modified (e.g. because all the data can be made available either via pre-existing subscriptions or because of the historical data handling) then step 6a and step 7a are skipped.

6a. If the data requested in step 1 are not yet available, the DCCF shall invoke the Nnf_EventExposure_Subscribe service operation by sending an HTTP POST request message request to the NF targeting the resource representing event exposure subscriptions to subscribe to a new event exposure subscription, e.g. as described in clause 5.5.2.2 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.2 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.3 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.2 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.2 of 3GPP TS 29.517 [12] for the AF.

Otherwise, if the requested data subscribed in step 1 partially matches data that is already being collected by the DCCF from an NF, and a modification of this subscription to the NF would satisfy both the existing data subscriptions as well as the newly requested data, the DCCF shall send a request to the individual event exposure subscription resource to update an existing event exposure subscription, e.g. as described in clause 5.5.2.5 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.2.3 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.3.3 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.2.3 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.2.3 of 3GPP TS 29.517 [12] for the AF.

7a. The NF responds to the Nnf_EventExposure_Subscribe service operation.

Upon receipt of an HTTP POST request, if the subscription is accepted to be created, the NF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

Upon receipt of an HTTP PUT request, if the subscription is accepted to be updated, the NF responds to the DCCF with "200 OK" or "204 No Content" status code.

5b. If the historical data handling is applicable, and the DCCF determines to retrieve data from the ADRF, the DCCF shall determine which ADRF instances might provide the data.

6b. In order to retrieve the historical data from the ADRF, the DCCF shall invoke the Nadrf_DataManagement_RetrievalSubscribe service operation by sending an HTTP POST request message targeting the resource "ADRF Data Retrieval Subscriptions" as described in clause 4.2.2.6 of 3GPP TS 29.575 [16].

7b. The ADRF responds to the Nadrf_DataManagement_RetrievalSubscribe service operation.

Upon receipt of the HTTP POST request, if the subscription is accepted to be created, the ADRF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

5c. If the historical data handling is applicable, and the DCCF determines to retrieve data from the NWDAF, the DCCF shall determine which NWDAF instances might provide the requested data.

6c. In order to retrieve the historical data from the NWDAF, the DCCF shall invoke the Nnwdaf_DataManagement_Subscribe service operation by sending an HTTP POST request message targeting the resource "NWDAF Data Management Subscriptions", as described in clause 4.4.2.2 of 3GPP TS 29.520 [5].

7c. The NWDAF responds to the Nnwdaf_DataManagement_Subscribe service operation.

Upon receipt of the HTTP POST request, if the subscription is accepted to be created, the NWDAF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

8. The DCCF responds to the Ndccf_DataManagement_Subscribe service operation with HTTP "204 No Content" status code.

9a. When the data are available, the NF invokes the Nnf_EventExposure_Notify service operation by sending an HTTP POST request message to notify the data events to the DCCF, e.g. as described in clause 5.5.2.4 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.4 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.2 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.4 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.4 of 3GPP TS 29.517 [12] for the AF.

10a. The DCCF responds to the Nnf_EventExposure_Notify service operation with HTTP "204 No Content" status code.

9b. When the historical data are available in the ADRF, the ADRF shall invoke the Nadrf_DataManagement_RetrievalNotify service operation by sending an HTTP POST request message to notify the historical data or Fetch Instructions to the DCCF as described in clause 4.2.2.8 of 3GPP TS 29.575 [16].

10b. The DCCF responds to the Nadrf_DataManagement_RetrievalNotify service operation with HTTP "204 No Content" status code.

9c. When the historical data are available in the NWDAF, the NWDAF shall invoke the Nnwdaf_DataManagement_Notify service operation by sending an HTTP POST request message to notify the historical data to the DCCF as described in clause 4.4.2.4 of 3GPP TS 29.520 [5].

10c. The DCCF responds to the Nnwdaf_DataManagement_Notify service operation with HTTP "204 No Content" status code.

11. If the DCCF is configured to deliver the data itself (and not via the MFAF), the DCCF invokes the Ndccf_DataManagement_Notify service operation by sending HTTP POST request message(s) to send the data to all notification endpoints indicated in step 1. Data sent to notification endpoints may be processed and formatted by the DCCF, so they conform to delivery requirements for each NF service consumer or notification endpoint.

NOTE: According to Formatting Instructions provided by the NF service consumer, multiple notifications from a NF can be combined in a single Ndccf_DataManagement_Notify so that many notifications from an NF result in fewer notifications (or one notification) to the Data Consumer. Alternatively, a notification can instruct the data notification endpoint to fetch the data from the DCCF.

12. The NF service consumer responds to the Ndccf_DataManagement_Notify service operation with HTTP "204 No Content" status code.

13. The Data Consumer invokes the Ndccf_DataManagement_Fetch service operation by sending an HTTP GET request message as described in clause 4.2.2.5 of 3GPP TS 29.574 [15] to fetch the data from the DCCF before an expiry time, if the fetch instruction was previously received via the NdccfDataManagement_Notify service operation in step 11.

14. The DCCF responds to the Ndccf_DataManagement_Fetch service operation with HTTP "200 OK" status code with the message body containing the data received earlier from the data source.

15. When the NF service consumer no longer needs the subscription to the requested data in step 1, it shall invoke the Ndccf_DataManagement_Unsubscribe service operation by sending an HTTP DELETE request message as described in clause 4.2.2.3.3 of 3GPP TS 29.574 [15]. The DCCF removes the NF service consumer from the list of NF service consumers that are subscribed for these data.

16. The DCCF responds to the Ndccf_DataManagement_Unsubscribe service operation with HTTP "204 No Content" status code, if the NF service consumer is successfully removed from the list of NF service consumers that are subscribed for these data.

17a. If there are no other NF service consumers subscribed to the data, the DCCF invokes the Nnf_EventExposure_Unsubscribe service operation by sending an HTTP DELETE request message to the Data Source, e.g. as described in clause 5.5.2.3 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.3 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.4 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.3 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.3 in 3GPP TS 29.517 [12] for the AF.

18a. The Data Source responds to the Nnf_EventExposure_Unsubscribe service operation with HTTP "204 No Content" status code, if the data event(s) subscription is successfully removed.

17b. If the DCCF determines that no other NF service consumers require the historical data from the ADRF, the DCCF invokes the Nadrf_DataManagement_RetrievalUnsubscribe service operation by sending an HTTP DELETE request message to the ADRF as described in clause 4.2.2.7 of 3GPP TS 29.575 [16].

18b. The ADRF responds to the Nadrf_DataManagement_RetrievalUnsubscribe service operation with HTTP "204 No Content" status code, if the data retrieval subscription is successfully removed.

17c. If DCCF determines that no other NF service consumers require the historical data from the NWDAF, the DCCF invokes the Nnwdaf_DataManagement_Unsubscribe service operation by sending an HTTP DELETE request message to the NWDAF as described in clause 4.4.2.3 of 3GPP TS 29.520 [5].

18c. The NWDAF responds to the Nnwdaf_DataManagement_Unsubscribe service operation with HTTP "204 No Content" status code, if the data subscription is successfully removed.

5.5.3.2 Data Collection via Messaging Framework

This procedure depicted in Figure 5.5.3.2-1 is used by a data consumer (e.g. NWDAF) to obtain data and be notified of events using the DCCF and a Messaging Framework. The 3GPP DCCF Adaptor (3da) Data Management service and 3GPP Consumer Adaptor (3ca) Data Management service of the Messaging Framework Adaptor Function (MFAF) are used to interact with the Messaging Framework. Whether the data consumer directly contacts the Data Source or goes via the DCCF is based on configuration.

Figure 5.5.3.2-1: Data Collection via DCCF and via Messaging Framework

1. In order to subscribe to notification(s) of events exposure via the DCCF based on local configuration, the Data Consumer invokes the Ndccf_DataManagement_Subscribe service operation by sending an HTTP POST request message targeting the resource "DCCF Data Subscriptions", as described in clause 4.2.2.2.4 of 3GPP TS 29.574 [15].

2a. If data is to be collected for a user, i.e. for a SUPI or GPSI, the user consent has not been checked by the data consumer, and local policy and regulations require to check user consent, the DCCF invokes Nudm_SDM_Get service operation by sending an HTTP GET request message targeting the resource "AccessAndMobilitySubscriptionData" at the UDM to request the data type "User consent" as described in clause 5.2.2.2 of 3GPP TS 29.503 [22]. Otherwise the procedure continues with step 4.

3a. The UDM responds to the Nudm_SDM_Get service operation. If the request is accepted, the response includes the requested data with "200 OK" status code. In subsequent steps, the NWDAF excludes the SUPI or GPSI from requests to collect data for users for whom the user consent is not granted.

2b. For the users for which the user consent is granted, the DCCF subscribes to notifications of changes of the user consent by invoking the Nudm_SDM_Subscribe service operation by sending an HTTP POST request message targeting the resource "SdmSubscriptions" at the UDM as described in clause 5.2.2.3 of 3GPP TS 29.503 [22].

3b. The UDM responds to the Nudm_SDM_Subscribe service operation. If the request is accepted, the UDM responds with "201 Created" status code.

4. If the DCCF is configured to perform data delivery via the MFAF, in order to create configuration of mapping data in the MFAF, the DCCF shall invoke the Nmfaf_3daDataManagement_Configure service operation by sending an HTTP POST request message targeting the resource "MFAF Configurations", as described in clause 4.2.2.2.2 of 3GPP TS 29.576 [17].

In order to update configuration of mapping data in the MFAF, the DCCF shall invoke the Nmfaf_3daDataManagement_Configure service operation by sending an HTTP PUT request message targeting the resource "Individual MFAF Configuration", as described in clause 4.2.2.2.3 of 3GPP TS 29.576 [17].

5. The MFAF responds to the Nmfaf_3daDataManagement_Configure service operation.

Upon receipt of the HTTP POST request message, if the configuration is accepted to be created, the MFAF responds to the DCCF with "201 Created" status code, and the URI of the created configuration is included in the Location header field.

Upon receipt of the HTTP PUT request message, if the configuration is accepted to be updated, the MFAF responds to the DCCF with "200 OK" or "204 No Content" status code.

6. The DCCF determines the NF type(s) and/or OAM to retrieve the data based on the Service Operation requested in step 1. If the NF instance or NF Set ID is not provided by the data consumer. the DCCF determines the NF instances that can provide data as described in TS 23.288 [2] clause 5A.2 and clause 6.2.2.2. If the consumer requested storage of data in an ADRF but the ADRF ID is not provided by the data consumer, or the collected data is to be stored in an ADRF according to configuration on the DCCF, the DCCF selects an ADRF to store the collected data.

If the historical data handling is not applicable or not supported, the DCCF shall proceed with step 7a, and skip step 7b, step 8b, step 9b, step 7c, step 8c, and step 9c.

If the historical data is available in an ADRF, the DCCF shall proceed with step 7a and step 7b, and skip step 7c, step 8c, and step 9c.

If the historical data is available in an NWDAF, the DCCF shall proceed with step 7a and step 7c, and skip step 7b, step 8b, and step 9b.

7a. The DCCF shall determine whether the data requested in step 1 are already being collected.

If the data requested are already being collected by a data consumer, the DCCF adds the data consumer to the list of data consumers that are subscribed for these data.

8a. If data requested in step 1 are not available yet, the DCCF shall invoke the Nnf_EventExposure_Subscribe service operation by sending an HTTP POST request message request to the NF targeting the resource representing event exposure subscriptions to subscribe to a new event exposure subscription, e.g. as described in clause 5.5.2.2 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.2 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.3 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.2 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.2 of 3GPP TS 29.517 [12] for the AF.

9a. The NF responds to the Nnf_EventExposure_Subscribe service operation.

Upon receipt of the HTTP POST request message, if the subscription is accepted to be created, the NF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

Upon receipt of the HTTP PUT request message, if the subscription is accepted to be updated, the NF responds to the DCCF with "200 OK" or "204 No Content" status code.

7b. If the historical data handling is applicable, and the DCCF determines to retrieve data from the ADRF, the DCCF shall determine which ADRF instances might provide the data.

8b. In order to retrieve the historical data from the ADRF, the DCCF shall invoke the Nadrf_DataManagement_RetrievalSubscribe service operation by sending an HTTP POST request message targeting the resource "ADRF Data Retrieval Subscriptions", as described in clause 4.2.2.6 of 3GPP TS 29.575 [16].

9b. The ADRF responds to the Nadrf_DataManagement_RetrievalSubscribe service operation.

Upon receipt of the HTTP POST request message, if the subscription is accepted to be created, the ADRF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

7c. If the historical data handling is applicable, and the DCCF determines to retrieve data from the NWDAF, the DCCF shall determine which NWDAF instances might provide the data.

8c. In order to retrieve the historical data from the NWDAF, the DCCF shall invoke the Nnwdaf_DataManagement_Subscribe service operation by sending an HTTP POST request message targeting the resource "NWDAF Data Management Subscriptions", as described in clause 4.4.2.2 of 3GPP TS 29.520 [5].

9c. The NWDAF responds to the Nnwdaf_DataManagement_Subscribe service operation.

Upon receipt of the HTTP POST request message, if the subscription is accepted to be created, the NWDAF responds to the DCCF with "201 Created" status code, and the URI of the created subscription is included in the Location header field.

10. The DCCF responds to the Ndccf_DataManagement_Subscribe service operation with HTTP "204 No Content" status code.

11a. When the data are available, the NF invokes the Nnf_EventExposure_Notify service operation by sending an HTTP POST request message to notify the data events to the MFAF, e.g. as described in clause 5.5.2.4 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.4 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.2 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.4 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.4 of 3GPP TS 29.517 [12] for the AF.

12a. The MFAF responds to the Nnf_EventExposure_Notify service operation with HTTP "204 No Content" status code.

11b. When the historical data are available in the ADRF, the ADRF shall invoke the Nadrf_DataManagement_RetrievalNotify service operation by sending an HTTP POST request message to notify the historical data or Fetch Instructions to the MFAF as described in clause 4.2.2.8 of 3GPP TS 29.575 [16].

12b. The MFAF responds to the Nadrf_DataManagement_RetrievalNotify service operation with HTTP "204 No Content" status code.

11c. When the historical data are available in the NWDAF, the NWDAF shall invoke the Nnwdaf_DataManagement_Notify service operation by sending an HTTP POST request message to notify the historical data to the MFAF as described in clause 4.4.2.4 of 3GPP TS 29.520 [5].

12c. The MFAF responds to the Nnwdaf_DataManagement_Notify service operation with HTTP "204 No Content" status code.

13. The MFAF invokes the Nmfaf_3caDataManagement_Notify service operation by sending HTTP POST request message(s) to send the data to all notification endpoints indicated in step 1. Data sent to notification endpoints may be processed and formatted by the MFAF so they conform to delivery requirements for each NF service consumer or notification endpoint.

NOTE: According to Formatting Instructions provided by the NF service consumer, multiple notifications from a NF can be combined in a single Nmfaf_3caDataManagement_Notify so that many notifications from an NF results in fewer notifications (or one notification) to the Data Consumer. Alternatively, a notification can instruct the data notification endpoint to fetch the data from the MFAF.

14. The NF service consumer responds to the Nmfaf_3caDataManagement_Notify service operation with HTTP "204 No Content" status code.

15. The Data Consumer invokes the Nmfaf_3caDataManagement_Fetch service operation by sending an HTTP GET request message as described in clause 4.2.2.5 of 3GPP TS 29.574 [15] to fetch the data from the DCCF before an expiry time, if the fetch instruction was received in Nmfaf_3caDataManagement_Notify service operation in step 13.

16. The MFAF responds to the Nmfaf_3caDataManagement_Fetch service operation with HTTP "200 OK" status code with the message body containing the NmfafResourceRecord data structure.

17. When the NF service consumer no longer needs the subscription to the requested data in step 1, it shall invoke the Ndccf_DataManagement_Unsubscribe service operation by sending an HTTP DELETE request message as described in clause 4.2.2.3.3 of 3GPP TS 29.574 [15]. The DCCF removes the NF service consumer from the list of NF service consumers that are subscribed for these data.

18. The DCCF responds to the Ndccf_DataManagement_Unsubscribe service operation with HTTP "204 No Content" status code, if the NF service consumer is successfully from the list of NF service consumers that are subscribed for these data.

19a. If there are no other NF service consumers subscribed to the data, the DCCF invokes the Nnf_EventExposure_Unsubscribe service operation by sending an HTTP DELETE request message to the Data Source, e.g. as described in clause 5.5.2.3 of 3GPP TS 29.503 [22] for the UDM, clause 5.3.2.3 of 3GPP TS 29.518 [18] for the AMF, clause 4.2.4 of 3GPP TS 29.508 [6] for the SMF, clause 4.2.2.3 of 3GPP TS 29.591 [11] for the NEF, or clause 4.2.3 in 3GPP TS 29.517 [12] for the AF.

20a. The Data Source responds to the Nnf_EventExposure_Unsubscribe service operation with HTTP "204 No Content" status code, if the data event(s) subscription is successfully removed.

19b. If DCCF determines that no other NF service consumers requiring the historical data from the ADRF, the DCCF may invoke the Nadrf_DataManagement_RetrievalUnsubscribe service operation by sending an HTTP DELETE request message to the ADRF as described in clause 4.2.2.7 of 3GPP TS 29.575 [16].

20b. The ADRF responds to the Nadrf_DataManagement_RetrievalUnsubscribe service operation with HTTP "204 No Content" status code, upon the data retrieval subscription is removed.

19c. If DCCF determines that no other NF service consumers require the historical data from the NWDAF, the DCCF may invoke the Nnwdaf_DataManagement_Unsubscribe service operation by sending an HTTP DELETE request message to the NWDAF as described in clause 4.4.2.3 of 3GPP TS 29.520 [5].

20c. The NWDAF responds to the Nnwdaf_DataManagement_Unsubscribe service operation with HTTP "204 No Content" status code, upon the data subscription is removed.

19d. When the DCCF determines that an NF service consumer mapping has to be removed from MFAF, the DCCF invokes the Nmfaf_3daDataManagement_Deconfigure service operation by sending an HTTP DELETE request message to the MFAF as described in clause 4.2.2.3 of 3GPP TS 29.576 [17].

20d. The MFAF responds to the Nmfaf_3daDataManagement_Deconfigure service operation with HTTP "204 No Content" status code, if the individual resource linked to the delete request is successfully removed.