Section: 4.3.6.5 Processing AF requests to influence traffic routing for HR-SBO session
Content: Processing an AF requests to influence traffic routing for HR-SBO session are based on procedure described in clause 4.3.6.2 and clause 4.3.6.4 with the following differences: In step 0 of figure 4.3.6.2-1, V-SMF supporting HR-SBO subscribes to notification of AF request by invoking Nnef_TrafficInfluenceData_Subscribe service from V-NEF (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and UE IP address) and (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and Any UE) and (Data Set = Application Data; Data Subset = AF traffic influence request information; Data Key = S-NSSAI and/or DNN and SUPI). - For any UE, the V-SMF supporting HR-SBO performs the above subscription using S-NSSAI and/or DNN as Data Key. - For individual UE or group of UE(s), when a PDU Session is authorized for HR-SBO as described in clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ]  [74], the V-SMF serving the PDU Session performs the above subscription using S-NSSAI and/or DNN and/or Internal Group Identifier(s) or SUPI as Data Key. The V-NEF subscribes to notification of AF request from V-UDR. Steps 4 and 5 of figure 4.3.6.2-1 are replaced with the following steps: - Step 4: The V-UDR notifies the subscribed V-NEF of the AF traffic influence request information. - Step 5: The V-NEF notifies the subscribed V-SMF of the AF traffic influence request information.