Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.288  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   4…   5…   5A…   6…   6.1.4…   6.1.4.4…   6.1A…   6.1B…   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.2A…   6.2B…   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…   7…   8…   9…   10…

 

6.2.6.2  Procedure for Data Collection from NWDAFp. 70

The procedure in Figure 6.2.6.2-1 is used by NWDAF service consumer to invoke the data management services at NWDAFs in order to retrieve runtime and historical data.
Reproduction of 3GPP TS 23.288, Fig. 6.2.6.2-1: Data Collection from NWDAF via Data Management Service
Up
Step 1.
NWDAF service consumer (e.g. NWDAF, DCCF) identifies that further data from an NWDAF is required in order to perform some operation related to Analytics ID. The triggers for further data collection are related to:
  1. the local policies of NWDAF or DCCF (e.g. preparation for future requests for Analytics ID as specified in clause 6.2.2.1);
  2. a request for analytics generation requiring data not available or not directly reachable via the NWDAF service consumer (e.g. out of the serving area);
  3. a request for model training;
  4. a request for data collection that NWDAF service consumer cannot provide by itself.
Step 2a.
NWDAF service consumer invokes Nnwdaf_DataManagement_Subscribe service from NWDAF to request a required data. The request comprises the Data Specification as well as Bulked Data Formatting and Processing as defined in clause 6.2.6.1, Notification Target Address (+ Notification Correlation ID).
When the required data is Event IDs, the NWDAF service consumer may include the Data Source, e.g. NF Instance (or NF Set) ID from which the data needs to be collected.
The NWDAF service consumer may include ADRF information indicating whether the data are to be stored in an ADRF, and optionally an ADRF ID.
The NWDAF service consumer may include ADRF ID or NWDAF ID (or ADRF Set ID or NWDAF Set ID) storing historical data (optional), directing NWDAF to the repository containing historical data.
The NWDAF checks if required data is related to a user, i.e. SUPI or GPSI, then, depending on local policy and regulations, as described in clause 6.2.9, the NWDAF checks or has checked the user consent by retrieving the user consent information from UDM using Nudm_SDM_Get including data type "User consent". If user consent is not granted, NWDAF sends a response to the NWDAF service consumer in step 2b, indicating that user consent for data collection was not granted, and the data collection for this SUPI or GPSI stops here. If the user consent is granted, the NWDAF can provide the required data to the NWDAF service consumer by performing the following steps 2b-7, and the NWDAF subscribes to UDM to notifications of changes on subscription data type "User consent" for this user using Nudm_SDM_Subscribe. When receiving the notification that user consent has been revoked, the NWDAF shall provide a Termination Request in Nnwdaf_DataManagement_Notify to request the NWDAF service consumer to cancel the subscription to the required data.
Step 2b.
Based on the received request, NWDAF creates a new bulked data for the requesting consumer. NWDAF sends Nnwdaf_DataManagement_Subscribe service response with a confirmation of successful request and the subscription correlation ID identifying the requested data.
Step 3.
NWDAF determines whether the request data is available at such NWDAF.
NWDAF maintains a local association of requested Event IDs or Analytics IDs to the list of triggered event subscription identifications from data sources to generate the requested data. Based on this local association, the NWDAF checks if the data to be collected is available at itself. If the data is available, NWDAF uses such data to generate the bulked data.
When data sources are NFs, the NWDAF discovers the proper NFs as defined in clause 6.2.2.1.
When the data sources are other NWDAFs, the NWDAF discovers the other NWDAFs as defined in clause 5.2.
When the data source is DCCF, the NWDAF discovers the proper DCCF as defined in clause 6.3.19 of TS 23.501.
Step 4a.
(Optional) If NWDAF receives a request for data that is not available or not reachable by such NWDAF (e.g. out of serving area), NWDAF determines the sources for the data that is not available, if the information has not been included in the subscription to the requested data.
Step 4b.
(Optional) NWDAF may trigger further data collection using any of the available mechanisms in clause 6.2.2 (e.g. if the data subscribed in step 2a partially matches data that are already being collected by the NWDAF from a data source and a modification of the subscription to the data source would satisfy both the existing data collection as well as the newly requested data) and clause 6.2.6 (e.g. recursively using data collection services from other needed NWDAFs, DCCFs, ADRFs, NFs).
NWDAF updates its local association of the mapping of the requested data (Event ID or Analytics ID) to the identification of the request/subscription for data collection from the further data sources.
Step 5.
Based on the properties of the received request and considering local bulked data instructions, NWDAF generates the requested data including the available or collected data (e.g. from other NWDAFs, DCCFs or ADRFs, NFs).
Step 6a.
If the fetch flag is set to true in step 2a, NWDAF waits until the requested data is ready and sends a Nnwdaf_DataManagement_Notify service message with the Notification Correlation ID, the Fetch Correlation ID and the target address where the data may be retrieved.
The requested data is ready when NWDAF generated the bulked data based on the available or collected data samples from the event notifications and the applicable bulked data processing and formatting instructions.
Step 6b.
If the fetch flag is set to false in step 2a, NWDAF uses the Nnwdaf_DataManagement_Notify service to send the Notification Correlation ID and requested data to the NWDAF service consumer.
NWDAF waits until the bulked data is generated or the bulked data deadline expires and uses Nnwdaf_DataManagement_Notify service with the indication of the outcome. In case of successful bulked data generation, NWDAF provides the bulked data via Nnwdaf_DataManagement_Notify service as defined in clause 6.2.6.1. In case of bulked data deadline expiration and unsuccessful bulked data generation, NWDAF provides the bulked data via Nnwdaf_DataManagement_Notify an indication of an unsuccessful bulked data generation with expired deadline. The Notification Target Address is used by the Nnwdaf_DataManagement_Notify service operation to deliver the message to the NWDAF service consumer.
Step 7(a.b).
Alternatively, when the fetch flag is set to true in Step 2a, the NWDAF service consumer shall fetch the required data from NWDAF via Nnwdaf_DataManagement_Fetch service operation. The NWDAF service consumer invokes the Nnwdaf_DataManagement_Fetch service operation with the input parameters including the Notification Correlation ID (+Fetch Correlation ID), that identifies the data to be fetched and receives a response with the requested data, as defined in clause 6.2.6.1.
Step 8.
The NWDAF service consumer uses the requested data for performing further processing. If the NWDAF service consumer is an NWDAF the requested data can be used for analytics generation or model training or for further exposing such data to other NWDAFs. If the NWDAF service consumer is a DCCF, the requested data can be used to be provided to a DCCF data consumer.
Step 9.
When the NWDAF service consumer determines that no more data is required or if receiving a Termination Request from the NWDAF, e.g. due to user consent revocation for the data collection related to a user, it unsubscribes to the requested data from NWDAF. If NWDAF had triggered further data collection in Step 3a and 3b, NWDAF also unsubscribe to all data sources.
Up

Up   Top   ToC