Question: In a 5GS Background Data Transfer (BDT) scenario, when an Application Function (AF) sends a PUT request to the Network Exposure Function (NEF) to update BDT negotiation data (excluding transfer policy selection and/or BDT warning notifications), how does the NEF handle the existing resource at the Policy Control Function (PCF)?
Option 1: The NEF updates the existing resource using a PATCH request on Npcf_BDTPolicyControl service.
Option 2: The NEF deletes the existing resource and creates a new one with the required values at the PCF using the Npcf_BDTPolicyControl service.
Option 3: The NEF ignores the update and maintains the current settings for BDT negotiation data.
Option 4: The NEF responds with an error, indicating that updates are not supported for such requests.
Explanation: According to the procedures for resource management of Background Data Transfer in 5GS, when the AF sends a PUT request to update BDT negotiation data (excluding selecting a transfer policy and/or toggling BDT warning notifications), the NEF can handle this by deleting the existing resource and creating a new one with the required values at the PCF. This approach ensures that the PCF has the most current settings for managing background data transfers efficiently, reflecting the updated preferences or conditions communicated by the AF.