target-nf-type=PCF) = or PCF instances, and NRF responds with 200 OK with the service instance ID, API versions, NF service status, and IPv4 addresses. Step 10: The SMF initiates Npcf_SMPolicyControl_createE Request by including SmPolicyContextData, which contains supi, gpsi, pduSessionld, ratType : WLAN, servingNetwork, userLocationinfo, ueTimeZone, PEI, online/offline charging, charging characteristics, PDU session type, allocated UE IP address/prefix(es), subsDefQos, and other information. Wi-Fi attach Step 11: The PCF responds with 201 Created with policy creation with SessRules, policyCtriReqTriggers, chargingInfo, pccRules, and revalidation time. Step 12: The SMF initiates a POST request (/npcf-smpolicycontrol/vl/sm-policies/ ism. 1. imsi - 123 xxxxxxxxxx/update to PCF Update) with access type, ipv6addressPrefix, RAT type, reppolicyCtriretriggers, ServingNetwork, ueTimezone, and user location info. Step 13: PCF responds with 200 OK for the successful transaction. NRF Discovery for PCFs CHF charging Create Req 201 Created N4 sx Session Est Req SX_Session_Est_Response Create Session Response IKE SA AUTH Response Figure 7.31 - Wi-Fi attach - part 3 Step 14: The SMF sends an HTTP GET request (//10.19.19.19:8080/nnrf-disc/vl/ nf-instances?preferred-locality=Belll&requester-nf-type=SMF&target nf - type=CHF) for CHF instances and NRF responds with 200 OK with the service instance ID, API versions, NF service status, and IPv4 addresses. Packet Core Procedures Step 15: The SMF sends an HTTP POST request, / request/nchf-convergedcharging/ - v2/chargingdata, to CHF initial with the invocation sequence number, timestamp, PDU session charging information, subscriber identifier, and notify URI. Step 16: The CHF responds with 201 Created with triggers and PDU session charging information. Step 17: The SMF sends a PFCP session establishment/modification request to the UPF and provides packet detection, enforcement, and reporting rules to be installed on the UPF for this PDU session (PDR, QER, FAR, and URR). Step 18: The UP