er, 5GC is able to trigger a specific application in the UE. The UE conveys the message to the application upon receiving the trigger message. Note that unlike LTE, 3GPP NR Rel-15 does not support dual-stack PDU session. The 5GC supports dual-stack UEs using separate PDU sessions for IPv4 and IPv6. In 3GPP NR, the QoS granularity is refined further to the flow level. In a typical case, mul- tiple applications will be running on a UE; however, in LTE eNB, each E-RAB does not have an associated QCI or an ARP, whereas in NR, the SDAP sublayer can be configured by RRC sublayer to map QoS flows to DRBs. One or more QoS flows may be mapped to one DRB. Thus, QFI is used to identify a QoS flow within the 5G system. User-plane traffic with the same QFI within a PDU session receives the same traffic forwarding treatment (e.g., scheduling, admission threshold, etc.). The QFI is carried in an encapsulation header on N3 and is unique within a PDU session. The 5GC is access-agnostic and allows running the N1 reference point on non-3GPP radio access schemes such as Wi-Fi. The UE can also send NAS messages for session and mobil- ity management to the 5GC via a non-3GPP access, which was not possible in the previous 3GPP radio access standards. Non-access stratum is the signaling protocol of the UE for mobility and session-related control messages, which requires a new security procedure in order to authenticate the UE over the non-3GPP access with the AMF in the 3GPP network. Non-3GPP access networks must be connected to the 5G core network via N3IWF entity. The N3IWF interfaces the 5G core network control-plane function and UPF via N2 and N3 interfaces, respectively. When a UE is connected via an NG-RAN and via a stand-alone non-3GPP access, multiple N1 instances, that is, one N1 instance over NG-RAN and one N1 instance over non-3GPP access, will be created. The UE is simultaneously connected to the same 5G core network of a PLMN over a 3GPP access and a non-3GPP access and is served by a single AMF provided that the selected N