name: AF
full_form: Application Function
context: This clause describes the procedures that are generally applicable independently of the Member UE filtering criteria sent by the AF. Figure 4.15.13.1-1: 5GC assistance to Member UE selection and update 1. AF subscribes the Member UE selection assistance information by sending a first Nnef_MemberUESelectionAssistance_subscribe request including a list of target member UEs, one or more member UE filtering criteria as listed in Table 4.15.13.2-1 and optionally, time window(s). Subsequently, the AF may only update the Member UE filtering criteria of the subscription as described in clause 4.15.13.0 by invoking Nnef_MemberUESelectionAssistance_subscribe and providing a Subscription Correlation ID, i.e. the AF does not provide the list of target member UEs again. NOTE: The time window(s) for selecting the candidate UE(s) is used by the NEF when subscribing/requesting to NWDAF. The NEF maps the time window(s) for selecting the candidate UE(s) to the Analytics target period, which should be included in the Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operations. 2a. [CONDITIONAL] If the AF request does not contain a Subscription Correlation ID, the NEF verifies the authorization of the AF Request and identifies which information needs to be collected for each UE in the list of target member UEs and executes the corresponding service operations based on the Member UE filtering criteria provided by the AF, e.g. events, analytics ID(s), notifications, etc. 2b. [CONDITIONAL] If the AF request contains a Subscription Correlation ID, the NEF correlates the Nnef_MemberUESelectionAssistance_Subscribe request to an existing subscription according to the Subscription Correlation ID. The NEF uses the list of target member UE(s) received in step 1 for the Member UE update using the updated filtering criteria. 3. NEF interacts with different 5GC network functions to collect the required information for each UE in the list of target member UEs. The set of interactions between the NEF and the 5GC NFs depend on the Member UE filtering criteria provided by the AF. See Table 4.15.13.2-1 for details. 4. Based on the collected information from other 5GC NFs, the NEF consolidates all the information to derive the list(s) of candidate UEs which fulfil the Member UE filtering criteria in the AF request. The NEF may derive recommended time window(s), considering the validity period(s) of the analytics used for Member UE selection criteria. The recommended time window(s) may be a subset of the time window(s) received from the AF. In different recommended time windows, the list of candidate UE(s) which fulfil the Member UE filtering criteria may be different. 5. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UEs and possibly additional information. See clause 5.2.6.32.4 for details.
description: Application Function (AF) refers to a set of procedures that are generally applicable, independent of the Member UE filtering criteria sent by the AF.
explanation: This is classified under Telecommunications Network Functions  because it relates to the functionality and role of Application Functions in telecommunications networks.
section_title: 4.15.13 Assistance for Member UE selection 4.15.13.1 Member UE selection general information flow
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,B-Network,O,O,O,B-Device,O,O,O,O,B-Network Function,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,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,B-Device,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,O,O,O,B-Network Function,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,B-Device,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Device,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,B-Network Function,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,O,O,O,B-Device,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Network,B-Network,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Device,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,O,O,B-Device,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,B-Device,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O
biotag_Description: B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O