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.7  Data Collection with Event Muting Mechanism |R17|p. 84

6.2.7.1  Generalp. 84

Additional mechanisms to limit signalling between Event Producer NF (e.g. AMF, SMF) and Event Consumer NF (NWDAF, DCCF) are provided, with the Event Provider NFs enhanced with the optional capability of muting the notification of the events while storing for a limited time and limited size the events until the Event Consumer NF retrieves such mute stored events.

6.2.7.2  Procedure for Data Collection with Event Muting Mechanismp. 84

The mute storage of events mechanism in the DCCF, the NWDAF, or NFs (if configured to support event muting mechanism) reuses the Event Reporting Information field of Event Exposure Framework to include the following flags:
  • Deactivate notification flag: The event consumer NF includes in the subscription to an event ID the deactivation flag to indicate to the event provider NF to collect, store the requested events but halt the notification to the consumer. The number of stored events may be limited based on NF configuration; when this number is reached, the NF continues to store new events and deletes the oldest events.
  • Retrieval notification flag: The event consumer NF includes in an event subscription modification request the subscription identification and the retrieval notification flag to indicate to the event producer NF to send the past collected events not already sent to this consumer NF. After sending the past collected events the event producer continues to store events without sending notifications to the event consumer.
Using the event muting mechanism NWDAF, DCCF can subscribe to events from NFs such as AMF and SMF (if configured to support event muting mechanism), to avoid constant notifications and retrieve the mute stored events when it requires.
The procedure in Figure 6.2.7.2-1 is used by Event Consumer NF to control the frequency of data collection from Event Producer NFs (except DCCF and NWDAF) via Event Exposure. For data collection via DCCF and NWDAF, the consumer may mute the notifications by using the formatting instructions as specified in clause 5A.4 or the Bulked Data Formatting and Processing parameters as specified in clause 6.2.6.1.
Reproduction of 3GPP TS 23.288, Fig. 6.2.7.2-1: Procedure for muting event notification
Up
Step 0a.
The Event Consumer NF, such as NWDAF or DCCF, is configured with local policies that are used to determine when the muted storage of events is triggered.
Step 0b.
The Event Consumer NF, such as NWDAF or DCCF, may receive a request with the Formatting and Processing parameters indicating Event Clubbing. The DCCF or NWDAF may utilize event muting when collecting data from NFs (if configured to support event muting mechanism).
Step 1.
The Event Consumer NF, DCCF or NWDAF subscribes for a (set of) Event ID(s) by invoking the Nnf_EventExposure_Subscribe service operation including in event reporting information the deactivate notification flag.
If the Event Producer NF supports the deactivate notification flag, the Event Producer NF sends a response back including the Subscription Correlation ID and an indication of successful deactivation of notifications. The Event Consumer NF may request the Event Producer NF to store data related to Event ID(s), or aggregated data related to UE(s).
If the Event Producer NF does not support the deactivate notification flag, the Event Producer NF sends a response back including an indication of failure. In this case, the Event Consumer NF re-sends the subscription request without including in the event reporting information the deactivate notification flag.
Step 2.
Based on the request from Event Consumer NF, DCCF or NWDAF, the Event Producer NF triggers a window of event collection for the Event Consumer NF, DCCF or NWDAF subscription with the indication of "deactivate notification flag". The Event Producer NF keeps the association between the Event ID, Subscription Correlation ID (which identifies the consumer of the event), subscriber information (e.g. notification target information) and the status of the transaction between the Event Consumer NF, DCCF or NWDAF and the Event Producer as "collecting events / non-notification".
Step 3.
Based on local policies or based on the Notification Time Window indicated in the Formatting and Processing parameters of the received request in step 0b, the Event Consumer NF, DCCF or NWDAF decides when to request the muted stored events from the Event Producer NF.
Step 4.
Event Consumer NF invokes the Nnf_EventExposure_Subscribe service operation from the Event Producer NF including, the Event ID, the Subscription Correlation ID, and the retrieval notification flag. These parameters denote the identification of the transaction required by the Event Consumer NF, i.e. retrieve muted stored events for a subscribed Event ID and trigger a new time window of muted stored event generation without notification.
Step 5.
Event Producer NF based on the parameters received in the request from Event Consumer NF verifies whether there is a subscription to the requested Event ID with a deactivate notification flag. In positive case, Event Producer NF identifies and sends the past collected events muted during the period between the received retrieval notification flag and the last deactivate flag received from the Event consumer NF for the Event ID, the Subscription Correlation ID.
Step 6.
The Event Producer NF checks whether overall event reporting information (e.g. the maximum time window for the subscription of such Event ID) has expired. If yes, it does not trigger another round of event muted storage and deactivates the subscription. If not expired, the Event Producer NF trigger another time window for muted stored of produced events, sets back the deactivated notification flag for the Event ID and Subscription Correlation ID.
If the Event Consumer NF wants to change an existing subscription to an Event Producer NF using muted stored events into a regular notification of events, it shall invoke Nnf_EventExposure_Subscribe service operation from Event Producer NF without deactivate notification flag.
Up

