name: BDT
full_form: Background Data Transfer
context: Figure 4.16.7.3-1: The procedure for BDT warning notification 1. The negotiation for Background Data Transfer (BDT) described in clause 4.16.7.2 is completed. In addition, the PCF has subscribed to analytics on "Network Performance" from NWDAF for the area of interest and time window of a background data transfer policy following the procedure and services described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ]  [50], including a Reporting Threshold in the Analytics Reporting information. The value for Reporting Threshold is set by the PCF based on operator configuration. 2. The PCF is notified with the network performance analytics in the area of interest from the NWDAF when the NWDAF determines that the network performance goes below the threshold as described for the Network Performance analytics in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ]  [50]. 3. The H-PCF may request from the UDR the stored BDT policies using Nudr_DM_Query (Policy Data, Background Data Transfer) service operation. 4. The UDR provides all the Background Transfer Policies together with the relevant information received from the AF (as defined in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20]) to the H-PCF. 5. The H-PCF identifies the BDT policies affected by the notification received from NWDAF. For each of them, the H-PCF determines the ASP of which the background traffic will be influenced by the degradation of network performance and which requested the H-PCF to send the notification. The PCF then performs the following steps for each of the determined ASPs, i.e. Steps 6 - 16 can occur multiple times (i.e. once per ASP). 6. The PCF decides based on operator policies, whether a new list of candidate Background Data Transfer policies can be calculated for the ASP. If the PCF does not find any new candidate BDT policy, the previously negotiated BDT policy shall be kept, no interaction with that ASP shall occur and the procedure stops for that BDT policy. NOTE 1: The BDT policies of an ASP which did not request to be notified are kept and no interaction with this ASP occurs. 7. The PCF sets the no longer valid BDT policy in the UDR as invalidated by invoking Nudr_DM_Update (Background Data Transfer Reference ID, invalidation flag) service. NOTE 2: The BDT policies that are applicable for future sessions are checked by the PCF in step 6. 8. The UDR sends a response to the H-PCF as acknowledgement. 9. The PCF sends the notification to the NEF by invoking Npcf_PolicyControl_Notify (Background Data Transfer Reference ID, list of candidate Background Data Transfer policies) service operation. 10. The NEF sends the BDT warning notification to the AF by invoking Nnef_BDTPNegotiation_Notify (Background Data Transfer Reference ID, list of candidate Background Data Transfer policies) service operation. 11. The AF checks the new Background Data Transfer policies included in the candidate list in the BDT warning notification. 12. If the AF selects any of the new Background Data Transfer policies, the steps 8-13 from clause 4.16.7.2 are executed. 13. If the AF doesn't select any of the new Background Data Transfer policies, the steps 8-11 from clause 4.16.7.2 are executed, with the AF indicating that none of the candidate Background Data Transfer policies is acceptable. 14.-15. If the step 13 is executed, the PCF removes the no longer valid BDT policy from UDR for the corresponding Background Data Transfer Reference ID. NOTE 3: The PCF can also remove the no longer valid BDT policy after an operator configurable time for the case that the AF does not respond. 16. If there is a new Background Data Transfer policy stored in the UDR or a BDT policy removed from the UDR, the PCFs are notified by the UDR accordingly. The PCFs check if the corresponding URSP rules need to be updated or removed and if so, use the procedure defined in clause 4.16.12.2 to update URSP rules for the relevant UEs. The AF can send a Stop notification by invoking Nnef_BDTPNegotiation_Update service, when the AF requests not to receive the BDT warning notification anymore. Then, the NEF invokes Npcf_BDTPolicyControl_Update service in order to provide this information for the H-PCF.
description: Background Data Transfer (BDT) is a procedure outlined in the 3GPP specifications, specifically within the context of network data analytics services and policy control framework for the 5G System. It involves a series of steps initiated by the Policy Control Function (PCF) upon receiving notification from the Network Data Analytics Function (NWDAF) about degraded network performance below a certain threshold. The procedure aims to adapt background data transfer policies in response to changes in network conditions, ensuring efficient and adaptive management of data transfers based on real-time analytics.
explanation: BDT is classified as a procedure because it outlines a structured series of actions taken by various network functions (PCF, NWDAF, NEF, AF) in response to specific triggers (network performance degradation). These steps include policy evaluation, notification exchanges between different functional entities, and potential updates or removals of background data transfer policies based on the current network state. This process is integral to maintaining optimal network performance and user experience in dynamic conditions.
section_title: 4.16.7.3 Procedure for BDT warning notification
biotag_Context: O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Specification,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,B-Miscellaneous,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,B-Technology,I-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,B-Network Function,O,O,O,O,B-Network Function,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,B-Network Function,O,O,B-Procedure,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,B-Network Function,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,O,O,B-Miscellaneous,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Procedure,I-Procedure,I-Procedure,O,O,O,O,B-Miscellaneous,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Procedure,I-Procedure,I-Procedure,O,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,B-Network Function,I-Network Function,I-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O