 N2 PDU session request contains N2 SM information and a NAS message. The NAS message contains the PDU session ID and N1 SM container containing the PDU Session Establishment Accept message. Hence via this message, the AMF directs the NAS container to the UE and the SM message for the gNB. In Step 24, the RAN may send an RRC connection reconfiguration message, which will relay to the UE the QoS rules for the PDU session. The gNB also allocates the RAN tunnel information for the PDU session. Packet Core Procedures In Step 25, the PDU session response is sent from the RAN to the AMF; this contains the PDU session ID, the cause, N2 SM information comprising of the PDU session ID, AN tunnel information (which corresponds to the N3 tunnel information), list of accepted or rejected QFIs, and a user plane enforcement policy notification. With the availability of the N3 tunnel information, the first uplink user data can now be sent from the UE to the 5G core. In Step 26, the PDU Session Update SM Context Request message is sent from the AMF to the SMF. It is used to forward the N2 SM information received from the RAN to the SMF. The SMF is provided with the list of accepted QFIs, which it further enforces via the UPF. In Steps 27 and 28, the N4 session modification procedure with the UPF is carried out by the SMF. The SMF provides the AN tunnel info it has received from the gNB via the AMF, and the UPF receives the forwarding rules. The UPF responds with an N4 Session Modification Response to the SMF. After this step, the UPF is ready to deliver any data packet in the downlink direction to the UE. In Step 29, the PDUSession_UpdateSMContext response message is sent from the SMF to the AMF. The SMF can subscribe to any UE mobility event notification from the AMF, and with the help of this, the SMF is notified about relevant events to the SMF. In the case of PDU session types IPv6 or IPv4v6, the SMF generates an IPv6 router advertisement and sends it to the UE after this stage. For the Ethernet PDU session type, the SMF can