5.9 Analytics Data Repository procedures
29.5523GPP5G SystemNetwork Data Analytics signalling flowsRelease 17Stage 3TS
5.9.1 General
The Analytics Data Repository procedures allow the NF service consumers (e.g. NWDAF, DCCF or MFAF) to store, retrieve or delete collected data and analytics in the ADRF.
5.9.2 Historical Data and Analytics Storage/Retrieval/Deletion procedure
The procedure is used by an NF service consumer (e.g. NWDAF, DCCF or MFAF) to store, retrieve or delete historical data and/or analytics, i.e. data and/or analytics related to past time period that has been obtained by the consumer.
Figure 5.9.2-1: Historical Data and Analytics storage/deletion procedure
1. In order to store data or analytics, the NF service consumer invokes Nadrf_DataManagement_StorageRequest service operation by sending an HTTP POST request targeting the resource "ADRF Data Store Records" in clause 4.2.2.2 of 3GPP TS 29.575 [16]. The request shall include one of the analytics subscription notification(s), network exposure function event exposure subscription notification(s), application function event exposure subscription notification(s), access and mobility function event exposure subscription notification(s), session management function event exposure subscription notification(s), or unified data management event exposure subscription notification(s).
2. The ADRF stores the data or analytics sent by the consumer. The ADRF may, based on implementation, determines whether the same data or analytics is already stored or being stored based on the information sent in step 1 by the consumer and, if the data or analytics is already stored or being stored in the ADRF, the ADRF decides to not store again the data or analytics sent by the consumer.
3. If the data or analytics is stored, the ADRF sends Nadrf_DataManagement_StorageRequest Response message to the consumer with HTTP "201 Created" status code including a representation of the created record.
4. In order to retrieve the stored data or analytics from the ADRF, the NF service consumer shall invoke the Nadrf_DataManagement_RetrievalRequest service operation by sending an HTTP GET request targeting the resource "ADRF Data Store Records" as described in clause 4.2.2.5 of 3GPP TS 29.575 [16]. The request shall include fetch correlation identifier(s), or the query parameter value of subscription information. In addition, the start time and stop time during which requested data is collected or is to be collected shall be provided if the request has been performed based on subscription information.
5. If the requested data is found, the ADRF sends Nadrf_DataManagement_RetrievalRequest Response message to the consumer with HTTP "200 OK" status code including a representation of the matched record.
6. In order to deleted the specified data or analytics from the ADRF, the NF service consumer shall invoke the Nadrf_DataManagement_Delete service operation by sending an HTTP DELETE request targeting the resource "Individual ADRF Data Store Record" as described in clause 4.2.2.9 of 3GPP TS 29.575 [16] if the NF service consumer delete the resource including the transaction identifier, or by sending an HTTP POST request including the time window in which the data to be deleted was collected and data or analytics specification.
7. The ADRF deletes the specified stored data or analytics requested by the consumer.
8. If the deletion is successful processed, the ADRF sends Nadrf_DataManagement_Delete Response message to the consumer with HTTP "204 No Content" status code.
5.9.3 Historical Data and Analytics Storage via Notifications
The procedure is used by an NF service consumer (e.g. NWDAF, DCCF) to store received notifications in the ADRF.
Figure 5.9.3-1: Historical Data and Analytics storage/deletion procedure
1-2. Based on provisioning or based on reception of a DataManagement subscription request (e.g. see clause 5.5.3.1), the NF service consumer (e.g. DCCF or NWDAF) determines that notifications are to be stored in the ADRF.
3. The NF service consumer invokes Nadrf_DataManagement_StorageSubscriptionRequest service operation by sending an HTTP POST request in clause 4.2.2.3 of 3GPP TS 29.575 [16]. The request shall include one of the analytics subscription information, network exposure function event exposure subscription information, application function event exposure subscription information, access and mobility function event exposure subscription information, session management function event exposure subscription information, or unified data management event exposure subscription information, and one of the target identifiers, and may include the formatting instructions and/or processing instructions.
4. The ADRF may, based on implementation, determines whether the same data or analytics is already stored or being stored based on the information sent in step 3 by the consumer.
5. If the request is successfully processed and accepted, the ADRF sends Nadrf_DataManagement_StorageSubscriptionRequest Response message to the consumer with HTTP "200 OK " status code including a transaction reference identifier. If the data and/or analytics is already stored or being stored in the ADRF, the ADRF sends Nadrf_DataManagement_StorageSubscriptionRequest Response message to the consumer indicating that data or analytics is stored.
6a. ADRF invokes Ndccf_DataManagement_Subscribe service operation to subscribe to the DCCF to receive notifications by sending an HTTP POST request message targeting the resource "DCCF Analytics Subscriptions", the HTTP POST message shall include notification endpoint address and a notification correlation ID as defined in clause 5.1.6.2.2 of 3GPP TS 29.574 [15].
6b. ADRF invokes Nnwdaf_DataManagement_Subscribe service operation to subscribe to the NWDAF to receive notifications by sending an HTTP POST request message targeting the resource "NWDAF Data Management Subscriptions", the HTTP POST message shall include notification endpoint address and a notification correlation ID as defined in clause 4.4.2.2 of 3GPP TS 29.520 [5].
7a If the Subscription is successfully processed and accepted, the DCCF sends Ndccf_DataManagement_Subscribe Response message to the consumer with HTTP "201 Created" status code with the message body containing a representation of the created subscription.
7b If the Subscription is successfully processed and accepted, the NWDAF sends Nnwdaf_DataManagement_Subscribe Response message to the consumer with HTTP "201 Created" status code with the message body containing a representation of the created subscription.
8. The NF service consumer (e.g. DCCF, MFAF or NWDAF) sends Analytics or Data notifications containing the notification correlation ID provided by the ADRF to ADRF notification endpoint address when the historical analytics data are available.
If the NWDAF is the service consumer in step 7, the NWDAF invokes Nnwdaf_DataManagement_Notify service operation as defined in clause 4.4.2.4 of 3GPP TS 29.520 [5]. The ADRF stores the notifications and responses to the Nnwdaf_DataManagement_Notify service operation with HTTP "204 No Content" status code.
If the DCCF is used for data collection in step 7, the DCCF invokes Ndccf_DataManagement_Notify service operation as defined in clause 4.2.2.4 of 3GPP TS 29.574 [15]. The ADRF stores the notifications and responses to the Ndccf_DataManagement_Notify service operation with HTTP "204 No Content" status code.
If the Messaging Framework is used for data collection in step 7, the procedure defined in clause 5.5.3.2 is applicable.
9. The NF service consumer determines that notifications no longer need to be stored in the ADRF.
10. In order to request the ADRF to delete the specified data or analytics subscription, the NF service consumer shall invoke the Nadrf_DataManagement_StorageSubscriptionRemoval service operation by sending an HTTP POST request as described in clause 4.2.2.4 of 3GPP TS 29.575 [16], including the transaction reference identifier.
11. If the deletion is successful processed, the ADRF sends Nadrf_DataManagement_StorageSubscriptionRemoval Response message with HTTP "204 No Content" status code to the consumer.
12a. ADRF invokes Ndccf_DataManagement_Unsubscribe service operation to subscribe to the DCCF to receive notifications by sending an HTTP DELETE request message targeting the resource "Individual DCCF Analytics Subscription", the HTTP URI shall include identifier of the existing analytics subscription that is to be deleted as defined in clause 4.2.2.3.2 of 3GPP TS 29.574 [15].
12b. ADRF invokes Nnwdaf_DataManagement_Unsubscribe service operation to subscribe to the NWDAF to receive notifications by sending an HTTP DELETE request message targeting the resource "Individual NWDAF Data Management Subscription", the HTTP DELETE URI shall include identifier of the existing analytics subscription that is to be deleted as defined in clause 4.4.2.3.2 of 3GPP TS 29.520 [5].
13a If the removal of the corresponding subscription is successfully processed and accepted, the DCCF sends Ndccf_DataManagement_Unsubscribe Response message to the consumer with HTTP "204 No Content" status code.
13b If the removal of the corresponding subscription is successfully processed and accepted, the NWDAF sends Nnwdaf_DataManagement_Unsubscribe Response message to the consumer with HTTP "204 No Content" status code.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2021-04 |
CT3#115e |
TS skeleton for TS 29.552. |
0.0.0 |
||||
|
2021-04 |
CT3#115e |
Inclusion of documents agreed in CT3#115e: C3-212120, C3-212389 |
0.1.0 |
||||
|
2021-05 |
CT3#116e |
Inclusion of document agreed in CT3#116e: C3-213373 |
0.2.0 |
||||
|
2021-08 |
CT3#117e |
Inclusion of document agreed in CT3#117e: C3-214475, C3-214476, C3-214162 |
0.3.0 |
||||
|
2021-10 |
CT3#118e |
Inclusion of document agreed in CT3#118e: C3-215481, C3-215482, C3-215220, C3-215221. |
0.4.0 |
||||
|
2021-11 |
CT3#119e |
Inclusion of document agreed in CT3#119e: C3-216463,C3-216428,C3-216241,C3-216242,C3-216243,C3-216244,C3-216464 |
0.5.0 |
||||
|
2022-01 |
CT3#119bis-e |
Inclusion of document agreed in CT3#119bis-e: C3-220495, C3-220356, C3-220090, C3-220091, C3-220336, C3-220332, C3-220333, C3-220357, C3-220358, C3-220338. |
0.6.0 |
||||
|
2022-02 |
CT3#120e |
Inclusion of document agreed in CT3#120e: C3-221470, C3-221477, C3-221481, C3-221622, C3-221623, C3-221624, C3-221625, C3-221591, C3-221285, C3-221680, C3-221296, C3-221683, C3-221685. |
0.7.0 |
||||
|
2022-03 |
CT#95e |
CP-220158 |
Presentation to TSG CT for approval |
1.0.0 |
|||
|
2022-03 |
CT#95e |
CP-220158 |
Approved by TSG CT |
17.0.0 |
|||
|
2022-06 |
CT#96 |
CP-221132 |
0001 |
1 |
F |
Adding “Prepared analytics subscription transfer” signalling flows. |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221131 |
0002 |
1 |
F |
Correction Nnwdaf_MLModelProvision Service notification |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0003 |
1 |
B |
Update procedure for Analytics Exposure via DCCF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221130 |
0004 |
1 |
B |
Update Data Collection Reference Architecture |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221130 |
0005 |
1 |
B |
Update Analytics Exposure Reference Architecture |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221130 |
0006 |
1 |
B |
Resolve editor’s note in Analytics Exposure via DCCF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221130 |
0007 |
1 |
B |
Resolve editor’s note in Analytics Exposure via DCCF and MFAF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0010 |
1 |
F |
Update Analytics Exposure via DCCF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0011 |
1 |
F |
Update Analytics Exposure via DCCF and MFAF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221133 |
0012 |
1 |
F |
Update Analytics context transfer initiated by target NWDAF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221133 |
0013 |
1 |
F |
Update Analytics aggregation with provisioning of Area of Interest |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0014 |
1 |
F |
Update Data Collection via DCCF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0015 |
1 |
F |
Update Data Collection via Messaging Framework |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221132 |
0016 |
1 |
B |
SMCCE analytics supports Nnwdaf_EventsSubscription_Subscribe service operation |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221130 |
0017 |
|
B |
Remove the redundant description for discovery and selection of NWDAF containing AnLF |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221131 |
0018 |
1 |
B |
Introducing the Analytics Data Repository procedures |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221136 |
0020 |
1 |
F |
Update of transferring ML model during analytics transfer |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221134 |
0021 |
|
B |
Remove the ENs about when the DCCF sends the response to the consumer |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221135 |
0022 |
1 |
B |
Update the Analytics context transfer and Analytics Subscription transfer |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221135 |
0023 |
1 |
F |
Correction to Analytics context transfer initiated by target NWDAF |
17.1.0 |
|
2022-09 |
CT#97e |
CP-222103 |
0025 |
1 |
F |
Remove EN about using Nadrf_DataManagement_RetrievalRequest in DCCF procedures |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222102 |
0026 |
1 |
F |
Add NSACF to the data source list of the NWDAF |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222102 |
0027 |
1 |
F |
Support prepared analytics subscription transfer |
17.2.0 |
|
2022-09 |
CT#97e |
CP-222102 |
0030 |
1 |
F |
Update the content of Nadrf_DataManagement_RetrievalNotify |
17.2.0 |
|
2022-12 |
CT#98e |
CP-223173 |
0031 |
1 |
F |
User consent corrections in data collection procedures |
17.3.0 |
|
2022-12 |
CT#98e |
CP-223172 |
0037 |
F |
Update historical data and analytics storage via Notifications |
17.3.0 |
|