6.2.8  Data Collection from the UE Application |R17|p. 86

6.2.8.1  Generalp. 86

The NWDAF may interact with an AF to collect data from UE Application(s) as an input for analytics generation and ML model training. The AF can be in the MNO domain or an AF external to MNO domain. The data collection request from NWDAF may trigger the AF to collect data from the UE Application. The AF in this clause is referred as the Data Collection AF which is described in TS 26.531.
The UE Application establishes a connection to the AF in the MNO domain or external to MNO domain over user plane via a PDU session. The AF communicates with the UE Application and collects data from UE Application.
For both an AF in trusted domain and an AF in untrusted domain (which supports to collect data from a UE Application), the SLA between the operator and the Application Service Provider (i.e. ASP) determines per Application ID in use by the ASP:
  • The AF for the UE Application to connect to (e.g. based on an FQDN).
  • The information that the UE Application shares with the AF, subject to user consent.
  • Possible Data Anonymization, Aggregation or Normalization algorithms (if used).
  • The authentication information that enable the AF to verify the authenticity of the UE's Application that provides data.
The AF (which supports the data collection) is configured based on the SLA above.
A UE Application (which supports to providing data to an AF) is configured by the ASP with the Application ID to use in the communication with the AF and then the UE Application is configured per Application ID with the following information:
  • The address of the AF to contact.
  • The parameters that the UE Application is authorized to provide to the AF.
  • The authentication information to enable the UE Application to verify the authenticity of the AF that requests data.
The Target for Event Reporting in the Naf_EventExposure request may be set to:
  • an external UE ID (i.e. GPSI) or an external Group ID, in case the AF is located in the untrusted domain;
  • a SUPI or an internal Group ID, in case the AF is located within the trusted domain.
The GPSI may be an External Identifier for individual UE as defined in TS 23.501 that includes the domain name. This domain name and the Application ID configured in the UE Application are different from each other.
Up

6.2.8.2  Procedure for data collection from the UE Applicationp. 87

