Section: 4.16.15.2.1 Procedures for negotiation of planned data transfer with QoS requirements
Content: This clause describes the PDTQ procedures to negotiate viable time window for the planned application data transfer via the support of the NEF. Figure 4.16.15.2.1-1: Negotiation for planned data transfer with QoS requirements Prior to the transmission of the Application AI/ML data, the AF negotiates with the 5G Core for the PDTQ policies that provide assistance for the application data transfer. The AF discovers its serving NEF, if it has not done so before, by using the mechanism described in clause 6.3.14 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2]. 1a. The AF invokes the Nnef_PDTQPolicyNegotiation_Create Request (ASP Identifier, Number of UEs, list of Desired time windows, QoS Reference or individual QoS parameters, Alternative Service Requirements (optional), Network Area Information, Request for notification, Application Identifier). The Request for notification is an indication that PDTQ warning notification can be sent to the AF. NOTE 1: Based on AF's internal logic (policy), the AF may determine the minimum QoS requirements by considering the UEs expected to participate in the Desired time windows, the network input data and the trigger conditions for group application data transfer. 1b-1c. The NEF may authenticate the AF and authorize the PDTQ request from the AF. If the authentication/authorization of the AF's request has failed, the NEF will respond to the AF's request through the Nnef_PDTQPolicyNegotiation_Create Response with a failure result and the following steps are skipped. The NEF may map the ASP ID into DNN and S-NSSAI to be used in step 2. NOTE 2: The Application ID provided by the AF and the Application ID provided to NWDAF can be different, and in such a case, a mapping is performed by the PCF. 2. Based on an AF request, the NEF may translate the information provided by the AF (e.g. Network Area Information, etc.) based on the local policy and invokes the Npcf_PDTQPolicyControl_Create (ASP Identifier, Number of UEs, list of Desired time windows, QoS Reference or individual QoS parameters, Alternative Service Requirements (optional), Network Area Information, Request for notification, Application Identifier) with the H-PCF to authorize the creation of the policy regarding the PDTQ. If the PCF was provided with Request for notification, then PCF will send PDTQ warning notification to the AF as specified in clause 4.16.15.2.2 to notify the AF when the network performance or DN Performance in the area of interest reaches the Reporting Threshold set by the PCF based on operator configuration or the PCF determines to update the previously selected PDTQ policy based on the latest periodic reported network performance or DN Performance analytics as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]. The PCF may be configured to map the ASP identifier to a target DNN and S-NSSAI if the NEF did not provide the DNN, S-NSSAI to the PCF. 3. H-PCF queries the UDR to retrieve all existing PDTQ polices for all the ASPs using Nudr_DM_Query (Policy Data, Planned Data Transfer with QoS requirements) service operation. 4. The UDR provides all the stored PDTQ policies and corresponding related information (e.g. the Number of UEs, the list of Desired time windows) to the H-PCF. 5. Based on information provided by the AF and other available information, the H-PCF queries or/and subscribes to the NWDAF as defined in clause 6.6.4 or clause 6.14.4 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ]  [50] to request the Network Performance analytics or the DN Performance analytics. When requesting the Network Performance analytics or the DN performance analytics, if "any UE" is used, then the AoI information is used to identify the target gNB(s) for the prediction of the availability of the network resources. The DNN, S-NSSAI and Application ID may be provided by H-PCF as Analytics Filter Information when requesting or subscribing to the relevant Analytic ID. 6. By referring to the outcome of the analytics report as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20], H-PCF determines one or more PDTQ policies. Each PDTQ policy includes a recommended time window for the traffic transfer for each of the AF sessions for each of the UEs involved. 7. The PCF sends one or more PDTQ policies to NEF in Npcf_PDTQPolicyControl_Create Response including the PDTQ Reference ID. 8. The NEF sends a Nnef_PDTQPolicyNegotiation_Create response to the AF to provide one or more PDTQ policies together with the PDTQ Reference ID. If the NEF received only one PDTQ policy from the PCF, steps 9-12 are not executed and the flow proceeds to step 13. Otherwise, the flow proceeds to step 9. 9. If more than one PDTQ policies were provided to the AF, the AF selects one of the PDTQ policies and notifies NEF for the selected PDTQ policy via Nnef_PDTQPolicyNegotiation_Update request together with the PDTQ Reference ID. The AF stores the PDTQ Reference ID for the future interaction with the PCF. 10-12. The NEF notifies H-PCF about the selected PDTQ policy by the AF. The H-PCF acknowledges NEF. The NEF responds to the AF request with a Nnef_PDTQPolicyNegotiation_Update Response. 13-14. The H-PCF stores the PDTQ Reference ID together with the new PDTQ policy in the UDR by invoking Nudr_DM_Update (PDTQ Reference ID, Policy Data, Planned Data Transfer with QoS requirements). The UDR sends a response to the H-PCF as acknowledgement.