Content for TS 23.288 Word version: 19.0.0

1… 4… 5… 5A… 6… 6.1.3 6.1.4… 6.1.4.4… 6.1.5… 6.1A… 6.1B… 6.1B.2.3… 6.1C 6.2… 6.2.3… 6.2.6… 6.2.6.2 6.2.6.3… 6.2.6.3.3 6.2.6.3.4 6.2.6.3.5 6.2.6.3.6… 6.2.7… 6.2.8… 6.2.9… 6.2.13… 6.2A… 6.2B… 6.2B.3 6.2B.4… 6.2C… 6.2D… 6.2E… 6.2F… 6.3… 6.4… 6.5… 6.6… 6.7… 6.7.3… 6.7.4… 6.7.5… 6.8… 6.9… 6.10… 6.11… 6.12… 6.13… 6.14… 6.16… 6.17… 6.18… 6.19… 6.20… 6.21… 7… 7.4… 7.7… 7.9… 8… 9… 10…

6.2B.3 Historical Data and Analytics Storage via Notifications
...

6.2B.3 Historical Data and Analytics Storage via Notifications p. 131

The procedure depicted in Figure 6.2B.3-1 is used by consumers (NWDAF, DCCF) to store received notifications in the ADRF. The consumer requests the ADRF to initiate a subscription for data and/or analytics. Data and/or analytics provided in notifications as a result of the subsequent subscription by the ADRF are stored in the ADRF.

The consumer may include in the subscription request the DataSetTag attribute defined in Table 6.2B-1.

Reproduction of 3GPP TS 23.288, Fig. 6.2B.3-1: Historical Data and Analytics Storage via Notifications

Figure 6.2B.3-1: Historical Data and Analytics Storage via Notifications

Step 0a-c.

NWDAF, DCCF or ADRF are configured with default operator storage policies as described in clause 5B.1.

Step 1a-d.

Based on provisioning or based on reception of a DataManagement subscription request (e.g. see clause 6.2.6.3.2), the DCCF or the NWDAF determines that notifications are to be stored in an ADRF. The subscription request may contain Storage Handling information with a requested ADRF storage lifetime and a request to be notified before data are deleted from the ADRF.

Step 2a-b.

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 and 6.2.6.3. The request to the ADRF specifies the data and/or analytics to which the ADRF will subscribe by invoking the Nadrf_DataManagement_StorageSubscriptionRequest service operation. The request may include the DataSetTag attribute which the data records are to be associated to when stored by ADRF. If the Storage Policy is not configured on the NWDAF or DCCF, the NWDAF or DCCF sends the Storage Handling Request to the ADRF. The NWDAF or DCCF may provide notification endpoint information to the ADRF for use by the ADRF to send notifications (implicit subscription) alerting the DCCF or NWDAF that data are about to be deleted (see step 12).

Step 3.

[Optional] The 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 2 by the consumer. If the DataSetTag attribute is included for data and/or analytics already stored or being stored, then ADRF associates the data records with such DataSetTag.

Step 3a-c.

[Optional] Based on Storage Handling information and Storage Policy, the ADRF, DCCF or NWDAF determines the Storage Approach (lifetime for storing data and whether consumer is notified prior to data deletion).

Step 4.

[Optional] If the data and/or analytics is already stored and/or being stored in the ADRF, the ADRF sends Nadrf_DataManagement_StorageSubscriptionRequest Response message to the consumer indicating that data and/or analytics is stored. The ADRF includes the Storage Approach if determined in step 3c.

Step 5a-b.

The DCCF or NWDAF sends a subscription response to the Data or Analytics Consumer. The response may contain the Storage Approach determined by the ADRF, NWDAF or DCCF.

Step 6a-b.

ADRF subscribes to the DCCF or the NWDAF to receive notifications, providing its notification endpoint address and a notification correlation ID.

Step 7.

The DCCF, the MFAF or the NWDAF sends Analytics or Data notifications containing the notification correlation ID provided by the ADRF to ADRF notification endpoint address. The Analytics or Data notifications shall contain timestamp. The ADRF stores the notifications.

Conditional on DCCF or NWDAF determining to stop storing data or analytics

Step 8a-b.

The DCCF or the NWDAF determines to stop storing notifications in the ADRF.

Step 9a-b.

The DCCF or the NWDAF requests that the ADRF unsubscribes to receive notifications.

Step 10a-b.

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 of notifications from the DCCF/MFAF or NWDAF to the ADRF are subsequently halted.

Conditional on ADRF Managing the Storage Approach

Step 11.

The ADRF determines that the lifetime of the stored data or analytics has expired (according to the Storage Approach).

Step 12.

If indicated by the Storage Approach, the ADRF sends a notification alerting the DCCF or NWDAF that data are about to be deleted.

Conditional if the Storage Appoach is based on Default Operator Policies provisioned on the NWDAF or DCCF (see step 3a-c and clause 5B.1)

Step 13.

The DCCF or NWDAF indicate in the response to the ADRF whether they will retrieve the Data or Analytics

Step 14.

The DCCF or NWDAF may retrieve the Data or Analytics from the ADRF

Conditional if the Storage Appoach is based on a Storage Handling Request received from the Data or Analytics Consumer (see step 3a-c and clause 5B.1)

Step 15a-b.

The NWDAF or DCCF sends a notification to the Data or Analytics Consumer alerting it that the data or analytics are about to be deleted.

Step 16a-b.

The Data or Analytics Consumer indicates in the response to the NWDAF or DCCF whether it will retrieve the Data or Analytics

Step 17.

The DCCF or NWDAF indicate in the response to the ADRF whether the consumer will retrieve the Data or Analytics

Step 18.

The Data or Analytics Consumer retrieves the stored data or analytics

Conditional on DCCF or NWDAF Managing the Storage Approach

Step 19a-b.

The NWDAF or DCCF determines that the lifetime of the stored data has expired (according to the Storage Approach).

Conditional if the Storage Appoach is based on Default Operator Policies provisioned on the NWDAF or DCCF (see step 3a-c and clause 5B.1)

Step 20.

The NWDAF or DCCF optionally retrieve the data or analytics from the ADRF

Step 21.

The NWDAF or DCCF request that the data or analytics be deleted from the ADRF

Conditional if the Storage Appoach is based on a Storage Handling Request received from the Data or Analytics Consumer (see step 3a-c and clause 5B.1)

Step 22a-b.

The NWDAF or DCCF sends a notification to the Data or Analytics Consumer alerting it that the data or analytics are about to be deleted.

Step 23a-b.

The Data or Analytics Consumer indicates in the response to the NWDAF or DCCF whether it will retrieve the Data or Analytics

Step 24.

The Data or Analytics Consumer retrieves the stored data or analytics

Step 25.

The NWDAF or DCCF request that the data or analytics be deleted from the ADRF

Step 26.

The ADRF deletes the data or analytics if:

the Storage Approach in the ADRF indicates alerting the consumer is not required prior to data or analytics deletion;
in Steps 13 or 17 the DCCF or NWDAF indicated data or analytics will not be retrieved prior to deletion;
data or analytics retrieval in steps 14 or 18 has completed or
A request to delete data or analytics was received in steps 21 or 25.

If the ADRF received a response from the NWDAF or DCCF in steps 14 or 17 indicating data or analytics will be retrieved but retrieval is not initiated before an adequate fixed time has elapsed, the ADRF may autonomously delete the data or analytics.