Based on provisioning or based on reception of a DataManagement subscription request (e.g. see clause 188.8.131.52.2
), the DCCF or the NWDAF determines that notifications are to be stored in an ADRF.
The DCCF or the NWDAF determines the ADRF where data and/or analytics needs to be stored, and requests that the ADRF subscribes to receive notifications. The determination may be made based on configuration or information supplied by the data consumer as described in clauses 6.1.4
. The request to the ADRF specifies the data and/or analytics to which the ADRF will subscribe by invoking the Nadrf_DataManagement_StorageSubscriptionRequest
[Optional] The ADRF may, based on implementation, determines whether the same data and/or analytics is already stored or being stored, based on the information sent in step 2 by the consumer.
[Optional] If the data and/or analytics is already stored and/or being stored in the ADRF, the ADRF sends Nadrf_DataManagement_StorageRequest Response message to the consumer indicating that data and/or analytics is stored.
ADRF subscribes to the DCCF or the NWDAF to receive notifications, providing its notification endpoint address and a notification correlation ID.
The DCCF, the MFAF or the NWDAF send Analytics or Data notifications containing the notification correlation ID provided by the ADRF to ADRF notification endpoint address. The ADRF stores the notifications.
The DCCF or the NWDAF determines that notifications no longer need to be stored in the ADRF.
The DCCF or the NWDAF requests that the ADRF unsubscribes to receive notifications.
The ADRF sends a request to the DCCF or the NWDAF to unsubscribe to data notifications.
The NWDAF may interact with the Data Source, and the DCCF may interact with the Data Source and/or MFAF. Delivery notifications from the DCCF/MFAF or NWDAF to the ADRF are subsequently halted.