T type, serving network, user location info, UE time zone, PEI, online/offline charging, charging characteristics, PDU session type, allocated UE IP address/prefix(es), and subsDefQos. Step 12: The PCF responds with 201 Created, PolicyCreation, SessRules, policyCtrlReq triggers, chargingInfo.pccRules, and revalidation time. Step 13: The SMF initiates a POST request/npcf - smpolicycontrol/vl / smpolicies/ ism. l. imsi - 1123123xxxxxx/update to PCFUpdate with access type, IPv6 address prefix, RAT type, reppolicyCtrire triggers, serving network, UE time zone, user location info. Step 14: The PCF responds with 200 OK for the successful transaction. Step 15a: The SMF sends an HTTP GET request /x.x.x.x: 8080/nnrf-di - Sc/V1/ nf-instances?preferred - locality= honoulu & requester-nf-type=SMF&target- - nf - type - CHF for CHF instances, and the NRF responds with 200 OK with service instance ID, API versions, NF service status, and IPv4 addresses. Step 15b: The SMF sends an HTTP POST request :/nchf-convergedcharging /V2/ chargingdata to CHF initial with 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. Next, we will present some snapshots from real traces. Figure 7.17 shows a packet capture between the PCF and SMF. This message contains the session and PCC rules sent by the PCF, along with a revalidation timer value, various triggers, and supporting features: IMS 5G PDU session establishment PCF->SMF [12]PCF Response - 201 Created HyperText Transfer Protocol 2 Stream: DATA, Stream ID: 3, Length 597 JavaScript Object Notation: application/json Object Member Key: sessRules Member Key: pccRules Member Key: revalidationTime > Member Key: policyCtrlReqTriggers Member Key: suppFeat Figure 7.17 - Packet capture PCF to SMF policy created response Figure 7.18 shows the packet capture depicting a discover message between the SMF and NRF. The NRF provides the details of a PCF tha