Question: When an Application Function (AF) requests traffic influence without identifying a UE by address, and the NEF determines the PDU session is not in HR-SBO mode, how does the NEF proceed for an individual UE identified by GPSI or one/more groups of UEs identified by External Group Identifier?
Option 1: The NEF directly updates the traffic influence parameters in the UDR without interacting with the UDM.
Option 2: The NEF interacts with the UDR to retrieve the SUPI or Internal Group Identifier before storing traffic influence parameters.
Option 3: The NEF shall interact with the UDM by invoking the Nudm_SubscriberDataManagement service to retrieve the SUPI or Internal Group Identifier.
Option 4: The NEF responds to the AF with an error status code indicating inability to process without UE address.
Explanation: When the NEF handles an AF request not identified by a UE address, targeting an individual UE (by GPSI) or groups of UEs (by External Group Identifier), it must first identify the UE(s) involved. To do this, the NEF interacts with the Unified Data Management (UDM) service to retrieve necessary identifiers (SUPI for individual UEs or Internal Group Identifier for groups). This step is crucial for mapping and managing traffic influence subscriptions accurately before engaging with the Unified Data Repository (UDR) for parameter storage.