ation: application/json Object > Member Key: n1MessageContainer > Member Key: n1n2FailureTxfNotifURI > Member Key: n2InfoContainer > Member Key: pduSessionId Boundary: \\\\--boundary\r\n Encapsulated multipart part: (application/vnd.3gpp.5gnas) Content-Id: n1msg\r\n Content-Type: application/vnd.3gpp.5gnas\r\n\r\n Non-Access-Stratum 5GS (NAS)PDU Plain NAS 5GS Message Extended protocol discriminator: 5G session management messages (46) PDU session identity: PDU session identity value 1 (1) Procedure transaction identity: 0 Message type: PDU session modification command (0xcb) Always-on PDU session indication > QoS rules - Authorized QoS rules QoS flow descriptions - Authorized Boundary: \r\n--boundary\r\n Encapsulated multipart part: (application/vnd.3gpp.ngap) Content-Id: n2msg\r\n Content-Type: application/vnd.3gpp.ngap\r\n\r\n NG Application Protocol PDUSessionResourceModifyRequestTransfer protocolIEs: 2 items Item 0: id-UL-NGU-UP-TNLModifyList > ProtocolIE-Field Item 1: id-QosFlowToReleaseList ProtocolIE-Field id: id-QosFlowToReleaseList (137) criticality: reject (0) value QosFlowListWithCause: 1 item Last boundary: \r\n--boundary-- Figure 7.27 - Packet capture SMF to AMF N1N2 transfer message We will now continue to the next phase of the call flow and go over the remaining steps one by one: VoNR call flow gNB/RAN PCSCF Nsmf_PDUSession_UpdateSMContext Nsmf_PDUSession_UpdateSM Context Response An Specific resorce modification N2 NAS uplink transfer Nsmf_PDUSession_Update SMContext Nsmf_PDUSession_UpdateSM Context Response CHF _Charging Data Update Request 200OK N4SX_Session_ Modification_Req N4SX_Session_ Modification_Response Figure 7.28 - VoNR call flow - part 2 Step 10: The AMF forwards the N2 SM information and the user location information received from the (R) AN to the SMF, and if the (R) AN rejects QFIs, the SMF updates the QoS rules and QoS parameters if needed for the QoS flow(s). Step 11: The SMF acknowledges with 204 No Content. Step 12: The UE acknowledges the PDU session modification command by se