6.2.8.2.1  Connection establishment between UE Application and AFp. 87
The UE Application receives the data collection configuration from ASP. The configuration information is as described in clause 6.2.8.1.
The UE Application establishes a user plane connection to the AF. Data collection procedure from the UE Application is performed via the user plane connection.
Both direct data collection procedure (from the UE Application to the AF, either in trusted domain or untrusted domain) and indirect data collection procedure (from the UE Application to the Application server and from the Application server to the AF) shall be supported. The data collection procedure is described in TS 26.531.
The AF retrieves and stores the IP address of the UE (in the PDU session used) in order to request data collection from the UE Application. The UE IP address is used by the AF to identify the user plane connection.
The UE Application provides the Application ID configured in the UE Application to the AF as described in TS 26.531.
Up
6.2.8.2.2  AF registration and discoveryp. 88
The AF registers its available NF profile to the NRF. The AF in trusted domain registers to the NRF by using the Nnrf_NFManagement service that is defined in clause 5.2.7.2 of TS 23.502. The AF in untrusted domain registers the available NF profile to the NRF via the NEF as described in clause 6.2.2.3.
The AF discovery and selection is described in TS 23.502.
Up
6.2.8.2.3  Data Collection Procedure from UEp. 88
Reproduction of 3GPP TS 23.288, Fig. 6.2.8.2.3-1: Data Collection Procedure from UE
Up
Step 1.
An NF subscribes to analytics from the NWDAF as described in clause 6.1.1.1, that includes Analytics ID, Analytics Filter Information including e.g. AoI, Internal Application ID(s) and Target of Analytics Reporting. NWDAF may also initiate the data collection prior to this subscription.
Step 2.
NWDAF discovers the AF that provides data collection (based on the AF profiles registered in NRF) as described in TS 23.502.
Step 3a is used for the AF in trusted domain while step 3b is used for the AF in untrusted domain.
Step 3a.
NWDAF subscribes to the AF in trusted domain for UE data collection (i.e. input data from UE for analytics), by using Naf_EventExposure_Subscribe as defined in clause 5.2.19.2 of TS 23.502. The NWDAF request contains an Application ID known in the core network and the UE Application provides the Application ID configured in the UE Application. The AF binds the NWDAF request for an Application Id and the UE data collection for an Application Id configured in the UE.
Step 3b.
NWDAF subscribes to the AF in untrusted domain for UE data collection (i.e. input data from UE for analytics), by using step 2 and step 3 of the procedure that is described in Figure 6.2.2.3-1.
Step 4.
The AF collects the UE data using either direct or indirect data collection procedure in clause 6.2.8.2.1. The establishment of the connection can be performed at any time prior to this. The AF links the data collection request from step 3 to the user plane connection as described in clause 6.2.8.2.4.
Step 5a is used for the AF in trusted domain while step 5b is used for the AF in untrusted domain.
Step 5a.
The AF in trusted domain receives the input data from the UE, and processes the data (e.g. anonymizes, aggregates and normalizes) according to the SLA that is configured in the AF described in clause 6.2.8.1 and Event ID(s) and Event Filter(s) set during step 3a. The trusted AF then notifies the NWDAF on the processed data according to the NWDAF subscription in step 3a.
Step 5b.
The AF in untrusted domain receives the input data from the UE, and processes the data (e.g. anonymizes, aggregates and normalizes) according to the SLA that is configured in the AF described in clause 6.2.8.1 and Event ID(s) and Event Filter(s) set during step 3b. The untrusted AF notifies the NWDAF on the processed data by using step 5b (i.e. Step 4 and step 5 of the procedure that described in Figure 6.2.2.3-1).
Step 6.
The NWDAF produces analytics using the UE data received from the AF.
Step 7.
The NWDAF provides analytics to the consumer NF.
If the Target of Analytics Reporting that was received from the consumer in step 1 includes an Internal Group ID, NWDAF includes such Internal Group ID in step 3a or step 3b to AF. In the case of step 3b, NEF translates the Internal Group ID to an External Group ID.
If the Target of Analytics Reporting that was received from consumer in step 1 is "any UE", NWDAF may either set the target of event reporting to "any UE" in step 3a or 3b to AF, or may determine a list of SUPIs from AMF and/or SMF based on the Analytics Filter Information and sends the step 3a or 3b to AF for the determined list of UEs.
Up
6.2.8.2.4  Correlation between UE data collection and the NWDAF data requestp. 89
6.2.8.2.4.1  Generalp. 89
The UE IP address is used to identify the user plane connection established between the UE application and the AF for data collection, while the AF receives the Naf_EventExposure_Subscribe to request for the specific UE data collection by using SUPI (for AF in trusted domain) or external UE ID (i.e. GPSI) (for AF in untrusted domain). AF is required to correlate the UE IP address to the SUPI or to GPSI.
If the AF supports requests addressed to External Group ID (for AF in untrusted domain) or Internal Group ID (for AF in internal trust domain), the AF must correlate the list of external UE ID (i.e. GPSI) or SUPI, respectively, with the group(s) the UE belongs to, so that the AF can further correlate the UE ID (external or internal) to the UE IP address.
AF may indicate in NF profile and register to NRF in clause 6.2.8.2.2 if it supports to do the mapping itself or ask NWDAF to do it. If the AF is in a trusted domain, it may also indicate the supported list of S-NSSAI, DNN combinations to NRF in NF profile.
Accordingly, if AF supports the mapping, for AF in trusted domain, it is required to correlate the UE IP address and SUPI as described in clause 6.2.8.2.4.2 after receiving the data collection request from NWDAF and there is no mapping information storage in the AF. For AF in untrusted domain, the procedure to correlate the UE IP address and GPSI is described in clause 6.2.8.2.4.4.
NWDAF may collect the mapping information as described in clause 6.2.8.2.4.4 before sending request to AF in step 3a or step 3b in Figure 6.2.8.2.3-1.
If the user plane session between the UE and the AF is released, the AF / NWDAF shall remove the stored correlation information between UE IP address / prefix and UE SUPI / GPSI.
For all procedures defined in this clause 6.2.8.2.4.3, a specific combination of S-NSSAI/DNN shall be corresponding to a single PDU session for a UE to access the AF (either in trusted domain or untrusted domain).
Up
6.2.8.2.4.2  AF in trusted domain correlates UE data collection and NWDAF requestp. 89
If the AF receives the Naf_EventExposure_Subscribe/Request including Target for Event Reporting set to SUPI and not including the UE's IP address and the AF does not locally store the UE's IP address, the AF finds the PDU session(s) serving the SUPI, DNN, S-NSSAI from UDM and the allocated IPv4 address or IPv6 prefix or both from SMF as described in Figure 6.2.8.2.4.2-1.
Reproduction of 3GPP TS 23.288, Fig. 6.2.8.2.4.2-1: AF in trusted domain correlates UE data collection and NWDAF request
Up
Step 0.
At the establishment of the user plane connection between the UE Application and the AF, the AF stores the UE IP address (for both direct and indirect reporting) as described clause 6.2.8.2.1.
Step 1.
The AF receives a request to retrieve input data as described in clause 6.2.8.2.3 including a SUPI. The AF finds the SMF serving the PDU session(s) for this SUPI using Nudm_UECM_Get_Request including SUPI, type of requested information set to SMF Registration Info and the S-NSSAI and DNN, as defined in clause 5.3.2.5.7 in TS 29.503.
Step 2.
The UDM provides the SMF id and the corresponding PDU Session id, S-NSSAI, DNN using Nudm_UECM_Get_Response to the AF. Using the AF supported S-NSSAI, DNN and the received information from UDM, AF determines the PDU session used for the user plane connection between UE and AF.
Step 3.
The AF sends Nsmf_EventExposure_Subscribe to the SMF identified in step 2, including the Target for Event Reporting set to the PDU Session id(s) provided in step 2 and the Event ID set to IP address/prefix allocation/change.
Step 4.
The SMF provides the allocated IPv4 address or IPv6 prefix to the AF.
Step 5.
The AF correlates the UE data that includes the UE IP address and the NWDAF request for a SUPI using the retrieved IPv4 address or IP v6 prefix.
If the user plane session between the UE and the AF is released, the AF shall remove the stored correlation information between the UE IP address / prefix and SUPI.
Up
6.2.8.2.4.3  AF in untrusted domain correlates UE data collection and NWDAF requestp. 90
If the AF receives the Naf_EventExposure_Subscribe from NWDAF, via NEF, including Target for Event Reporting set to GPSI and not including the UE's IP address and the AF does not locally store the UE's IP address, the AF request the NEF to provide the allocated IPv4 address or IPv6 prefix or both as described in Figure 6.2.8.2.4.3-1.
Reproduction of 3GPP TS 23.288, Fig. 6.2.8.2.4.3-1: AF in untrusted domain correlates UE data collection and NWDAF request
Up
Step 0.
Same step as step 0 in Figure 6.2.8.2.4.3-1.
Step 1.
The AF receives a request to retrieve input data as described in clause 6.2.8.2.3 including a GPSI. The AF requests NEF to provide the IPv4address or IPv6 prefix or both serving the PDU session for this GPSI towards the AF using Nnef_UEid_Get_Request.
Step 2.
The NEF is configured with the DNN, S-NSSAI to access this AF. The NEF finds the SMF serving the PDU session(s) for this GPSI, DNN, S-NSSAI using Nudm_UECM_Get_Request including type of requested information set to SMF Registration Info and the S-NSSAI and DNN, as defined in clause 5.3.2.5.7 of TS 29.503.
Step 3.
The UDM provides the SMF id(s) and the tuple (PDU Session id (S-NSSAI, DNN) using Nudm_UECM_Get_Response to the NEF. Using the configuration in NEF, as described in step 2, the NEF determines the PDU session used for the user plane connection between UE and AF.
Step 4.
The NEF sends Nsmf_EventExposure_Subscribe to the SMF(s) identified in step 3, including the Target for Event Reporting set to the PDU Session id(s) provided in step 3 and the Event ID set to IP address/prefix allocation/change.
Step 5.
The SMF provides the allocated IPv4 address or IPv6 prefix or both to the NEF.
Step 6.
The NEF provides the allocated IPv4 address or IPv6 prefix or both provided by SMF in step 5 to the AF.
Step 7.
The AF correlates the UE data that includes the UE IP address and the NWDAF request for the GPSI using the retrieved IPv4 address or IP v6 prefix.
If the user plane session between the UE and the AF is released, the AF shall remove the stored correlation information between the UE IP address / prefix and GPSI.
Up
6.2.8.2.4.4  NWDAF correlates UE data collection and NWDAF request for trusted AF and untrusted AFp. 91
NWDAF receives the analytics subscription from consumer and discover an AF as described in clause 6.2.8.2.3. NWDAF finds the PDU session(s) serving the SUPI, DNN, S-NSSAI from UDM and the allocated IPv4 address or IPv6 prefix from SMF as described in Figure 6.2.8.2.4.4-1.
Reproduction of 3GPP TS 23.288, Fig. 6.2.8.2.4.4-1: NWDAF correlates UE data collection and NWDAF request
Up
Step 1.
The NWDAF finds the SMF(s) serving the PDU session(s) for this SUPI or GPSI using Nudm_UECM_Get_Request including SUPI or GPSI, type of requested information set to SMF Registration Info and the list of S-NSSAI and DNN combinations, as defined in clause 5.3.2.5.7 in TS 29.503. The NWDAF acquires the DNN, S-NSSAI used to access the AF using Nnrf_NFDiscovery_Request service operation or is configured with the DNN, S-NSSAI used to access the AF.
Step 2.
The UDM provides the SMF id(s) and the corresponding PDU Session id(s), per S-NSSAI, DNN combination using Nudm_UECM_Get_Response to the NWDAF. Based on the S-NSSAI, DNN used to access the AF in step 1, NWDAF determines the PDU session used for the user plane connection between UE and AF.
Step 3.
The NWDAF sends Nsmf_EventExposure_Subscribe to the SMF identified in step 2, including the Target for Event Reporting set to the PDU Session id(s) provided in step 2 and the Event ID set to IP address/prefix allocation/change.
Step 4.
The SMF provides the allocated IPv4 address or IPv6 prefix to the NWDAF.
Step 5.
Step 3a for AF in trusted domain or step 3b for AF in untrusted domain in Figure 6.2.8.2.3-1 is performed with the exception that NWDAF sets the allocated IPv4 address or IPv6 prefix that were received in step 4 as target of event reporting.
If NWDAF subscribed for the PDU session used for the user plane connection between the UE and the AF is released notification in step 3, the SMF informs the NWDAF that the UE IP address / prefix is released via Nsmf_EventExposure_Notify. Based on this information, the NWDAF shall remove the stored correlation information between the UE IP address / prefix and SUPI.
Up
6.2.8.2.4aVoid

6.2.9  User consent for analytics |R17|p. 92

Depending on local policy or regulations, to protect the privacy of user data, the data collection, ML model training and analytics generation for a SUPI or GPSI, Internal or External_Group_Id or "any UE" may be subject to user consent bound to a purpose, such as analytics or ML model training. The user consent is subscription information stored in the UDM, which includes:
  1. whether the user authorizes the collection and usage of its data for a particular purpose;
  2. the purpose for data collection, e.g., analytics or model training.
The NWDAF retrieves the user consent to data collection and usage from UDM for a user, i.e. SUPI prior to collecting user data from an NF as described in clause 6.2.2 and from a DCCF as described in clause 6.2.6.
If a request for analytics is for "any UE", meaning that the consumer requests analytics for all UEs registered in an area, such as a S-NSSAI or DNN or AoI, then the NWDAF resolves "any UE" into a list of SUPIs using the Namf_EventExposure service with EventId "Number of UEs served by the AMF and located in an area of interest" and retrieves user consent for each SUPI. If a request for analytics is for an Internal or External Group Id, NWDAF resolves it into a list of SUPIs and retrieves user consent for each SUPI.
If user consent for a user is granted, then the NWDAF subscribes to user consent updates in UDM using Nudm_SDM_Subscribe service operation. Otherwise, the NWDAF excludes the corresponding SUPI from the request to collect data and generate analytics or ML model on the other users for which user consent is granted if the request is for a group of UE or "any UE".
When data is collected from the UE Application, the ASP is responsible to obtain user consent to share data with the MNO.
If the UDM notifies that the user consent changed, then the NWDAF checks if the user consent is not granted for the purpose of analytics or model training. If user consent was revoked for a UE, the NWDAF stops data collection for that UE. For analytics subscriptions to UE related analytics with the Target of Analytics Reporting set to that UE, the NWDAF stops generation of new analytics and stops providing affected analytics to consumers. For ML model subscriptions with Target of ML Model Reporting set to that UE, the NWDAF containing MTLF stops (re-)training of ML model(s) using data from the UE and stops providing the ML model(s) to consumers (NWDAF containing AnLF) for analytics. If the Target of Analytics Reporting or Target of ML model Reporting is either an Internal or External Group Id or a list of SUPIs or "any UE", the NWDAF skips those SUPIs that do not grant user consent for the purpose of analytics or model training. The NWDAF may unsubscribe to be notified of user consent updates from UDM for users for which data consent has been revoked.
The Analytics ID that needs to check user consent before collecting input data are those that collect input data per user, i.e. per SUPI, GPSI, Internal or External Group Id, or those with the Target of Analytics Reporting or Target of ML model Reporting set to a SUPI, GPSI or External or Internal Group Id, and are described in clause 6.
Up

Up   Top   ToC