Content for  TS 23.436  Word version:  19.4.0

The consumer (A-DCCF or ADAE server) requests that the A-ADRF subscribes to Data Producer for receiving notifications. The determination may be made based on configuration or information supplied by the data or analytics. As specified in Table 8.10.3.2-1, the request to the A-ADRF specifies the data and/or analytics to which the A-ADRF will subscribe. The request includes identity of the consumer, security credential(s) for authorization and verification, and may include Storage Handling information (e.g. an expiration time for how long the data or analytics should be stored), indicate if a notification alerting the consumer needs to be sent prior to data deletion from the A-ADRF, notification endpoint information for use by the A-ADRF to send notifications (implicit subscription) alerting the consumer that data is about to be deleted, as specified in Table 8.10.3.2-1.

The A-ADRF may, based on implementation, determine whether the same data and/or analytics is already stored or being stored, based on the information sent in step 1 by the consumer. Based on Storage Handling information, the A-ADRF determines the Storage Approach (e.g. lifetime for the stored data and whether consumer is notified prior to data deletion).

If the data and/or analytics is already stored and/or being stored in the A-ADRF, the A-ADRF sends data storage subscription response message to the consumer indicating that data and/or analytics is stored. The storage subscription response includes the Storage Approach, as specified in Table 8.10.3.3-1.

The A-ADRF subscribes to the data producer (e.g. A-DCCF, ADAE server) to receive notifications with data or analytics, providing its notification endpoint address and a notification correlation ID.

The data producer sends data or analytics notifications containing the notification correlation ID provided by the A-ADRF to notification endpoint address. The analytics or data notifications shall contain timestamp. The ADRF stores the notifications.

The consumer (e.g. ADAE server, A-DCCF) sends data storage request to the A-ADRF for storing data and/or analytics. The request message includes identity of the consumer, security credential(s) for authorization and verification, collected data with timestamp and/or analytics with timestamp, and may include Storage Handling information (e.g. a lifetime for how long the data or analytics should be stored), indicate if a notification alerting the consumer needs to be sent prior to data deletion from the A-ADRF, notification endpoint information for use by the A-ADRF to send notifications (implicit subscription) alerting the consumer that data is about to be deleted, as specified in Table 8.10.3.4-1.

Based on Storage Handling information (if available), the A-ADRF determines the Storage Approach (e.g. lifetime for storing data and whether consumer is notified prior to data deletion).

The A-ADRF stores the data and/or analytics sent by the consumer. The A-ADRF may, based on implementation, determine whether the same data and/or analytics is already stored or being stored based on the information sent in step 1 by the consumer and, if the same data and/or analytics is already stored or being stored in the A-ADRF, the A-ADRF decides to not store again the data and/or analytics sent by the consumer.

The ADRF sends data storage response message to the consumer indicating that data and/or analytics is stored, whether the A-ADRF determined at step 3 that data or analytics is already stored and the Storage Approach, as specified in Table 8.10.3.5-1.

A-ADRF determines to remove data or analytics previously stored by a consumer (e.g. ADAE server, A-DCCF), as the lifetime of the stored data or analytics has expired (according to the Storage Approach).

If indicated by the Storage Approach, the A-ADRF sends a data deletion notification alerting the consumer that data is about to be deleted. The data deletion notification message includes Data or Analytics Deletion Alert, as specified in Table 8.10.3.6-1.

The consumer (e.g. ADAE server, A-DCCF) determines that the data or analytics has to be deleted. The consumer sends data deletion request to the A-ADRF to remove specified data previously stored at the A-ADRF by the consumer. The request message includes the identifier(s) of the data set to be removed, as specified in Table 8.10.3.7-1.

The A-ADRF checks the relevant authorization for the request. If the authorization is successful, the A-ADRF deletes all copies of the stored data.

The A-ADRF sends data deletion response to the consumer. The response includes the deletion result (i.e. data deleted, data not found, data found but not deleted), as specified in Table 8.10.3.8-1.