Section: 4.15.6.9 Procedures for AF-triggered dynamically changing access and mobility management policies 4.15.6.9.1 General
Content: Access and mobility management policies may be modified due to several inputs including the AF as described in clause 4.16.2. Clause 4.15.6.9 describes the procedures for triggering such modifications in scenarios belonging to "case B" of clause 4.16.2.0 that are initiated by the AF. The following cases can be distinguished: - AF requests targeting an individual UE (identified by its SUPI or GPSI) without conditions related to the application traffic; these requests are routed (by the AF or by the NEF) to the PCF for the UE as described in clause 6.2.1.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ]  [20], This case is described in clause 4.15.6.9.2. - AF requests targeting an individual UE (identified by its GPSI), a group of UEs (identified by an Internal Group Identifier or an External Group Identifier), any UE accessing a combination of DNN and S-NSSAI, or any UE, or any inbound roaming UEs identified by their home PLMN ID(s) using an application identified by an External Application Identifier. For such requests the AF shall contact the NEF and the NEF stores the AF request information in the UDR. The PCF(s) receive a corresponding notification if they had subscribed to the creation / modification / deletion of the AF request information corresponding to UDR Data Keys / Data Sub-Keys. The AF is not aware if the target UEs are with or without an already established AM Policy Association and with or without ongoing PDU Sessions. This case is described in clause 4.15.6.9.3. NOTE: "any UE" refers to the UEs within the PLMN of the NEF.